Applies to: Office 2010 Topic Last Modified: 2011-07-15 If you plan to deploy Microsoft Office 2010 in a Remote Desktop Services environment (formerly known as Terminal Services), review the best practices and recommended guidelines that are in this article. Remote Desktop Services is a server role in Windows Server 2008 R2. It provides technologies that enable users to access session-based desktops, virtual machine-based desktops, or applications in the datacenter from both inside a corporate network and from the Internet. In this article: • • •. To function correctly, remote Desktop Services must be deployed with Microsoft Office a volume license key. In the 2007 Microsoft Office system, installations could be completed on an operating system that had Remote Desktop Services configured, even if a non-volume license key (for example, retail) was used. Piano Exercises For Dummies Download.

However, when users started an application, they were presented with the following message: “This copy of Microsoft Office Program cannot be used on Terminal Server. Nq Mobile Vault Download Apk. Please contact your local authorized Microsoft retailer for more information.” In Office 2010, a setup time check is introduced. If the permissions that are associated with the product key do not allow for Remote Desktop Services, the Setup program is blocked immediately, which indicates that the SKU is not supported on the computer that is running Remote Desktop Services. You can run Office 2010 on a computer that is running Windows Server 2003 R2, Windows Server 2008, or Windows Server 2008 R2.

You cannot install or run Office 2010 on a server operating system that was released earlier than Windows Server 2003. Deploying Office 2010 on Remote Desktop Services requires a review of the design changes in Office 2010, and a review of the server requirements, depending on the version of Windows Server (2003 or 2008) that you intend to use. Because the current server hardware can support multiple concurrent sessions, performance may be greatly affected. Processor and memory requirements vary, depending on the workload. The following table shows the results of some recent tests. Windows Server version Core processor Memory Concurrent sessions Windows Server 2008 32 256 GB 1140 Windows Server 2008 16 256 GB 860 Windows Server 2003 4 16 GB 150 You can configure Remote Desktop Services to load balance on a Remote Desktop Session Host (RD Session Host) server farm if your customers need that functionality. As Windows Server 2003 RD Session Host server capacity and scaling shows, the number of concurrent sessions depends on many factors, such as workload and configuration.