Export (0) Print
Expand All

Deploying Microsoft Project Server for Users in Distributed Geographic Locations

Archived content. No warranty is made as to technical accuracy. Content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.
Published: March 1, 2003

Microsoft Corporation

Applies to:
Microsoft Project Server 2002
Microsoft Project Professional 2002
Microsoft Project Web Access 2002

Summary Learn how to effectively deploy Microsoft Project Server so that everyone can use Microsoft Project Professional and Microsoft Project Web Access to access Microsoft Project Server data. (4 printed pages)

If your organization has users in multiple geographic locations, you can still effectively deploy Microsoft® Project Server so that everyone can use Microsoft Project Professional and Microsoft Project Web Access to access Microsoft Project Server data. Microsoft Project Server can be deployed to a single domain or spread out across multiple domains. All domain-level deployments rely on wide area network (WAN) links to connect the servers. In addition, Terminal Services can be used to provide access to the Microsoft Project Server database for users who are experiencing slow connections to the server or for users who need to access the server from outside of the domain.

Note: For more information about deploying Terminal Services with Microsoft Project Server, see the Using Terminal Services to Connect Microsoft Project Professional to Microsoft Project Server article.

There are several scenarios for deploying Microsoft Project Server for organizations that have users distributed across multiple geographic locations, ranging from placing all Microsoft Project Server components in a single domain to distributing Microsoft Project Server components across domains.

On This Page

A Single-Domain Deployment with Users in Multiple Geographic Locations
A Multi-Domain Network with Microsoft Project Server Components Deployed in a Single Domain and Users in Multiple Geographic Locations
A Multi-Domain Network with Microsoft Project Server Components Deployed in Multiple Domains and Users in Multiple Geographic Locations
Deployment and Support Guidelines

A Single-Domain Deployment with Users in Multiple Geographic Locations

When Microsoft Project Server is deployed in a single network domain, users anywhere in the domain will be able to connect to Microsoft Project Server using either Microsoft Project Professional or Microsoft Project Web Access. In the example illustrated below, all servers and components related to Microsoft Project Server are deployed to the same data center and WAN links exist between domains. However, users in any domain will be able to connect to Microsoft Project Server using a WAN link and all users, including mobile users, will be able to connect to Microsoft Project Server using Terminal Services.

Cc751420.wan_msp01(en-us,TechNet.10).gif

Figure 1: Microsoft Project Server deployed to a single data center in a single domain. Users can access Microsoft Project Server using WAN links or Terminal Services.

A Multi-Domain Network with Microsoft Project Server Components Deployed in a Single Domain and Users in Multiple Geographic Locations

In an organization with multiple network domains, Microsoft Project Server components can be deployed to a single domain, yet still be available to users in other domains. In the example illustrated below, servers and components related to Microsoft Project Server are deployed to a single domain (represented only by the Microsoft Project Server server icon for illustration purposes) and WAN links exist between domains. Users in one domain will be able to connect to Microsoft Project Server components located in other domains using a WAN link connection (implied in the illustration) as long as a trust relationship exists between the domains. Users will also be able to connect to Microsoft Project Server using Terminal Services.

Cc751420.wan_msp02(en-us,TechNet.10).gif

Figure 2: Microsoft Project Server deployed to a single data center in a single domain. Users can access Microsoft Project Server using WAN links or Terminal Services.

A Multi-Domain Network with Microsoft Project Server Components Deployed in Multiple Domains and Users in Multiple Geographic Locations

In a multi-domain network, you can deploy servers related to Microsoft Project Server in multiple domains. When deploying across multiple domains, the following server pair combinations must occur:

  • The server running the Microsoft Project Server IIS components and the server running SharePoint™ Team Services from Microsoft must be in the same domain.

  • The server running the Microsoft Project Server database and all Terminal Services servers used to provide access to Microsoft Project Server should be in the same domain.

  • Analysis Services can be placed in any domain.

In the example illustrated below, servers and components related to Microsoft Project Server are deployed to multiple domains and WAN links exist between domains; however, users are able to access Microsoft Project Server from any domain. Users in one domain will be able to connect to Microsoft Project Server components located in other domains using a WAN link connection as long as a trust relationship exists between the domains. Users will also be able to connect to Microsoft Project Server using Terminal Services.

Cc751420.wan_msp03(en-us,TechNet.10).gif

Figure 3: Microsoft Project Server deployed across multiple domains. Users can access Microsoft Project Server using WAN links or Terminal Services.

Deployment and Support Guidelines

The following list describes some support issues you should consider when deploying Microsoft Project Server in an environment where users will need to connect to Microsoft Project Server using a WAN link or a Terminal Services server:

  • Monitoring Use System Monitor to analyze network performance, including network interface cards, routers, and hubs to ensure optimal performance. Microsoft Project Professional sends groups of smaller packets over the network. This is due to the nature of a project file and the number of tasks, assignments, and resources associated with the file. If users of Microsoft Project Professional are experiencing slow connection times when interacting with Microsoft Project Server, consider adding a Terminal Services server (see below).

    Note: Network Monitor is a utility that included with Systems Management Server (SMS). A lite version is also included with Microsoft Windows 2000 Server.

  • Running Terminal Services Terminal Services clients can be run from many locations, including remote desktops, by logging on to a Terminal Services server and accessing Microsoft Project Professional directly, by logging on to Terminal Services using the Terminal Service client included with Windows XP, or by logging on to a Terminal Services server using Remote Desktop Connection Web, which is a Web-based Terminal Services client that is available as part of the Terminal Services Advanced Client. Any user with access to Internet Explorer and the ability to download Microsoft ActiveX® controls will be able to access Terminal Services using Remote Desktop Connection Web. For more information about deploying Terminal Services with Microsoft Project Server, see the Using Terminal Services to Connect Microsoft Project Professional to Microsoft Project Server article.

  • Network Bandwidth WAN link connections should be at least 10 Mbps. If your connections are under 10 Mbps, then Terminal Services should be deployed to provide a way around the slow network connection.

  • Establishing trust between domains Two-way trust is automatically created between domains if Active Directory® is implemented and both domains reside in the same forest (or collection of Active Directory domains). Two-way trust must be created if the domains do not reside in the same forest or if one of the domains is running Windows NT 4.0.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft