If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Office 2003 deployment w/o volume key
Hi all,
I want to do a fully automated Office 2003 deployment, only trouble is that I have the OEM Version of Office 2003 instead of the Select or Open with a volumekey, and so have to use a unique key for every computer. For Windows XP (same issue) this is not much trouble, since http://www.microsoft.com/technet/pro...on130121120120 gives me generic keys to do the hands-off installation of the OS and scripts to do the activation, or I can use the UDP-Files to set the unique key for each workstation and use "AutoActivate = Yes" in the unattend.txt. For the Office installation I found no such things. I probably could write some script to insert a unique key depending on the computername into the setup.ini (or simply create one setup.ini per computer) but I still have to activate the copy. Does someone know of a method to do this? Thanks, Uli |
#3
|
|||
|
|||
Office 2003 deployment w/o volume key
vishal subramaniam (msft) wrote:
RESOLUTION: ============ Creating a transform by using the Custom Installation Wizard Thanks, but my problem is not how to do the deployment (I know the setup.ini and MST methods), my problems are 1) how can I provide a unique product-ID for each computer 2) how can I automate the Office 2003 activation across the Internet. I think, 1) is not a big deal since I can extract the correct key for the computer that is currently installed and put it (PIDKEY=[string]) into the setup.ini by some VBS-Magic. For 2) I found no solution. Windows XP activation can be automated by using WMI (win32_WindowsProductActivation) but as far as I know there is no corresponding method for Office 2003. Uli |
Thread Tools | |
Display Modes | |
|
|