Jump to content


  • Posts

  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by randalldale

  1. Not sure if you got an answer but according to Microsoft something is written wrong in your mass storage listings or one of the drivers listed is spelled wrong. You might try removing just one line at a time to find the error. Randy
  2. Hi guys, Real quick is there anyway to add an MSI application to WinPE 2.0 or install during boot? I need to run a data migration utility that has to be installed as it can not run through command line. After some checking it appears that MsiExec.exe is not installed in WinPE 2.0 is there a way to integrate it so that I can run msi installs from WinPE? UPDATE: Ok, I was thinking of doing an install on a Vista based machine and then matching the registry on the WinPE 2.0 system by mountrw the edit the registry hive. At the moment I'm having an issue getting Vista to mount the winpe boot.wim file. Any thoughts anyone? Thanks, Randy
  3. This is probably a dumb question but did you sysprep with the -factory switch?
  4. Does anyone know how to turn on Windows Update in Vista through the BDD 2007 solution? I need to deploy Vista with Update enabled, turned on and accepting weekly updates. Anyone have any ideas? Again thanks for your help, Randy
  5. Well I will try using just the registry setting becasue nothing in sysprep seems to work. Here is what I tried: [unattended] OemSkipEula=Yes InstallFilesPath=C:\sysprep\i386 [GuiUnattended] AdminPassword="" EncryptedAdminPassword=NO AutoLogon=Yes AutoLogonCount=2 OEMSkipRegional=1 OemSkipWelcome=1 [unattend] UnattendMode=DefaultHide OemSkipEula=Yes OemPreinstall=Yes UnattendSwitch=Yes TargetPath=\WINDOWS OemPNPDriversPath="c:\sysprep\i386\$oem$\inf\;c:\sysprep\i386\$oem$\inf1\;c:\sysprep\i386\$oem$\inf2\;c:\sysprep\i386\$oem$\inf3\;c:\sysprep\i386\$oem$\inf4\;c:\sysprep\i386\$oem$\inf5\;c:\sysprep\i386\$oem$\inf6\;c:\sysprep\i386\$oem$\inf7\;c:\sysprep\i386\$oem$\inf8\;c:\sysprep\i386\$oem$\inf8\APPS\PROSETDX\Win32\DRIVERS\;c:\sysprep\i386\$oem$\inf8\PRO100\Win32\;c:\sysprep\i386\$oem$\inf8\PRO1000\Win32\;c:\sysprep\i386\$oem$\inf9\;c:\sysprep\i386\$oem$\inf\10\;c:\sysprep\i386\$oem$\inf\11\;c:\sysprep\i386\$oem$\inf\12\;c:\sysprep\i386\$oem$\inf\13\;c:\sysprep\i386\$oem$\inf\14;c:\sysprep\i386\$oem$\inf\15\;" WaitForReboot=No [userData] Also tried: InstallFilesPath=C:\sysprep\i386 OemPNPDriversPath="\$oem$\inf\;\$oem$\inf1\;\$oem$\inf2\;\$oem$\inf3\;\$oem$\inf4\;\$oem$\inf5\;\$oem$\inf6\;\$oem$\inf7\;\$oem$\inf8\;\$oem$\inf8\APPS\PROSETDX\Win32\DRIVERS\;\$oem$\inf8\PRO100\Win32\;\$oem$\inf8\PRO1000\Win32\;\$oem$\inf9\;\$oem$\inf\10\;\$oem$\inf\11\;\$oem$\inf\12\;\$oem$\inf\13\;\$oem$\inf\14;\$oem$\inf\15\;" InstallFilesPath=C:\sysprep\ OemPNPDriversPath="\i386\$oem$\inf\;\i386\$oem$\inf1\;\i386\$oem$\inf2\;\i386\$oem$\inf3\;\i386\$oem$\inf4\;\i386\$oem$\inf5\;\i386\$oem$\inf6\;\i386\$oem$\inf7\;\i386\$oem$\inf8\;\i386\$oem$\inf8\APPS\PROSETDX\Win32\DRIVERS\;\i386\$oem$\inf8\PRO100\Win32\;\i386\$oem$\inf8\PRO1000\Win32\;\i386\$oem$\inf9\;\i386\$oem$\inf\10\;\i386\$oem$\inf\11\;\i386\$oem$\inf\12\;\i386\$oem$\inf\13\;\i386\$oem$\inf\14;\i386\$oem$\inf\15\;" InstallFilesPath=C:\ OemPNPDriversPath="c:\sysprep\i386\$oem$\inf\;c:\sysprep\i386\$oem$\inf1\;c:\sysprep\i386\$oem$\inf2\;c:\sysprep\i386\$oem$\inf3\;c:\sysprep\i386\$oem$\inf4\;c:\sysprep\i386\$oem$\inf5\;c:\sysprep\i386\$oem$\inf6\;c:\sysprep\i386\$oem$\inf7\;c:\sysprep\i386\$oem$\inf8\;c:\sysprep\i386\$oem$\inf8\APPS\PROSETDX\Win32\DRIVERS\;c:\sysprep\i386\$oem$\inf8\PRO100\Win32\;c:\sysprep\i386\$oem$\inf8\PRO1000\Win32\;c:\sysprep\i386\$oem$\inf9\;c:\sysprep\i386\$oem$\inf\10\;c:\sysprep\i386\$oem$\inf\11\;c:\sysprep\i386\$oem$\inf\12\;c:\sysprep\i386\$oem$\inf\13\;c:\sysprep\i386\$oem$\inf\14;c:\sysprep\i386\$oem$\inf\15\;" None worked any ideas?
  6. After a couple of days I'm still not having a lot of success. Still working on it though... just seems to only work with complete statements in both the sysprep.inf and Registry. I had thought that it would have been a little more intuative. I mean all my unattends only need to know where to look (InstallFilesPath) and not have to have a registry entry too! Plodding onward I guess...
  7. Can you have multiple entires like... c:\windows\inf;c:\sysprep;c:\$oem$... ?
  8. Hmmm... good point. I had thought that the install files path listed where the system looked for the drivers i.e. 'c:\sysprep\i386' when installing windows. Basically you are saying that my OEMPnPpath statement should have been 'sysprep\i386\inf;sysprep\i386\inf1;...' I tried changing the naming structure as suggested, 'sysprep\i386\inf\;sysprep\i386\inf1\;...' and it made no difference. I also switched the location of the INF folders to the root of c: and it made no difference, any ideas?
  9. Hey guys, I have been here a while and do a lot of unattends but this is my first sysprep image and danged if I can figure out why my driver infs are not being recognized! I have located my drivers inside the sysprep folder as such: c:\sysprep\i386\inf or c:\sysprep\i386\$oem$\inf and neither one finds a single driver??? Here is the needed section of my sysprep.inf [unattended] OemSkipEula=Yes InstallFilesPath=C:\sysprep\i386 [GuiUnattended] AdminPassword="xxxxxxxx" EncryptedAdminPassword=NO AutoLogon=Yes AutoLogonCount=2 OEMSkipRegional=1 TimeZone=85 OemSkipWelcome=1 [unattend] UnattendMode=DefaultHide OemSkipEula=Yes OemPreinstall=Yes UnattendSwitch=Yes TargetPath=\WINDOWS OemPNPDriversPath="inf\;inf1\;inf2\;inf3\;inf4\;inf5\;inf6\;inf7\;inf8\;inf8\APPS\PROSETDX\Win32\DRIVERS\;inf8\PRO100\Win32\;inf8\PRO1000\Win32\;inf9\;inf\10\;inf\11\;inf\12\;inf\13\;inf\15\;" WaitForReboot=No [setupMgr] DistFolder=C:\sysprep\i386 DistShare=windist I hate acting like a NOOBE here but I'm at a loss as to why the image is not picking up the drivers? I should note that I have tried adding a slash to the path statement ("\inf\;\inf1;...) and it still doesn't work. I do a sysprep.exe -mini -reseal Anyone have any ideas, I'm stumped...
  10. My problem is simple I get an error that the screen resolution needs to be 800 x 600. This happens during the runonce.cmd and my system has not rebooted to know that the video drivers are installed. Is there any way to fake out Cisco to think that the screen is 800 x 600?
  11. Problem solved guys, I reinstalled Ghost Suite 2.0 and grabbed the file again to test it in a USB thumbdrive. When it worked I moved the original ghost32.exe to the root of the CD thinking it couldn't be embedded and got the same error? Luckly I tried the new file and it worked fine. So I deleted the old file added the new file to the BOOT.WIM and things are working fine. So the usual that typically happens did the first file was bad, getting another copy fixed things. But the really weird part was that it worked under WinPE 2005 Server 2003 based. Thanks for your thoughts and help on this. Randy
  12. WinPE 2.0 does not support .NET. But .NET is not required for Ghost v11 either. I did setup the BOOT.WIM file with all options as space is not an issue on my installs becasue I use DVDs. As far as seeing all my drives, that is not an issue as I even run a .cmd to map a network drive and that completes just fine. I'm able to create .WIM files to the network drive so seeing drives are not an issue. The one thing I do have is the ghost32.exe embeded into the BOOT.WIM file under system32. I will try it from a USB thunb drive to see if it makes a difference.
  13. Anyone have any idea why ghost32.exe v11 has the disk cloning either to an image or disk grayed out when booting in WinPE 2.0? I was told it works in WinPE 2.0 but so far after integrating into the boot.wim file options to clone are grayed out??? Thanks for your insight as usual.
  14. Thanks, I will hit the site read and pull the data and let everyone know the update. Randy
  15. I was wondering has anyone attempted to run a virtual floppy from within WinPE 2.0 to do udpates? I need to be able to boot winpe 2.0 and run a virtual floppy to make some changes to the BIOS, as the tool I have only works in DOS, before installing the OS. Anyone have any ideas. Thanks for your help, Randy
  16. I work with the HP notobooks regularly and to add to the comments you will need the sata drivers from HP.com for the error to disappear. Although resetting the bios will work until you change the bios back you do loose some functionality inside the OS. Randy
  17. Thanks I will add that to my information DB as you can never have to much information in the WinPE world. Randy
  18. Thanks although I got my WinPE 2.0 version working so ended up not having to rebuild using WinPE 2005.
  19. Hello, First thanks for all the insightful information. Now on to the fun. I install XP SP2 through an unattend.txt and I'm using HTA files to get user information so that I can dynamically build the unattend.txt and runonce.cmd files. Once my HTA file finishes copying I can't seem to figure out the scritping to tell WinPE to reboot. I know that on WinPE 2.0 you just script 'wpeutil reboot' to restart the PC and begin the setup. But nothing I've tried seems to work on WinPE 2005. Is there anything that will work from a .BAT, HTA or VBS file that I can use to tell the system to restart once I finsh copying and execute the winnt32.exe? I know it is probably something simple I'm missing. Things I've tried: objWShell.Run ("cmd.exe shutdown -r") objWShell.Run ("exit") objWShell.SendKeys "exit" Thanks for the help, Randy
  20. Well I'm still gettting the error even with the fix to the diskpart.txt file. Oh and I have Intel based boards that are on the most current BIOS.
  21. Nigel, If you look in the Sata driver readme from HP there are instructions on how to make the Mass Storage work for the ICH7 family in unattends or sysprep systems. I actually do multisystem unattends on DVDs for HP under different contracts and have been scripting the SATA drivers for quite some time. Randy
  22. Does anyone know if the current USMT tool 3.0 copies the digital certificates for say web certificates and if so do you know where to find them in the moved data? Thanks, Randy
  23. Thanks guys it was a sequence thing as suggested. Once I created the Lab Deployment things went smoothly. Thanks again, Randall
  24. Does anyone know how to get an OEMDuplicatorString into the registry for image version using the 'Deployment Workbench' from BDD 2007, Business Desktop Deployment system? I tired a typical registry entery but that failed as I'm sure some sort of permission stucture is involved. Thanks, Randy
  25. Ok guys little help please, I'm getting an error during the 'Update' function of a 'Deployment Point' that states "distribution share does not contain the required "Boot" directory. Please ensure that you have created and updated the lab deployment point..." I have no idea how to update lab deployment point nor where to put it and can't seem to find it in any of the help files or instructions. Any one have any ideas? Thanks...

  • Create New...