Enable file sharing in Windows MultiPoint Server 2012

Enable file sharing in Windows MultiPoint Server 2012
You can allow users on your Windows MultiPoint Server 2012 stations to share files in two ways:
If you have a file server on the network, it is recommended that you create a shared folder on the file server.
If you have a small network of 2-3 MultiPoint Server computers, with no dedicated file server, one of the MultiPoint Server computers can act as the file server for all the MultiPoint Server computers. Create a shared folder on that computer, and then create local user accounts for all users on that computer. The shared folder can be on the original internal drive, or you can attach additional internal or external drives to the computer.
System administration in Windows MultiPoint Server 2012
Before you start using your Windows MultiPoint Server 2012 system, it’s a good idea to do some basic system administration.
Note
For additional information about administering your system, see Help and Support for MultiPoint Manager. To open Help and Support, press F1 while working in MultiPoint Manager, or click the Help button in the top right corner of the window.
In this section
Configure Disk Protection in Windows MultiPoint Server 2012
Install Server Backup on your Windows MultiPoint Server 2012 computer
Configure sleep settings in Windows MultiPoint Server 2012
Configure group policies for a domain deployment
Configure Disk Protection in Windows MultiPoint Server 2012
Use the procedures in this topic to enable Disk Protection in Windows MultiPoint Server 2012 to protect your system volume from unintended updates, to schedule Windows Updates to be retained while Disk Protection is active, to temporarily disable Disk Protection, and to uninstall Disk Protection.
By enabling Disk Protection in Windows MultiPoint Server 2012, you can protect the system volume (the drive where Windows is installed—usually C:) from unwanted changes. When Disk Protection is enabled, changes made to the system volume are stored in a temporary location so that simply restarting the computer discards them and automatically returns the system to the previous known-good state.
The administrator can easily install software or make configuration changes by temporarily disabling disk protection. In order to keep the system current with Windows Updates and anti-malware definitions, Disk Protection schedules a maintenance window to download and install updates. The administrator can also provide a custom script to run during the maintenance window to accommodate any maintenance needs beyond Windows Update.
Enable Disk Protection
Before you enable Disk Protection, make sure all applications and drivers are installed and up to date, and move your user profiles to a volume that will not be protected. If you need to make manual updates after you enable Disk Protection, you can temporarily disable Disk Protection. However, it's easiest to get the system into an ideal state before Disk Protection is turned on.
To enable Disk Protection in Windows MultiPoint Server 2012
1. Log on to Windows MultiPoint Server 2012 as an administrator.
2. Before you enable Disk Protection:
Ensure the MultiPoint Server system is in exactly the state in which you want it to remain. For example, ensure that installed software, system settings, and updates are correct.
Move user profiles to a volume that is not protected, or set up a shared file location off the system volume as described in Enable file sharing in Windows MultiPoint Server 2012.
3. From the Start screen, open MultiPoint Manager.
4. Click the Home tab, click Enable disk protection, and then click OK.
|
When Disk Protection is enabled for the first time, the system is prepared by installing a driver and creating a cache file on the system volume. The cache file will temporarily store any changes made to the system volume while Disk Protection is active. Because system updates are stored in the cache file, they do not alter the protected contents of the volume outside the cache file. Each time the system starts, the cache file is reset, which discards any changes stored there since the previous system start. Thus, the system always starts in the same state as when Disk Protection was enabled.
Windows needs to update a few system files – including the system pagefile, crash dump location, and event logs. Those files are not discarded when Disk Protection is enabled. To accomplish this, a new volume named DpReserved is created when Disk Protection is enabled for the first time, and those files are moved to that volume. The DpReserved partition is not protected, so writes to those files persist through restarts, even when Disk Protection is enabled.
Schedule software updates
If Windows is configured to automatically install Windows Updates, Disk Protection allows these updates at the configured time, and does not discard the updates. For example, if Windows updates are scheduled for 3:00 a.m., Disk Protection checks for updates each day at 3:00 a.m. If any updates are found, MultiPoint Server temporarily disables Disk Protection, applies the updates, and then re-enables Disk Protection.
To schedule software updates in Windows MultiPoint Server 2012
1. In MultiPoint Manager, display the Home tab, and then click Schedule software updates.
2. In the Schedule Software Updates dialog box, click Update at, and select a time for updates - for example, 3:00 AM.
3. Select the Run Windows Update check box.
4. If your organization runs its own update script, select the Run the following program check box, and specify the location of your organization’s update script.
5. Select a maximum time to allow updates to run.
6. Under When finished, choose whether to have the system return to its previous power state or shut down after applying updates.
7. Click OK.
| Temporarily disable Disk Protection
If an administrator needs to install software, change system settings, or perform other maintenance tasks that involve system updates, they can temporarily disable Disk Protection. After the changes are made, re-enable Disk Protection. During system restarts, the system will retain its state when Disk Protection was enabled.
To disable disk protection
1. In MultiPoint Manager, click the Home tab.
2. On the Home tab, click Disable disk protection, and then click OK.
|
Note
Remember to re-enable Disk Protection after maintenance is complete. The system will not be protected again until the administrator explicitly re-enables Disk Protection.
Uninstall Disk Protection
Uninstalling Disk Protection removes the driver and the cache file, so you should only do this if you want to stop using Disk Protection long-term. If you simply want to perform maintenance or stop protection temporarily, use the Disable disk protection task instead.
You can uninstall Disk Protection whether it is enabled or disabled.
To uninstall Disk Protection
1. In MultiPoint Manager, click the Home tab.
2. On the Home tab, and click Uninstall disk protection, and then click OK.
After you click OK, the computer restarts. The uninstallation process requires several restarts, during which the driver and cache file are removed. The DpReserved partition remains, and the pagefile, crash dump location, and event log files remain configured to use the DpReserved partition.
| Install Server Backup on your Windows MultiPoint Server 2012 computer
It is recommended that you consider a backup and recovery plan for your MultiPoint Server. For more information on the backup and recovery tools available on MultiPoint Server, see Windows Server Backup Feature Overview (http://technet.microsoft.com/library/jj614621.aspx).
Configure MultiPoint Server Backup
A good backup and recovery plan is important for any size environment. Windows Server Backup is a feature in Windows Server 2012 that provides a set of wizards and other tools for you to perform basic backup and recovery tasks for the server on which it is installed. You can use Windows Server Backup to back up a full server (all volumes), selected volumes, the system state, or specific files or folders, and to create a backup that you can use to rebuild your system.
You can recover volumes, folders, files, certain applications, and the system state. And, for disasters like hard disk failures, you can rebuild a system either from scratch or by using alternate hardware. To do this, you must have a backup of the full server or just the volumes that contain operating system files and the Windows Recovery Environment. This restores your complete system onto your old system or onto a new hard disk.
A key feature of Windows Server Backup is the ability to schedule backups to run automatically.
Use the following procedures to set up the type of backup you require.
To install backup and recovery tools
1. From the Start screen, open Server Manager.
2. Click Add Roles and Features to start the Add Roles Wizard. Then click Next after you review the Before you begin notes.
3. Select the Role based or feature based installation option, and then click Next.
4. Select the local computer that you are managing, and click Next.
The Add Features Wizard opens.
5. On the Select Features page, expand Windows Server Backup Features, select the check boxes for Windows Server Backup and Command-line Tools, and then click Next.
Note
Or, if you just want to install the snap-in and the Wbadmin command-line tool, expand Windows Server Backup Features, and then select the Windows Server Backup check box only—make sure the Command-line Tools check box is clear.
6. On the Confirm Installation Selections page, review your choices, and then click Install.
If any errors occur during the installation, the Installation Results page will note the errors.
7. After the installation completes successfully, you should be able to access these backup and recovery tools:
To open the Windows Server Backup snap-in, on the Start screen, type backup, and then click Windows Server Backup in the results.
To start the Wbadmin tool and view syntax for its commands: On the Start screen, type command. In the results, right-click Command Prompt, click Run as administrator at the bottom of the page, and then click Yes at the confirmation prompt. At the command prompt, type wbadmin /? and press ENTER. You should see command syntax and descriptions for the tool.
|
To configure backups using Windows Server Backup
Follow the instructions in Backing Up Your Server.
|
Configure sleep settings in Windows MultiPoint Server 2012
To save energy on your Windows MultiPoint Server 2012 system, you can configure the server to hibernate or enter sleep mode when user sessions time out. You will need to configure several sleep settings on the MultiPoint Server computer, and update the Registry to configure the session timeout.
Configure sleep settings on the Windows MultiPoint Server 2012 computer
Update settings in power management to allow sleep mode:
Allow the computer to enter sleep mode when idle
Turn off the logon requirement when the computer wakes up
Enable the computer to hibernate
Allow the computer to enter sleep mode when idle
If you want the MultiPoint Server to go into sleep mode after it has been idle for a certain length of time, turn on the power management setting, as described in the following procedure.
To allow the computer to go to sleep
1. Log on to the MultiPoint Server computer as an administrator.
2. From the Start screen, open Control Panel.
3. In Control Panel, display Power Options. (Type power in the search box.)
4. In Power Options, click Change when the computer sleeps.
5. Under Put the computer to sleep, select the amount of time to allow the computer to remain idle before entering sleep mode, and then click Save Changes.
If this setting is not available, click Change settings that are currently unavailable, and then update the setting. This overrides the current setting in your preferred power plan.
| Turn off the logon requirement when the computer wakes up
If you turn on the power management setting to allow the computer to go to sleep, and the computer requires a password to wake it from sleep, your computer might not work and you might lose unsaved data. If this happens, you must restart the computer. To avoid this issue, turn off the requirement for a password when the computer wakes from sleep by completing the following procedure. If you have configured a screen saver, you might need to update the screen saver settings also.
To turn off the password requirement to wake the computer from sleep
1. In Control Panel, display Power Options, and then click Require a password on wakeup.
2. On the Define power buttons and turn on password protection page, in the Password protection on wakeup section, select Don’t require a password, and then click Save changes.
If this option is not available, click Change settings that are currently unavailable, and then change the setting. This overrides the default setting in your preferred power plan.
|
If you have configured a screen saver for the computer, use the following procedure to verify that the screen saver will not require a logon when the computer wakes from sleep.
To turn off the password-on-wakeup for a screen saver
1. In Control Panel, click Appearance and Personalization.
2. Under Personalization, click Change screen saver.
3. In the Screen Saver Settings dialog box, ensure that the On resume, display logon screen check box is not selected. Then click OK.
| Enable the computer to hibernate
By default, hibernate is disabled in Windows MultiPoint Server 2012. If you want to be able to turn on hibernation using the power button, after you enable hibernation, configure the power button to hibernate the computer when pressed.
To enable hibernation
1. Log on to the MultiPoint Server computer as an administrator.
2. Open a command prompt. (Hold down the Windows key, and press R to open the Run dialog box. Then type cmd, and press ENTER.)
3. At the command prompt, type: powercfg.exe –h on
|
To configure the power button on the computer to go to hibernate when pressed
1. In Control Panel, display Power Options, and then click Choose what the power buttons do.
2. Beside When I press the power button, select Hibernate.
Note
On some computers, you might see different options. For example, some computers allow different Hibernate settings when a computer is plugged in and when it is running off a battery.
3. Click Save changes.
| Configure a session time-out for idle user sessions
By default, the MultiPoint Server computer does not go to sleep if a user is logged on to any station, even if the user’s session has been idle for a while. MultiPoint Server does not automatically disconnect an idle session, which prevents the computer from entering sleep mode.
To enable sleep mode on a MultiPoint Server computer, update the registry to set a session idle time out interval.
Important
Directly editing the registry could make your MultiPoint Server computer inoperable. We strongly recommend that you back up the registry before you make any changes to it. You should only change values in the registry that you understand or are instructed to change by a source that you trust.
To set the SessionIdleTimeout registry key
1. To open the Registry Editor with elevated permissions:
a. On the Start screen, type cmd.
b. In the results, right click Command Prompt, and then click Run as an administrator at the bottom of the screen.
c. At the User Account Control prompt, click Yes.
d. At the command prompt, type Regedit, and press ENTER.
2. In the Registry Editor, navigate to HKEY_LOCAL_MACHINE\Software\Microsoft\Windows MultiPoint Server, and select the SessionIdleTimeout registry key.
If you do not see a SessionIdleTimeout registry key, add the registry key:
a. In the left pane, right-click Windows MultiPoint Server, click New, and then click DWORD (32-bit) Value.
b. In the key name, type SessionIdleTimeout, and then press ENTER.
3. Right-click the SessionIdleTimeout registry key, and then click Modify.
4. In the Edit dialog box, enter the amount of time, in milliseconds, to allow a user session to remain idle before the session is disconnected by MultiPoint Server, and then click OK.
5. Restart the computer to apply the changes.
|
Configure group policies for a domain deployment
To ensure that your domain deployment of MultiPoint Server works properly, apply the following group policy settings to the WMSshell user account on a MultiPoint Server system.
Important
Some group policy settings can prevent required configuration settings from being applied to MultiPoint Server. Be sure that you understand and define your group policy settings so that they work correctly on MultiPoint Server. For example, a Group Policy setting that prevents Autologon could present problems with MultiPoint Server logon behavior.
Update group policies for the WMSshell user account
Note
To find out how to update group policies, see Local Group Policy Editor (http://technet.microsoft.com/library/dn265982.aspx).
POLICY: User Configuration > Administrative templates > Control Panel > Personalization
Assign the following values:
Setting
|
Values
|
Enable screen saver
|
Disabled
|
Screen saver timeout
|
Disabled
Seconds: xxx
|
Password protect the screen saver
|
Disabled
|
POLICY: Computer Configuration >Windows Settings >Security Settings >Local Policies >User Rights Assignment > Allow log on locally
Setting
|
Values
|
Allow log on locally
|
Ensure that the list of accounts includes the WMSshell account.
Note: By default, the WMSshell account is a member of the Users group. If the Users group is in the list, and WMSshell is a member of the Users group, you do not need to add the WMSshell account to the list.
|
Important
When you set any group policies, make sure that the policies do not interfere with automatic updates and error Windows error reporting on the MultiPoint Server computer. These are set by the Install updates automatically and Automatic Windows Error Reporting settings that were selected during Windows MultiPoint Server installation, configured in MultiPoint Manager using Edit server settings, or configured in scheduled updates for Disk Protection.
Update the Registry
For a domain deployment of Windows MultiPoint Server 2012, you should update the following registry subkeys.
Important
Incorrectly editing the registry may severely damage your system. Before making changes to the registry, you should back up any valued data on the computer.
To update Registry subkeys for a domain deployment of Windows MultiPoint Server 2012
1. Open Registry editor. (At a command prompt, type regedit.exe, and press ENTER.)
2. In the left pane, locate and then select the following registry subkey:
HKEY_USERS\<SIDofWMSshell>\Software\Policies\Microsoft\Windows\Control Panel\Desktop
where <SIDofWMSshell> is the security identifier (SID) for the WMSshell account. To find out how to identify the SID, see How to Associate a Username with a Security Identifier (SID) (http://support.microsoft.com/kb/154599).
3. In the list on the right, update the following subkeys.
Subkey
|
Value name
|
Value data
|
ScreenSaveActive
|
REG_SZ
|
0 (zero)
|
ScreenSaveTimeout
|
REG_SZ
|
120
|
ScreenSaverIsSecure
|
REG_SZ
|
0 (zero)
|
To update a Registry subkey:
a. With the Registry key selected in the left pane, right-click the subkey in the right pane, and then click Modify.
b. In the Edit String dialog box, type a new value in Value data, and then click OK.
4. After you finish updating Registry subkeys, restart the computer to activate the changes.
|
Appendixes: Deploying Windows MultiPoint Server 2012
The appendixes provide additional resources to help with your Windows MultiPoint Server 2012 deployment.
In the appendixes
Task Lists: Deploying Windows MultiPoint Server 2012
Display language scenarios for Windows MultiPoint Server 2012
Glossary
Task Lists: Deploying Windows MultiPoint Server 2012
Use the task lists in this topic to help you’re the deployment of your Windows MultiPoint Server 2012 system and keep track of completed tasks. Not all tasks apply to every environment. For example, some tasks are performed only if you deploy MultiPoint Serer on an Active Directory domain. Others, such as creating split-screen stations or deploying virtual desktops for stations, are optional. For procedures that explain how to perform these tasks, see Deploying Windows MultiPoint Server 2012.
Task list: Deploy the server
Task
|
Description
|
1
|
Plan a Windows MultiPoint Server 2012 Deployment (http://technet.microsoft.com/library/jj916408.aspx)
|
2
|
Collect hardware and device drivers needed for the installation
|
3
|
Set up the physical computer and primary station
|
4
|
Install Windows MultiPoint Server 2012
|
5
|
Update and install device drivers if needed
|
6
|
Set the date, time, and time zone
|
7
|
Join the MultiPoint Server computer to a domain (optional) (MultiPoint Server 2012 Premium only)
|
8
|
Install updates
|
9
|
Attach additional stations to your Windows MultiPoint Server 2012 computer
|
10
|
Activate Windows MultiPoint Server 2012 and add CALs
|
11
|
Install software on your Windows MultiPoint Server 2012 system
|
Task list: Optional configurations
Task
|
Set up a split-screen station in Windows MultiPoint Server 2012
|
Add printers in Windows MultiPoint Server 2012
|
Enable access over a wireless LAN in Windows MultiPoint Server 2012
|
Create Windows 7 or Windows 8 Enterprise virtual desktops for stations
|
Change the display language in Windows MultiPoint Server 2012
|
Task list: Prepare your system for users
Task
|
Plan user accounts for your Windows MultiPoint Server 2012 environment
|
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
|
Task list: Server administration
Task
|
Configure Disk Protection in Windows MultiPoint Server 2012
|
Install Server Backup on your Windows MultiPoint Server 2012 computer
|
Configure sleep settings in Windows MultiPoint Server 2012
|
Configure group policies for a domain deployment
|
Display language scenarios for Windows MultiPoint Server 2012
This appendix describes how to mix languages in a multi-language installation of Windows MultiPoint Server 2012. Find out which language packs are fully localized, which are supported, and what to expect when the default system language or a user’s display language is not fully localized.
Note
To find out how to change the default system language or a user’s display language, see Change the display language in Windows MultiPoint Server 2012.
Which languages can I use?
Fully localized language packs - MultiPoint Server is available fully localized in the following languages. If you apply one of those language packs to the server, the MultiPoint Server Dashboard, MultiPoint Manager, and the desktop display the selected language.
Table: The 18 languages in which MultiPoint Server is fully localized
Arabic
|
German
|
Polish
|
Chinese Traditional
|
Hebrew
|
Portuguese (Brazil)
|
Chinese (Hong Kong SAR)
|
Hungarian
|
Portuguese (Portugal)
|
Chinese (Simplified)
|
Italian
|
Russian
|
English
|
Japanese
|
Spanish
|
French
|
Korean
|
Turkish
|
Important
Arabic and Hebrew are only available by applying a Windows Server 2012 Language Pack to another DVD language such as English. Complete DVD images of MultiPoint Server 2012 are available for all of the other languages.
Other supported language packs - Windows MultiPoint Server supports all the language packs that are available for Windows Server 2012. However, if you apply a language pack for which MultiPoint Server is not fully localized, the desktop displays the selected language, but the MultiPoint Server Dashboard and MultiPoint Manager display the default language for the MultiPoint Server system. For a list of available language packs, see Windows Server 2012 language packs (http://www.microsoft.com/oem/en/installation/downloads/Pages/Windows-Server-2012-Language-Packs.aspx?mtag=TW-P-S12#fbid=25o0epAptQN) in Microsoft’s OEM Partner Center.
Display language scenarios
When you change the language pack used by the MultiPoint Server system or a user account, the language displayed in different areas of the product depends on whether MultiPoint Server is fully localized in the selected language.
Simple Scenarios Apply a language pack that is one of the 18 MultiPoint Server languages
If you start with any language of Windows MultiPoint Server and apply a different language pack from the MultiPoint Server list of 18, MultiPoint Manager, the Multipoint Server Dashboard, and the desktop all display the new language.
Apply a language pack that is not one of the 18 MultiPoint Server languages
If you start with any language of MultiPoint Server and apply a language pack that is not one of the 18 MultiPoint Server languages, the desktop displays the new language, and MultiPoint Manager and the MultiPoint Server Dashboard display English.
Complex Scenarios Set a fully localized display language
If you install one of the 18 language packs for which MultiPoint Server is fully localized, and you set the MultiPoint Server system to use that language (that is, as the display language for a user account and also as the language of the Welcome screen and system accounts), as described in Change the display language in Windows MultiPoint Server 2012, MultiPoint Manager, the MultiPoint Dashboard, and the MultiPoint Server setup screens display the language that you installed and set.
Set a display language that is not fully localized
If you install a language pack for which MultiPoint Server is not fully localized, the language displayed in MultiPoint Manager and the MultiPoint Server setup screens might be English, depending on how you set the display language for the system. The following two scenarios describe this behavior:
Set the display language for the user account, and do not set the language for the Welcome screen and system accounts
If you set the display language for the user account to a language that is not one of the fully localized languages, but you do not set the language for the Welcome screen and system accounts, MultiPoint Manager and the MultiPoint Dashboard display English, and the MultiPoint Server setup screens display the language of the fully localized version of MultiPoint Server that you installed.
For example, if you installed the German version of MultiPoint Server and the Polish language pack, MultiPoint Manager and the MultiPoint Dashboard display English, and the MultiPoint Server setup screens display German.
Set the language for the Welcome screen and system accounts, and do not set the display language for the user account
If you set the language for the Welcome screen and system accounts to a language in which MultiPoint Server is not fully localized, but you do not set the display language for the user account, MultiPoint Manager displays the language of the fully localized version of MultiPoint Server that you installed, and the MultiPoint Server setup screens display English.
For example, if you installed the German version of MultiPoint Server and the Polish language pack, MultiPoint Manager will displays in German, and the MultiPoint Server setup screens will display in English.
Glossary
associate a station
To specify which monitor is used with which station and peripheral devices, such as a keyboard and mouse. For direct video connected stations, this is done by pressing a specified key on the station’s keyboard when prompted to do so. For USB zero client connected stations, this typically happens automatically.
|
bus-powered hub
A hub that draws all of its power from the computer’s USB interface. Bus-powered hubs do not need separate power connections. However, many devices do not work with this type of hub because they require more power than this type of hub provides.
|
console mode
One of the two MultiPoint Server modes. When the system is in console mode, no stations are available for use. Instead, all of the monitors are treated as a single extended desktop for the console session of the computer system. Console mode is typically used to install, update, or configure software, which cannot be done when the computer is in station mode. See also: station mode.
|
direct-video-connected station
A MultiPoint Server station that consists of a monitor that is directly connected to a video output on the server, and at a minimum, it includes a keyboard and mouse that are connected to the server through a USB hub.
|
domain user account
A user account that is hosted on a domain computer. Domain user accounts can be accessed from any computer that is connected to the domain, and they are not tied to any particular computer.
|
downstream hub
A hub that is connected to a station hub to add more available ports for station devices. A downstream hub must not have a keyboard attached to it.
|
externally powered hub
Also known as a self-powered hub, this hub takes its power from an external power supply unit; therefore, it can provide full power (up to 500 mA) to every port. Many hubs can operate as bus-powered or externally-powered hubs.
|
HID consumer control device
A Human Interface Device (HID) is a computer device that interacts directly with humans. It may take input from or deliver output to humans. Examples are keyboard, mouse, trackball, touchpad, pointing stick, graphics table, joystick, fingerprint scanner, gamepad, webcam, headset, and driving simulator devices. A HID consumer control device is a particular class of HID devices that includes audio volume controls and multimedia and browser control keys.
|
intermediate hub
A hub that is between a root hub on the server and a station hub. Intermediate hubs are typically used to increase the number of available ports for stations hubs or to extend the distance of the stations from the computer.
|
local user account
A user account on a specific computer. A local user account is available only on the computer where the account is defined.
|
multifunction hub
MultiPoint Server system
A collection of hardware and software that consists of one computer that is running MultiPoint Server and at least one MultiPoint Server station. For more information about system layout options, see MultiPoint Server Site Planning.
|
partition
A section of space on a physical disk that functions as if it is a separate disk.
|
primary station
The station that is the first to start up when MultiPoint Server is started. The primary station can be used by an administrator to access startup menus and settings. When it is not being used by the administrator, it can be used as a normal station (it does not have to be reserved exclusively for administration). The primary station’s monitor must always be connected directly to a video output on the computer that is running MultiPoint Server. See also: station.
|
RDP-over-LAN-connected station
A station that is a thin client, traditional desktop, or laptop computer that connects to MultiPoint Server by using Remote Desktop Protocol (RDP) through the local area network (LAN).
|
root hub
A USB hub that is built-in to the host controller on a computer’s motherboard.
|
split screen
A station where a single monitor can be used to display two independent user desktops. Two sets of hubs, keyboards, and mice are associated with a single monitor. One set is associated with the left side of the monitor, and the other set is associated with the right side of the monitor.
|
standard station
In contrast to the primary station, which can be used by an administrator to access startup menus, standard stations will not display startup menus, and they can only be used after MultiPoint Server has completed the startup process. See also: station.
|
station
User endpoint for connecting to the computer running MultiPoint Server. Three station types are supported: direct-video-connected, USB-zero-client-connected, and RDP-over-LAN-connected stations. For more information about stations, see MultiPoint Server Stations.
|
station hub
A USB hub that has been associated with a monitor to create a MultiPoint Server station. It connects peripheral USB devices to MultiPoint Server. See also: USB zero client and USB hub.
|
station mode
One of the two MultiPoint Server modes. Typically, the MultiPoint Server system is in station mode. When in station mode, the MultiPoint Server stations behave as if each station is a separate computer that is running the Windows operating system, and multiple users can use the system at the same time. See also: console mode.
|
USB hub
A generic multiport USB expansion hub that complies with the universal serial bus (USB) 2.0 or later specifications. Such hubs typically have several USB ports, which allows multiple USB devices to be connected to a single USB port on the computer. USB hubs are typically separate devices that can be externally powered or bus-powered. Some other devices, such as some keyboards and video monitors, may incorporate a USB hub into their design. See also: USB zero client.
|
USB over Ethernet zero client
A USB zero client that connects to the computer through a LAN connection rather than a USB port. This client appears to the server as a USB device even through the data is sent through the Ethernet connection.
|
USB zero client
An expansion hub that connects to the computer through a USB port and enables the connection of a variety of non-USB devices to the hub. USB zero clients are produced by specific hardware manufacturers, and they require the installation of a device-specific driver. USB zero clients support connecting a video monitor (through VGA, DVI, and so on), and peripherals (through USB, sometimes PS/2, and analog audio). The USB zero client can be externally powered or bus-powered. See also, USB hubs.
|
USB zero client connected station
A MultiPoint Server station that consists of (as a minimum) a monitor, keyboard, and mouse, which are connected to the server through a USB zero client.
|
|