Aug 24, 2010. The first rule is that workstations running Terminal Server sessions have to have a license to the software they are running. Before Office 2007, this was very, very loosely enforced, but with Office 2007 (and 2010), things have been tightened up significantly. For one, you have to install the Enterprise version. Nov 29, 2011 Office 2010 Volume Licensing on TS. 3 activations because he has 3 terminal servers to activate office on. You cannot run Office 2010 on a Terminal Server. Discusses how to enable Office Professional Plus 2010 to. 2008 Terminal Services to let users use Office. Activate Office Professional Plus 2010. The trial download page says specifically: Terminal Server and windows on Windows (WOW) (which allows installing 32-bit versions of Office 2010 on 64-bit operating. Use the following procedure to manually install Office 2010 on a Remote Desktop Services-enabled computer. Make sure that Remote Desktop Services is already installed and that you run the Setup program from the Office 2010 installation CD or from a network installation point. To manually install Office 2010 • Click Start, point to Settings, and then click Control Panel. For Windows 7, click Start, and then click Control Panel. • Double-click Add or Remove Programs, and then click Add New Program. A list of available programs is displayed. For Windows 7, under Programs, double-click Get programs. A list of available programs is displayed. • Locate the Setup program (Setup.exe) for Office 2010. This can be on the Office 2010 installation CD or on a network installation point. • Click setup.exe, and then click Open. • On the Enter your Product Key page, type the product key, and then click Continue. • On the Read the Microsoft Software License Terms page, click the I accept the terms of this agreement check box, and then click Continue. • On the Choose the Installation you want page, click Customize. • On the Install Options tab, click an application or feature and change the installation state to either Run from my computer or Not available. • If you want to customize the other settings, click the File Location tab or the User Information tab, and then make the changes that you want. • To start the installation, click Install Now. • When the installation is complete, click Close to close the Setup program. • On the After Installation page, click Next. • On the Finish Admin Install page, click Finish. The automated installation is a two part process. First, you must configure the Remote Desktop Services-enabled computer for install mode. Then, you must configure it for execute mode. Before you start, make sure that you have created a Setup customization (.msp) file and that you have configured the installation states for features and applications as recommended in the article. Run the Setup program from a network installation point that you have already created. To configure the Remote Desktop Services-enabled computer for install mode • Click Start, click Run, type Cmd, and then click OK. • At the command prompt, type the following command, and then press ENTER: Change user /install • Run the automated installation exactly as you would on a client computer. • When the automated installation is complete, configure the Remote Desktop Services-enabled computer for execute mode. To configure the Remote Desktop Services-enabled computer for execute mode • Click Start, click Run, type Cmd, and then click OK. • At the command prompt, type the following command, and then press ENTER: Change user /execute. Note With Interactive Installations, by default, the user name field is populated with the currently logged-on user’s information. This is also true for the user name that is set in the Config.xml file. Remote Desktop Services mirrors this registry key to HKLM Software Microsoft WindowsNT CurrentVersion TerminalServer Install Software Microsoft Office Common UserInfo. New users then receive the defaults from the HKLM UserInfo key in their own user profiles. Because a user name already exists, any new Remote Desktop Services users are not prompted to input their own names, and instead they get the default user name of the administrator. To resolve this issue for new users in a current Remote Desktop Services deployment, the administrator of the computer that is running Remote Desktop Services should remove values from the registry key HKLM Software Microsoft WindowsNT CurrentVersion TerminalServer Install Software Microsoft Office Common UserInfo. To resolve the issue for all users in a current Remote Desktop Services deployment, the administrator of the computer that is running Remote Desktop Services should perform one of the following tasks: • During installation, select Customize, and then clear the user name and initial values. ![]() ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
March 2018
Categories |