kiwidj Posted June 24, 2009 Share Posted June 24, 2009 Hi I'm having issues with out unattended build process, basically this has been working fine for XP SP1 & SP2 but for some reason this has stopped working correctly for SP3.Basically the issue is the build will complete successfully but when you view the permissions set on C: there are corrupt permissions there, such as:C:Administrators (HOSTNAME\Administrators) : Full ControlS-1-5-21-918433936-2086638591-69549339-1108 : ModifyS-1-5-21-918433936-2086638591-69549339-1112 : Read & ExecuteIt's obviously not matching the SID with the group (SYSTEM & Users I think) but I'm not sure why.. the permission on the folders below are set correctly??Here's the build process we're using (this has been done in vbscript but I've listed it here in batch script for readability..):diskpartselect disk 0cleancreate partition primaryselect partition 1activeformat quick fs=ntfs label="SYSTEM"assign letter=cexitmd c:\Sourcemd c:\Source\Controlcopy M:\Deploy\Builds\OPTIMIZED\subbuild\unattend.txt c:\Source\Control\*.*md c:\Sysprepcopy M:\Deploy\Builds\OPTIMIZED\subbuild\sysprep.inf c:\Sysprep\*.*imagex /apply M:\Build\Source\WindowsXPSP3.wim 1 C:md c:\driverscopy "C:\Source\Control\Build.cmd" "X:\Build.cmd" : (See below for build.cmd details..)x:\Build.cmdpeshutdown /rebootBUILD.CMDcscript //nologo M:\Control\updatedrvpath.vbs C:\Source\Control\unattend.txt c:\driverscscript //nologo M:\Control\updatedrvpath.vbs C:\SysPrep\SysPrep.inf c:\driversC:\Source\OS\i386\winnt32.exe /unattend1:C:\Source\Control\unattend.txt /s:C:\Source\OS\i386 /s:C:\Source\OS\i386 /s:C:\Source\OS\i386 /s:C:\Source\OS\i386 /s:C:\Source\OS\i386 /s:C:\Source\OS\i386 /s:C:\Source\OS\i386 /s:C:\Source\OS\i386 /syspart:c: /tempdrive:c: /copysource:lang /debug4:C:\source\OSdebug.logI've tested the wim (I386) source is okay and not corrupt, have created a new version of the unattend.txt using MDT2008 Update 1 and this also gives me the same corrupt permissions.. so it must me an issue with my process and with SP3??This also does not seem to be hardware specific, virtual or physical I get the same results..Any ideas why this might be happening?? Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now