You cannot use remote assistance after using the mandatory configuration file.

I haven't updated my blog for a long time. Have you received any attention recently.

Recently, in a VDI project, the virtual desktop adopts the pooled and restored mode (similar to the internet cafe mode deployment). The virtual desktop configuration file adopts the mandatory configuration file.

After the mandatory configuration file is deployed, the virtual desktop function is tested and the Remote Assistance of the virtual desktop cannot be used. In fact, the remote assistance function provided by Windows is directly called.

650) This. width = 650; "Title =" image "style =" border-right-width: 0px; border-bottom-width: 0px; border-top-width: 0px; "Border =" 0 "alt =" image "src =" http://img1.51cto.com/attachment/201408/18/2011872_14083766737q9q.png "width =" 231 "Height =" 44 "/>

However, the following error occurs when we open it.

650) This. width = 650; "Title =" clip_image001 "style =" border-top: 0px; border-Right: 0px; border-bottom: 0px; border-left: 0px; "Border =" 0 "alt =" clip_image001 "src =" http://img1.51cto.com/attachment/201408/18/2011872_1408376680QQ8X.jpg "Height =" 175 "/>

The prompt is that you do not have the permission or guest account, but our accounts use the standard Domain Users group users.

If the same user does not use a forced configuration file and the local configuration file does not find this problem, change the forced configuration file ntuser. Man back to ntuser. dat to create a local configuration file.

This problem persists when other users use the mandatory configuration file.

After checking the information, it is found that this problem occurs in win7 due to the configuration file status. You can modify the registry and modify the configuration file.

1. The specific solution in win7 is as follows:

1. Modify the Registry

Change the value of state to 0.

2. Solve the problem through group policies

Open User Policy \ preferences \ Windows Settings \ REGISTRY

Create a registry entry here

HKLM \ Software \ Microsoft \ Windows NT \ CurrentVersion \ profilelist \ % logonusersid %

Configuration unit:	HKLM
Registry path:	SOFTWARE \ Microsoft \ Windows NT \ CurrentVersion \ profilelist \ Logonusersid %
Value Name:	State
Value Type:	REG_DWORD
Numerical data:	0

The configuration is as follows:

650) This. width = 650; "Title =" image "style =" border-right-width: 0px; border-bottom-width: 0px; border-top-width: 0px; "Border =" 0 "alt =" image "src =" http://img1.51cto.com/attachment/201408/18/2011872_1408376698qcIW.png "width =" 381 "Height =" 360 "/>

650) This. width = 650; "Title =" image "style =" border-right-width: 0px; border-bottom-width: 0px; border-top-width: 0px; "Border =" 0 "alt =" image "src =" http://img1.51cto.com/attachment/201408/18/2011872_1408376707hUAX.png "width =" 335 "Height =" 413 "/>

After the configuration is complete, issue the policy. If you enable the Local Group Policy for the ou for a specific computer, enable the loopback mode.

650) This. width = 650; "Title =" image "style =" border-top: 0px; border-Right: 0px; border-bottom: 0px; border-left: 0px; "Border =" 0 "alt =" image "src =" http://img1.51cto.com/attachment/201408/18/2011872_1408376720J7Ml.png "Height =" 342 "/>

For example, you can enable remote assistance.

2. solution under Windows Server 2008 r2

When this problem occurs when you deploy a xenapp-type virtual application or terminal service under Windows Server 2008 R2, you can use a dedicated hotfix. The hotfix address provided by Microsoft is as follows. You only need to download and install it, if the problem persists, refer to the win7 solution.

Http://support.microsoft.com/kb/2936674

This article from the "Meng Ji Chao technology blog" blog, please be sure to keep this source http://superdream.blog.51cto.com/2011872/1541808