Installed Office 2K before I installed terminal services. Now what?

[Guest]

I installed Office 2000 Professional on my Windows 2000 Server and then
installed Terminal Services. I am finding out that this was the
inappropriate way of doing this. Now I want to fix it but I want to do it
in such a manner that I will cause minimal damage/problems to the machine
and the operating system.

My thoughts are:

Put Terminal Services in Admin mode.
Remove Office 2000 Professional
Setup Terminal Serivces in Application Mode
Reinstall Office 2000 Professional using the termsvr.mst file that was
supposed to be used.
Then let my users back into the system.

Could someone please tell me if I am on the right track and if not point me
in the right direction.

Thanks,

Mike Stevens

 

[Vera Noest [MVP]]

I would uninstall Terminal Services completely, instead of
switching modes. Otherwise go as outlined. To be on the safe side,
reboot after removing Office. This might help with the
installation of Office, once TS is in Application mode:

224313 - How to Install Office 2000 on Windows 2000 Terminal
Server
http://support.microsoft.com/?kbid=224313

 

[Guest]

Vera,

Thank you for the information and reassurance of how to go about fixing
this problem. I did as you recommended and removed Terminal Services
completely before uninstalling Office 2000. Once I rebooted and removed
Office 2000 and rebooted once again, the installation went without a hitch.
I only have one more question regarding the installation of Office 2000.
When I log in as one of my users, I get an event logged referring to the
registry value HKCU\software\Microsoft\Office\9.0\access\UserData as missing
in the registry. Is it possible that I ended up screwing something up to
make this not work correctly or do I have to check a setting somewhere?

Thanks again,

Mike Stevens

 

[Vera Noest [MVP]]

I don't know what caused this, but it is a pretty common problem.
I *believe* that you can simple add the registry key. But to be
sure, have a look at www.eventid.net and type in the eventid and
the source of the event. I remember seeing a description of the
problem and some solutions there.