Ghosting Windows XP
#Steve
Anything I should read up on, take not off, for the roll out of XP ? any
differences to Win2k ?
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.419 / Virus Database: 235 - Release Date: 13/11/2002
Covey
"#Steve" <rem0v3.pu...@btopenworld.com> wrote in message
news:arj7vo$77c$1...@venus.btinternet.com...
> Just stating the migration Win2k to Windows XP.
>
> Anything I should read up on, take not off, for the roll out of XP ? any
> differences to Win2k ?
If you are rolling XP out to individual PC's there are no major problems we
have come across, although the ghost system needs almost identical PC's to
work effectively.
If you are running W2K server, then it is probably easier to use the Remote
Install facility, which will cope with different motherboard combinations,
because it does a proper "install" rather than copies a fixed image. If
however you have say one suite of PC's running Pll and one running P4 then
you will probably have to make two different images to cope with the
different generation motherboards.
Covey.
MrEdd
"Covey" <> wrote in message ...
>
> "#Steve" <> wrote in message
> ...
> > Just stating the migration Win2k to Windows XP.
> >
> > Anything I should read up on, take not off, for the roll out of XP ? any
> > differences to Win2k ?
>
> If you are rolling XP out to individual PC's there are no major problems
we
> have come across, although the ghost system needs almost identical PC's to
> work effectively.
>
> If you are running W2K server, then it is probably easier to use the
Remote
> Install facility, which will cope with different motherboard combinations,
> because it does a proper "install" rather than copies a fixed image. If
> however you have say one suite of PC's running Pll and one running P4 then
> you will probably have to make two different images to cope with the
> different generation motherboards.
>
> Covey.
>
very close compatible hardware for it to work properly.
Edd
Steve
cheers
Steve
"MrEdd" <ed...@NOJUNKmredd.enta.net> wrote in message
news:3ddeb70e.0@entanet...
MrEdd
"Steve" <> wrote in message ...
> Have you tried a sysprep.inf file with a [BuildMassStorageDevices] section
?
>
>
Edd
Steve
which seems to cover it. The section name is slightly different from what I
remembered!
see also http://support.microsoft.com/default.aspx?scid=KB;en-us;q303786
all details are on the Xp Pro CD (under Doc I think..)
cheers
Steve
"MrEdd" <ed...@NOJUNKmredd.enta.net> wrote in message
news:3de01f80.0@entanet...
Richard Hindley
news:arj7vo$77c$1...@venus.btinternet.com...
>
> Anything I should read up on, take not off, for the roll out of XP ? any
> differences to Win2k ?
You'll need to use Sysprep. A few tips which I discovered in practice:
1. You need to use separate Ghost images for ACPI and older non-ACPI
hardware. If you create the image on an ACPI machine and Ghost onto a
non-ACPI machine, it will crash during boot. Doing it the other way round
will work, but you'll lose power management functionality.
2. If you are Ghosting the same base image onto multiple hardware types, you
need to include a [SysprepMassStorage] section to ensure that you include
correct IDE controller for each hardware type.
3. Try to avoid using the PNP switch - you probably won't need to use it
even if you are Ghosting onto different hardware types. I recommend you
avoid it, because it can cause issues with sound drivers.
4. If you are Ghosting onto hard disks of different sizes, include
ExtendOemPartition=1 in the [Unattended] section of Syspre.inf. This will
ensure that the installation partition is auomatically extended to fill the
whole disk.
5. You should definitely Disable Desktop Cleanup before running Sysprep, as
per Q307543. If you don't, there seems to be an intermittant bug which will
cause the whole process to fail.
Richard