Sysprep appears to be changing SourcePath in the registry
Updated: 21 May 2010 | 5 comments
This issue has been solved. See solution.
Hello~
We just started using Sysprep to capture our images. We are using the default.inf in DS. What's happening is after we migrate a pc we get a Windows File Protection error. After some research I've found Sysprep may be the culprit as it has a tendency to change the SourcePath and ServicePackSourcePath in the registry back to the CD-ROM. I've checked the registries of pc's I've migrated and both the paths have been set back to D:\
How can I go about fixing this?
Thanks in advance,
Ann
discussion Filed Under:
Comments
It might be helpful to have
It might be helpful to have more information on the specific Windows File Protection error you receive after imaging, i.e. copied from the Event Log. What version of DS are you using?
Mike Clemson, Systems Engineer
Intuitive Technology Group -- Symantec Platinum Partner
I've had this issue in the
I've had this issue in the past, and I believe it's something to do with if you have slipstreamed any Service Pack or Hotfix to your I386 folder.
Do you use WinPE as your boot disk?
This might work:
After deploying the image, run the following:
Reg load HKLM\Offline c:\windows\system32\config\software
Reg add "HKLM\Offline\Microsoft\Windows\CurrentVersion\Setup" /v "ServicePackSourcePath" /t "REG_SZ" /d "C:\I386" /f
Reg add "HKLM\Offline\Microsoft\Windows NT\CurrentVersion" /v "SourcePath" /t "REG_SZ" /d "C:\I386" /f
Reg Unload HKLM\Offline
This is from memory, and theory based, so don't kill me if it's wrong :)
Cheers,
Gerard
We are using DS 6.9 SP3 Build
We are using DS 6.9 SP3 Build 375.
The exact error is "Windows File Protection: Files that are required for windows to run properly have been replaced by unknown versions" Then it instructs me to insert the WinXP SP3 disk.
Event Type: Information
Event Source: Windows File Protection
Event Category: None
Event ID: 64001
Date: 11/2/2009
Time: 9:32:27 AM
User: N/A
Computer: PC9425
Description:
File replacement was attempted on the protected system file c:\windows\apppatch\sysmain.sdb. This file was restored to the original version to maintain system stability. The file version of the bad file is 0.0.0.1, the version of the system file is 0.0.0.1.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Disable Sfcscan
Try disabling Sfcscan. It might be causing your issue if the error appears after sysprep.
http://support.microsoft.com/kb/222193
From the article:
"The second protection mechanism that is provided by the WFP feature is the System File Checker (Sfc.exe) tool. At the end of GUI-mode Setup, the System File Checker tool scans all the protected files to make sure that they are not modified by programs that were installed by using an unattended installation."
"The SfcScan value in the following registry key has three possible settings:
The settings for the SfcScan value are:
Does this help?
Mike Clemson, Systems Engineer
Intuitive Technology Group -- Symantec Platinum Partner
Yes it does help. Thank you
Yes it does help. Thank you very much.
Would you like to reply?
Login or Register to post your comment.