Network Requirements for MultiPoint Server

MultiPoint Server can be deployed in a variety of network environments, and it can support both local user accounts and domain user accounts. Generally, MultiPoint Server user accounts will be managed in one of the following network environments:

  • Single-server with local user accounts

  • Multiple-server with local user accounts

  • Multiple-server with domain accounts

By definition, local user accounts can only be accessed from the computer on which they were created. In contrast, Domain user accounts are user accounts that reside on a domain controller and can be accessed from any computer connected to the domain. When deciding which type of network environment to use, some things to consider include the following:

  • Will resources be shared among servers?

  • Will users access database servers?

  • Will users access internal Web servers?

This section addresses user account management in these networking environments.

Single-Server with Local User Accounts

In single-server environments, the network requirements for MultiPoint Server may be as basic as a router and an Internet service provider (ISP). Network connections associated with a network adapter on MultiPoint Server are configured, by default, to obtain an IP address and DNS server address automatically. Internet routers are typically configured as DHCP servers, providing private IP addresses to computers that connect to them on the internal network. Therefore, a single MultiPoint Server may be able to connect to the internal interface of the router, obtain automatic IP information, and connect to the Internet, all without significant effort or configuration.

A common way to manage users in this kind of environment is to create a local user account for each person who will access the system. Local user accounts are user accounts that are created on a specific computer that is running MultiPoint Server. Anyone who has a user account on that computer can log on to MultiPoint Server from any station associated with it.

Multiple-Servers with Local User Accounts

Given that local user accounts are only accessible from the computer on which they were created, when you deploy MultiPoint Server in a multiple-server environment, you can manage user accounts in one of two ways: you can create user accounts for specific individuals on specific servers, or you can create individual accounts for every user on every server. For example, if you plan to assign users to a specific MultiPoint Server, you might create four local user accounts on Server A (user01, user02, user03, and user 04) and four user accounts on Station B (user05, user06, user07, and user08). However, whereas users 01-04 can log on to Server A from any station that is connected to Server A, they cannot log on to Server B, and vice versa.

If every user must be able to log on to any of the available MultiPoint Servers, a local user account must be created for each user on each computer that is running MultiPoint Server. Choosing to manage users in this manner, though, introduces certain complexities. For example, if user01 logs on to Server A on Monday and saves a file in his or her Documents folder, and then logs on to Server B on Tuesday, he or she will not be able to access the file saved in the Documents folder on Server A from the day before.

Note that creating local accounts for each user on every available MultiPoint Server involves additional complications. For example, if a person has a user account on both Server A and Server B, there is no way to automatically synchronize the passwords for each account. This can result in users having difficulty logging on should the account password be changed on one server, but not them all. You can simplify user account management in this kind of network environment by assigning each user to a single MultiPoint Server. This way, the user can log on to any of the stations that are associated with that computer and always have access to his or her files.

Multiple-Servers with Domain Accounts

Domain environments are common in large network environments that include multiple servers. For example, you might connect several MultiPoint Servers to a domain, and then use Microsoft® Active Directory® to manage user accounts that can be accessed from any computer in the domain. This allows for individual domain user accounts to be created and accessed from any station or server in the domain, regardless of which server the user is connected to.

When deploying MultiPoint Server in a domain environment, there are several factors to consider:

  • If domain accounts are used, they cannot be managed from MultiPoint 管理員.

  • By default, MultiPoint Server is configured to give each user permission to log on to only one computer at a time If you decide to let users log on to multiple stations at the same time, when they are using a single account, you must modify the Remote Desktop Services setting that will allow for multiple logons. For more information, see Configure the Number of Simultaneous Remote Connections Allowed for a Connection (

  • The location of domain controllers will affect the speed and reliability with which users will be able to authenticate with the domain and locate resources.