This is a strange one.  I've been creating, collecting and deploying images via our K2000 for a couple of years now.  Recently I collected an updated image.  I tested it several times on many different hardware platforms successfully.  Now I have deployed to three different computers, two different hardware platforms (in the process of testing more) that have failed coming out of sysprep at the [Specialize] pass [Microsoft-Windows-Shell-Setup] component.  I was able to drop to command line with Shift-F10 and trace the error to CopyProfile of Administrator profile.  If I did not change the image or any tasks related to it, how all of a sudden does it do this now?  Here's what I know:
  • Using WIM, not K-Image
  • Imaging directly from the main K2000 appliance, not an RSA (though we have close to 50 in the environment)
  • K2000 is v3.7.120251 - we cannot update it at this point in time.
  • Old image still works.
  • Updated image was updated from image I save prior to original sysprep - I do this so I'm starting back before sysprep modifies anything.
  • Updates included Windows/Office updates, updated Citrix Receiver client, updated Adobe Reader and Flash player.
  • I encountered no issues or errors in sysprepping the image prior to collecting with K2000
  • Image was built in VMWare so no drivers are installed prior to sysprep or image collection.
  • Updated image worked on several computers and several hardware platforms with no issue.
  • Unattend file has not changed
  • When sysprep fails, I can Shift-F10 into command prompt and copy the entire contents of c:\users\administrator to c:\users\default without any errors (xcopy /S /E /H /R /Y).  I verified by fooling Windows into thinking sysprep exited normally (HKLM\system\setup\status\childcompletion\setup.exe = 3) to see the profile had actually copied without issue.
  • Image was collected 6 days ago and worked 3 days ago.
  • K2000 tasks are identical to the old image - no change to imaging process has been made anywhere
  • All drivers get pushed successfully - verified in device manager of failed image deployment.
  • One of the computers that failed was one that worked before (again, testing with more now)
Any ideas are welcome.  It's just baffling that usually the CopyProfile fails due to file permissions, either write or read.  These files would not have changed between when the image worked and now.  I tried to include everything I could think of but if you have any questions, I'll be happy to include what I can.  Of course I'm now working on building a new one from scratch

Update:  Pushed image to two more different hardware platforms, both worked last week.  Both now fail as well in the same way.
0 Comments   [ - ] Hide Comments


Please log in to comment

Answer this question or Comment on this question for clarity


Run a chkdsk /f prior to sysprep

Also look the the registry to make sure a temp or ghost profile did not get created and leave the keys in the registry.  I have seen that cause this problem

check keys for extra entries beside the system defaults and admins
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileGuid
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList
Answered 12/20/2016 by: SMal.tmcc
Red Belt

  • Good point and I had already checked that early on. I failed to mention that in my bullet points. I also verified in the failed image attempt there are no other user entries in the registry.
Please log in to comment