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
|
|||
|
|||
Microsoft Office Standand 2003 AND Invalid Product Key
We have an enterprise version of Microsoft Office Professional 2003 and
Microsoft Office Standard 2003. Our company moved from having all Professional to x number of pcs with standard. Originally Office Professional was deployed to all machines via Zenworks with a MST that included the licensing, product key, etc. This has been working for the past few years fine. We now have two scenarios. The first is causing much problems with the lift off of Office Professional from the machine (which is working fine), but then the distribution to the machine of Office Standard (which again is coming from a source on the network). It appears from digging that the machines running the Windows Installer 3.1 are receiving Invalid Product Key errors. On other machines the installation works fine. They are all Windows XP SP2 machines (some of the same image, but different software on them). If I run the MSI by itself, it fails with a Invalid Product Key error. If I do a run command with the /i ... /t.... PIDKEY="XXXX" /qb+ it runs fine. This is the same product key that we built in ORKTOOLs with the Custom Installation Wizard. Nothing different from what was accomplished with Professional. We need ideas? Thanks. |
#2
|
|||
|
|||
Microsoft Office Standand 2003 AND Invalid Product Key
We found the problem for any other with this situation. Apparently our
Enterprise Standard 2003 edition was a download with an MSI, setup.exe and a bunch of cab files. If I look at the source files, we are missing the program files or PFILES and all the files which are still compressed within the CAB files. We ended up running the msiexec /a %sourcepath%\std11.msi and expanded to our source directory. Utilized the MST file and now everything works perfectly. Apparently when the PIDKEY would not take when the files we compressed. This was NOT a student or trial install, but a full installation. "SkyEyes" wrote: We have an enterprise version of Microsoft Office Professional 2003 and Microsoft Office Standard 2003. Our company moved from having all Professional to x number of pcs with standard. Originally Office Professional was deployed to all machines via Zenworks with a MST that included the licensing, product key, etc. This has been working for the past few years fine. We now have two scenarios. The first is causing much problems with the lift off of Office Professional from the machine (which is working fine), but then the distribution to the machine of Office Standard (which again is coming from a source on the network). It appears from digging that the machines running the Windows Installer 3.1 are receiving Invalid Product Key errors. On other machines the installation works fine. They are all Windows XP SP2 machines (some of the same image, but different software on them). If I run the MSI by itself, it fails with a Invalid Product Key error. If I do a run command with the /i ... /t.... PIDKEY="XXXX" /qb+ it runs fine. This is the same product key that we built in ORKTOOLs with the Custom Installation Wizard. Nothing different from what was accomplished with Professional. We need ideas? Thanks. |
Thread Tools | |
Display Modes | |
|
|