1 Reply by StylusPilot

(41 replies, posted in Universal Imaging)

OfflineSysprep Issue

"An Error Occurred while trying to update the registry"

I have read this issue is either caused by having a read only sysprep.inf, or having the build mass storage in sysprep.inf

neither of which I have.

what else causes this? how can I diagnose?

I am so close to a universal image lol

Go to forum: Universal Imaging

2 Reply by StylusPilot

(204 replies, posted in Universal Imaging)

lol,

thanks for that. makes complete sense. I will adjust accordingly and try and use KTD to move them.

for KTD can I use the Path of just C:\D\

or do I have to specify each folder to keep it=e C:\D\M,C:D\whatever

Go to forum: Universal Imaging

3 Reply by StylusPilot

(204 replies, posted in Universal Imaging)

I use offlinesysprep to change the hal. the latest version works great. I haven't had any yet that it wouldn't work on.

Thanks for the info, how can I use offline sysprep with my setup, ie do I boot the VM of say BartPE then run offlinesysprep then create an image of the disk?

as for your process, I have a couple of questions.

step 5: why do you copy the xp cd to sysprep/i386?

I previously was having font issues not sure why however having the CD there stops that from happening, and it gets deleted anyways

you sysprep.bat:
devpath is for adding drivers to the registry. You should be executing devpath on the drivepacks folder not on c:

Yep screwed up there I corrected devpath to be C:\SOFTWARE\DRIVERPACKS\D

you don't need the enabling image for amd/intel. you are building in vmware which doesn't even have intelppm.

Gotten rid of that now as well.

for -bmsd
The drivers for bmsd never change so you only need to run it once. As for scanning the drivepacks for mass storage, are you only choosing certain ones? like ide only. If you try to add them all you will definitely run in to memory issues.

I run the -bmsd only once before I run the sysprep.bat

I only get the intel drivers from driverpacks mass storage else I would get the memory problem

Go to forum: Universal Imaging

4 Reply by StylusPilot

(204 replies, posted in Universal Imaging)

Ok I changed a few things and it's working better

I am now using mysysprep with the CPU option for UP Hal or MP Hal and seems to work on a few more machines.

does anyone have a success rate of 90% and above? in a single universal image?

what do you guys do for the ones which don't work - make a complete seperate image?

Go to forum: Universal Imaging

5 Reply by StylusPilot

(204 replies, posted in Universal Imaging)

Hi everyone,

firstly there is alot of information on here I have been reading through and it's been a steep learning curve for a first time sysprep'er

I am having a little trouble building a universal image (seems to be a HAL issue black screen on bootup before mini-setup)

I just wanted to show the way I have been doing it and ask for some pointers.

Windows XP x86 Sysprep image

1. I created a uni processor virtual machine in VMWare Workstation
2. Install all my windows updates the long way from windowsupdate.com
3. I copied the Windows XP service pack 3 sysprep to C:\SYSPREP
4. Extracted the Driver packs to C:\SOFTWARE\DRIVERPACKS\
5. Copied the Windows XP SP3 CD to C:\SYSPREP\i386
6. Edited my Sysprep.inf as follows

 

[Unattended]
    OemSkipEula = Yes
    OemPnPDriversPath = C:\SOFTWARE\DRIVERPACKS\D
    UpdateInstalledDrivers = Yes
    InstallFilesPath = C:\SYSPREP\i386
    DriverSigningPolicy = Ignore
    NonDriversSigningPolicy = Ignore
    
[GuiUnattended]
    AdminPassword="**********"
    EncryptedAdminPassword=NO
    AutoLogon=Yes
    AutoLogonCount=1
    OEMSkipRegional=1
    TimeZone=255
    OemSkipWelcome=1

[UserData]
    ProductKey=**************
    FullName="**********"
    OrgName="**********"
    ComputerName=WINXP-01

[Display]
    BitsPerPel=32
    Xresolution=1024
    YResolution=768
    Vrefresh=60

[TapiLocation]
    CountryCode=61
    Dialing=Tone
    AreaCode=02

[RegionalSettings]
    LanguageGroup=13,17,3,2,5,16,4,12,15,11,1
    SystemLocale=00000c09
    UserLocale=00000c09
    InputLocale=0c09:00000409

[SetupMgr]
    DistFolder=C:\sysprep\i386
    DistShare=windist

[Identification]
    JoinWorkgroup=WORKGROUP

[Networking]
    InstallDefaultComponents=Yes

[GuiRunOnce]
    Command0=%SYSTEMDRIVE%\SOFTWARE\SCRIPTS\SYSPREP\CheckForIntel.vbs

[SysPrepMassStorage]

7. In my CMD Lines I use this

[COMMANDS]
"%SYSTEMDRIVE%\SOFTWARE\SCRIPTS\SYSPREP\HalUpdate.cmd"
"%SYSTEMDRIVE%\SYSPREP\SYSPREP.exe -clean"

The Halupdate.cmd is the one from QuadDamage

I have also copied devcon.exe to C:\Windows so it's in the Path for that script.
I have copied all the relevant scripts to C:\SOFTWARE\SCRIPTS\SYSPREP
I have copied the Driverpacks exe's to C:\
I have edited the DriverPacks ini to be as follows:

[Settings]
; DO NOT SET THIS MANUALLY, LET THE DriverPacks BASE DO IT FOR YOU! (may NOT contain any spaced, if it does, all exceptions must be adapted to be compatible!)
DPsRoot	= "%SystemDrive%\SOFTWARE\DriverPacks"
; DO NOT SET THIS MANUALLY, LET THE DriverPacks BASE DO IT FOR YOU!
KTD = "False"
; system variables supported (see remarks for a list) one location cannot be used as
; KTDlocation: the root directory specified in[Settings]\DPsRoot
KTDlocation	= "%SystemRoot%\SOFTWARE\DriverPacks\KTD"
; system variables supported (see remarks for a list)
logLocation = "%SystemRoot%\SOFTWARE\DriverPacks"
; enables/disables debug mode (enabled by default)
debug = "true"

I am using the Hal files supplied by Quad Damage and have copied those to C:\Windows\System32\

and then finally I run this batch file to start the process after stopping unnessary processes etc

C:\sysprep\sysprep.bat

ECHO.
ECHO This will tell Driver Packs to run after next reboot
%SYSTEMDRIVE%\DevPath.exe C:\

ECHO.
ECHO ROE Time
%SYSTEMDRIVE%\Sysprep\ROE.exe 937

ECHO.
cd %SYSTEMDRIVE%\SYSPREP

ECHO Enabling image for AMD and Intel processors
reg add "HKLM\SYSTEM\ControlSet001\Services\intelppm" /v Start /t REG_DWORD /d 4 /f

ECHO.
ECHO Flushing data to disks (preliminary):
sync -r -e

ECHO.
ECHO Cleaning up old driver caches:
del /s /q %SYSTEMDRIVE%\WINDOWS\INF\Infcache.1

ECHO.
ECHO Closing open SMB connections:
net use * /delete /yes

ECHO.
ECHO Terminating unneeded processes:
pskill -t vptray
pskill -t ccapp
pskill -t explorer
pskill -t alg
pskill -t ati2evxx
pskill -t ccevtmgr
pskill -t ccsetmgr
pskill -t defwatch
pskill -t lucoms~1
pskill -t mdm

ECHO.
ECHO Stopping unnessary services:
net stop alerter /yes
net stop wuauserv /yes
net stop browser /yes
net stop cryptsvc /yes
net stop dhcp /yes
net stop mdm /yes
net stop trkwks /yes
net stop protectedstorage /yes
net stop remoteregistry /yes
net stop seclogon /yes
net stop samss /yes
net stop wscsvc /yes
net stop lanmanagerserver /yes
net stop "symantec antivirus" /yes
net stop defwatch /yes
net stop ccevtmgr /yes
net stop sndsrvc /yes
net stop ccpwdsvc /yes
net stop ccsetmgr /yes
net stop sens /yes
net stop srservice /yes
net stop schedule /yes
net stop lmhosts /yes
net stop ups /yes
net stop uphclean /yes
net stop webclient /yes
net stop audiosrv /yes
net stop sharedaccess /yes
net stop msiserver /yes
net stop w32time /yes
net stop wzcsvc /yes
net stop lanmanworkstation /yes
net stop spooler /yes

ECHO.
ECHO Flushing data to disks (finalization):
sync -r -e

ECHO.
ECHO Executing system preparation tool (reseal / minisetup)...
ECHO.
start sysprep -forceshutdown -reseal -mini -quiet

So what have I stuffed up?

It seems to get to the point before mini setup and sit there with a black screen - so it's a HAL issue I figure?

Also I am doing that correct for Driver packs to install the relevant drivers?

Once the sysprep is finished, I create an image using FOG, and then deploy that image also with FOG

EDIT: Forgot to mention, before I run sysprep.bat I run sysprep -bmsd and then use the FindHWID to scan the driver packs for Mass Storage drivers and add them to Sysprep.inf

Go to forum: Universal Imaging