Licensing Issue

[Guest]

I have a client who has a large operation with 4 different departments. Each
workstation has a large amount of Windows software that has to be configured.
In order to save time when implementing a new workstation, we mirrored a new
install recently at the point of software install/configuration that was
applicable to each department. The theory was that everytime we install a
new box we would save time and cash by having a new hard drive ready to
install with the basic software and configuration.

I delivered a new box with a new copy of OEM WIndows XP Pro. Upon placing
the mirrored drive into the box and booting it required Activation. My
expectation was that the system would say this copy has been activated
already and ask for the new product key. That didn't happen, it activated
without any problem.

A couple of days went by and now the workstation that has the original copy
of the OEM Win XP Pro cannot access the domain controllers.

I think I can legally license the new CPU by doing a repair install so that
I can input the new copy of WinXPPro key number but I was wondering if the
inability of the original CPU to access the domain controller is caused by
the second newer workstation having the same copy of WinXP/Product key on the
network.

 

[Shenan Stanley]

I have a client who has a large operation with 4 different
departments. Each workstation has a large amount of Windows software
that has to be configured. In order to save time when implementing a
new workstation, we mirrored a new install recently at the point of
software install/configuration that was applicable to each
department. The theory was that everytime we install a new box we
would save time and cash by having a new hard drive ready to install
with the basic software and configuration.

I delivered a new box with a new copy of OEM WIndows XP Pro. Upon
placing the mirrored drive into the box and booting it required
Activation. My expectation was that the system would say this copy
has been activated already and ask for the new product key. That
didn't happen, it activated without any problem.

A couple of days went by and now the workstation that has the
original copy of the OEM Win XP Pro cannot access the domain
controllers.

I think I can legally license the new CPU by doing a repair install
so that I can input the new copy of WinXPPro key number but I was
wondering if the inability of the original CPU to access the domain
controller is caused by the second newer workstation having the same
copy of WinXP/Product key on the network.

I recommend projects like:

http://unattended.sourceforge.net/
and/or
http://unattended.msfn.org/
and/or
http://www.gc.peachnet.edu/www/wbeck/W2KXP.htm#Master

I also recommend (since you used the word "large") a volume licensing
agreement.
http://www.microsoft.com/licensing/resources/downloads/default.mspx

As for your question, it COULD be, but shouldn't be that they have the SAME
SID, as you said nothing about changing that or the machine name.

 

[Guest]

I recommend projects like:

http://unattended.sourceforge.net/
and/or
http://unattended.msfn.org/
and/or
http://www.gc.peachnet.edu/www/wbeck/W2KXP.htm#Master

I also recommend (since you used the word "large") a volume licensing
agreement.
http://www.microsoft.com/licensing/resources/downloads/default.mspx

As for your question, it COULD be, but shouldn't be that they have the SAME
SID, as you said nothing about changing that or the machine name.

--
<- Shenan ->
--
The information is provided "as is", it is suggested you research for
yourself before you take any advice - you are the one ultimately
responsible for your actions/problems/solutions. Know what you are
getting into before you jump in with both feet.

System ID (computer name/domain and IP addresses) was changed to a different
name reflective of user/department. We use the OEMs only on new CPUs added.
Company does use licensing and has reserved it for upgrades thus far when
applicable. The vast amount of third party insurance software with its
limitations has prevented some departments/users from making jump to XP.

I am checking the links you provided, thanks.

 

[Michael Stevens]

I have a client who has a large operation with 4 different
departments. Each workstation has a large amount of Windows software
that has to be configured. In order to save time when implementing a
new workstation, we mirrored a new install recently at the point of
software install/configuration that was applicable to each
department. The theory was that everytime we install a new box we
would save time and cash by having a new hard drive ready to install
with the basic software and configuration.

I delivered a new box with a new copy of OEM WIndows XP Pro. Upon
placing the mirrored drive into the box and booting it required
Activation. My expectation was that the system would say this copy
has been activated already and ask for the new product key. That
didn't happen, it activated without any problem.

A couple of days went by and now the workstation that has the
original copy of the OEM Win XP Pro cannot access the domain
controllers.

I think I can legally license the new CPU by doing a repair install
so that I can input the new copy of WinXPPro key number but I was
wondering if the inability of the original CPU to access the domain
controller is caused by the second newer workstation having the same
copy of WinXP/Product key on the network.

Click on the link below, or copy and paste the link into the address box
if using the web based newsgroup.
I need to change my XP Product KEY #18
http://michaelstevenstech.com/xpfaq.html#18
--
Michael Stevens MS-MVP XP
(e-mail address removed)
http://michaelstevenstech.com
For a better newsgroup experience. Setup a newsreader.
http://michaelstevenstech.com/outlookexpressnewreader.htm

 

[Guest]

Click on the link below, or copy and paste the link into the address box
if using the web based newsgroup.
I need to change my XP Product KEY #18
http://michaelstevenstech.com/xpfaq.html#18
--
Michael Stevens MS-MVP XP
(e-mail address removed)
http://michaelstevenstech.com
For a better newsgroup experience. Setup a newsreader.
http://michaelstevenstech.com/outlookexpressnewreader.htm



Thanks Michael, very helpful info.

 

[Tim H]

I have a client who has a large operation with 4 different departments. Each
workstation has a large amount of Windows software that has to be configured.
In order to save time when implementing a new workstation, we mirrored a new
install recently at the point of software install/configuration that was
applicable to each department. The theory was that everytime we install a
new box we would save time and cash by having a new hard drive ready to
install with the basic software and configuration.

I delivered a new box with a new copy of OEM WIndows XP Pro. Upon placing
the mirrored drive into the box and booting it required Activation. My
expectation was that the system would say this copy has been activated
already and ask for the new product key. That didn't happen, it activated
without any problem.

A couple of days went by and now the workstation that has the original copy
of the OEM Win XP Pro cannot access the domain controllers.

I think I can legally license the new CPU by doing a repair install so that
I can input the new copy of WinXPPro key number but I was wondering if the
inability of the original CPU to access the domain controller is caused by
the second newer workstation having the same copy of WinXP/Product key on the
network.

I'm not sure if the duplicate key is the cause of the problem you
reference... but, in the future, you may want to use a utility like
SYSPREP (available from MS for free if I'm not mistaken). This is what
we use in our organization when building images as you describe. It
removes the product key (or will replace it with a volume license key),
resets the install and can be set up to prompt for such things as
machine name, automatically join domain, etc. on first boot. A real
time-saver.