Hy, We're using Windows Thin PC with FBWF to connect to citrix. Ramdomly our Thin PC seem to lose their activation key and become "not genuine". That's a strange thing since we're use KMS. The activation process itself seem to work properly since the Thin Pc show a activation of 180 day and register ok in the KMS server. They never reach 180 day before stop working and seem random between 1 day to never. No patern so far can be found. What can cause this behavior? Do we need special exclusion in the FBWF to allow the kms to work properly? Ty

"Mlavoie44" wrote in message news:7c9fa597-8eb2-4b90-9217-ab445f658435... Hy, We're using Windows Thin PC with FBWF to connect to citrix. Ramdomly our Thin PC seem to lose their activation key and become "not genuine". That's a strange thing since we're use KMS. The activation process itself seem to work properly since the Thin Pc show a activation of 180 day and register ok in the KMS server. They never reach 180 day before stop working and seem random between 1 day to never. No patern so far can be found. What can cause this behavior? Do we need special exclusion in the FBWF to allow the kms to work properly? Ty I have no idea what it would show (if anything - I've never seen such a report from a Thin PC) but an MGADiag report on a failing system would be interesting to see. To properly analyse and solve problems with Activation and Validation, we need to see a full copy of the report produced by the MGADiag tool (download and save to desktop - http://go.microsoft.com/fwlink/?linkid=52012 ) Once saved, run the tool. Click on the Continue button, which will produce the report. To copy the report to your response, click on the Copy button in the tool (ignore any error messages at this point), and then paste (using either r-click/Paste, or Ctrl+V ) into your response. Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth

Diagnostic Report (1.9.0027.0): ----------------------------------------- Windows Validation Data--> Validation Code: 50 Cached Online Validation Code: N/A, hr = 0xc004f012 Windows Product Key: *****-*****-K7TQG-66MRP-CQ22C Windows Product Key Hash: nmmU/kLqn/5DFFVtcrEVnanS4Ho= Windows Product ID: 03934-010-0007106-03460 Windows Product ID Type: 1 Windows License Type: KMS Client Windows OS version: 6.1.7601.2.00010140.1.0.065 ID: {9AB96FE2-7993-4F9E-9A78-7BDA520AE621}(1) Is Admin: Yes TestCab: 0x0 LegitcheckControl ActiveX: N/A, hr = 0x80070002 Signed By: N/A, hr = 0x80070002 Product Name: Windows Embedded Standard Architecture: 0x00000000 Build lab: 7601.win7sp1_gdr.120330-1504 TTS Error: T:20120620085509887- Validation Diagnostic: Resolution Status: N/A Vista WgaER Data--> ThreatID(s): N/A, hr = 0x80070002 Version: N/A, hr = 0x80070002 Windows XP 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: N/A, hr = 0x80070002 OGAExec.exe Signed By: N/A, hr = 0x80070002 OGAAddin.dll Signed By: N/A, hr = 0x80070002 OGA Data--> Office Status: 109 N/A OGA Version: N/A, 0x80070002 Signed By: N/A, hr = 0x80070002 Office Diagnostics: B4D0AA8B-543-80070002_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--> File Mismatch: C:\Windows\system32\wat\watadminsvc.exe[Hr = 0x80070003] File Mismatch: C:\Windows\system32\wat\npwatweb.dll[Hr = 0x80070003] File Mismatch: C:\Windows\system32\wat\watux.exe[Hr = 0x80070003] File Mismatch: C:\Windows\system32\wat\watweb.dll[Hr = 0x80070003] File Mismatch: C:\Windows\system32\fr-FR\sppc.dll.mui[6.1.7600.16385], Hr = 0x80004005 File Mismatch: C:\Windows\system32\fr-FR\sppsvc.exe.mui[6.1.7600.16385], Hr = 0x80004005 Other data--> Office Details: <GenuineResults><MachineData><UGUID>{9AB96FE2-7993-4F9E-9A78-7BDA520AE621}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010140.1.0.065</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-CQ22C</PKey><PID>03934-010-0007106-03460</PID><PIDType>1</PIDType><SID>S-1-5-21-1512556551-2709479606-3388885453</SID><SYSTEM><Manufacturer>IBM</Manufacturer><Model>8189R1F</Model></SYSTEM><BIOS><Manufacturer>IBM</Manufacturer><Version>2AKT51AUS</Version><SMBIOSVersion major="2" minor="31"/><Date>20050706000000.000000+000</Date></BIOS><HWID>85B93607018400EC</HWID><UserLCID>0C0C</UserLCID><SystemLCID>040C</SystemLCID><TimeZone>Est(GMT-05:00)</TimeZone><iJoin>1</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM/><GANotification/></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults> Spsys.log Content: U1BMRwEAAAAAAQAABAAAAAZAAAAAAAAAWmICAEhdo5nxX6zs407NAROJf9ybj7SsIEe8hMh9DOFnggBTZYz8MmqiT4ShuSkAdTHeiw+XGgBd5f2C3YrqEuos3/Q683oNIjELxeWVyR0zkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAx4dZsxs/sxaQSZh6DCEuBHKp4Fou645DT7nxmwN/bizLFhL3eTXrnEmsm38ylhmpkzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgM Licensing Data--> Version du service de licences logicielles : 6.1.7600.16385 Erreur : cl de produit introuvable. Windows Activation Technologies--> HrOffline: 0x00000000 HrOnline: N/A HealthStatus: 0x0000000000000000 Event Time Stamp: N/A ActiveX: Not Registered - 0x80040154 Admin Service: Not Registered - 0x80040154 HealthStatus Bitmask Output: HWID Data--> HWID Hash Current: LAAAAAEAAgABAAEAAAABAAAAAQABAAEAnJ+yDIJl4sdmJiLyZJykDvKkkOg= 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 PTLTD APIC FACP IBM THINKCEN BOOT PTLTD $SBFTBL$ TCPA IBM THINKCEN

Interesting! the non-genuine error is caused by the two 0x80040005 errors - 'Access Denied'. Please check access permissionsto the two files concerned ICACLS C:\Windows\system32\fr-FR\sppsvc.exe.mui ICALCS C:\Windows\system32\fr-FR\sppc.exe.mui I *think* that they should both be Read&Execute for Administrators, SYSTEM, and Users - with TrustedInstaller being owner with full permissions. Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth

Interesting! the non-genuine error is caused by the two 0x80040005 errors - 'Access Denied'. Please check access permissionsto the two files concerned ICACLS C:\Windows\system32\fr-FR\sppsvc.exe.mui ICALCS C:\Windows\system32\fr-FR\sppc.exe.mui I *think* that they should both be Read&Execute for Administrators, SYSTEM, and Users - with TrustedInstaller being owner with full permissions. Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth Those are exactly the permissions they have on the file :-(

Can it be that windows thin pc doesn't like to be in french ? like : http://support.microsoft.com/kb/2105247/en-us ? Ty

"Mlavoie44" wrote in message news:a3915042-f908-4297-be23-9796820e92e5... Those are exactly the permissions they have on the file :-( I just noticed that there's also a Trusted Store Tamper present in the report - TTS Error: T:20120620085509887- Try checking the Event Viewer for that time (20th June, 08:55) and see if anything relevant appears there. Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth

Just before I can see that msiInstaller run a few time to install some citrix stuff. "Windows Installer reconfigured the product. Product name : Citrix receiver (SSON). ....." Can an app reconfig could do that?

"Mlavoie44" wrote in message news:800c2159-eea2-4fd6-8c88-7896be2351df... Just before I can see that msiInstaller run a few time to install some citrix stuff. "Windows Installer reconfigured the product. Product name : Citrix receiver (SSON). ....." Can an app reconfig could do that? If the app is badly-behaved enough, yes. Certain AV's cause problems with the earlier releases of Vista causing Trusted Store, Kernel, and Mod-Auth Tampers. Bad IRST drivers cause major problems with Win7 (and probably with Vista as well) A Trusted Store tamper may be cured by using System Restore (note that the tamper notification will remain in the report whether it's still present or not), or by uninstalling the program which caused it. Often the timestamp will update with every boot until the tamper is cleared - if you see that happening, then at least you have an indicator that it's gone, and can set about repairing any damage caused. I just wish that MS would provide an easy way to remove the indicator so that a retest would show whether it's still present or not! Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth

Hi, Here are three articles can be referred to. How to troubleshoot the Key Management Service (KMS) http://technet.microsoft.com/en-us/library/ee939272.aspx Troubleshooting KMS Activation - Part 1, the client http://blogs.technet.com/b/migreene/archive/2007/10/08/2136048.aspx Configuring KMS Clients http://technet.microsoft.com/en-us/library/ff793406.aspxIvan-Liu TechNet Community Support

"Ivan-Liu" wrote in message news:bbd09346-b82a-4f65-9029-9a294dd43f6b... Hi, Here are three articles can be referred to. How to troubleshoot the Key Management Service (KMS) http://technet.microsoft.com/en-us/library/ee939272.aspx Troubleshooting KMS Activation - Part 1, the client http://blogs.technet.com/b/migreene/archive/2007/10/08/2136048.aspx Configuring KMS Clients http://technet.microsoft.com/en-us/library/ff793406.aspx Ivan - there is nothing wrong here with the KMS, it's purely a problem with the Client failing validation due to file corruption and tampers. Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth

Does not seem to be the problem. we're only not using the lastest citrix client that would correct that log entrie. See #9 of the patch http://support.citrix.com/article/CTX131270 Any other idea would be welcome at this stage.

"Ivan-Liu" wrote in message news:bbd09346-b82a-4f65-9029-9a294dd43f6b... Hi, Here are three articles can be referred to. How to troubleshoot the Key Management Service (KMS) http://technet.microsoft.com/en-us/library/ee939272.aspx Troubleshooting KMS Activation - Part 1, the client http://blogs.technet.com/b/migreene/archive/2007/10/08/2136048.aspx Configuring KMS Clients http://technet.microsoft.com/en-us/library/ff793406.aspx Ivan - there is nothing wrong here with the KMS, it's purely a problem with the Client failing validation due to file corruption and tampers. Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth Absolutely. The KMS server is working for everything. Only the Thin PC seem to loose it 's activation.

If I try to "push" a KMS product key from the KMS server to a unlicenced computer, it's said "Product key not available". That's kind of strnage since half the computer got "licence renew" and the other half "unlicense". Ty

I think we may be back at the language packs here. Was the original language for all installs French, or did you install the packs using DISM? (or some other way) The article you referred to earlier - http://support.microsoft.com/kb/2105247/en-us was specifically written around public versions of Win7 below Ultimate/Enterprise, that had Language packs installed using a program called Vistalizator. This program gave rise to a very specific set of errors. - see this post for details.... http://social.microsoft.com/Forums/en-US/genuinewindows7/thread/6f6b1cb8-e84e-4c1f-a2ac-181a77d2f772 While you have two errors which are similar, the rest are different. I don't honestly know whether it would show anything more in a thin PC, but installing the WAT Update (KB971033) sometimes improves fault identification (it would also eliminate the other four errors in your report, assuming it's applicable in a thin client!). My knowledge of Embedded/Thin PC's and of Citrix is absolute zero - so if nothing new turns up there, then I would advise raising a support incident per KB2105247 and see if WGA Support can assist. Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth

I think we may be back at the language packs here. Was the original language for all installs French, or did you install the packs using DISM? (or some other way) The article you referred to earlier - http://support.microsoft.com/kb/2105247/en-us was specifically written around public versions of Win7 below Ultimate/Enterprise, that had Language packs installed using a program called Vistalizator. This program gave rise to a very specific set of errors. - see this post for details.... http://social.microsoft.com/Forums/en-US/genuinewindows7/thread/6f6b1cb8-e84e-4c1f-a2ac-181a77d2f772 While you have two errors which are similar, the rest are different. I don't honestly know whether it would show anything more in a thin PC, but installing the WAT Update (KB971033) sometimes improves fault identification (it would also eliminate the other four errors in your report, assuming it's applicable in a thin client!). My knowledge of Embedded/Thin PC's and of Citrix is absolute zero - so if nothing new turns up there, then I would advise raising a support incident per KB2105247 and see if WGA Support can assist. Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth Well, KB971033 doesn't wan to be install. Said it wrong product since it's thin pc.

In that case, I'm afraid I'm out of ideas - you should raise a support incident with MS to pursue the matter. Please come back with their solution for future reference! (although I suspect it will be to reinstall)Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth

The case is open. I really doubt reinstall is a solution. I got 30+ pc having the same problem. After a fresh install, they register on the KMS server and they work for sometime before showing "not genuine" again.

I suspect in that case that there is a problem with the initial image - and that will have to be addressed.Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth

I suspect in that case that there is a problem with the initial image - and that will have to be addressed. Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth The image has been re-build from scratch 3 time already. Always the same problem. I got a case open with microsoft but so far no luck.

Thanks for the update!Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth

Finally got a answer from microsoft (they don't seem to know this product at all). For use on Windows Thin Pc and FBWF, you need to use MAK key. I'll try that config in the next few day and keep this post updated.

Thanks VERY much for the update - it's a scenario I've never seen, so had no real idea how to respond. Anything you can tell us will be invaluable for future queries.Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth