General discussion

Locked

Office apps on Terminal Server

By jonhunt2 ·
We replaced our old server NT 4.0 with a new Windows 2003 server. Then we installed Windows 2003 Terminal server on the old server. We installed Terminal server in application mode and purchased 5 TS-CALs. We have installed Great Plains and now Office 2003, but when we run Office 2003 from a Terminal Service session, Word, Excel, etc. all give the error - 'This feature is not available. Contact your System Administrator.' That's it. When you click OK, the program exits. We installed Office via Control Panel Add/Remove. If we log into Terminal Services as Administrator, they all run just fine. This is probably a simple rights or licensing issue, but I haven't found the solution yet. Your thoughts would be very helpful.

Thanks,
Jon

This conversation is currently closed to new comments.

8 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

by BFilmFan In reply to Office apps on Terminal S ...

What access rights are being granted clients to the terminal server, such as access this computer from the network and logon interactively?

Did you publish the applications on the terminal server?

Work Thin has a pretty good host of articles on terminal Server.

http://www.workthin.com/tshta.htm

Collapse -

by jonhunt2 In reply to

Thanks for link, but it turned out to be simply activating the product.

Collapse -

by NotSoChiGuy In reply to Office apps on Terminal S ...

During the initial setup of office, did you make sure that each component was fully installed locally, and not selected as 'install on first run' or whatever that is?

If Office isn't setup fully on the hard drive, it will look to install the individual pieces of office for each person when they log onto the server. Assuming they don't have Admin rights (and since it won't be in ADD/Remove mode, anyway), the install will bomb.

Hope this helps. Good luck!

Collapse -

by jonhunt2 In reply to

Thanks for you help, but it turned out be simply activating the product.

Collapse -

by jonhunt2 In reply to Office apps on Terminal S ...

The users can logon interactively to the local machine, and I believe they also have log on from network as well. I don't know what is meant by "publish" the app on the terminal server. How do I do that?

And yes, all modules were installed completely, not install on first run. We did not activate the product because if this will not work, we may install this package on a different computer. We're well within the trial period.

Collapse -

by jonhunt2 In reply to Office apps on Terminal S ...

Point value changed by question poster.

Collapse -

by jonhunt2 In reply to Office apps on Terminal S ...

It was the activation of the product. Regular users were not authorized as Users or even Power Users to activate the product and that's when the error message came up - not authorized to use this feature - or something like that. Those in the Administrator's group could use the products by cancelling the activation. Once the product was activated, regular remote access users could begin using the Office applications. :) Thanks.

Collapse -

by jonhunt2 In reply to Office apps on Terminal S ...

This question was closed by the author

Back to Networks Forum
8 total posts (Page 1 of 1)  

Related Discussions

Related Forums