The CD Forum > OfflineSysPrep

Jack_F

Feb 15 2010, 11:35 PM

QUOTE (Galapo @ Feb 16 2010, 02:23 PM)

Have you installed ImDisk to your system? Is the system under which you're building LiveXP 64-bit? If so, have you enabled the ability to install test-signed drivers (so the test-signed ImDisk driver will install to the 64-bit system)?

Is this to just allow me to by-pass burning to a CD? Cause remember the system I'm trying to OfflineSysPrep is running in VMWare so what I am doing is burning a CD and booting the VMWare from CD and going from there.

Think I've confused myself even more...

Galapo

Feb 15 2010, 11:39 PM

No, it's so during the LiveXP build process, a raw image can be mounted to the system and assigned a drive letter so that all the PE files can be copied there. This is the image which will be loaded to ram during boot and so giving you a writable systemdrive.

Regards,
Galapo.

Galapo

Feb 15 2010, 11:40 PM

Also, no need to even burn a CD. Just point VMWare to the outputted ISO image.

Jack_F

Feb 16 2010, 08:20 AM

As per our PM discussions - ended up going the 'Create ISO' route with the 2 necessary files added for FWBF.

Booting into LiveXP (in VMWare) I see 4 versions of Sysprep, and have tried them all with simiular failures.

1. First of all, since I am using a VLK I cannot use '-activated' (aka I must select the 'Don't Reset Grace Period' option selected) - but what I've discovered when running Sysprep 5.2.3790.1830 that if I have it ticked, along with, 'pnp', 'mini', select 'Quit' and then hit 'Reseal' the sysprep dialog popup comes up for 2 seconds then disappears.

2. If I go ahead and deselect the 'Don't Reset Grace Period', I recivce the 'Grace period has been reached...' jargon and cannot proceed.

3. Sysprep 6.0.4390.0 doesn't even give options for -mini etc..

I'm lost for words atm lol - sooooo many tries and it seems God is agasint me.

Cheers

Galapo

Feb 16 2010, 04:18 PM

QUOTE (Jack_F @ Feb 16 2010, 11:20 PM)

but what I've discovered when running Sysprep 5.2.3790.1830 that if I have it ticked, along with, 'pnp', 'mini', select 'Quit' and then hit 'Reseal' the sysprep dialog popup comes up for 2 seconds then disappears.

That is normal. The process has completed.

QUOTE

3. Sysprep 6.0.4390.0 doesn't even give options for -mini etc.

Basically no option to disable it in reality. With this version you always get minisetup.

Regards,
Galapo.

Jack_F

Feb 16 2010, 04:46 PM

QUOTE (Galapo @ Feb 17 2010, 07:18 AM)

That is normal. The process has completed.

Basically no option to disable it in reality. With this version you always get minisetup.

Regards,
Galapo.

Oh wow, I was expecting it to take 10-20 minutes like my 1st Sysprep - guess its alot quicker... THERE IS STILL hope

.

With 'Sysprep Ver. 6' does it automatically do pnp etc also? I'm assuming the newest version would be the one to aim for, but wasn't sure what it would do automatically aka pnp, mini (which I know it does now), but activate and SID?

Ill let you know how it goes, I'm about to boot into WDS and capture since apparently you say thats it

.

EDIT: See from the attached screenshot - is this fine? Happens everytime, no matter what options are selected.

Cheers

Galapo

Feb 16 2010, 07:48 PM

QUOTE (Jack_F @ Feb 17 2010, 07:46 AM)

With 'Sysprep Ver. 6' does it automatically do pnp etc also? I'm assuming the newest version would be the one to aim for, but wasn't sure what it would do automatically aka pnp, mini (which I know it does now), but activate and SID?

I think it should do these things. Personally, I like to use v.5.1.2600.0.

Regarding the DRM issue, that's normal running sysprep offline. If you're concerned about it, select the option on the Advanced interface:

Regards,
Galapo.

Jack_F

Feb 16 2010, 07:57 PM

Just finishing capturing the image, and about to deploy (OH THE EXCITMENT!!!!!)

One question though, since using WDS, I have a sysprep.inf under ImageGroup\[Name]\$OEM$\$1\sysprep - do I keep the -bmsd/[SysprepMassStorage]/BuildMassStorage=Yes options in that one or take them out like the sysprep.inf for the 2nd Sysprep we did?

Cheers

Galapo

Feb 16 2010, 08:05 PM

Sorry, I have no experience with WDS so I have no idea.

Regards,
Galapo.

Jack_F

Feb 16 2010, 08:26 PM

Hmm alrightly - I'm just trying to think it out logically here.

- Our 1st Sysprep used [SysprepMassStorage] tag with the -bmsd output, with -reseal and -forceshutdown.
- Our 2nd Sysprep ran inside LiveXP with no [SysprepMassStorage], -reseal, -mini, and -pnp.

As I don't fully understand what gets removed each Sysprep, or copied to the system - would I assume that the -bmsd has been ADDED and kept from the 1st Sysprep and there is no need to pass BuildMassStorage=Yes or [SysprepMassStorage] again...

*Thinks*

Jack_F

Feb 16 2010, 09:44 PM

Heres an interesting one for you haha.

CODE

Upload image to WDS, boot into Network PXE, Loads WDS - Grabs and installs Image from WDS.

Reboots to continue as is all normal, get to the "Please wait for Windows to setup..." screen, gets past that, start to see Black Background with Mouse Pointer then PC just Shutdown.....

I've crossed out that its nothing to do with WDS by removing 'Unattended' methods all together so its JUST the image - I'm thinking somethings differently gone wrong in ethier of the Syspreps.

Ideas for me to try mate?

EDIT: I've used HAL Automatic Detection on First Boot - this was correct yeah?

Galapo

Feb 16 2010, 10:02 PM

Auto HAL option on first boot sets the HAL then shuts down the system. This is normal. If it didn't, there would be a registry glitch on first boot. After shutdown, you just need to restart the PC which should then boot with minisetup then starting.

Reagrds,
Galapo.

Jack_F

Feb 16 2010, 10:27 PM

QUOTE (Galapo @ Feb 17 2010, 01:02 PM)

Auto HAL option on first boot sets the HAL then shuts down the system. This is normal. If it didn't, there would be a registry glitch on first boot. After shutdown, you just need to restart the PC which should then boot with minisetup then starting.

Reagrds,
Galapo.

Nah yea I figured that, but upon reboot I get the "The system is not fully installed. Please run setup again"...

Galapo

Feb 16 2010, 11:21 PM

What version of Windows Media Player is installed on the system? Version 11 is known to produce this issue with sysprep.

Jack_F

Feb 16 2010, 11:27 PM

QUOTE (Galapo @ Feb 17 2010, 02:21 PM)

What version of Windows Media Player is installed on the system? Version 11 is known to produce this issue with sysprep.

Media Player 11 is installed, however the first image I ever created (just using DriverPacks) worked fine with it installed.

I moved to wanting to try OSP because its commented as being better for MassStorage drivers.

Galapo

Feb 16 2010, 11:35 PM

See here:
http://www.edugeek.net/forums/windows/9770...etup-again.html
http://www.experts-exchange.com/OS/Microso...Q_22087525.html
http://blog.dynamoo.com/2007/03/system-is-...ed-windows.html

Regards,
Galapo.

Jack_F

Feb 18 2010, 12:39 AM

QUOTE (Galapo @ Feb 17 2010, 02:35 PM)

See here:
http://www.edugeek.net/forums/windows/9770...etup-again.html
http://www.experts-exchange.com/OS/Microso...Q_22087525.html
http://blog.dynamoo.com/2007/03/system-is-...ed-windows.html

Regards,
Galapo.

Thanks for those, I'm still waiting on Overflow to reply as to the steps needed to be taken with S.A.D...

However, in the meantime, I was thinking what might be causing issues with my process. I'm thinking the double 'sysprep'in' might be an issue, as I havern't heard anyone doing this before.

Is there a way to inject MassStorage drivers and just run a singular 'Sysprep' - I understand the issue is with -bmsd, but is there no way to include this within LiveXP/OfflineSysPrep? Do I even need to be having the -bmsd output if I'm running a OfflineSysPrep inject?

What I'm trying to achieve is the BEST universal image I can for any circumstance as I'm sure you can understand.

Cheers

Galapo

Feb 18 2010, 01:14 AM

QUOTE (Jack_F @ Feb 18 2010, 03:39 PM)

However, in the meantime, I was thinking what might be causing issues with my process. I'm thinking the double 'sysprep'in' might be an issue, as I havern't heard anyone doing this before.

What you should be doing is doing the -bmsd in the virtual machine, then the -reseal procedure, then boot it and let it go through its configuration. Once system is working, then reboot to PE and run OfflineSysPrep for the DP mass storage driver injection.

QUOTE

Is there a way to inject MassStorage drivers and just run a singular 'Sysprep' -

Sure, just select the option on the Advanced interface to not run sysprep.

QUOTE

Do I even need to be having the -bmsd output if I'm running a OfflineSysPrep inject?

Like I said a couple of times, you only need to do this if you either a) want support for out-of-the-book drivers supplied with XP/2k3; or b) if you want support these drivers and CriticalDeviceDatabase and corresponding services have been pared down and they need to be added back.

Regards,
Galapo.

Jack_F

Feb 18 2010, 01:41 AM

QUOTE (Galapo @ Feb 18 2010, 04:14 PM)

What you should be doing is doing the -bmsd in the virtual machine, then the -reseal procedure, then boot it and let it go through its configuration. Once system is working, then reboot to PE and run OfflineSysPrep for the DP mass storage driver injection.

Well heres one thing I didn't do the first time around.. But I'm alittle confused by this comment - if I sysprep, reseal and reboot so DriverPacks install, won't when I reboot into LiveXP to do OfflineSysPrep/Inject MassStorage and re-sysprep - the final Image I'm capturing won't install DriverPacks since I'm imaging an PC already setup? I understand this working if I was creating an image for just ONE type of PC (aka Dell GX670 or w/e).

QUOTE

Sure, just select the option on the Advanced interface to not run sysprep.

Like I said a couple of times, you only need to do this if you either a) want support for out-of-the-book drivers supplied with XP/2k3; or

if you want support these drivers and CriticalDeviceDatabase and corresponding services have been pared down and they need to be added back.

My thinking is if I setup DriverPacks how I want, do a sysprep -reseal -mini -pnp -forceshutdown THEN boot into LiveXP inject MassStorage then NOT do another sysprep - won't the image then be sysprep ready + have the injected MassStorage next time the image boots onto a new Workstation?

OR

Setup DriverPacks how I want, boot into LiveXP inject MassStorage then do a sysprep -reseal -mini -pnp -forceshutdown?

Cheers

Galapo

Feb 18 2010, 06:20 PM

Here's what I would do:

1. Run -bmsd.
2. Run -reseal -forceshutdown
3. Boot system and then do your driverpack stuff
4. Boot to PE and run OfflineSysPrep with these options:

5. When sysprep starts, select your options
6. Image system

Regards,
Galapo.

Jack_F

Feb 18 2010, 10:14 PM

DAMMIT - right, so followed both your and Overflows' directions to 'the t' BUT once again, it shutdowns randomly during the install process and when I go to restart I get to the "The System is not fully installed. Please run setup again" - I had uninstalled WMP 11 previously.

Apprantely reading into it some more the WMP 11/Random Patch that was causing the error can be avoided with -Mini, which I'm running so...

If I follow the steps you outlined above, wouldn't I have to RE-SETUP the machine after step 2? (Computer name etc, since when you boot after a sysprep it re-does all that no?)

Cheers

Cheers

Galapo

Feb 18 2010, 10:33 PM

QUOTE (Jack_F @ Feb 19 2010, 01:14 PM)

If I follow the steps you outlined above, wouldn't I have to RE-SETUP the machine after step 2? (Computer name etc, since when you boot after a sysprep it re-does all that no?)

Yes, you would have to do that. That's the inconvience of needing to do -bmsd. If no HWIDs supported by out-of-the-box drivers have been pruned from CriticalDeviceDatabase (and corresponding services) then there's no need to do -bmsd at all anyway. In time, I'll add a function to do this build into OfflineSysPrep. In the meantime, you can do this offline yourself without using sysprep by extracting driver.cab somewhere, then overwriting with sp*.cab. Then run peimg.exe on machine.inf, pnpscsi.inf, scsi.inf, and mshdc.inf. Details on using peimg.exe here: http://www.911cd.net/forums//index.php?showtopic=21867.

Regards,
Galapo.

Jack_F

Feb 18 2010, 11:35 PM

QUOTE (Galapo @ Feb 19 2010, 01:33 PM)

Yes, you would have to do that. That's the inconvience of needing to do -bmsd. If no HWIDs supported by out-of-the-box drivers have been pruned from CriticalDeviceDatabase (and corresponding services) then there's no need to do -bmsd at all anyway. In time, I'll add a function to do this build into OfflineSysPrep. In the meantime, you can do this offline yourself without using sysprep by extracting driver.cab somewhere, then overwriting with sp*.cab. Then run peimg.exe on machine.inf, pnpscsi.inf, scsi.inf, and mshdc.inf. Details on using peimg.exe here: http://www.911cd.net/forums//index.php?showtopic=21867.

Regards,
Galapo.

As I'm skipping this BSMD option, could THIS be causing the random, shutdown and 'installation' errors? If not I'd like to get that sorted first before I worry about -bmsd - is there any logs I can provide you with or information to help decipher this?

My first time using sysprep I simply only ran with DriverPacks - then they suggested I use OSP aswell for MassStorage - the first time (with just DriverPacks) I created a image successfully with no issues, so I'm defo thinking its something in between the move to LiveXP or double 'sysprep'...

EDIT1: Thinking this could also be an issue with that Longhorn Reloaded NTLDR... Do you have a XP64bit ntldr I can check with to see if we get some actual bootup?

EDIT2: Following the guide here: http://support.microsoft.com/kb/320279 - I booted in LiveXP and did the registry changes, upon reboot I wasn't presented with the normal "Please wait while Setup runs..." just straight back to my Administrator Login page, if I log in, its just as if I had never ran OSP - DriverPacks doesn't run, but all files are still sitting there in C: etc - to me this is reading as OSP is NOT working...

Cheers

Galapo

Feb 19 2010, 12:28 AM

QUOTE (Jack_F @ Feb 19 2010, 02:35 PM)

Do you have a XP64bit ntldr I can check with to see if we get some actual bootup?

Please do not ask for this when you can just download a service pack...

QUOTE

DriverPacks doesn't run, but all files are still sitting there in C: etc - to me this is reading as OSP is NOT working...

I have no idea what you mean by "DriverPacks doesn't run". You can tell if OfflineSysPrep has injected drivers successfully (if you selected this option) if driver SYS files have been copied to the drivers folder and if HWIDs have been entered into CriticalDeviceDatabase.

Regards,
Galapo.

Jack_F

Feb 19 2010, 12:43 AM

QUOTE (Galapo @ Feb 19 2010, 03:28 PM)

Please do not ask for this when you can just download a service pack...

I have no idea what you mean by "DriverPacks doesn't run". You can tell if OfflineSysPrep has injected drivers successfully (if you selected this option) if driver SYS files have been copied to the drivers folder and if HWIDs have been entered into CriticalDeviceDatabase.

Regards,
Galapo.

I apoligise, I didn't realize it was simply in SP2 of XP64 - Downloading it now to test if its just the Longhorn NTLDR - Will report back....

When I said the DriverPacks doesn't run, normally DriverPacks finisher will boot up, install various drivers/applications, the finisher will then run and delete everything. If I go in and use the fix in that Windows link, it seems (to me atleast) that the 2nd Sysprep I'm running - from OfflineSysPrep is NOT finalizing and making sure it does a -mini because no Mini setup is run...

I don't know if the above is coming true because I am hacking into the Registry and fixing that entry, but to me it seems the OfflineSysPrep sysprep is not properly resealing etc...

Galapo

Feb 19 2010, 12:50 AM

QUOTE (Jack_F @ Feb 19 2010, 03:43 PM)

If I go in and use the fix in that Windows link, it seems (to me atleast) that the 2nd Sysprep I'm running - from OfflineSysPrep is NOT finalizing and making sure it does a -mini because no Mini setup is run...

Well, by doing the "fix" you will be telling the system to not run minisetup or whatever. What's the value of the 'CmdLine' string under 'HKLM\System\setup'?

Jack_F

Feb 19 2010, 01:01 AM

QUOTE (Galapo @ Feb 19 2010, 03:50 PM)

Well, by doing the "fix" you will be telling the system to not run minisetup or whatever. What's the value of the 'CmdLine' string under 'HKLM\System\setup'?

Well that would explain that then.. Didn't look at the value, if your telling me that changing that will not probably run things then I understand.

What I can't understand is W T F is going on between setting up DriverPacks, sysprep'in, LiveXP and doing OfflineSysPrep with the settings you suggested above and then sysprep'in again for the system to completly break..

RAWRRRRRRRRRRRRRRRRRRR

Galapo

Feb 19 2010, 01:14 AM

You'll need to tell me the CmdLine value in order to be able to get an indication of what might be happening.

Thanks,
Galapo.

Jack_F

Feb 19 2010, 02:31 AM

QUOTE (Galapo @ Feb 19 2010, 04:14 PM)

You'll need to tell me the CmdLine value in order to be able to get an indication of what might be happening.

Thanks,
Galapo.

CmdLine value is:

hiderun.exe /w cmd.exe /c %SystemDrive%\Sysprep\OSP\OfflineSysPrep.exe -HALauto XPsp3 "\windows"

Galapo

Feb 19 2010, 02:37 AM

Ok, now we're getting somewhere. OfflineSysPrep didn't complete its HAL setting routine on first boot on your system.

Some questions:

1. Is hiderun.exe under system32?
2. What files exist at %SystemDrive%\Sysprep\OSP?
3. Under your booted system, what happens if you type that cmdline into a command prompt?

Thanks,
Galapo.

Jack_F

Feb 19 2010, 03:12 AM

QUOTE (Galapo @ Feb 19 2010, 05:37 PM)

Ok, now we're getting somewhere. OfflineSysPrep didn't complete its HAL setting routine on first boot on your system.

Some questions:

1. Is hiderun.exe under system32?
2. What files exist at %SystemDrive%\Sysprep\OSP?
3. Under your booted system, what happens if you type that cmdline into a command prompt?

1. Yes, it is indeed there
2. [See pictures attached]
3. The file sysprep.exe is missing from "C:\Sysprep\OfflineSysPrep\sysprep". Offline syspreping will not be able to be performed; HAL replacement, and 'Advanced Options' will, however, be possible...

Galapo

Feb 19 2010, 03:20 AM

QUOTE

name='Jack_F' date='Feb 19 2010, 06:12 PM' post='161744']
2. [See pictures attached]

Sorry, you gave me files under %SystemDrive%\Sysprep. I want the list of files which exist under %SystemDrive%\Sysprep\OSP.

QUOTE

3. Booting into non-LiveXP now to test command....

Yes, boot into the full OS to test, not under PE.

Thanks,
Galapo.

Galapo

Feb 19 2010, 03:22 AM

QUOTE (Jack_F @ Feb 19 2010, 06:12 PM)

3. The file sysprep.exe is missing from "C:\Sysprep\OfflineSysPrep\sysprep". Offline syspreping will not be able to be performed; HAL replacement, and 'Advanced Options' will, however, be possible...

You didn't type the commandline properly. You need to type it exactly.

Jack_F

Feb 19 2010, 03:23 AM

QUOTE (Galapo @ Feb 19 2010, 06:20 PM)

Sorry, you gave me files under %SystemDrive%\Sysprep. I want the list of files which exist under %SystemDrive%\Sysprep\OSP.

Yes, boot into the full OS to test, not under PE.

3. The file sysprep.exe is missing from "C:\Sysprep\OfflineSysPrep\sysprep". Offline syspreping will not be able to be performed; HAL replacement, and 'Advanced Options' will, however, be possible...

Jack_F

Feb 19 2010, 03:26 AM

QUOTE (Galapo @ Feb 19 2010, 06:22 PM)

You didn't type the commandline properly. You need to type it exactly.

I copied it WORD for WORD straight from regedit mate.. can get screenshots if necessary.

Edit1: Upon rebooting (first time I issued the above command it gave the error, then shutdown), so rebooting to screenshot for you, copy and pasted command again - pasted into cmd prompt - and this time no error...

Could of been a mistake on my part OR 2nd time round doesn't have error...?

Rebooting after the time with NO error, CmdLine still has same value - should this be disappearing if applied correctly?

Galapo

Feb 19 2010, 03:54 AM

QUOTE (Jack_F @ Feb 19 2010, 06:26 PM)

Could of been a mistake on my part OR 2nd time round doesn't have error...?

Mistake on your part first time. Test tells me that the command works, so something else wrong.

Please post the contents of %SystemDrive%\Sysprep\OSP\HALauto.reg.

Thanks,
Galapo.

Jack_F

Feb 19 2010, 03:56 AM

QUOTE (Galapo @ Feb 19 2010, 06:54 PM)

Mistake on your part first time. Test tells me that the command works, so something else wrong.

Please post the contents of %SystemDrive%\Sysprep\OSP\HALauto.reg.

Thanks,
Galapo.

CODE

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\Setup]
"SetupType"=dword:00000001
"SystemSetupInProgress"=dword:00000001
"CmdLine"=hex(7):73,00,65,00,74,00,75,00,70,00,2e,00,65,00,78,00,65,00,20,00,\
  2d,00,6e,00,65,00,77,00,73,00,65,00,74,00,75,00,70,00,20,00,2d,00,6d,00,69,\
  00,6e,00,69,00,00,00,00,00
"SystemPrefix"=hex:c7,0b,00,00,00,c0,4b,40
"SystemPartition"="\\Device\\HarddiskVolume1"
"OsLoaderPath"="\\"
"BootDiskSig"=dword:aca9aca9
"CloneTag"=hex(7):46,00,72,00,69,00,20,00,46,00,65,00,62,00,20,00,31,00,39,00,\
  20,00,31,00,36,00,3a,00,34,00,39,00,3a,00,31,00,37,00,20,00,32,00,30,00,31,\
  00,30,00,0a,00,00,00,00,00
"MiniSetupDoPnP"=dword:00000001
"MiniSetupInProgress"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\Setup\AllowStart]

[HKEY_LOCAL_MACHINE\SYSTEM\Setup\AllowStart\AFD]

[HKEY_LOCAL_MACHINE\SYSTEM\Setup\AllowStart\DcomLaunch]

[HKEY_LOCAL_MACHINE\SYSTEM\Setup\AllowStart\EventLog]

[HKEY_LOCAL_MACHINE\SYSTEM\Setup\AllowStart\PlugPlay]

[HKEY_LOCAL_MACHINE\SYSTEM\Setup\AllowStart\ProtectedStorage]

[HKEY_LOCAL_MACHINE\SYSTEM\Setup\AllowStart\Rpcss]

[HKEY_LOCAL_MACHINE\SYSTEM\Setup\AllowStart\Sacsvr]

[HKEY_LOCAL_MACHINE\SYSTEM\Setup\AllowStart\SamSs]

[HKEY_LOCAL_MACHINE\SYSTEM\Setup\AllowStart\WS2IFSL]

[HKEY_LOCAL_MACHINE\SYSTEM\Setup\Pid]
"Pid"="76487270"

I'm at work - waiting after hours so we can get this resolved - *cracks open a Dr Pepper* lets roll

Galapo

Feb 19 2010, 04:07 AM

So cmdline in the REG file is 'setup.exe -newsetup -mini', which is what it should be. It's not being inserted into your registry.

Here's the call I'm using: 'regedit.exe /S %SystemDrive%\Sysprep\OSP\HALauto.reg'. What happens when you run that from a command prompt. Make sure you enter it exactly.

Thanks,
Galapo.

Jack_F

Feb 19 2010, 04:12 AM

QUOTE (Galapo @ Feb 19 2010, 07:07 PM)

So cmdline in the REG file is 'setup.exe -newsetup -mini', which is what it should be. It's not being inserted into your registry.

Here's the call I'm using: 'regedit.exe /S %SystemDrive%\Sysprep\OSP\HALauto.reg'. What happens when you run that from a command prompt. Make sure you enter it exactly.

Thanks,
Galapo.

Nothing happens - did you want me to do a reboot? (My C: still has all these DriverPacks files that has never installed/run - is that another issue entirely, or once we solve this, DriverPacks SHOULD run after HALauto works?)

Galapo

Feb 19 2010, 04:13 AM

Check HKEY_LOCAL_MACHINE\SYSTEM\Setup,CmdLine now.

Jack_F

Feb 19 2010, 04:15 AM

Upon reboot (didn't wait for your reply) I know have a "Windows XP Setup" popup with "Waiting..." OOOOOOOOOOOOMG PROMISING!

Edit1: Its now "Detecting and installing devices" now

Edit2: Attached Pic

Galapo

Feb 19 2010, 04:18 AM

Ok, so the question now is: why didn't this happen upon first boot?

Jack_F

Feb 19 2010, 04:20 AM

QUOTE (Galapo @ Feb 19 2010, 07:18 PM)

Ok, so the question now is: why didn't this happen upon first boot?

I would LOVE to know - so I can start deploying these on Monday... Something within the latest LiveXP script?

Edit1: YAY!
Edit2: HUUUUUUUUUUUUUUUUUUUUUUUUUZAH! DriverPacks finished, booted in Windows PERFECT, added all drivers - nothing in Hardware with '?' - added to domain PERFECT - sweet f'ing AS!

Now we just need to figure out what-the-biscuits! is going on with LiveXP..

/Dance

Galapo

Feb 19 2010, 04:36 AM

Nice news!

Have to get to the bottom of this. Please use the test version here. Overwrite the OfflineSysPrep.exe file under LiveXP.

Do your sysprep procedure again on fresh system. On first boot after running sysprep and when you get to the desktop, post the contents of the file %SystemDrive%\Sysprep\OSP\Jack_F_debug.txt.

Thanks,
Galapo.

Jack_F

Feb 19 2010, 04:43 AM

QUOTE (Galapo @ Feb 19 2010, 07:36 PM)

Nice news!

Have to get to the bottom of this. Please use the test version here. Overwrite the OfflineSysPrep.exe file under LiveXP.

Do your sysprep procedure again on fresh system. On first boot after running sysprep and when you get to the desktop, post the contents of the file %SystemDrive%\Sysprep\OSP\Jack_F_debug.txt.

Thanks,
Galapo.

Rebooting VMWare to LiveXP as we speak - report back ASAP. Out of interest do you want me to use all those Advanced Options, and normal sysprep options then reseal and quit like normal?

Galapo

Feb 19 2010, 04:48 AM

Just select the driver injection and auto HAL on first boot option. Run whatever sysprep options you've been using. Then reboot.

Jack_F

Feb 19 2010, 04:52 AM

QUOTE (Galapo @ Feb 19 2010, 07:48 PM)

Just select the driver injection and auto HAL on first boot option. Run whatever sysprep options you've been using. Then reboot.

Using the attached Settings correct? If I do this, its gonna take about 30 mins to re-capture image with ImageX again - thats right yeah? You want me doing this with a whole new fresh .wim correct?

OR

Or push same old image out, and in between the reboot (which normally results in a crash Shutdown) quickly boot LiveXP and replace poo, or is crap already broken by then?

Galapo

Feb 19 2010, 04:54 AM

Settings are correct. No need to capture and deploy. Just reboot and see what happens.

Galapo

Feb 19 2010, 04:56 AM

Sorry, wrong DP mass storage option is checked. You need to be using the lower option. Option you have only installs a single mass storage driver. Under VMWare, that will be the vmscsi driver if it's detected as needed.

Galapo

Feb 19 2010, 04:57 AM

Also, you're not using the test version I linked to above! Download and use that version please.