Enter License key for RIS installs

[Mark]

I try to enter the license key for RIS installs for XP in the following
location:

ristndrd.sif file
[UserData]
ProductKey = 12345-12345-12345-12345-12345

This doesn't work, I have seen places that say to have ProductID there and I
have tried it both with and without quotes. I am still prompted when RISing
a machine to enter the license key. How should this be put in?

Thanks.
Mark

 

[David Hancock]

Mark,

You are correct in placing the ProductKey under [UserData]...however, in order to use the answer file
you created you have to associate it to one of your RIS images.Give this a shot

Go to Active Directory Users and Computers
Expand Domain Controllers
Right Click Your RIS Server and go to Properties.
Click the Remote Install tab and then click the Advanced Settings Button.
Then click the Images tab and press Add button.
Select the default (Associate a new answer file) press Next and select the "An
Alternate Location" radio button. and press Next.
Enter the path or browse to the .sif (answer) file you want to use and press Next.
Then select the images that you want to associate this answer file with.
Complete the wizard.

Try to RIS a box.

*****************************************************************************

David Hancock [MSFT]

Microsoft Server Setup Team


Search our Knowledge Base at http://support.microsoft.com/directory

Visit the Windows 2000 Homepage at

http://www.microsoft.com/windows2000/default.asp

See the Windows NT Homepage at http://www.microsoft.com/ntserver/



NOTE: Please reply to the newsgroup and not directly to me. This allows

others to add to and benefit from these threads and also helps to ensure a

more timely response. Thank you!



This posting is provided "AS IS" without warranty either expressed or

implied, including, but not limited to, the implied warranties of

merchantability or fitness for a particular purpose.

The views and opinions expressed in this newsgroup posting are mine and do

not necessarily express or reflect the views and / or opinions of Microsoft.

******************************************************************************

 

[jmd]

Hello.
I have the same problem (W2003 server and WXP clients).
The solution I use is to put the settings (Product Key, Video resolution &
Regional) in the generated riprep.sif of the ris image.
But I must do this after each image generation !!!
Before (W2000 server and 2000 clients) all settings was in the cd-image
ristnrd.sif and all was ok.

Is there anything I must look for ?
Each time I modify the ristnrd.sif MUST I reaffect it to the riprep images ?

Thank you.
jean-marie

Mark,

You are correct in placing the ProductKey under [UserData]...however, in order to use the answer file
you created you have to associate it to one of your RIS images.Give this a shot

Go to Active Directory Users and Computers
Expand Domain Controllers
Right Click Your RIS Server and go to Properties.
Click the Remote Install tab and then click the Advanced Settings Button.
Then click the Images tab and press Add button.
Select the default (Associate a new answer file) press Next and select the "An
Alternate Location" radio button. and press Next.
Enter the path or browse to the .sif (answer) file you want to use and press Next.
Then select the images that you want to associate this answer file with.
Complete the wizard.

Try to RIS a box.

****************************************************************************
*

David Hancock [MSFT]

Microsoft Server Setup Team


Search our Knowledge Base at http://support.microsoft.com/directory

Visit the Windows 2000 Homepage at

http://www.microsoft.com/windows2000/default.asp

See the Windows NT Homepage at http://www.microsoft.com/ntserver/



NOTE: Please reply to the newsgroup and not directly to me. This allows

others to add to and benefit from these threads and also helps to ensure a

more timely response. Thank you!



This posting is provided "AS IS" without warranty either expressed or

implied, including, but not limited to, the implied warranties of

merchantability or fitness for a particular purpose.

The views and opinions expressed in this newsgroup posting are mine and do

not necessarily express or reflect the views and / or opinions of Microsoft.****************************************************************************
**

 

[David Hancock]

Hello Jean-Marie

The answer I've been given here is No, you shouldn't need to reassociate the ristndrd.sif after
modification.
*****************************************************************************

David Hancock [MSFT]

Microsoft Server Setup Team



Search our Knowledge Base at http://support.microsoft.com/directory

Visit the Windows 2000 Homepage at

http://www.microsoft.com/windows2000/default.asp

See the Windows NT Homepage at http://www.microsoft.com/ntserver/



NOTE: Please reply to the newsgroup and not directly to me. This allows

others to add to and benefit from these threads and also helps to ensure a

more timely response. Thank you!



This posting is provided "AS IS" without warranty either expressed or

implied, including, but not limited to, the implied warranties of

merchantability or fitness for a particular purpose.

The views and opinions expressed in this newsgroup posting are mine and do

not necessarily express or reflect the views and / or opinions of Microsoft.

******************************************************************************

 

[Mark]

I am just using the default answer file so it should be used without having
to do this, correct? I know we have had to modify this file before to add
OEM drivers. Should I have quotes around the product key and should the
product key have dashes in it?

Thanks.
Mark

 

[jmd]

ok.
Thank you very much.

Hello Jean-Marie

The answer I've been given here is No, you shouldn't need to reassociate the ristndrd.sif after
modification.
****************************************************************************
*

David Hancock [MSFT]

Microsoft Server Setup Team



Search our Knowledge Base at http://support.microsoft.com/directory

Visit the Windows 2000 Homepage at

http://www.microsoft.com/windows2000/default.asp

See the Windows NT Homepage at http://www.microsoft.com/ntserver/



NOTE: Please reply to the newsgroup and not directly to me. This allows

others to add to and benefit from these threads and also helps to ensure a

more timely response. Thank you!



This posting is provided "AS IS" without warranty either expressed or

implied, including, but not limited to, the implied warranties of

merchantability or fitness for a particular purpose.

The views and opinions expressed in this newsgroup posting are mine and do

not necessarily express or reflect the views and / or opinions of Microsoft.****************************************************************************
**

 

[David Hancock]

Hi Mark,

Here is some more info that I found regarding ProductID/ProductKey from KB article 313040.

When creating an unattended answer file, the version of Setup Manager that is included with Windows
XP may include the following line in the [UserData] section of the answer file:
ProductID=XXXXX-XXXXX-XXXXX-XXXXX-XXXXX

While the ProductID value is still acceptable in answer files for Windows XP and Windows Server 2003,
the preferred keyword is now ProductKey .
ProductKey=XXXXX-XXXXX-XXXXX-XXXXX-XXXXX

The version of Setup Manager that is included with Windows Server 2003 has been revised to use the
value ProductKey instead of ProductID

It appears as if you don't need quotes, but do need the dashes.

*****************************************************************************

David Hancock [MSFT]

Microsoft Server Setup Team



Search our Knowledge Base at http://support.microsoft.com/directory

Visit the Windows 2000 Homepage at

http://www.microsoft.com/windows2000/default.asp

See the Windows NT Homepage at http://www.microsoft.com/ntserver/



NOTE: Please reply to the newsgroup and not directly to me. This allows

others to add to and benefit from these threads and also helps to ensure a

more timely response. Thank you!



This posting is provided "AS IS" without warranty either expressed or

implied, including, but not limited to, the implied warranties of

merchantability or fitness for a particular purpose.

The views and opinions expressed in this newsgroup posting are mine and do

not necessarily express or reflect the views and / or opinions of Microsoft.

******************************************************************************