See Also
Windows Multipoint Server 2012 - Creating Virtual Desktop Stations – Part 1
Windows Multipoint Server 2012 - Creating Virtual Desktop Stations – Part 2
Change the display language in Windows MultiPoint Server 2012
Windows MultiPoint Server 2012 supports multi-language installations. Each user can choose their preferred desktop language, and they can see that language on any station that they log on to, even if that station is shared by more than one user. By default, new users pick up the language and location of MultiPoint Server.
MultiPoint Server is fully localized in 18 languages, and supports all language packs that are available for Windows Server 2012, although the level of support is more limited for languages for which MultiPoint Server is not fully localized. For a list of available languages, and information about the interplay between fully localized language packs and supported language packs in various display language scenarios, see Display language scenarios for Windows MultiPoint Server 2012.
Setting the display language
After MultiPoint Server is installed, you can change the display language for MultiPoint Server and for individual users. By default, new users pick up the language and location of MultiPoint Server. After you install a language pack for one user, it is available to all users.
The language for the MultiPoint Server system and for an individual user is determined by different settings in Control Panel:
System display language - Update Region settings on the server to set the display language for the Welcome screen and logon screens, and the default language for new user accounts.
User’s primary language - To change the display language of the menus and dialog boxes that a specific user sees, log on as that user, and update Languages settings.
 To change the system display language for Windows MultiPoint Server 2012
1. If disk protection is enabled, disable it before you make these changes:
a. From the Start screen, open MultiPoint Manager.
b. On the Home tab, click Disable disk protection, and then click OK.
c. When the computer restarts, log on as Administrator.
 Important
If you make these changes when disk protection is enabled, your changes will be discarded the next time the computer restarts.
2. On the Start screen, type Region. On the Search pane, click Settings. Then click Region in the search results on the left side of the page.
3. Click the Administrative tab, and then click Copy Settings.
4. In the Region dialog box, confirm that the display language, input language (for the keyboard), and location under Current user are the ones that you want to apply to the system.
5. To apply your settings to the MultiPoint Server system, select the Check the Welcome screen and system accounts check box
6. To make your settings the default settings for new user accounts, select the New user accounts check box.
7. Click OK.
8. Turn disk protection back on (recommended). On the Home tab of MultiPoint Manager, click Enable disk protection. The computer restarts automatically, and the updates are applied.
-Or-
If you do not want to enable disk protection, restart the computer to apply the updates.
|
To change a user’s primary language
1. Log on to a station with the account that the person uses in MultiPoint Server.
2. On the Start screen, type Language. Under Search, click Settings In the Settings results on the left, click Language.
3. Use Add a language to add the language that the user needs to use.
4. To make the language the user’s primary language, move it to the top of the list.
| Prepare your Windows MultiPoint Server 2012 system for users
After you install and configure Windows MultiPoint Server 2012, and perform any additional configuration and hardware setups, you are ready to give users access to the system. You will need to plan and create user accounts. In some environments, you also need to configure stations for auto-logon and allow multiple sessions for your shared user accounts. And you need to decide how to set up file sharing for your users. All of these topics are covered in this section.
 Note
After you create your user accounts and make the other configuration updates to prepare for users, we recommend that you turn on Disk Protection so that no user can inadvertently make changes to system files and settings. For more information, see Configure Disk Protection in Windows MultiPoint Server 2012.
In this section
Plan user accounts for your Windows MultiPoint Server 2012 environment
Example scenarios: Windows MultiPoint Server 2012 user accounts
Create local user accounts in Windows MultiPoint Server 2012
Limit users' access to the server in MultiPoint Server 2012
Configure stations for automatic logon
Allow one account to have multiple sessions
Enable file sharing in Windows MultiPoint Server 2012
Plan user accounts for your Windows MultiPoint Server 2012 environment
The best way to implement user accounts in Windows MultiPoint Server 2012 depends on the size and complexity of your deployment:
Local user accounts - For a small deployment with only a few computers running Windows MultiPoint Server 2012 and few users, you might find it most convenient to use local user accounts that are created on the MultiPoint Server computer. You can create an individual account for each person who will use the system, or create a generic account for each station, which anyone can use to log on. MultiPoint Server administrators create and manage local user accounts by using MultiPoint Manager. The local accounts can be administrators, have limited administrative rights, or be regular users with no access to the MultiPoint Server Desktop or MultiPoint Manager.
Domain accounts - If your environment has many computers running MultiPoint Server and many users, you probably will find it more useful to set up an Active Directory Domain Services (AD DS) domain and use domain user accounts, which enable a user to access her own user profile and settings from any station in the domain. Domain user accounts must be created on the domain controller by a domain administrator.
Note
The following sections discuss scenarios that you might implement for local user accounts in Windows MultiPoint Server 2012. If you are using domain user accounts, see the “One or more MultiPoint Server computers in a domain network environment” scenario in Example scenarios: Windows MultiPoint Server 2012 user accounts. For information about setting up domain user accounts in Active Directory Domain Services (AD DS), see Create a New User Account (http://technet.microsoft.com/library/dd861308.aspx).
Planning local user accounts
The following sections consider the advantages, disadvantages, and requirements for several ways to implement individual or shared local user accounts in your Windows MultiPoint Server 2012 environment.
When creating local user accounts, you have the option of assigning each student to a particular computer running MultiPoint Server and creating a single account for each student. Alternatively, you might want to create an individual account for each student on every available computer running MultiPoint Server. A key advantage of implementing individual user accounts is that each user has his or her own Windows desktop experience that includes private folders for storing data. There are two approaches to creating individual local user accounts with MultiPoint Server: assign each user to a specific computer running MultiPoint Server, and then create an individual account for each user only on the computer to which they have been assigned; or, create local user accounts for all users on every computer running MultiPoint Server.
From a system management perspective, assigning users to a specific MultiPoint Server computer might be more convenient. For example, if you have two computers running MultiPoint Server with five stations each, you might create local user accounts as illustrated in the following table.
Table 1: Assigning local user accounts to specific computers running MultiPoint Server
Computer A
|
Computer B
|
UserAccount_01
|
UserAccount_06
|
UserAccount_02
|
UserAccount_07
|
UserAccount_03
|
UserAccount_08
|
UserAccount_04
|
UserAccount_09
|
UserAccount_05
|
UserAccount_10
|
In this scenario, each user has a single account on a particular computer. Therefore, everyone who has a local account on Computer A can log on to her or his account from any station associated with Computer A. However, these users cannot access their accounts if they use a station associated with Computer B, and vice versa. An advantage to this approach is that, by always connecting to the same computer, users can always find and access their files.
In contrast, it is also possible to replicate individual user accounts on all computers running MultiPoint Server, as illustrated in the following table.
Table 2: Replicating user accounts on all computers running MultiPoint Server
Computer A
|
Computer B
|
UserAccount_01
|
UserAccount_01
|
UserAccount_02
|
UserAccount_02
|
UserAccount_03
|
UserAccount_03
|
UserAccount_04
|
UserAccount_04
|
UserAccount_05
|
UserAccount_05
|
An advantage of this approach is that users have a local user account on every available computer running MultiPoint Server. However, the disadvantages might outweigh this advantage. For example, even if the user name and password for a particular person are the same on both computers, the accounts are not linked to each other. Therefore, if a user logs on to his or her account on Computer A on Monday, saves a file, and then logs on to his or her account on Computer B on Tuesday, he or she will not be able to access the file previously saved on Computer A. Additionally, replicating user accounts on multiple computers increases the administrative overhead and storage requirements.
If your MultiPoint Server system is not connected to a domain, and you do not want to create an individual account for each user, you can create generic accounts for each station. For example, if you have two computers running MultiPoint Server, and five stations are associated with each computer, you might decide to create user accounts similar to those shown in the following table.
Table 3: Creating generic user accounts, one account per station
Computer A
|
Computer B
|
Computer_A-Station_01
|
Computer_B-Station_01
|
Computer_A-Station_02
|
Computer_B-Station_02
|
Computer_A-Station_03
|
Computer_B-Station_03
|
Computer_A-Station_04
|
Computer_B-Station_04
|
Computer_A-Station_05
|
Computer_B-Station_05
|
In this scenario, every station account has the same password, and both the passwords and generic user account names are available to all users. An advantage to this approach is that the overhead of managing user accounts is likely to be less than if using individual accounts, because there typically are fewer stations than users. Additionally, the overhead caused by replicating user accounts on every server is eliminated.
Another option is to create generic accounts on each server. Every user logs on to a server as the same account. To allow this, you must enable multiple sessions per account. You can further simplify by using the same account name and password on all servers. This simplifies logon for the users, who need only know one account name and password to use any station on any server. It should be noted that in this scenario all users can see any change that any user makes. For example, if a file is saved to the desktop, all users can see the file.
Important
It is important to understand that when users share a user account, either one per server or one per station, files saved on the server – even files saved in My Documents - are not private. Any user who logs on with the account has access to those files. When you use one account per station, if a user saves files to My Documents on one station, the user does not have access to those files on a different station. The same occurs when logging on to different MultiPoint Server computers.
To enable users to access their files from any station, you can use a file server, create a file share for each user account, or let users store their personal documents on a USB flash drive or other private storage device. Individual USB flash drives enable individual users to store private documents even if they are sharing a user account in MultiPoint Server.
|
