- Desktop all users windows 2012
- ALLUSERS property
- Example
- Default Value
- Recommended hotfixes and updates for Remote Desktop Services in Windows Server 2012 R2
- Summary
- Prerequisites
- Updates and hotfixes for Remote Desktop Connection Brokers
- Updates and hotfixes for Remote Desktop Gateway
- Updates and hotfixes for Remote Desktop Licensing
- Updates and hotfixes for Remote Desktop Session Hosts
- Updates and hotfixes for Remote Desktop Virtualization Hosts
- Updates and hotfixes for Remote Desktop Web Access
- Remote Desktop clients (mstsc.exe)
Desktop all users windows 2012
Сообщения: 26992
Благодарности: 7877
Там рядом есть ещё одна символическая ссылка «Все пользователи», которая ссылается туда же, на «C:\ProgramData». И когда Вы входите в «папку» «C:\Users\All Users» — на самом деле Вы находитесь в каталоге «C:\ProgramData».
Теперь, если мы посмотрим хоть по связи «C:\Users\All Users», хоть в каталоге «C:\ProgramData» (смотреть-то мы будем в одно и то же место), мы увидим, что там отсутствует как каталог «Desktop», так и каталог «Рабочий стол». Вместо этого там присутствуют две связи каталогов с такими же именами, которые обе ссылаются обратно на (Сюрприз! Сюрприз! 
) каталог «C:\Users\Public\Desktop»:
Потому, когда Вы смотрите в Проводнике что в «C:\Users\All Users\Desktop», что в «C:\Users\All Users\Рабочий стол» — Вы видите содержимое каталога «C:\Users\Public\Desktop».
Кроме вышеуказанных связей в «C:\Users\All Users» («C:\ProgramData») Вы можете увидеть ещё кучу связей аналогичного назначения: пары Documents/Документы, Favorites/Избранное, Start Menu/Главное меню, Templates/Шаблоны. Все они так же будут ссылаться на другие каталоги, первые две пары — внутрь каталога «C:\Users\Public», а две последние — внутрь каталога «C:\ProgramData\Microsoft\Windows».
Красиво, правда 
?
ALLUSERS property
The ALLUSERS property configures the installation context of the package. The Windows Installer performs a per-user installation or per-machine installation depending on the access privileges of the user, whether elevated privileges are required to install the application, the value of the ALLUSERS property, the value of the MSIINSTALLPERUSER property and the version of the operating system.
The value of the ALLUSERS property, at installation time, determines the installation context.
An ALLUSERS property value of 1 specifies the per-machine installation context.
An ALLUSERS property value of an empty string («») specifies the per-user installation context.
If the value of the ALLUSERS property is set to 2, the Windows Installer always resets the value of the ALLUSERS property to 1 and performs a per-machine installation or it resets the value of the ALLUSERS property to an empty string («») and performs a per-user installation. The value ALLUSERS=2 enables the system to reset the value of ALLUSERS, and the installation context, dependent upon the user’s privileges and the version of Windows.
Windows 7: Set the ALLUSERS property to 2 to use the MSIINSTALLPERUSER property to specify the installation context. Set the MSIINSTALLPERUSER property to an empty string («») for a per-machine installation. Set the MSIINSTALLPERUSER property to 1 for a per-user installation. If the package has been written following the development guidelines described in Single Package Authoring, users having user access can install into the per-user context without having to provide UAC credentials. If the user has user access privileges, the installer performs a per-machine installation only if Admin credentials are provided to the UAC dialog box.
Windows Vista: Set the ALLUSERS property to 2 and Windows Installer complies with User Account Control (UAC). If the user has user access privileges, and ALLUSERS=2, the installer performs a per-machine installation only if Admin credentials are provided to the UAC dialog box. If UAC is enabled and the correct Admin credentials are not provided, the installation fails with an error stating that administrator privileges are required. If UAC is disabled by the registry key, group policy, or the control panel, the UAC dialog box is not displayed and the installation fails with an error stating that administrator privileges are required.
Windows XP: Set the ALLUSERS property to 2 and Windows Installer performs a per-user installation if the user has user access privileges.
If the value of the ALLUSERS property does not equal 2, the Windows Installer ignores the value of the MSIINSTALLPERUSER property.
Example
Default Value
The recommended default installation context is per-user. If ALLUSERS is not set, the installer does a per-user installation. You can ensure the ALLUSERS property has not been set by setting its value to an empty string («»), ALLUSERS=»».
Recommended hotfixes and updates for Remote Desktop Services in Windows Server 2012 R2
This article describes the hotfixes and updates that are currently available for Remote Desktop Services in Microsoft Windows Server 2012 R2.
Original product version: В Windows Server 2012 R2
Original KB number: В 3147099
Summary
This article describes the currently available fixes that are highly recommended for Remote Desktop Services in Windows Server 2012 R2 environments. These fixes have prerequisites for all Remote Desktop Services roles, and they apply to the following areas for Remote Desktop Services 2012 R2:
- Remote Desktop Connection Brokers
- Remote Desktop Gateway
- Remote Desktop Licensing
- Remote Desktop Session Hosts
- Remote Desktop Virtualization Hosts
- Remote Desktop Web Access
Additional Remote Desktop client information is introduced:
- RDP 8.1 updates for Windows 7
- RDP 8.1 and 8.0 new features
We recommend that you install these fixes to ensure the highest level of reliability.
Prerequisites
Before you install the hotfix for any Remote Desktop Services role, you must have the following updates installed.
| Date the update was added | Related Knowledge Base article | Title | Component | Why we recommend this update |
|---|---|---|---|---|
| Ongoing | Any remaining Windows updates | N/A | Multiple | The most recent Windows updates and fixes outside of normal security updates, in addition to the rollup packages that are listed in this table. |
| December 2014 | 3013769 | December 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 | Multiple | An update rollup package that resolves issues and includes performance and reliability improvements. Available from Windows Update and for individual download from the Microsoft Download Center. To apply this update, you must first install the update 2919355 on Windows Server 2012 R2. |
| November 2014 | 3000850 | November 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 | Multiple | A cumulative update that includes the security updates and non-security updates (including for Remote Desktop Services) that were released between April 2014 and November 2014. Available from Windows Update and for individual download from the Microsoft Download Center. To apply this update, you must first install the update 2919355 on Windows Server 2012 R2. |
Updates and hotfixes for Remote Desktop Connection Brokers
See the prerequisites table before you install any update or hotfix for this server role.
| Date the update was added | Related Knowledge Base article | Title | Component | Why we recommend this update |
|---|---|---|---|---|
| November 2015 | 3091411 | User connection fails when many connections are made to Windows Server 2012 R2-based RD Connection Broker | Multiple | This rollup contains the following improvements:
|
| December 2014 | 3020474 | Communication issues occur when Remote Desktop Connection Broker connects to SQL Server in Windows Server 2012 R2 | script | If you are using RD Connection Broker High Availability, make sure that you watch for the security events that are described in the Knowledge Base article that indicate communication issues between the RD Connection Brokers and SQL Server. You have to enable auditing for failure events by using the script auditpol /set /subcategory:»Filtering Platform Connection» /success:disable /failure:enable |
This script unblocks only UDP port 1434 from a Windows level. If you have a network device that also blocks this port, you must unblock at this level, too.
Updates and hotfixes for Remote Desktop Gateway
See the prerequisites table before you install any update or hotfix for this server role.
| Date the update was added | Related Knowledge Base article | Title | Component | Why we recommend this update |
|---|---|---|---|---|
| March 2016 | 3123913 | Remote Desktop Gateway server crashes during certain user disconnect scenarios in Windows Server 2012 R2 | aaedge.dll | Latest version of Aaedge.dll that resolves several issues in which the RD Gateway service crashes and causes user disconnections. Also includes 3042843. |
Updates and hotfixes for Remote Desktop Licensing
See the prerequisites table before you install any update or hotfix for this server role.
| Date the update was added | Related Knowledge Base article | Title | Component | Why we recommend this update |
|---|---|---|---|---|
| March 2016 | 3108326 | Licensing servers become deadlocked under high load in Windows Server 2012 R2 | lserver.dll | Latest version of Lserver.dll that resolves an issue in which multiple RD Licensing servers crash or restart on high load. Any RDSH that is configured in Per-Device mode would refuse all connections requests while their LS is in this state. Also includes 3092695 and 3084952. |
| January 2015 | 3013108 | RDS License Manager shows no issued free or temporary client access licenses in Windows Server 2012 R2 | licmgr.exe | Latest version of Licmgr.exe that fixes an issue in which the RDS License Manager shows no issued free or temporary client access licenses in Windows Server 2012 R2. |
Updates and hotfixes for Remote Desktop Session Hosts
See the prerequisites table before you install any update or hotfix for this server role.
| Date the update was added | Related Knowledge Base article | Title | Component | Why we recommend this update |
|---|---|---|---|---|
| April 2016 | 3146978 | RDS redirected resources showing degraded performance in Windows 8.1 or Windows Server 2012 R2 | Multiple | This update resolves slow RDP performance issues when you use redirected resources (drives, printers, and ports). |
| December 2015 | 3127673 | Stop error 0x000000C2 or 0x0000003B when you’re running Remote Desktop Services in Windows Server 2012 R2 | win32k.sys & dxgkrnl.sys | This article describes a hotfix package that fixes a problem that causes Windows Server 2012 R2 to crash when you’re running Microsoft Remote Desktop Services (RDS). |
| October 2015 | 3103000 | RemoteApp windows disappear and screen flickers when you switch between windows in Windows 8.1 or Windows Server 2012 R2 | rdpshell.exe | This update contains the latest RemoteApp server side components (mainly Rdpinit.exe/Rdpshell.exe) and includes all other RemoteApp section fixes that are listed in 2933664. |
There may also be fixes on the client side for RemoteApp. These fixes are listed again in 2933664 in the Remote Desktop Client section.
Updates and hotfixes for Remote Desktop Virtualization Hosts
See the prerequisites table before you install any update or hotfix for this server role.
| Date the update was added | Related Knowledge Base article | Title | Component | Why we recommend this update |
|---|---|---|---|---|
| November 2015 | 3092688 | UPD profiles corrupted when a network connectivity issue occurs in Windows Server 2012 R2 | sessenv.dll | Latest version of Sessenv.dll. This update resolves an issue in which UPDs become corrupted when network connectivity issue occurs. |
If the VDI guest VMs are running Windows 8.1, you must also install this within the guest virtual machines.
Updates and hotfixes for Remote Desktop Web Access
See the prerequisites table before you install any update or hotfix for this server role.
| Date the update was added | Related Knowledge Base article | Title | Component | Why we recommend this update |
|---|---|---|---|---|
| November 2015 | 3069129 | Blank page is displayed when you try to access RemoteApps on a Windows-based RD Web Access server | Multiple | Resolves an issue in which the RD Web Access server displays a blank web page if the number of published RemoteApps is greater than 999. Also includes the update 2957984. |
Remote Desktop clients (mstsc.exe)
RDP 8.1 updates for Windows 7
These fixes update the Remote Desktop Services server-side roles and components that are built around Remote Desktop Protocol (RDP) 8.1. However, although updates are performed on the server-side infrastructure, the Remote Desktop Clients are often left untouched. This can cause performance and reliability issues. By default, older clients such as Windows 7 Service Pack 1 (SP1) are restricted to RDP 7.1 and do not provide the new features and improvements that are available in RDP 8.1. Therefore, we have released the RDP 8.1 client for Windows 7 to provide significant performance and reliability improvements when these clients are connected to RDS 2012 R2 environments. To enable RDP 8.1 on Windows 7, follow these steps:
Verify which version of RDP you’re using. To do this, start the Remote Desktop Connection client program (mstsc.exe), click the small Remote Desktop icon in the top-left corner of the application dialog box, and then select About. Verify that the About message indicates Remote Desktop Protocol 8.1 supported.
If the About message indicates Remote Desktop Protocol 7.1 supported, install the following updates for RDP 8.1:
2574819: An update is available that adds support for DTLS in Windows 7 SP1 and Windows Server 2008 R2 SP1
2857650: Update that improves the RemoteApp and Desktop Connections features is available for Windows 7
2830477: Update for RemoteApp and Desktop Connections feature is available for Windows
2913751: Smart card redirection in remote sessions fails in a Windows 7 SP1-based RDP 8.1 client
2923545: Update for RDP 8.1 is available for Windows 7 SP1.31255
3125574: Convenience rollup update for Windows 7 SP1 and Windows Server 2008 R2 SP1
Install any outstanding Windows Updates.
RDP 8.1 and RDP 8.0 new features
For a list of features that were introduced in RDP 8.0, see Remote Desktop clients.
