Good afternoon,

I come here in desperation and a little bit of frasutration . Over the past few weeks I have been tasked with setting up our WSUS and WDS Server at work (YAY IS ME... haha) and after successfully implementing WSUS I moved onto WDS.

This is were the hair pulling begins. We currently have a number of PCs around the Office used by Employees (Ranging from Dells to HPs, and one or two old school Compaqs - they range from UP to MP so where it all began). I than have to deal with our Thin Clients which are deployed to our Customers.

First things first, we'll deal with Employee PCs/Laptops:

Shortly after I began my new venture, I learnt of HAL and the issues of Drivers the hard one, here I am, Sysprep'in a PC, capturing the image with WDS and then imaging the 10 or so of those HP machines - I'm thinking BRILLIANT couldn't be easier - WRONG haha.

Long story short (so as not to make this a WALL OF TEXT) - I discovered OfflineSysprep through the DriverPacks website, tried following the instructions posted on here (which are most def. outdated by now I'm sure), tried various applications like MySysPrep etc to no avail.

After reading through this sticky, I'm somewhat even more lost now (haha) - hearing good things about OfflineSysPrep but don't quite understand it fully, or think it suits what I'm trying to do. Here is what I have atm, and hope someone can point me in the right direction - I would be more than happy to write an update HOWTO guide for the public once this DILEMMA is over.

1. Installed XP Pro on fresh machine
2. Installed SP3 - various Hotfixes/Patches
3. Installed our companys' various required Applications (Anti-Virus, Altiris, VNC etc)
4. Downloaded all the 'latest' DriverPacks packages and extracted them all to C: (C:\D, with the .inf in C: )
5. Have all the SysPrep tools from the Deploy.cab extracted to C:\sysprep
6. ROE.exe in C:\sysprep, DPsFnshr.ini and extract DPsFnshr.7Z to C:, DevPath.exe in C: and also ATICCC.ins in there.

Then gone ahead and imaged it with Ghost (learnt the hardway, had to rebuild the above setup numerous times after 'bad' images) - and awaiting your feedback.

On a sidenote: I hope to go completly 'unattended' with WDS as I had done when I was imaging those 20 or so PCs I did successfully before (Using sysprep.inf and an unattended .xml on the WDS server).

Looking forward to hearing where I've been going wrong....

That's all the steps you did? Did you run anything after step 6?

You need to detail what you're trying to do and what exactly is going wrong?

Regards,
Galapo.

Those instructions are for DriverPack BASE, not OfflineSysPrep.

Regards,
Galapo.

No, I understand that - I've run through NUMEROUS steps previously to try and get it working. I was only outlining what I have done UP UNTIL THIS POINT - waiting to see what my next action should be, if I've done the previous actions fine, and if OfflineSysPrep is even suitable for what I'm trying to do on my local machines.

Thanks,
Jack

Sorry, I can't say whether the steps are correct because I don't know what you're trying to do. Like I said, need to detail what you're trying to do and what exactly is going wrong.

Regards,
Galapo.

Well I covered what I wanted to achieve in my very first post.

What I'm trying to gather is if OfflineSysPrep can be used to do what I am trying to achieve - that is create a universal XP Pro image that can be deployed via our WDS server without the issue of concerns over HAL, and drivers (thus the use of DriversPack in coordination with OfflineSysPrep).

The steps I have outlined is what I have done up until this point - the system is now sitting next to me until I can be informed by you what/how to achieve what I want to do next.

Cheers

I have no idea about WDS servers. But what I can tell you is that OfflineSysPrep can be used for injecting DriverPacks mass storage drivers into an offline system or mounted image, set HAL (either manually, or HAL determined under PE, or automatically at first boot), perform a number of operations that sysprep normally performs, or provide the ability to run sysprep on the offline system.

Hope this helps.

Regards,
Galapo.

When you say offline or mounted, thats where I get a little confused.

The normal way I have been doing it in the past (with the default Sysprep from Microsoft) is putting together the system how I want it, and then running Sysprep -mini -reseal -restart.

I'm not sure I'm understanding how I can sysprep and offline computer? I have made an image in Ghost of the system if that helps? I also have a BartPE CD at the ready..

What I'm looking to do is create an image that will be able to be used on any machine I wish to run it on (be it UP or MP etc).

Cheers

he means running it from PE

When you say from PE, I assume you mean from say BartPE? I currently have a TechEd version from October a number of years back, how can I get OfflineSysPrep onto there?

Before I do that, what state does the PC I am imaging need to be in? Must it have all the software I want installed, with user accounts setup? Do I need to do any preparation in regards to DriversPack etc?

Thanks,
Jack

Not necessarily BartPE. LiveXP or any other (32-bit) PE can run it. The way you use OfflineSysPrep on BartPE is either to build it with the plugin, or use the standalone version. The way you use it in LiveXP is to simply enable the script before building. Read the the pinned topics of this sub-forum for more details.

Regards,
Galapo.

We've just recently bought VMWare products so wanted to give this a whirl in here rather then constantly rebooting and having to Ghost images back on when sh*t hit the fan.

My question to you is, am I able to have OfflineSysPrep point to an offline VMWare HDD? Also I saw mention a while back on the DriverPacks forum that you were looking into implementing -BSMD option so we don't have to, is this true in the latest version?

I am still slightly confused the difference between having DriverPacks do MassStorage instead of OfflineSysPrep but heard OfflineSysPrep was the way to go...

Yes, assuming it's mounted and assigned a drive letter.


No, not implemented. Would probably take me around 2 days to get working and I just don't have time to devote to that at the moment.


DriverPacks BASE will integrate mass storage drivers into a windows installation media. OfflineSysPrep will inject mass storage drivers into a currently installed system.

Regards,
Galapo.

When you say a 'currently installed system' do you mean to say that OfflineSysPrep cannot be used to create a Universal Image for imaging Notebooks and PCs within a company? To me, 'installed' system reads as it has already gone through the unattended mode that SysPrep prepares for.

I mean that you get your system ready to image, prior to sysprepping. Then instead of using traditional sysprep.exe, you use OfflineSysPrep.exe, which optionally allows you to run sysprep.exe against the offline/non-booted system. Then you image. Then you can deploy.

Regards,
Galapo.

Ahhh I see, so I can set DriverPacks up (minus the MassStorage), shutdown system (without Syspreping as you normally would) then run OfflineSysPrep on my offline mapped VMWare Image HDD?

Yes, that's right. If you want to use a sysprep.inf file, supply it in the \sysprep\ folder in the OfflineSysPrep folder, or you can select to run SysprepInfEditor from the Advanced options to create one before sysprep is started.

Regards,
Galapo.

I guess I should add that if you're going to be injecting all the DPs mass storage drivers, then you will need to update ntldr from xp 64bit otherwise the memory limit will be breached and you'll get the ntfs.sys error (doesn't happen in PE because PE can use compressed drivers so hasn't reached the limit yet).

If you don't want to update ntldr, then you will need to disable drivers through the user_settings.ini file. Details in that file. I forget what Ilko and I worked out in our tests, but it was somewhere around 75 drivers that could be injected before the memory limit was reached. You just have to work out which controllers you want to support with your image.

Hope this helps.

Regards,
Galapo.

And if I wanted to update ntldr where would I be looking for that information - the system I am imaging is Windows XP Professional 32Bit - not sure if it was your spelling but did you mean I had to move to 64Bit? I would like to include ALL MassStorage Drivers for 'any' circumstance - is the ntldr update process tediously complicated?

Cheers

OfflineSysPrep is only for 32bit systems.

You'd obtain 64bit ntldr from downloading a servicepack to 64bit XP and extracting from there. Longhorn ntldr works also with added advantage of automatic HAL swaps. Details here: http://www.911cd.net/forums//index.php?sho...st&p=144100.

Regards,
Galapo.

If your saying what I think you are I LOVE you lol. I have Windows 7 Ultimate DVD here (we will be migrating to this as a Standard within the company once Budgeting is done in Financial Year).

So you're saying if I grab the ntldr from my Win 7 DVD, replace Windows XP one, following instructions from Link above, OfflineSysPrep will inject all the MassStorage Drivers AND as an added bonus, let me get away with INDEPENDENT HAL installations?

I have been battling with HAL for the past 2 weeks, if this is the solution, and I can get rid of all these hack together .bat scripts I currently run when doing a 'sysprep' I will be REJOICING!

Thanks!

Sorry, I did say Longhorn and I meant it. Early stages of Longhorn development there was still ntldr as bootloader, but beefed up with extra features. Somewhere in latter stages of development, further progress was made which became the Vista/Win7 bootloader, something quite different to ntldr.

As far as HAL swaps is concerned, OfflineSysPrep can handle this automatically upon first boot (like MySysprep, but it only supports acpiapic_up and acpiapic_mp) for standard, acpipic, acpiapic_up and acpiapic_mp HALs.

Regards,
Galapo.

Alright, I'll go in search of a Longhorn DVD - you or Oleg_II or someone else in your team wouldn't have its' ntldr handy would you?

Your second line about HAL, were you saying MySysPrep could only handle those, or OfflineSysPrep can handle only those? I read it as if you were saying OfflineSysPrep is superior, correct me if I am wrong.

My search begins... Oh and if I find one, is it simply copy and paste, overwriting the XP one?

Cheers mate!

MySysprep can handle swaps between acpiapic_up and acpiapic_mp HALs.

OfflineSysPrep can handle swaps between standard, acpipic, acpiapic_up and acpiapic_mp HALs.

As for ntldr, yes, overwrite with the Longhorn or xp 64bit one.

Regards,
Galapo.

Just to confirm, the XP 64bit won't do the HAL switching tho?

No, won't do automatic HAL detection and switching, but has a higher memory limit so tolerates more drivers at boot.

Regards,
Galapo.

Have you had much experience with DriverPacks, now after attaining a Longhorn version of the ntldr I need to now prep my system for SysPrep. Below is what I've done so far to the system after overwriting the XP ntldr.



Cheers

Right, so I've created the 'UnderWindows' version ready to go, followed your Instructions to the 't'.

Map my VMWare Image drive to R: and I get the following attached error. I have tried different Drive Letters, ended every Task in TaskMgr that could POSSIBILY be using it, nothings running and the error still presists.

Ideas mate?

Error indicates that the offline registry hive wasn't mounted successfully. From your screenshot, it would appear that you are running under Vista or Win7. If that's the case, likely you will need to disable UAC and run the program as administrator.

Regards,
Galapo.

UAC has been off since day one, and running as Administrator is providing the same error unfortunately.

Running Windows 7 Ultimate 64bit if this helps.

I do not have a 64-bit system in order to be able to test, hence running the app under such an architecture is untested by me (and therefore also unable to be fixed if there is some bug). Looks like your test shows it is not compatible with 64-bit OS.

You'll need then to run it under 32-bit OS or under 32-bit PE.

Regards,
Galapo.

Guess we can say its a good thing we found a bug, but annoying at the same time heh.

Just built a LiveXP disc with OfflineSysPrep enabled - as I have never used OfflineSysPrep before just want to confirm (since this isn't using the UnderWindows version), the script will prompt for a sysprep.inf to use?

I have prepared my DriverPacks (Using S.A.D), created my sysprep.inf and ran sysprep.exe -bmsd (but did NOT add anything else cause I assume OfflineSysPrep will do this?), copyed over Longhorn ntldr and booted into LiveXP ready to initiate script - this should be all I need to do as OfflineSysPrep will now take over, once shutdown I can boot into WDS capture, then deploy?

Cheers.

I always suspected that it wouldn't work under 64-bit without some adjustments. But unfortunately I don't have the necessary hardware to test.


No, no prompt. If you want to use one, you need to supply one. Either a) on the script interface at PE build-time; b) copying to the sysprep folder before running OfflineSysPrep; or c) secting to use the SysprepInfEditor on the Advanced options interface to create one before sysprep is called.


If you want to use the -bmsd option, you will need to do the following. Boot into the system you want to sysprep. Run 'sysprep.exe -bmsd', then run 'sysprep.exe -forceshutdown -reseal'. Then boot LiveXP to run OfflineSysPrep etc. You need to do it this way because running sysprep.exe against an offline system only works if sysprep.inf does NOT contain a [SysprepMassStorage] section or a BuildMassStorage=yes line.


Yes, with the above caveats in mind.

Regards,
Galapo.

When you say copy to sysprep folder before running OfflineSysPrep do you mean on the Systems C: or prior to creating LiveXP? Since LiveXP is already built, and if the previous statement can't be done, I'll end up just using the SysprepInfEditor I guess.




Does the -bmsd option really need to be even run prior to injecting MassStorage with OfflineSysPrep, or does the injecting bypass/superior to -bmsd anyway?

On a sidenote, should I be including the MassStorage pack into my DriverPacks or let OfflineSysPrep handle ALL the MassStorage side of things? Also is there any use in using Vernalax's SysPrep Driver Scanner or once again, this is handled by DriverPacks/OfflineSysPrep?

Cheers

If you point the OfflineSysPrep script to your sysprep.inf file, it will be included at PE build-time. Otherwise, I mean copying it to 'x:\Program Files\OfflineSysPrep\sysprep\' folder (or wherever OfflineSysPrep will be run from) after the PE is booted.


Running 'sysprep.exe -bmsd' adds support for the drivers supplied out-of-the-box with XP/2k3. If they're not needed and/or the CriticalDeviceDatabase and corresponding service entries for them already exist, then you don't need to do this. OfflineSysPrep adds the DPs mass storage drivers, ie sata and raid drivers not supplied out-of-the-box.


OfflineSysPrep used to make use of that app, but has now been replaced by an internal function doing the same. Up to you if you want to use either option. But this way, you system will be doing a pnp at first boot which is highly recommended.

Regards,
Galapo.

Since I'm trying to make a Universal Image, I think I'm going to play it safe and ensure I do the 'sysprep.exe -bsmd', followed by 'sysprep.exe -forceshutdown -reseal' - but should I be including -minisetup in that, or when I go to OfflineSysPrep it again, this will be adding the -minisetup to it?

Its just worrying me (since I'm not 100% what I'm doing - newb I know) - that if I'm syspreping twice, its going to blow all the settings I've setup for DriverPacks etc for the first 'sysprep'?

If you want to have minisetup run, then select it on the sysprep gui when OfflineSysPrep starts it. I guess you'll also choose pre-activated and pnp, then make sure you select quit as the shutdown option.

Regards,
Galapo.

Just an update to where we are:

- Ran sysprep.exe -reseal -forceshutdown on system so I could capture -bmsd drivers.
- Booted into LiveXP, used Editor to create sysprep.inf
- Ran OfflineSysPrep as per the screenshot attached.
- Error appeared.

Ideas mate?

Sidenote: Its advised NOT to run 'Pre-Activated' with VLK (Volume Liscense Keys) but OfflineSysPrep gave an error about Grace Period being over when I tried without it...

You'll get that error if one of these things are true: a) your sysprep.inf is read-only; b) you have a [SysprepMassStorage] section in sysprep.inf; or c) you have a BuildMassStorage=yes line in sysprep.inf.

Regards,
Galapo.

Currently re-running 'Sysprep' in base system, then I will load into LiveXP and run again.

I did copy my 'sysprep.inf' from a USB into C: maybe I should check if its 'Read-Only'? Could that of been it, because the Editor doesn't have ALL the options I require in mine.

Any news on that weird Activation error?

Cheers.

The thing about the grace period is a limitation of sysprepping offline.

Regards,
Galapo.

Meaning that I HAVE to use 'Activated' or just ignore the error (which I did but didn't seem OSP proceeded)?

Do you know what this will do to a VLK system? Is there a quick fix?

All seems fine with regards to 'Read-Only' - simply copied it from my USB, removed anything associated with MassStorage..

I just ignore.


Don't know. You'll have to report back so we're aware.

Regarding the sysprep error, you could possibly try another version of sysprep. I've found 6.0.4093.0 to be good even on XP systems. The WB script provides options for more than one version, but you need to have a writable systemdrive on PE, either through using FBWF with ISO method, or using BootSDI ram-loading method.

Regards,
Galapo.

Going to go out on a limb here and say its probably because I didn't (I guilty admit I just discovered it as I have never used WB before heh) the configurable options for OSP BEFORE I build the LiveXP CD.

All these options, should I be pointing them to a file structure on the LiveXP or point to files on the system now (I'm using VMWare so my system is running behind it obviously) - for example the path to Devcon, should that be relevant to LiveXP structure or my current system.

What options whould I be keeping an eye on for what I'm trying to achieve?

- I need to switch to option 'Writable' system?
- Does the Base and MassStorage pack location refer to NOW or on the system I'm imaging?
- Rebuild each run or once, or now - what is the perferred option?

Cheers

As default, the paths are relative to the location you run WinBuilder.exe from. Regarding devcon, if it's not found when the script runs, it will be automatically downloaded from Microsoft.


Personally, I always do this. I recommend you do as well. You'll get a writable system either using file-based write filter with CreateISO or selecting the BootSDI ram-loading script (will use the FiraDisk ram driver by default).


Refers to the location of PE build-time files. Don't alter anything and it'll make use of these files supllied default with LiveXP.


Leave this alone unless you have a reason to alter.

Regards,
Galapo.

Updated as follows - I'll re-build LiveXP once again and see if this works. I downloaded BASE and the .7z MassStorage, put it in a folder named DPs under my C:, did the same for devcon under C:\Devcon.



Little confused with this comment, do I actually have to be editing anything else in WB or this will all be done automatically for me.

If these settings are correct I'll go ahead and build - waiting for your reply.

Well, I'd do it like this -- that way you get some more versions to play with:



Make sure the FiraDisk script is selected, deselect CreateISO, and select BootSDI:



You get an outputted ISO image which will load an image to ram.

Prior to do this, you'll need to install ImDisk. If you're running under 64-bit, you need to allow running test-signed drivers.

Regards,
Galapo.

Having issues it seems with 'Boot SDI' - complaining about not being able to copy to [b]Z:\[b].

zCopy error - Target path Z:\ not found

Ideas? I don't even know where its getting Z:\ from... Is Boot SDI the only way to get this working?

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)?