/build/static/layout/Breadcrumb_cap_w.png

Creating a New Windows XP Image

Guys , Im creating a new Windows XP image for the company Im now working for. Everything is going great , but when I roll the image out on to new pcs , Windows XP keeps asking me to activate it. How can I stop this for happening ?

0 Comments   [ + ] Show comments

Answers (13)

Posted by: TheFergie101 15 years ago
Blue Belt
0
Ok , thats what I thought. The company I work for now have no pc image at all - they just boot up their Dell machines with XP on it and let the users fire away. This is bad as 1 , there is so much crap with the Dell out of the box pcs , plus I now need to be able to build pcs fast. I had used Ghost and I was able to build/roll out 50-60 pcs a day. From a tech support point of view , I could always wipe a pc back with ghost if there were lots of issues. I want to create a brand new base Windows Xp image with the lastet patches on it as a base model to start with it. I did a test build , but I used the key on the side of the pc - it activated fine , but when i imaged it to another pc , it asked me to reactivate it. In my old company , the image we used (I didnt make this image) when I build a pc , it would boot up ,install the drivers , reboot , add its self to the domain and then away you went - it didnt require to be activated. I think this was because it was build using a Windows XP select agreement disc and Volume licence. I also had used ghostwalker to rename the pc image and refresh the sid before first boot.
Posted by: TheFergie101 15 years ago
Blue Belt
0
Another question !

Before I start , I am better off using a Select Agreement Windows XP install disc with the volume licence ?
All I have at the moment , in the Windows XP install disc that came in the DELL PC Hardware with the OEM key posted on the side of the box ?
Posted by: DeployTech 15 years ago
Orange Senior Belt
0
VL and Select codes need different media from OEM discs.
Posted by: smason 15 years ago
Orange Belt
0
If you're using Dells, and used the Dell CD to create the image, it shouldn't behave that way.
I do this regularly and it never asks for a key, or for activation.

How are you creating this image?
Posted by: bacanter01 15 years ago
Yellow Belt
0
smason is correct, or at least in my experience I've never had any issues. I've deployed over 200 machines and used the same disc to create all of my images. I think the older Dell discs gave me problems but those were from home machines (Dimension Desktops) about 6 or 8 years ago. All of our machines are Optiplex or Latitudes and they all come with the "Magic Dell Key" hard coded into the disc.

Initially I used sysprep but when I found this out I quit messing with, if Dell sends it to me with that key then there isn't too much that MS can say. Or at least they can't say much if you bought all of your machines with an OS.
Posted by: DeployTech 15 years ago
Orange Senior Belt
0
With the correct key type, you don't get asked.

A question for smason and bacanter01 -

If you are deploying to a mixed environment of, say, HP and Dell, how do you feel about using the Dell Key in that scenario?
Just wondering.
Posted by: jcarri06 15 years ago
Senior Purple Belt
0
If you're creating an image you want deployed across multiple systems, even if they're the same vendor, you need a volume license key. Otherwise, you're using a single OEM license for multiple systems, which I'm not entirely sure is even within the license agreement or not, which means you may have to enter each individual key per deployment you do to remain in compliance (I'm sure this is documented somewhere, don't quote me).

Also, using an OEM license you run the risk of the CD you're using not taking the key you're providing (this has happened to me...and it's annoying) so you're making your life difficult in the long run. Get your volume key/cd, create your image, and you'll never run into this scenario.
Posted by: smason 15 years ago
Orange Belt
0
We're strictly Dell here, but if we weren't I'd definitely not use a Dell image on an HP.
The Dell OEM XP CD will only boot on a Dell computer, wont' even work in a VM on a Dell computer, as it needs to see a Dell BIOS before it'll run.
There is a key with the Dell CD but it's built-in to the install, you don't actually get a chance to enter it.
Posted by: DeployTech 15 years ago
Orange Senior Belt
0
Are you using a Volume License?
Posted by: DeployTech 15 years ago
Orange Senior Belt
0
In your Unattend.txt try

[Unattended]
AutoActivate = Yes
Posted by: DeployTech 15 years ago
Orange Senior Belt
0
Have a look at ref.chm in Deploy.cab in the Support folder on your Windows XP CD.

That has all of the unattended keys, and descriptions of what they do.
Posted by: TheFergie101 15 years ago
Blue Belt
0
DelpoyTech

This is something that does confuse me. Whats a volume licence ? I know there are differences with product keys etc
Posted by: DeployTech 15 years ago
Orange Senior Belt
0
Righto,

Volume licensing is a single key for all of the Windows Installations for the business.
When you buy PCs and you have a WIndows sticker on them with a 25 character code, those are OEM (the licenses cannot be transferred to different hardware)
When you buy a retail box for a windows OS, that is Windows Retail and the license can be transferred once (I think).

If your company has a "Select" or "Enterprise" agreement, that is similar to the Volume License where you jus thave one code.

Are you manually entering a different license for each PC, or do you have a single code to enter?
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ