Terminal Services problem
Posted 20 November 2001 - 01:28
Posted 21 November 2001 - 10:59
I have the same problem with applications that were installed after Office. Every time they are launched Windows Installer asks for Office CD's. This is a workaround which may or may not be suitable.
Create an MMC with local machine Group Policy - Computer Config - Admin templates - Windows Components - Windows Installer. Double click the Disable Windows Installer and set to Enable and Disable Always. This will stop Win installer popping up but will also stop you from installing any further software. Disable then reenable between software installs. This is a very crude workaround and I look forward to any other posts that tackle this in a better way.
Rgds Doug
Posted 23 November 2001 - 02:43
I had thought of that, and have now disabled the service, however the applications still try to launch the MSI but does stop the loop.
Posted 23 November 2001 - 15:59
I've had another look at this. Look at MS article Q235620 and http://www.microsoft...ox.htm#keypath.
It appears that the apps we have installed after Office 2000 have overwritten Office files so the auto repair feature kicks in and tries to repair the install.
The Keypath XL sheet may shed some light on what is being "repaired". Have a look at the event log for the ComponentID. It seems possible that if we run a repair of the Office install, all the correct components will be repaired and the Installer should not be invoked. I havn't tried this though.
Hope this helps . .
Posted 23 November 2001 - 16:36
Martin
Posted 27 November 2001 - 06:40
However having said that, this setting is user specific and incorporated in the users profile. When creating a new user, the registry still needs updating manually. This would indicate to me that the original office install mst file may have been corrupted. However I'm prepared to live this know error for the time being and will address this a some time in the future when a server rebuild is required.