Multiple Windows Activations

R

Ray

I'm in a small school. We purchased about 50 computers for the
school. We custom installed one of each type of configuration we were
implementing. We then repackaged the machines using sysprep and
created a ghost imageof each for distribution.

This works fine initially - we load the image, customize the machine
name, etc...Then we have to activate Windows... This all went at
planned - however - being in a school, things get trashed from time to
time - so we quickly wipe and reload the machine with the appropriate
image we created. The problem is - as I understand it - we're only
allowed to activate a particular Windows Product Key a certain number
of times...

What is the correct method to accomplish this many times....

Thanks
Ray
 
D

Don Phillipson

I'm in a small school. We purchased about 50 computers for the
school. We custom installed one of each type of configuration we were
implementing. We then repackaged the machines using sysprep and
created a ghost imageof each for distribution.

This works fine initially - we load the image, customize the machine
name, etc...Then we have to activate Windows... This all went at
planned - however - being in a school, things get trashed from time to
time - so we quickly wipe and reload the machine with the appropriate
image we created. The problem is - as I understand it - we're only
allowed to activate a particular Windows Product Key a certain number
of times...

What is the correct method to accomplish this many times....

The vendor of your MS Windows licence should be able to tell you.
 
R

Ray

So ... You're saying go back to Dell and ask them? We don't have an
actual MS License pack for windows... We do for Office.... because it
was purchased separately...
 
J

Jim

Ray said:
So ... You're saying go back to Dell and ask them? We don't have an
actual MS License pack for windows... We do for Office.... because it
was purchased separately...

Yes, go back to Dell. In fact, go back to Dell for solutions to whatever
problems you might have.

Jim
 
Z

Zaphod Beeblebrox

Ray said:
I'm in a small school. We purchased about 50 computers for the
school. We custom installed one of each type of configuration we
were
implementing. We then repackaged the machines using sysprep and
created a ghost imageof each for distribution.

This works fine initially - we load the image, customize the
machine
name, etc...Then we have to activate Windows... This all went at
planned - however - being in a school, things get trashed from time
to
time - so we quickly wipe and reload the machine with the
appropriate
image we created. The problem is - as I understand it - we're only
allowed to activate a particular Windows Product Key a certain
number
of times...

What is the correct method to accomplish this many times....

Although there is no problem reactivating a key as many times as
needed on the same PC (although you may have to endure the
inconvenience of calling up MS to manually activate), since it appears
from later posts that you are working with Dell computers, when you
sysprep the machine you can preserve the OEM activation per
http://technet.microsoft.com/en-us/library/bb457078(TechNet.10).aspx
inslead of using the code on the sticker. Should save time and
aggravation.

--
Zaphod

Arthur: All my life I've had this strange feeling that there's
something big and sinister going on in the world.
Slartibartfast: No, that's perfectly normal paranoia. Everyone in the
universe gets that.
 
W

William R. Walsh

Hi!
This works fine initially - we load the image, customize the machine
name, etc...Then we have to activate Windows... This all went at
planned - however - being in a school, things get trashed from time to
time

Something that might help is to make the user accounts for your students
restricted rights ("non-administrator") accounts. In that way, the only
thing they could really trash is their account. Set a strong password for
the administrator, and configure the systems so they try to start up from
the hard drive first. Consider setting a password to access the system setup
program.

These things aren't bulletproof, but they'll deter those who don't want to
go to a lot of effort and run a higher risk of discovery to cause problems.
For example, it's not hard to sneak a startup CD into the computer room to
reset an administrator password. Few people would likely notice. It's also
not hard to open the cover of a machine to attempt to clear the system setup
password, but it is more likely to be noticed and called into question.
(Many of Dell's system cases have a place to put a padlock if need be.
Removing that is bound to cause all kinds of bells and sirens to go off if
anyone else is around.)
What is the correct method to accomplish this many times....

I'm surprised that you do have to activate Windows on these systems, if
you've installed Windows from the Dell supplied media. Dell typically ships
their copies of Windows in a pre-activated state so long as you're using the
appropriate version of Windows for your Dell system. Are you sure that you
used the correct installation media when setting these up?

That said, I have computers that are nothing more than "testing grounds" for
software projects. Some of them are Dell systems, and of the ones that
shipped with Windows XP in some release, I have not run into this problem.
However, I do have specific disk images to restore for each unique system,
as they are all of differing models, ages, hardware design and processor
type. I don't think one image would work in that case. These systems haven't
prompted for activation after being restored, but I did set each one up with
its factory-provided Windows XP installation disc.

I did find that Microsoft restricts at least server product keys, as I once
had a hard time getting a Windows Server Enterprise Edition "test bed"
system up and running. I kept messing it up from inexperience with the
platform and doing the wrong/stupid things. I had to reinstall several times
from scratch over a period of a few hours. As you can imagine, activation
failed because of this, and I had to telephone Microsoft. Eventually, they
did have to give me a new product key. I don't know how closely this would
relate to a desktop version of Windows, but it does suggest that after some
point a product key is "no good" and a new one must be issued when you
telephone.

Later on, when I went to reload Windows Server 2003 on that system (about
three and 1/2 years later) I found that the original, bundled CD key worked
once again for the purpose of activating Windows Server. I had written down
the one I was given over the phone, but I couldn't find it and grew
impatient looking for it. So I said "what the heck, no harm in trying" and
was delighted to find it worked.

And since it's Microsoft you call to activate, I don't think you'll get far
by calling Dell with this question. Dell is obligated to handle bundled
Windows software support issues, but product activation *always* goes
directly to Microsoft.

William
 
R

Ray

Thank you -

The first batch of computer are Optiplex 320 systems. I originally
uncased the computer - plugged it in, and immediately created an image
even before the first booting. I then booted it up, installed the
nexessary software, then sysprep'd it for re-distribution to the other
computers... Maybe I missed a step somewhere ... after all, this is
the first time I've actually done this. I will review my steps again
and do some experimenting to see what I can figure out.

One of the reasons for the reimage has to do with the introduction of
spyware and the like. Even though these are primarily student
computers, the teachers will sometimes log in and check their email on
them instead of on their laptops. I think that's where the majority of
our problems come from....

Thanks again for your feedback... I'm looking for all I can get..

I will say that I have semi-successfully implemented SteadyState in
our computer lab. I say Semi because there are many "Gotchas"
involved. But - with the disk protection enabled... a simple reboot
and we're back to our previous "approved" state. But that's a
discussion for a different group...

Thanks Again...
Ray
 
Z

Zaphod Beeblebrox

"William R. Walsh"
Hi!


Something that might help is to make the user accounts for your
students
restricted rights ("non-administrator") accounts. In that way, the
only
thing they could really trash is their account. Set a strong
password for
the administrator, and configure the systems so they try to start up
from
the hard drive first. Consider setting a password to access the
system setup
program.

These things aren't bulletproof, but they'll deter those who don't
want to
go to a lot of effort and run a higher risk of discovery to cause
problems.
For example, it's not hard to sneak a startup CD into the computer
room to
reset an administrator password. Few people would likely notice.
It's also
not hard to open the cover of a machine to attempt to clear the
system setup
password, but it is more likely to be noticed and called into
question.
(Many of Dell's system cases have a place to put a padlock if need
be.
Removing that is bound to cause all kinds of bells and sirens to go
off if
anyone else is around.)

Another approach would be to use one of the products available that
can reset the system back to a defined state so that you never have to
reimage. In fact, I think MS has one called Steady State, and I think
it is free (although I haven't ever used it so I can't say for sure).
I'm surprised that you do have to activate Windows on these systems,
if
you've installed Windows from the Dell supplied media. Dell
typically ships
their copies of Windows in a pre-activated state so long as you're
using the
appropriate version of Windows for your Dell system. Are you sure
that you
used the correct installation media when setting these up?

The difference here is that the OP is using sysprep and pulling an
image to deploy. Among other things, sysprep resets activation so
unless you supply the "magic key" that tells Dell (and other large OEM
systems) to validate against a BIOS signature, that tis, you plug in
the key from the sticker on the case, you have to validate.

And since it's Microsoft you call to activate, I don't think you'll
get far
by calling Dell with this question. Dell is obligated to handle
bundled
Windows software support issues, but product activation *always*
goes
directly to Microsoft.
Spot on. This is all MS, Dell really isn't a part of the picture.
 
K

Klaus Jorgensen

Zaphod Beeblebrox explained on 15-04-2009 :
The difference here is that the OP is using sysprep and pulling an image to
deploy. Among other things, sysprep resets activation so unless you supply
the "magic key" that tells Dell (and other large OEM systems) to validate
against a BIOS signature, that tis, you plug in the key from the sticker on
the case, you have to validate.

The COA on the sticker is never used with pre-activated installations.
The product key from OEM installation media comes from the
i386\winnt.sif file, and that is what should be used in sysprep.inf.

What MUST be included for the BIOS signature recognition to function
correctly, is the four oembios.* files from the original installation
media, but if the image is built from the original installation, these
should already be there.
 
Z

Zaphod Beeblebrox

Klaus Jorgensen said:
Zaphod Beeblebrox explained on 15-04-2009 :

The COA on the sticker is never used with pre-activated
installations.

I wasn't saying that the COA on the sticker was used with preactivated
installations. Rather, I was saying that if you don't know about OEM
preactivation and use sysprep, and then use the COA key, you'll force
it to go through reactivation. In that case, a call to MS will be
required.
The product key from OEM installation media comes from the
i386\winnt.sif file, and that is what should be used in sysprep.inf.

I had forgotten about that, but then it's been a while. In another
post I did point the OP to an MS technet article that has keys that
can be used as well (though I've not used them personally).
What MUST be included for the BIOS signature recognition to function
correctly, is the four oembios.* files from the original
installation media, but if the image is built from the original
installation, these should already be there.
Agreed. From the OP's description of the process he's followed, they
should be there.

--
Zaphod

Arthur Dent, speaking to Trillian about Zaphod:
"So, two heads is what does it for a girl?"
"...Anything else he's got two of?"
 
W

William R. Walsh

Hi!
Among other things, sysprep resets activation so
unless you supply the "magic key" that tells Dell (and other large
OEM systems) to validate against a BIOS signature, that tis,
you plug in the key from the sticker on the case, you have to
validate.

I did not know that. I have not used Sysprep very much and certainly
not very recently. I suspect that a keyfinder could be useful, but one
should keep firmly in mind any licensing issues and such. I've never
been curious enough to try one. Nor have I cared that much.
Spot on.  This is all MS, Dell really isn't a part of the picture.

Yes, and Dell support should just say that. However, knowing them as I
do, I suspect the path to finding this out would be long and have some
interesting turns or multiple calls. :)

William
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top