Systems Deployment

Yes, I syspreped it before capture. WIth just the "use minisetup" box ticked and hit Reseal as I've always done on ghost or acronis. I 've also tried with the newer SP3 version of sysprep and I created a brand new sysprep answers .inf file. still no luck.

I don't use sysprep from comand line, I've always assumed it generalized by default when used from the gui.

I've just removed all the drivers from the postinstall directory, I'm going to run driver feed builder again to see if that makes any difference. - babaton 10 years ago

Remember the K2000 is not Acronis. A lot of acronis users are still in the mindset if it worked on Acronis or Altiris it should work on the k2000.

This article might help.

http://www.kace.com/support/resources/kb/article/K2000-Sysprep-Creator-Wizard - c_brock 10 years ago

This article looks helpful too. http://www.kace.com/support/resources/kb/article/Adding-Drivers-in-Windows-XP-Sysprep-Server-Configuration - c_brock 10 years ago

thanks brock, heading home now but will give them a read in the morning. It's really frustrating because it was all going nicely,. My image was deploying ok, I was building up drivers libraries using driver feed builder when suddenly my image started to fail. I'll have a read and go back to the beginning. - babaton 10 years ago

Ah. Ok. It sounds like a failure in the process used to add the drivers to the driver library. I hope the second article helps. :) - c_brock 10 years ago

ok, I'm still having issues with this.......having read the 2nd article I'm a bit confused. I thought the purpose of the driver feed builder was to extract the driver files and upload the to the correct directory on the k2000.

The directory structure created by the driver feed builder is totally different to that suggested in the article. Do I really need to manually create an i386 folder with every driver for every machine on my network? This article indicates that the structure created by driver feed builder will work with deployed and scripted images - http://www.kace.com/support/resources/kb/article/K2000%20-Setting-up-Driver-Feed-with-non-Dell-Systems-in-3-4?action=artikel&cat=54&id=1128&artlang=en

Also, when I first capture an image if I deploy it straight away from the kbe without rebooting it deploys ok. However If I reboot the PC and then try to deploy I get the following error in the log file.....

can't get short name '{02D4B~1' for 'C:\WINDOWS\Registration\{02D4B3F1-FD88-11D1-960D-00805DC79235}'{95FCF471-893D-4070-AB5A-F615A280B349}'crmlog' because it is in use by 'C:\WINDOWS\Registration\{02D4B3F1-FD88-11D1-960D-00805FC79235}'{5F4F5510-886C-4876-9DB3-9B27B0FD48D9}'crmlog' - babaton 10 years ago

I worked it out, adding a preinstallation task to format the c drive as ntfs seems to have sorted it. I didn't have it configured this way initially though, I think my problems started when I updated to 3.4.

Anyway all working now..... - babaton 10 years ago