Installing Office 2000 on Terminal Server

Installing Office on Terminal Server isn't as simple as it might seem. Follow these directions to make sure you do it right.

With the growing popularity of Windows Terminal Server, it's a good bet that more network administrators are planning on installing programs such as Microsoft Office on the server. But it isn't as simple as it might seem.

If you're using NT's Terminal Server and Microsoft Office 2000, you've probably seen an error message directing you to the Office 2000 Resource Kit for instructions and tools. Here's what the error's all about. You must use what's called a Transform file, a file that ends in the .mst extension that will make changes to the Setup.exe file. So, if you simply try to install Office 2000 from Autorun on the CD, the .mst file won't be in the path.

Here are the steps to install Office 2000 correctly on the NT Terminal Server (or Windows 2000 Terminal Server) operating system:

* Go to Control Panel | Add/Remove Programs.

* Click Install | Next.

* Browse to the root folder of Office Disc 1, select Setup.exe, and click OK. This will add Setup.exe to the Command Line For Installation Program box.

* In the Command Line For Installation Program box, after Setup.exe, add a space followed by TRANSFORMS="path:TermSrvr.mst" (where path is the location of the .mst file) and click Next.

* In the Change User Options dialog box, select All Users Begin With Common Application Settings and click Next.

* Type your customer information and accept the End User License Agreement.

* Click Install Now, and when prompted, restart the computer and log back on to Windows as the same user to allow Office 2000 Setup to complete successfully.

**SearchNetworking member Richard May suggests this modification to the above:

In the Command Line For Installation Program box, after Setup.exe, add a space followed by TRANSFORMS="pathTermSrvr.mst" (where path is the location of the .mst file) and NOUSERNAME=1 and click Next.

Did you like this tip? Why not let us know? Email to sound off:
This was first published in September 2001

Dig Deeper



Find more PRO+ content and other member only offers, here.



Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:









  • Virtual desktop security guide

    To secure virtual desktops, consider antivirus, certificates and network vulnerabilities. Just remember, VDI doesn't always ...

  • Guide to low-cost desktop virtualization

    In this guide, learn to virtualize desktops without spending more than you would when deploying PCs, and what VDI vendors are ...

  • VDI pilot project guide

    A VDI pilot project should start with a VDI project plan. Know what pitfalls to avoid and test product options to achieve a ...