I have tried following the steps you kindly shared in http://community.landesk.com/support/docs/DOC-7444, but the image once downlaoded boots back into Audit Mode and does not look like LANDesk sysprep 'unattend.xml' worked as it did not join to the domain etc.
We are using Ghost 11.5.1 to capture and deploy the image. I have done all the required changes e.g. appplicaiton installs etc. After that I sysprepped it with the option "Enter System Audit Mode" and "Shutdown". Then I uploaded the image. After downloading the image back using LANDesk OSD it boots straight into Audit Mode and doesn't look like LANDesk copied the unattend.xml to the c: drive. Any help on this would be much appreciated.
Our Core Server is: LDMS 9.0 SP2
1. We have our own sysprep.xml file with various components. Not sure how LANDesk sysprep would merge the 2, as your post mentions not use a sysprep template in OSD
2. We are using PXE boot from LANDesk
3. The image has a hidden 100MB partition and the rest of the drive is one whole partition where the OS is installed. Is there a way to check if the OS volume is labelled C: in WinPE? This could be the place where things may be going wrong since nothing from the LANDesk unattend seem to have run.
4. Non of the LANDesk Unattand.xml seem to have run and the machine boots right into Audit Mode
To eliminate LD and PE and drive setup as the problem, I copied the LANDesk generated xml to the root of C: on my reference machine and then run sysprep manually without capturing as below:
sysprep /audit /reboot /unattend:c:\unattend.xml
It seemed to have gone through the motions of \sysprep\sysprep.exe /oobe /generalize /reboot after a reboot as I could see it on the screen. The machine then rebooted again and now I get an error as below:
Windows could not parse or process the unattend answer file for pass [specialize].
The settings specified in the answer file cannot be applied.
The error was detected while processing settings for component [Microsoft-Windows-Shell-Setup].
To me this looks like the %computername% in the specialize pass, but may be wrong. Any ideas?
Attached is my LANDesk generated unattend.xml from the \\corename\ldmain\landesk\files
Let me know if you would like to also see our own Sysprep xml that we run manually once the image is finalised for capture and deploying. We were hoping LANDesk could merge the 2 in one just like how it was in Windows XP when using it as a template, but doesn't seem to be the case
Laptop_ALPHA_V2.txt.zip 1.3 K