I am hoping to find an answer to my issue with pushing out an XP
Pro image to a machine. First a little info: I am using Management Suite 8.7
with SP5 and new agents on the machines in question. I am using a PXE rep and
PXE booting the machine being imaged. The machine I am trying to image has been
wiped completely.The image I am trying to push out was taken from a machine
with SP3 installed and it has been sysprepped. I am also using the latest
version of sysprep. I have had no problems capturing the image, which I used
imagex.exe to do.
So here is what I did: I created a provisioning template that
follows these steps: In the "OS Installation" section of the
template, 1. Maps a drive to a UNC share that the image is stored; 2. Deploys
the image using imagex.exe; In the "Post OS Installation" section of
the template, 3. Injects my sysprep file; 4. Adds a temporary agent to the
template (with the "Unique ID" checkbox checked); 5. Reboots; In the
"System Configuration" section of the template, 6. Installs the
standard LANDesk agent.
I am pretty sure that it has something to do with the sysprep
file I am injecting into the provisioning template. The point at which the
template fails is Step 4, when it tries to add the temporary agent. The log
file on the machine being imaged says this:
ldProvision.exe:Relpacing variable ldDeviceID = COA-359-35
*ConfigTargetOSHandler.exe:validate GUID string=COA-359-35 fail will not be
ConfigTargetOSHandler.exe:Found dir c:\Program Files\LANDesk\Shared Files
*ConfigTargetOSHandler.exe:Could not write INI file c:\Program
Files\LANDesk\Shared Files\cbaroot\actions.ini : 3*
ConfigTargetOSHandler.exe:Could not enable cba8 startup!!!
It looks like the "ConfigTargetOSHandler.exe" file is
failing for some reason. I am not sure where it is trying to start the cba8
service but I checked on the core and it looks like it is running OK. I even
rebooted the core just to make sure. And I checked the permissions on the
"actions.ini" file on my PXE rep and they look OK also. I even opened
up the Shared folder on the PXE rep to everyone (and turned off the firewall)
but it still can't be written to. I don't even know what that file does.
You will notice that the second line of the log file says that
it cannot validate the string. To remedy this, I tried to use a Public variable
called "ldHostName" and put "%ldHostname%" in the
"computer name" section of my sysprep file. When I did that, I did
not get the validate GUID error but it still failed right after that. I have
attached my sysprep file so please let me know if there may be something else
in that file that is screwing me up.
I am also attaching the serviceHost and residentAgent logs from the machine I was trying to image.
I hope I didn't forget anything. Sorry for being so long winded
but I wanted to give as much info as possible. This has been very frustrating
because I have tried so many different things and I still can't completely push
out an image...and the thought of manually renaming 70 machines and adding them
to our domain makes me somewhat perturbed. Please help. Thanks.