locked
Office 2003 Pro reports not genuine RRS feed

  • Question

  • After 2 or 3 years my MS Office 2003 Pro is now reporting it is not a genuine… but it is. 

     

    On checking through the forums a lot of people appear to be having the same problem.  Out of interest I loaded and ran a Keyfinder program and have discovered the product key for my Office is not the same as on my product envelope, not even near.

     

    I have tried to change the product key (first deleting DigitalProductID & ProductID in the registry) but Office will not accept the correct key.  Also tried remove and re-install, again does not accept the key.

     

    Any ideas……

     

    John

    Thursday, September 3, 2009 3:55 PM

Answers

  • Hello John Bickell,

    The information contained in the setup.ini file that you posted has confirmed (at least for me) my suspicions that you have a counterfeit Office CD.

    You have stated that the CD's appearance is that of an OEM CD, having the phrase "For distribution with a new PC only" on the label of the CD, and being acquired in the typical plain white cardboard CD envelope, with the OEM CoA on the back.

    The file above, also from this supposed-to-be-OEM CD, tells a different story.  Have a look at the snippet below:
    [MSI]
    ; The MSI section gives the name of the MSI file to install. This file must be in
    ; the same folder as Setup.exe, and both must be in the root of the installation
    ; tree.
    MSI=PRO11.MSI

    [Product]
    ProductCode={90110409-6000-11D3-8CFE-0150048383C9}
    ProductName=Microsoft Office 2003
    ProductVersion=11.0.5614.0
    Recache=1

    First, the file name PRO11.MSI is as expected, the main installation file for Office 2003 Professional.  Office 2003 is the eleventh edition of Office, thus the "11" in the file name, and "PRO" of course means the Professional edition of the suite.

    The give-away is the Product Code value, otherwise known as the GUID (globally unique identifier).  Using this MS KB article http://support.microsoft.com/kb/832672/ as a key or legend, we can see that the first eight digits of the GUID are telling us that the contents of the CD are the fisrt release of the software (the number 9), that the contents of the CD are an Enterprise edition (the number 0), and that the edition of the contents of the CD is Microsoft Office Professional Enterprise Edition 2003.  The numbers 0409 tell us this is the English version.

    So what we have is a CD that presents the appearance of an OEM CD but actually has the contents of a Volume Licensing CD.  As I wrote in a previous post, "This is a typical pirating method-- make the CD look like an OEM CD but the contents are really Volume Licensing bits.  Lots of XP counterfeiting uses this technique."

    Based on this analysis, I would strongly suggest that you follow the Office Genuine Advanatge Notifications Utility prompts, and submit a piracy report and submit the materials you have for analysis and consideration as hi-quality counterfeits.  If judged to be high quality counterfeits, Microsoft will replace them for free.


    For great advice on all topics XP, visit http://www.annoyances.org/exec/forum/winxp
    • Marked as answer by Darin Smith MS Wednesday, September 9, 2009 7:49 PM
    Saturday, September 5, 2009 7:18 PM

All replies

  • Hello John Bicknell,

    In order to recieve the best support, we request all users initially download and run the Genuine Diagnostics tool at this link http://go.microsoft.com/fwlink/?linkid=52012. Click the "Continue" button, click the "Copy" button, then paste the report into your post.


    For great advice on all topics XP, visit http://www.annoyances.org/exec/forum/winxp
    Thursday, September 3, 2009 4:07 PM
  • Thanks for your response.  I have printed the details from the report below.

     

    I have little doubt that the Office Pro element will prove to be wrong my issue is that product key for my Office is not the same as on my product envelope (the product sticker that shows the key). 

     

    As I have already said “I have tried to change the product key (first deleting DigitalProductID & ProductID in the registry) but Office will not accept the correct key.  Also tried remove and re-install, again does not accept the key.”

     

    A bit more information about removing and re-installing Office Pro.  After removal (and restart) the first part of installing Office Pro 2003 is to enter the product key which is rejected immediately and the installation halted on this computer.  On my laptop which has Office Pro 97 on it the product key was accepted (the installation was then cancelled).

     

    So how to I remove all references to the old and illegal? product key to allow the clean installation of the legal Office Pro.

     

    Thanks……

     

    John

     

     

     

    Diagnostic Report (1.9.0011.0):

    -----------------------------------------

    WGA Data-->

    Validation Status: Genuine

    Validation Code: 0

     

    Cached Validation Code: 0x0

    Windows Product Key: *****-*****-XMVJR-JW3PT-T8P2T

    Windows Product Key Hash: Z11Yg78VhkD94AC+d8eA84ykjoU=

    Windows Product ID: 89578-OEM-7304106-18185

    Windows Product ID Type: 3

    Windows License Type: OEM System Builder

    Windows OS version: 6.0.6002.2.00010300.2.0.003

    ID: {42083225-0852-47AF-92D0-7D4B9C974CA3}(3)

    Is Admin: Yes

    TestCab: 0x0

    WGA Version: Registered, 1.9.9.1

    Signed By: Microsoft

    Product Name: Windows Vista (TM) Home Premium

    Architecture: 0x00000000

    Build lab: 6002.lh_sp2rtm.090410-1830

    TTS Error:

    Validation Diagnostic:

    Resolution Status: N/A

     

    WgaER Data-->

    ThreatID(s): N/A, hr = 0x80070002

    Version: 6.0.6001.18000

     

    WGA Notifications Data-->

    Cached Result: N/A, hr = 0x80070002

    File Exists: No

    Version: N/A, hr = 0x80070002

    WgaTray.exe Signed By: N/A, hr = 0x80070002

    WgaLogon.dll Signed By: N/A, hr = 0x80070002

     

    OGA Notifications Data-->

    Cached Result: N/A, hr = 0x80070002

    Version: 2.0.48.0

    OGAExec.exe Signed By: Microsoft

    OGAAddin.dll Signed By: Microsoft

     

    OGA Data-->

    Office Status: 108 Invalid VLK

    Microsoft Office Professional Edition 2003 - 108 Invalid VLK

    Microsoft Office FrontPage 2003 - 100 Genuine

    OGA Version: Registered, 2.0.48.0

    Signed By: Microsoft

    Office Diagnostics: 025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3

     

    Browser Data-->

    Proxy settings: N/A

    User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)

    Default Browser: C:\Program Files\Internet Explorer\IEXPLORE.exe

    Download signed ActiveX controls: Prompt

    Download unsigned ActiveX controls: Disabled

    Run ActiveX controls and plug-ins: Allowed

    Initialize and script ActiveX controls not marked as safe: Disabled

    Allow scripting of Internet Explorer Webbrowser control: Disabled

    Active scripting: Allowed

    Script ActiveX controls marked as safe for scripting: Allowed

     

    File Scan Data-->

     

    Other data-->

    Office Details: <GenuineResults><MachineData><UGUID>{42083225-0852-47AF-92D0-7D4B9C974CA3}</UGUID><Version>1.9.0011.0</Version><OS>6.0.6002.2.00010300.2.0.003</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-T8P2T</PKey><PID>89578-OEM-7304106-18185</PID><PIDType>3</PIDType><SID>S-1-5-21-3069794304-4292742130-4212004812</SID><SYSTEM><Manufacturer>System manufacturer</Manufacturer><Model>System Product Name</Model></SYSTEM><BIOS><Manufacturer>Phoenix Technologies, LTD</Manufacturer><Version>ASUS P5ND2 SE ACPI BIOS Revision 0501</Version><SMBIOSVersion major="2" minor="4"/><Date>20061219000000.000000+000</Date></BIOS><HWID>80303507018400FA</HWID><UserLCID>0809</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>GMT Standard Time(GMT+00:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM/><GANotification><File Name="OGAAddin.dll" Version="2.0.48.0"/></GANotification></MachineData><Software><Office><Result>108</Result><Products><Product GUID="{90110409-6000-11D3-8CFE-0150048383C9}"><LegitResult>108</LegitResult><Name>Microsoft Office Professional Edition 2003</Name><Ver>11</Ver><Val>7F39C3E059A8500</Val><Hash>GVF/qNsKtW+tAAVW+CgMhzr3tkQ=</Hash><Pid>73931-640-2103134-57986</Pid><PidType>14</PidType></Product><Product GUID="{91170409-6000-11D3-8CFE-0150048383C9}"><LegitResult>100</LegitResult><Name>Microsoft Office FrontPage 2003</Name><Ver>11</Ver><Val>9BC439DC19D7DF3</Val><Hash>6W5jU3iN03yZgFgGtfWb0EWlAzc=</Hash><Pid>72079-761-0084646-55520</Pid><PidType>1</PidType></Product></Products><Applications><App Id="15" Version="11" Result="108"/><App Id="16" Version="11" Result="108"/><App Id="17" Version="11" Result="100"/><App Id="18" Version="11" Result="108"/><App Id="19" Version="11" Result="108"/><App Id="1A" Version="11" Result="108"/><App Id="1B" Version="11" Result="108"/><App Id="44" Version="11" Result="108"/></Applications></Office></Software></GenuineResults> 

     

    Spsys.log Content: 0x80070002

     

    Licensing Data-->

    Software licensing service version: 6.0.6002.18005

    Name: Windows(TM) Vista, HomePremium edition

    Description: Windows Operating System - Vista, OEM_COA_NSLP channel

    Activation ID: f3acdd3c-119a-4932-a3d7-0b6f33a1dca9

    Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f

    Extended PID: 89578-00146-041-018185-02-2057-6000.0000-1752007

    Installation ID: 011073278966100745187463783651960285688312984526121940

    Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=43473

    Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=43474

    Use License URL: http://go.microsoft.com/fwlink/?LinkID=43476

    Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=43475

    Partial Product Key: T8P2T

    License Status: Licensed

     

    HWID Data-->

    HWID Hash Current: OAAAAAEABAABAAIAAQACAAAAAgABAAEAJJQw3dXDwCBCqsD7SCT8AiYLqoby9OZE3CwuUqxWKoU=

     

    OEM Activation 1.0 Data-->

    N/A

     

    OEM Activation 2.0 Data-->

    BIOS valid for OA 2.0: yes, but no SLIC table

    Windows marker version: N/A

    OEMID and OEMTableID Consistent: N/A

    BIOS Information:

      ACPI Table Name    OEMID Value            OEMTableID Value

      APIC                         Nvidia             ASUSACPI

      FACP                                    Nvidia             ASUSACPI

      HPET                                    Nvidia             ASUSACPI

      MCFG                                   Nvidia             ASUSACPI

      SSDT                                    Nvidia             ASUSACPI

      SSDT                                    Nvidia             ASUSACPI

     

    Thursday, September 3, 2009 10:11 PM
  • Hello John Bicknell,

    Using Add or Remove Programs, uninstall Office 2003 and restart.  Uninstall Front Page 2003 and restart.  Restart once more.

    Now install Office 2003.  Restart at completion.  Do not install Front Page.

    Visit www.microsoft.com/genuine and click on Validate Office.

    Rerun the mgadiag utility http://go.microsoft.com/fwlink/?linkid=52012 and post a fresh report in a reply in this thread.


    For great advice on all topics XP, visit http://www.annoyances.org/exec/forum/winxp
    Friday, September 4, 2009 3:45 AM
  • Hellow Dan

    Done as you asked but closes down and restarted another couple of times.

    When I inserted the Office disk I was asked for the key, it would not accept it and got error Code 800702E4.  The forums surgest you navigate to the 'setup' on the CD and run it as Administrator.  Done loaded cleanly.  When I opened 'word' it did not ask for the key.  I ran Keyfinder again and it still reports the illegal? key so back where I started. 

    As I said in my first post  'I have tried to change the product key (first deleting DigitalProductID & ProductID in the registry) but Office will not accept the correct key.' 

    Help please, I don't want to wipe and re-install vista as well.

    Thanks....

    John

    The report for your reference:.

    Diagnostic Report (1.9.0011.0):
    -----------------------------------------
    WGA Data-->
    Validation Status: Genuine
    Validation Code: 0

    Cached Validation Code: 0x0
    Windows Product Key: *****-*****-XMVJR-JW3PT-T8P2T
    Windows Product Key Hash: Z11Yg78VhkD94AC+d8eA84ykjoU=
    Windows Product ID: 89578-OEM-7304106-18185
    Windows Product ID Type: 3
    Windows License Type: OEM System Builder
    Windows OS version: 6.0.6002.2.00010300.2.0.003
    ID: {42083225-0852-47AF-92D0-7D4B9C974CA3}(3)
    Is Admin: Yes
    TestCab: 0x0
    WGA Version: Registered, 1.9.9.1
    Signed By: Microsoft
    Product Name: Windows Vista (TM) Home Premium
    Architecture: 0x00000000
    Build lab: 6002.lh_sp2rtm.090410-1830
    TTS Error:
    Validation Diagnostic:
    Resolution Status: N/A

    WgaER Data-->
    ThreatID(s): N/A, hr = 0x80070002
    Version: 6.0.6001.18000

    WGA Notifications Data-->
    Cached Result: N/A, hr = 0x80070002
    File Exists: No
    Version: N/A, hr = 0x80070002
    WgaTray.exe Signed By: N/A, hr = 0x80070002
    WgaLogon.dll Signed By: N/A, hr = 0x80070002

    OGA Notifications Data-->
    Cached Result: N/A, hr = 0x80070002
    Version: 2.0.48.0
    OGAExec.exe Signed By: Microsoft
    OGAAddin.dll Signed By: Microsoft

    OGA Data-->
    Office Status: 108 Invalid VLK
    Microsoft Office Professional Edition 2003 - 108 Invalid VLK
    OGA Version: Registered, 2.0.48.0
    Signed By: Microsoft
    Office Diagnostics: B4D0AA8B-604-645_025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3

    Browser Data-->
    Proxy settings: N/A
    User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
    Default Browser: C:\Program Files\Internet Explorer\IEXPLORE.exe
    Download signed ActiveX controls: Prompt
    Download unsigned ActiveX controls: Disabled
    Run ActiveX controls and plug-ins: Allowed
    Initialize and script ActiveX controls not marked as safe: Disabled
    Allow scripting of Internet Explorer Webbrowser control: Disabled
    Active scripting: Allowed
    Script ActiveX controls marked as safe for scripting: Allowed

    File Scan Data-->

    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>{42083225-0852-47AF-92D0-7D4B9C974CA3}</UGUID><Version>1.9.0011.0</Version><OS>6.0.6002.2.00010300.2.0.003</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-T8P2T</PKey><PID>89578-OEM-7304106-18185</PID><PIDType>3</PIDType><SID>S-1-5-21-3069794304-4292742130-4212004812</SID><SYSTEM><Manufacturer>System manufacturer</Manufacturer><Model>System Product Name</Model></SYSTEM><BIOS><Manufacturer>Phoenix Technologies, LTD</Manufacturer><Version>ASUS P5ND2 SE ACPI BIOS Revision 0501</Version><SMBIOSVersion major="2" minor="4"/><Date>20061219000000.000000+000</Date></BIOS><HWID>80303507018400FA</HWID><UserLCID>0809</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>GMT Standard Time(GMT+00:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM/><GANotification><File Name="OGAAddin.dll" Version="2.0.48.0"/></GANotification></MachineData><Software><Office><Result>108</Result><Products><Product GUID="{90110409-6000-11D3-8CFE-0150048383C9}"><LegitResult>108</LegitResult><Name>Microsoft Office Professional Edition 2003</Name><Ver>11</Ver><Val>7F39C3E059A8500</Val><Hash>GVF/qNsKtW+tAAVW+CgMhzr3tkQ=</Hash><Pid>73931-640-2103134-57986</Pid><PidType>14</PidType></Product></Products><Applications><App Id="15" Version="11" Result="108"/><App Id="16" Version="11" Result="108"/><App Id="18" Version="11" Result="108"/><App Id="19" Version="11" Result="108"/><App Id="1A" Version="11" Result="108"/><App Id="1B" Version="11" Result="108"/><App Id="44" Version="11" Result="108"/></Applications></Office></Software></GenuineResults> 

    Spsys.log Content: 0x80070002

    Licensing Data-->
    Software licensing service version: 6.0.6002.18005
    Name: Windows(TM) Vista, HomePremium edition
    Description: Windows Operating System - Vista, OEM_COA_NSLP channel
    Activation ID: f3acdd3c-119a-4932-a3d7-0b6f33a1dca9
    Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
    Extended PID: 89578-00146-041-018185-02-2057-6000.0000-1752007
    Installation ID: 011073278966100745187463783651960285688312984526121940
    Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=43473
    Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=43474
    Use License URL: http://go.microsoft.com/fwlink/?LinkID=43476
    Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=43475
    Partial Product Key: T8P2T
    License Status: Licensed

    HWID Data-->
    HWID Hash Current: OAAAAAEABAABAAIAAQACAAAAAgABAAEAJJQw3dXDwCBCqsD7SCT8AiYLqoby9OZE3CwuUqxWKoU=

    OEM Activation 1.0 Data-->
    N/A

    OEM Activation 2.0 Data-->
    BIOS valid for OA 2.0: yes, but no SLIC table
    Windows marker version: N/A
    OEMID and OEMTableID Consistent: N/A
    BIOS Information:
      ACPI Table Name OEMID Value OEMTableID Value
      APIC   Nvidia  ASUSACPI
      FACP   Nvidia  ASUSACPI
      HPET   Nvidia  ASUSACPI
      MCFG   Nvidia  ASUSACPI
      SSDT   Nvidia  ASUSACPI
      SSDT   Nvidia  ASUSACPI



    Friday, September 4, 2009 9:51 AM
  • Friday, September 4, 2009 1:59 PM
  • Hi Dan

    Picture A, even the part no. matches.

    John
    Friday, September 4, 2009 2:52 PM
  • Hello John Bicknell,

    You are telling us that you have what's in Picture A.

    Picture A is a picture of a typical CD and sleeve/envelope for an OEM license kit for Office 2003.  On the back of the sleeve there should be a Certificate of Authenticity with the Product Key, 25 characters in a 5 x 5 format.  On the CD, in the upper left quadrant, there should be the wording "For distribution with a new PC only.  For support, contact the manufacturer of your PC."

    However, what is being installed on the computer is what would be installed by a Volume Licensing CD that looks like the CD in picture B (the actual wording on the CD in B is for Office XP, but the Office 2003 CD is visually identical with different wording to reflect Office 2003).

    This would appear to be a situation where the CD you have has been made to look like an OEM CD but really has the contents of a Volume License CD and is installing a Volume License edition of Office 2003 on the computer.

    Given the above, it is not surprising that the Product Key on the back of your sleeve/envelope is being rejected by Setup, as you mentioned before, "...enter the product key which is rejected immediately and the installation halted on this computer."  This is expected behavior because the product keys for different editions and channel of Office are generated with different algorithms so that only an OEM product key would be accepted by an OEM CD, and only a Volume Licensing product key would be accepted by a Volume License CD.

    This is a typical pirating method-- make the CD look like an OEM CD but the contents are really Volume Licensing bits.  Lots of XP counterfeiting uses this technique.

    A good way to verify that this OEM-looking CD is installing a VL edition of Office would be to install it on a computer that does not have Office installed now.  Once installation is complete, run the mgadiag utility against it to see what is report in the OGA Data section of the report.  If it reports that it is a Volume Licensing installation, that would pretty much verify what I suspect.

    My suggestion at this point would be to follow the prompts being shown by the Office Genuine Advantage Notifications Utility, and choose the option to prepare a piracy report and to submit your CD and related materials to Microsoft for evaluation as possible hi grade counterfeits.

    The part that I can't figure is how the VL key has gotten "stuck" in the computer.  If you have the time, uninstall Office again and restart twice.  Then follow method B in this MS KB article:  http://support.microsoft.com/kb/903275/en-us  I am hoping that might clear out the persistent data that seems to be keeping the VLK in the computer.


    For great advice on all topics XP, visit http://www.annoyances.org/exec/forum/winxp
    Friday, September 4, 2009 3:39 PM
  • Hi Dan

    It is picture A, it is Office 2003.  The splash screens are 2003, it looks like 2003.  I have used Office XP and still do from time to time at a friends business so know what it looks like.  You are seeing it as Office XP because my computer is holding on to the duff product key.

    I have now un-installed Office 2003, deleted the Opa11.dat file, deleted the DigitalProductID and ProductID in the registry, restarted the computer 3 times.  I have printed the report again before I do anything else which follows.  Does it still say I have Office XP??

    I am going to try to install Office one more time.  If it fails again I will get a new HD on Sat and reinstall Vista and Office 2003.

    Dan, I do appreciate you help.  I no longer care how much work I have to do, or how much it costs; this is a real valid copy of Office Pro 2003 and I am going to prove it.  If you have any ideas how I could do it without re-installing everything please let me know.

    I guess it is you weekend now so enjoy the break.

    John

    Diagnostic Report (1.9.0011.0):
    -----------------------------------------
    WGA Data-->
    Validation Status: Genuine
    Validation Code: 0

    Cached Validation Code: 0x0
    Windows Product Key: *****-*****-XMVJR-JW3PT-T8P2T
    Windows Product Key Hash: Z11Yg78VhkD94AC+d8eA84ykjoU=
    Windows Product ID: 89578-OEM-7304106-18185
    Windows Product ID Type: 3
    Windows License Type: OEM System Builder
    Windows OS version: 6.0.6002.2.00010300.2.0.003
    ID: {42083225-0852-47AF-92D0-7D4B9C974CA3}(3)
    Is Admin: Yes
    TestCab: 0x0
    WGA Version: Registered, 1.9.9.1
    Signed By: Microsoft
    Product Name: Windows Vista (TM) Home Premium
    Architecture: 0x00000000
    Build lab: 6002.lh_sp2rtm.090410-1830
    TTS Error:
    Validation Diagnostic:
    Resolution Status: N/A

    WgaER Data-->
    ThreatID(s): N/A, hr = 0x80070002
    Version: 6.0.6001.18000

    WGA Notifications Data-->
    Cached Result: N/A, hr = 0x80070002
    File Exists: No
    Version: N/A, hr = 0x80070002
    WgaTray.exe Signed By: N/A, hr = 0x80070002
    WgaLogon.dll Signed By: N/A, hr = 0x80070002

    OGA Notifications Data-->
    Cached Result: N/A, hr = 0x80070002
    Version: 2.0.48.0
    OGAExec.exe Signed By: Microsoft
    OGAAddin.dll Signed By: Microsoft

    OGA Data-->
    Office Status: 109 N/A
    OGA Version: Registered, 2.0.48.0
    Signed By: Microsoft
    Office Diagnostics: B4D0AA8B-604-645_B4D0AA8B-604-645_025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3

    Browser Data-->
    Proxy settings: N/A
    User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
    Default Browser: C:\Program Files\Internet Explorer\IEXPLORE.exe
    Download signed ActiveX controls: Prompt
    Download unsigned ActiveX controls: Disabled
    Run ActiveX controls and plug-ins: Allowed
    Initialize and script ActiveX controls not marked as safe: Disabled
    Allow scripting of Internet Explorer Webbrowser control: Disabled
    Active scripting: Allowed
    Script ActiveX controls marked as safe for scripting: Allowed

    File Scan Data-->

    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>{42083225-0852-47AF-92D0-7D4B9C974CA3}</UGUID><Version>1.9.0011.0</Version><OS>6.0.6002.2.00010300.2.0.003</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-T8P2T</PKey><PID>89578-OEM-7304106-18185</PID><PIDType>3</PIDType><SID>S-1-5-21-3069794304-4292742130-4212004812</SID><SYSTEM><Manufacturer>System manufacturer</Manufacturer><Model>System Product Name</Model></SYSTEM><BIOS><Manufacturer>Phoenix Technologies, LTD</Manufacturer><Version>ASUS P5ND2 SE ACPI BIOS Revision 0501</Version><SMBIOSVersion major="2" minor="4"/><Date>20061219000000.000000+000</Date></BIOS><HWID>80303507018400FA</HWID><UserLCID>0809</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>GMT Standard Time(GMT+00:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM/><GANotification><File Name="OGAAddin.dll" Version="2.0.48.0"/></GANotification></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults> 

    Spsys.log Content: 0x80070002

    Licensing Data-->
    Software licensing service version: 6.0.6002.18005
    Name: Windows(TM) Vista, HomePremium edition
    Description: Windows Operating System - Vista, OEM_COA_NSLP channel
    Activation ID: f3acdd3c-119a-4932-a3d7-0b6f33a1dca9
    Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
    Extended PID: 89578-00146-041-018185-02-2057-6000.0000-1752007
    Installation ID: 011073278966100745187463783651960285688312984526121940
    Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=43473
    Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=43474
    Use License URL: http://go.microsoft.com/fwlink/?LinkID=43476
    Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=43475
    Partial Product Key: T8P2T
    License Status: Licensed

    HWID Data-->
    HWID Hash Current: OAAAAAEABAABAAIAAQACAAAAAgABAAEAJJQw3dXDwCBCqsD7SCT8AiYLqoby9OZE3CwuUqxWKoU=

    OEM Activation 1.0 Data-->
    N/A

    OEM Activation 2.0 Data-->
    BIOS valid for OA 2.0: yes, but no SLIC table
    Windows marker version: N/A
    OEMID and OEMTableID Consistent: N/A
    BIOS Information:
      ACPI Table Name OEMID Value OEMTableID Value
      APIC   Nvidia  ASUSACPI
      FACP   Nvidia  ASUSACPI
      HPET   Nvidia  ASUSACPI
      MCFG   Nvidia  ASUSACPI
      SSDT   Nvidia  ASUSACPI
      SSDT   Nvidia  ASUSACPI

     


    Friday, September 4, 2009 10:08 PM
  • Hi Dan

    Update.

    Just installed Office again.  Installed from the setup as Administrator (the Vista problem) so does not ask for the product key - opened 'Word' still not asked for the key.

    Ran the Keyfinder and it is still the rogue product key.  Another MS report would be pointless.

    Looks like it may be a long weekend...... o joy.

    John

    Friday, September 4, 2009 10:27 PM
  • Hello John Bicknell,

    My reference to Office XP was to clarify that although the sample pic that I linked to for Pic B was an Office XP disc, the Office 2003 Volume Licensing CDs are visually identical with the exception that they have of course Office 2003 on them instead of Office XP.  Sorry for any unintentional confusion! :-)

    On your Office installation CD, navigate to the \filessetup folder and locate a small text file called setup.ini.  Please post the text of this file.  Thx!
    For great advice on all topics XP, visit http://www.annoyances.org/exec/forum/winxp
    Friday, September 4, 2009 10:42 PM
  • Hi Dan

    Requested file:

    John

    ; Microsoft Office SETUP.EXE settings file.

    [MSI]
    ; The MSI section gives the name of the MSI file to install. This file must be in
    ; the same folder as Setup.exe, and both must be in the root of the installation
    ; tree.
    MSI=OWC11.MSI

    [Product]
    ProductCode={90A40409-6000-11D3-8CFE-0150048383C9}
    ProductName=Microsoft Office 2003 Web Components
    ProductVersion=11.0.5614.0
    Recache=1

    [MST]
    ; The MST section gives the full path to a transform that should be applied.
    ;MST1=\\server\share\some transform.mst
    ;MST1=D:\transforms\my transform.mst

    [Options]
    ; The option section is used for specifying individual Installer Properties.
    ;USERNAME=Customer
    ;COMPANYNAME=my company
    ;INSTALLLOCATION=C:\Program Files\MyApp

    [Display]
    ; The diplay section is used for overriding the default UI
    ;       Value           Default         Description
    ;       Display         full            Option to override the default UI
    ;                                       [none, quiet, basic, reduced, full]
    ;       CompletionNotice Yes            Option to display a setup completion
    ;                                       notice for otherwise quiet setup
    ;Display=None
    ;CompletionNotice=Yes

    [Logging]
    ; The logging section provides settings for controlling the Setup log files.
    ;       Value           Default         Description
    ;       Type            vpiwaeo         Logging modes 
    ;                                       [a, c, e, i, m, o, p, r, u , v,
    ;                                       w, *, +]
    ;       Path            %TEMP%          Path to create logfiles
    ;       Template        SetupLog(*).txt File name for log file should end in
    ;                                       "(*).txt"; the * is replaced with a 4
    ;                                       digit number to make the file name unique
    Template=Microsoft Office 2003 Web Components Setup(*).txt
    Type=piwaeo
    ;Path=\\MyServer\logfiles\
    ;Template=Product %UserName%(*).txt

    [MinOSRequirement]
    ; MinOSRequirement is used for defining the minimal OS requirement for
    ; installing the product.
    VersionNT_1=500
    WindowsBuild_1=2195
    ServicePackLevel_1=3

    [Cache]
    ; The cache section provides settings for caching the install source locally
    ;       Value           Default         Description
    ;       CDCACHE            2             Option to specify cache level
    ;                                       [auto, 0, 1, 2]
    ;       LOCALCACHEDRIVE <predefined>    Option to specify a drive to cache
    ;                                       the install source to
    ;       DELETABLECACHE  1                Option to display UI to remove the
    ;                                       cache at the end of setup [0,1]
    ;       PURGE           0               Option to always remove cache at end of
    ;                                       setup [0,1]
    CDCACHE=auto
    ;LOCALCACHEDRIVE=C:\
    DELETABLECACHE=1
    PURGE=0

    Friday, September 4, 2009 10:52 PM
  • Hello John Bicknell,

    You posted the d:\files\owc11\setup.ini file.  Sorry for the error, I mistyped the location.

    Should be this location d:\files\setup\setup.ini.

    Thanx!
    For great advice on all topics XP, visit http://www.annoyances.org/exec/forum/winxp
    Saturday, September 5, 2009 12:33 AM
  • Hi Dan

    Requested file as follows:

    John

    ; Microsoft Office SETUP.EXE settings file.

    [MSI]
    ; The MSI section gives the name of the MSI file to install. This file must be in
    ; the same folder as Setup.exe, and both must be in the root of the installation
    ; tree.
    MSI=PRO11.MSI

    [Product]
    ProductCode={90110409-6000-11D3-8CFE-0150048383C9}
    ProductName=Microsoft Office 2003
    ProductVersion=11.0.5614.0
    Recache=1

    [MST]
    ; The MST section gives the full path to a transform that should be applied.
    ;MST1=\\server\share\some transform.mst
    ;MST1=D:\transforms\my transform.mst

    [Options]
    ; The option section is used for specifying individual Installer Properties.
    ;USERNAME=Customer
    ;COMPANYNAME=my company
    ;INSTALLLOCATION=C:\Program Files\MyApp

    [Display]
    ; The diplay section is used for overriding the default UI
    ;       Value           Default         Description
    ;       Display         full            Option to override the default UI
    ;                                       [none, quiet, basic, reduced, full]
    ;       CompletionNotice Yes            Option to display a setup completion
    ;                                       notice for otherwise quiet setup
    ;Display=None
    ;CompletionNotice=Yes

    [Logging]
    ; The logging section provides settings for controlling the Setup log files.
    ;       Value           Default         Description
    ;       Type            vpiwaeo         Logging modes 
    ;                                       [a, c, e, i, m, o, p, r, u , v,
    ;                                       w, *, +]
    ;       Path            %TEMP%          Path to create logfiles
    ;       Template        SetupLog(*).txt File name for log file should end in
    ;                                       "(*).txt"; the * is replaced with a 4
    ;                                       digit number to make the file name unique
    Template=Microsoft Office 2003 Setup(*).txt
    Type=piwaeo
    ;Path=\\MyServer\logfiles\
    ;Template=Product %UserName%(*).txt

    [MinOSRequirement]
    ; MinOSRequirement is used for defining the minimal OS requirement for
    ; installing the product.
    VersionNT_1=500
    WindowsBuild_1=2195
    ServicePackLevel_1=3

    [Cache]
    ; The cache section provides settings for caching the install source locally
    ;       Value           Default         Description
    ;       CDCACHE            2             Option to specify cache level
    ;                                       [auto, 0, 1, 2]
    ;       LOCALCACHEDRIVE <predefined>    Option to specify a drive to cache
    ;                                       the install source to
    ;       DELETABLECACHE  1                Option to display UI to remove the
    ;                                       cache at the end of setup [0,1]
    ;       PURGE           0               Option to always remove cache at end of
    ;                                       setup [0,1]
    CDCACHE=auto
    ;LOCALCACHEDRIVE=C:\
    DELETABLECACHE=1
    PURGE=0

    [OfficeWebComponents]
    MSI=OWC11.MSI

    Saturday, September 5, 2009 9:23 AM
  • Hello Dan

     

    I purchase a new HD today but are waiting to hear what you say before I continue with the re-install the whole system choice.

     

    Related in a way to the topic could I ask a question.

    I have pre-ordered Windows 7, due about 22 Oct.  Starting with a clean sheet I am confident my Office Pro 2003 will install the correct and legal key (hope there are no conflict issues with Windows 7 & Office 2003).  Will the current setup of Office with the wrong key continue to work for another 7 weeks all-be-it with the warnings?

     

    Thanks…….

     

    John

    Saturday, September 5, 2009 3:04 PM
  • Hello John Bickell,

    The information contained in the setup.ini file that you posted has confirmed (at least for me) my suspicions that you have a counterfeit Office CD.

    You have stated that the CD's appearance is that of an OEM CD, having the phrase "For distribution with a new PC only" on the label of the CD, and being acquired in the typical plain white cardboard CD envelope, with the OEM CoA on the back.

    The file above, also from this supposed-to-be-OEM CD, tells a different story.  Have a look at the snippet below:
    [MSI]
    ; The MSI section gives the name of the MSI file to install. This file must be in
    ; the same folder as Setup.exe, and both must be in the root of the installation
    ; tree.
    MSI=PRO11.MSI

    [Product]
    ProductCode={90110409-6000-11D3-8CFE-0150048383C9}
    ProductName=Microsoft Office 2003
    ProductVersion=11.0.5614.0
    Recache=1

    First, the file name PRO11.MSI is as expected, the main installation file for Office 2003 Professional.  Office 2003 is the eleventh edition of Office, thus the "11" in the file name, and "PRO" of course means the Professional edition of the suite.

    The give-away is the Product Code value, otherwise known as the GUID (globally unique identifier).  Using this MS KB article http://support.microsoft.com/kb/832672/ as a key or legend, we can see that the first eight digits of the GUID are telling us that the contents of the CD are the fisrt release of the software (the number 9), that the contents of the CD are an Enterprise edition (the number 0), and that the edition of the contents of the CD is Microsoft Office Professional Enterprise Edition 2003.  The numbers 0409 tell us this is the English version.

    So what we have is a CD that presents the appearance of an OEM CD but actually has the contents of a Volume Licensing CD.  As I wrote in a previous post, "This is a typical pirating method-- make the CD look like an OEM CD but the contents are really Volume Licensing bits.  Lots of XP counterfeiting uses this technique."

    Based on this analysis, I would strongly suggest that you follow the Office Genuine Advanatge Notifications Utility prompts, and submit a piracy report and submit the materials you have for analysis and consideration as hi-quality counterfeits.  If judged to be high quality counterfeits, Microsoft will replace them for free.


    For great advice on all topics XP, visit http://www.annoyances.org/exec/forum/winxp
    • Marked as answer by Darin Smith MS Wednesday, September 9, 2009 7:49 PM
    Saturday, September 5, 2009 7:18 PM
  • Hello Dan

     

    Despite your conclusions I put in that new HD, an old XP OS and loaded Office 2003.  Although it appears ok the Keyfinder shows it is using the duff product key, it’s a fake……..

     

    I am sorry to doubt you Dan but even now knowing it is an illegal copy it is impossible to find anything wrong with its presentation.  The holograms the printing and the cardboard wallet.

     

    Thank you for your efforts on my behalf, I will drown my sorrows down the pub later, have a good day.

     

    John Bicknell

    Monday, September 7, 2009 8:25 AM