dlevens Posted October 20, 2004 Share Posted October 20, 2004 Please note I am using sysprep.inf and not unattended. I cannot get my folders in $1 to copy to the C drive. I am using ghost to deploy my image and have the following structure on C drive before I run sysprep. This is my Windows 2000 image. I install a raw image then run sysprep. Here is my file structure.C:\Drivers\(all of my indivudual hardware folders with drivers are here)C:\Sysprep\sysprep.infC:\Sysprep\i386\$OEM$\cmdlines.txtC:\Sysprep\i386\$OEM$\$$\System32\(I have reg.exe, cmdow.exe, shutdown.exe)C:\Sysprep\i386\$OEM$\$1\Install\(I have RunOnceEx.cmd here)Here is a copy of my sysprep.inf;SetupMgrTag[Unattended] OemPreinstall = Yes ConfirmHardware = No OverwriteOemFilesOnupgrade = No OemSkipEula = Yes TargetPath = WINNT DriverSigningPolicy = Ignore OemPnPDriversPath = Drivers\000_intel_INF;Drivers\001_Network;Drivers\002_Sound;Drivers\003_Video;Drivers\004_Other InstallFilesPath = C:\Sysprep\i386 CrushDumpSetting = 1 KeepPageFile = 0 ExtendOemPartition = 1[GuiUnattended] EncryptedAdminPassword = NO AutoLogon = Yes AutoLogonCount = 3 OEMSkipRegional = 1 OEMSkipWelcome = 1 TimeZone = 4[UserData]; ProductID = FullName = "xx" OrgName = "xx"[Display] BitsPerPel = 24 Xresolution = 1024 YResolution = 768[TapiLocation] AreaCode = 909[SetupMgr] DistFolder = C:\sysprep\i386 DistShare = whistlerdist[Identification] JoinWorkgroup = WORKGROUP[Networking] InstallDefaultComponents = Yes[GuiRunOnce] Command1="%systemdrive%\Install\RunOnceEx.cmd"[Sysprep] BuildMassStorageSection=Yes[SysprepMassStorage]Why are the folders not copying to C? I have a feeling my folder structure is wrong. I already have my unattended working but the folder structure is different since it is coming from a CDROM and the $OEM$ is on the same level as i386. But for sysprep.inf I seem to recall that the structure is $OEM$ inside the i386 folder?Dennis Link to comment Share on other sites More sharing options...
ribond Posted October 20, 2004 Share Posted October 20, 2004 The $OEM$ structure is used by both Unattended setup and Sysprep, but the file copy part only happens during Unattended setup. I don't think this is going to work for you. Link to comment Share on other sites More sharing options...
dlevens Posted October 20, 2004 Author Share Posted October 20, 2004 Interesting info,So sysprep will run the commands in C:\Sysprep\i386\$OEM$\cmdlines.txt but will not copy anything in C:\Sysprep\i386\$OEM$\$1I guess there is really no point since I could just copy the files myself before I sysprep. I was hoping to make it work so I can use the same structure for both unattended and sysprep.I also find it odd that with unattended installs you are supposed to put the $OEM$ at the same level at i386 but for sysprep you are supposed to put the $OEM$ inside the i386. Also my C:\Sysprep\i386 folder is pretty much empty as it only contains the $OEM$. Does this seem right?Unattended is so much easier I wish this company would let ghost and sysprep die. hehe Dennis Link to comment Share on other sites More sharing options...
ribond Posted October 21, 2004 Share Posted October 21, 2004 I also find it odd that with unattended installs you are supposed to put the $OEM$ at the same level at i386 but for sysprep you are supposed to put the $OEM$ inside the i386.If my memory serves me correctly.... The default config for Unattended installations should be: <platform>\$oem$\stuffas in: \i386\$oem$\$1And Sysprep would be: %systemdrive%\sysprep\$oem$...Be that as it may, you can actually change this around to use a consistent structure. Take a look at the "OEMFILESPATH" setting in the unattend documentation. 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