Windows Forum

Ask something
Discussion Locked

New Document - Start menu - fails

0 helpful
5 replies

by srd

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

In a Terminal Services connection, the New Office Document and the Open Office Document selections fail, unless the user is logged in as Administrator. The Windows Installer pops up, then the message that you don't have the right to install software to a terminal server.

Granting that user Admin priveleges, you can complete the install when Installer pops up by putting in the CD, and, the shortcuts then work. But, putting that user back to User or Power User priveleges, it fails again.
Office was installed using the ORK tool, TermServ.mst. Terminal Server is running in Application Server mode. Users are either on Thin Client appliances or PCs with W2K operating systems. Most current W2K service packs have been applied, as wellas the Office updates.

Ideas? For some people, this is a major issue as they utilize these shortcuts all the time.

Thank you.

5 replies

by srd

Thanks - I have read through that info previously and just did so again. On my install on W2K Server, I was NOT given the option of "All users begin with common application settings" - there is no such option to select when using Add/Remove programs. This is mentioned in the article, saying that otherwise, Setup runs in Execute rather than Install mode. However, it is not an option that presents itself on installation. Ideas?

by srd

update: Office was uninstalled and reinstalled on the server, with the server running in Terminal Services Application mode, and the change user /install command applied. After the install, the change user /execute command was applied. I believe this is exactly how Microsoft tells you to install software for multiple user use through terminal services. Note that the New Office Document and Open Office Document choices from the start menu are still not available to an ordinary user. Anyone have any experience with this, or with customizing the terminal server transform, if that might be a workaround?

This discussion is closed to new replies.