Multiple Hardware Deployment

  • Thread starter Thread starter Paul Kent
  • Start date Start date
P

Paul Kent

Morning all....i have problem and i hope that you can find the answer for me

I have been tasked by my company to develope an XP system that can copied to
a Ghost image and then deployed over different hardware. I will use Symantec
Ghost Walker to change the SID ID's....

I was thinking of using SysPrep, but have been told that this will only let
me deploy the build onto similar hardware - is this true?? My company need a
build that is future proof, not matter what hardware it is being installed
onto.

I have heard a rumour that a corporate version of XP and registration key
can be deployed onto any hardware, does anyone know if this is true or not??

Or is there another way of doing things?? I am looking at deploying the
build over 275+ PC's

Any help will be appreciated

PKS
 
Microsoft Volume Licensing Program
http://www.microsoft.com/licensing/default.mspx

How to Acquire Microsoft Product Licenses Through Microsoft's Volume Licensing Programs
http://www.microsoft.com/licensing/howtoacquire.mspx

Microsoft Volume Licensing FAQ
http://www.microsoft.com/licensing/resources/faq.mspx

How to Prepare Images for Disk Duplication with Sysprep
http://www.microsoft.com/technet/prodtechnol/winxppro/deploy/duplication.mspx

How to Use Sysprep with Windows Product Activation or Volume License Media to Deploy Windows XP
http://support.microsoft.com/default.aspx?scid=kb;en-us;299840&Product=winxp

How to Use Sysprep: An Introduction
http://www.microsoft.com/windowsxp/pro/using/itpro/deploying/introduction.asp

Windows XP SP1a Corporate Deployment Tools
http://www.microsoft.com/windowsxp/pro/downloads/servicepacks/sp1/deploytools.asp

Summary of the limitations of the System Preparation tool
http://support.microsoft.com/default.aspx?scid=kb;en-us;830958&Product=winxp

When you clone a Windows XP installation to many computers,
the destination computers have the same SID and computer name as the source
Windows installation. Because Windows XP networks use each computer's
SID and computer name to uniquely identify the computer on the network, you must
change the SID and computer name on each destination (client) computer after cloning.

Visit:
http://service1.symantec.com/SUPPOR...=2003 for windows 2000/nt/me/98&osv=&osv_lvl=

--
Carey Frisch
Microsoft MVP
Windows XP - Shell/User

Be Smart! Protect your PC!
http://www.microsoft.com/security/protect/

--------------------------------------------------------------------------------------------


| Morning all....i have problem and i hope that you can find the answer for me
|
| I have been tasked by my company to develope an XP system that can copied to
| a Ghost image and then deployed over different hardware. I will use Symantec
| Ghost Walker to change the SID ID's....
|
| I was thinking of using SysPrep, but have been told that this will only let
| me deploy the build onto similar hardware - is this true?? My company need a
| build that is future proof, not matter what hardware it is being installed
| onto.
|
| I have heard a rumour that a corporate version of XP and registration key
| can be deployed onto any hardware, does anyone know if this is true or not??
|
| Or is there another way of doing things?? I am looking at deploying the
| build over 275+ PC's
|
| Any help will be appreciated
|
| PKS
 
Thanks for that....I'll take a look at all the links. I need to check what
license is being used currently and hopefully its a Volume License

Thanks again

PSK
 
Oh, am i right in assuming that a Volume License can be ghosted and
installed onto any hardware and that XP won't crash??
 
Hello Paul,
You have to ensure that the machine types are the same for hardware or you
will have issues or lose functionality, so you need an image for each
machine type of hardware that you have.
You have to add-in drivers that are not supported out of the box by devices
that are in the systems. Look in the deploy.cab for the help file that
talks about adding in drivers.
There is not one answer for all hardware.
Microsoft only supports Sysprep to change the SID. Sysprep will help with
some of the hardware detection issues. You still have to worry about
adding in drivers that are not included and you need to create images for
each machine type that you have.
Thanks,
Darrell Gorter[MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights
--------------------
From: "Paul Kent" <[email protected]>
Newsgroups: microsoft.public.windowsxp.setup_deployment
References: <xIPHc.471$%[email protected]>
Click to expand...
 
Back
Top