SOLVED: K2000 Sysprepped Image Deployment Post Installation Task Problems
I am trying to use the K2000 to deploy Windows XP with all the updates included. I am able to deploy the images just fine by themselves, but when I start to add Postinstallation Tasks I start to get strange behavior. I have searched through the posts and made sure that I don't have any guirunonce entries as well as not having a Windows\Setup\Scripts directory. No matter which apps I include post-installation tasks I seem to choose, it only gets to the first 2 or 3. It appears to do any combination of 2 or 3 so it doesn't seem as if one package is killing the tasks, and I'm calling for no reboots.
Relevant (maybe?) info:
I am using sysprep -reseal -quiet -activate -mini -shutdown when I prepare the image for uploading to the K2000.
My sysprep.inf file with my personal info removed:
AdminPassword=" (removed) "
FullName=" (removed) "
OrgName=" (removed) "
JoinWorkgroup = WORKGROUP
;JoinDomain = Domain
;DomainAdmin = Domain\administrator
;DomainAdminPassword = password
accessopt = "off"
chat = "off"
deskpaper = "off"
freecell = "off"
hearts = "off"
media_clips = "off"
media_utopia = "off"
minesweeper = "off"
msmsgs = "off"
msnexplr = "off"
OEaccess = "Off"
pinball = "off"
solitaire = "off"
spider = "off"
templates = "off"
zonegames = "off"
Profiles = "WindowsFirewall.TurnOffFirewall"
Mode = "0"
And again, no C:\Windows\Setup\Scripts or whatever that directory might be (exact path eludes me at the moment) and no guirunonce in the .inf..
It appears that my first 2-3 apps are installing no matter what apps those might be, but I get no progress indicator like on the scripted installs.
Thank you for your time,
My custom .bat scripts were not being executed using the call command, so they were breaking the installcmds.bat script that is ran after the image is applied. Much thanks to dugullett. via dugullett: Take out all of your .bat files out of your post installs and see how far it gets. I'm not sure if you are creating them using "Add New BAT Script...", or if you are importing them. I seem to remember having trouble with them running if I imported them as an app. You could try calling them? This should work if you add the "call" command for your .bat files.
I've had this be a problem before and it turned out I had a typo in one of my post installs. I would login to the machine after the failure and navigate to C:\kace\installcmds.bat (sorry I don't have a machine in front of me, this should be close to the path). See if you can run this manually. If not remove the line after your last working app. See if this will continue.
The image will not give you a progress indicator.
You should be able to log in while your post install tasks are running. This may help you to see whether something is rebooting the machine. If you have been rotating your scripts and it is always only completing two or three, you may find that something else has the machine rebooting after a certain amount of time, and what completes is just based on how much finishes in that time frame.