OGA uses a new beast, is called OGAEXEC.exe (\windows\system32). I guess it check the integrity of so called OGACheckControl.dll Before I knew the OGA IP (posted above), I just do this: On command prompt (cmd): cd c:\windows\system32 [enter] copy con OGACheckControl.dll [enter] press F6 and enter Say YES to overwrite (in case you already have it installed). Now the last step, type: attrib +r OGACheckControl.dll [enter] Believe it or not, it worked fine for me for years.
I have message of genuine apearing each start of outlook 2007 Whit lines he will stop of apear? Or the lines are only for not get this update yet?
That's not quire right. Plus its been known for a LONG time, and was used to update on blacklisted VLK XPs (I used the FCKGW key genuine for years thanks to that! ) mpa is the server, I just added sls for safety as that is another server. they both handle wga and oga. It does make them useless in a way, because everytime it tries to contact the server, it gets looped, so it assusmes genuine. Hazar
I receive this update yesterday (Brazil) and it is a optional one, so I hide it. My problem is the VLK key wich is blocked.
Did not receive the Office Genuine update...maybe because the 2 lines added in hosts file is effective.
I have those lines in my host file. 127.0.0.1 sls.microsoft.com 127.0.0.1 mpa.one.microsoft.com 127.0.0.1 genuine.microsoft.com Still I have it in my list of updates.
There was a way to export updates that you hide so you can automaticly hide them with unattended install, you know how?