RIS

[George K.]

Will be deploying about 50 copies of XP Pro. Using 2003 Std as Domain
controller for RIS. I have about 50 individual OEM copies of the xp
software each with unique keys.

How do I use RIS to maintain unique keys on 50 different machines and then
go about Activating with MS?

Also, what if I must redploy a messed up users desktop with RIS and I have
already activated a particular copy, what then?

Any help is greatly appreciated.

George

 

[Herb Martin]

Will be deploying about 50 copies of XP Pro. Using 2003 Std as Domain
controller for RIS. I have about 50 individual OEM copies of the xp
software each with unique keys.

How do I use RIS to maintain unique keys on 50 different machines and then
go about Activating with MS?

This isn't really (or fully) an AD question but we always try to help
if we can anyway. There might be a licensing group around somewhere
that could help better.

BUT here is what I think you will find: You will need to use a Bulk
License Key (obtainable from your software vendor) instead of individual
Retail keys to make this seamless.

You might be able to give out a key to each installer, and enter it at
installation time but I have not tested this. It is, in any case, going to
require more interaction.

Also, what if I must redploy a messed up users desktop with RIS and I have
already activated a particular copy, what then?

Redeploying a "messed up desktop" should seldom require
installing the OS again except for REPAIR INSTALLS which
should not ask for the key.

You must do the repair install from regular source (CD or DISK)
rather than through RIS.