Example scenarios: Windows MultiPoint Server 2012 user accounts

  • Article

 

Applies To: Windows MultiPoint Server 2012

What do you need to do to implement the user account scenario that you chose for your Windows MultiPoint Server 2012 environment? The following tables describe each task to perform to configure user accounts and prepare stations for shared or individual user accounts on a stand-alone MultiPoint Server computer or on networked servers in a workgroup or an Active Directory domain. Choose the scenario that applies to your environment. Then follow the links in the table to complete each required configuration task.

Note


If you have not yet decided how to set up your user accounts, see Plan user accounts for your Windows MultiPoint Server 2012 environment for more information about how each choice affects users.

Single MultiPoint Server computer in a stand-alone environment (no network)

My users do not need to log on. The stations can be available to anyone who walks up to them. They do not need an individual Windows desktop experience that includes private folders for storing data or personalized desktops. 1. Create a single local user account (For instructions, see Create local user accounts in Windows MultiPoint Server 2012.)
2. Allow one account to have multiple sessions
3. Configure stations for automatic logon
My users can all share the same user logon. They do not need an individual Windows desktop experience that includes private folders for storing data or personalized desktops. 1. Create a single local user account (For instructions, see Create local user accounts in Windows MultiPoint Server 2012.)
2. Allow one account to have multiple sessions
My users must have their own individual Windows desktop experience. Create a local user account for each user (For instructions, see Create local user accounts in Windows MultiPoint Server 2012.)

Multiple MultiPoint Server computers on a network, but with no domain

My users do not need to log on. The stations can be available to anyone who walks up to them. They do not need an individual Windows desktop experience that includes private folders for storing data or personalized desktops. 1. Create a single local user account on each server. (For instructions, see Create local user accounts in Windows MultiPoint Server 2012.)
2. Allow one account to have multiple sessions on each server
3. Configure stations for automatic logon on each server
My users can all share the same user logon. They do not need an individual Windows desktop experience that includes private folders for storing data or personalized desktops. 1. Create a single local user account on each server. (For instructions, see Create local user accounts in Windows MultiPoint Server 2012.)
2. Allow one account to have multiple sessions on each server.
My users must have their own individual Windows desktop experience.

- Option A - My users will always use local stations connected to the same MultiPoint Server computer.
- Option B - My users will use local stations on more than one MultiPoint Server computer.
- Option C - My users will use remote clients on the LAN.		 - Option A - Create a single local user account on each server for the users of that server. (For instructions, see Create local user accounts in Windows MultiPoint Server 2012.)
- Option B - Create local user accounts for every user on every server. Note: This means that each user will have a profile on each server. In other words, if they save a file in My Documents while logged onto Server A’s station, they will not see the file when logging onto Server B’s station. (For instructions, see Create local user accounts in Windows MultiPoint Server 2012.)
- Option C - Assign each user to a specific MultiPoint Server computer. Create local user accounts for the assigned users on each server. (For instructions, see Create local user accounts in Windows MultiPoint Server 2012.)

One or more MultiPoint Server computers in a domain network environment

My users do not need to log on. The stations can be available to anyone who walks up to them. They do not need an individual Windows desktop experience that includes private folders for storing data or personalized desktops. 1. Create a domain account to log onto the servers.
2. Allow one account to have multiple sessions on each server.
3. Configure stations for automatic logon on each server.
My users can all share the same user logon. They do not need an individual Windows desktop experience that includes private folders for storing data or personalized desktops. 1. Create a domain account for a group or for each user.
2. Allow one account to have multiple sessions on each server.
My users must have their own individual Windows desktop experience.

- Option A - Any user with a domain account can use the MultiPoint Server computer.
- Option B - I want to limit which domain accounts can access the server.		 - Option A - No setup is required. By default, all domain users have access to any MultiPoint Server computer on the network.
- Option B - Limit the access of domain user accounts to the MultiPoint Server computer. For instructions, see [LINK TK].
I want to use local user accounts and manage them separately from my domain accounts. For example, you want someone to manage the MultiPoint server but not the domain or you do not want to give domain accounts to all MultiPoint Server users. Create one or more local user accounts on each server. (For instructions, see Create local user accounts in Windows MultiPoint Server 2012.)

 Note: This means that each user account will have a profile on each server. In other words, if they save a file in My Documents while logged onto Server A’s station, they will not see the file when logging onto Server B’s station.