(these locations are mentioned below in my antivirus exclusions list)Īntivirus exclusions are in place for the followings on each session host. I have already used Process Explorer to check if there is a process locking the VHDX file, but there is none across all locations the file could appear. This user will not be able to logon to RDS02 and 03 until the next server reboot for RDS01 which clears the locked file.Īnother weird thing is, even with the user logged off, the C:\users\username and C:\users\local_username folders remain there. This looks to me something is blocking a clean log off for this user from RDS01 the first time.
So with the above example, I would block off access to RDS02 and RDS03 temporarily and force the user logon to RDS01. I normally can get the user logged in again by disallowing remote access to all except the original RDS server.
There are no such VHDX files under C:\ProgramData\FSLogix\Proxy. (The process cannot access the file because another process has locked a portion of the file.) Configuration Read (DWORD): SOFTWARE\FSLogix\Profiles\PreventLoginWithFailure. When I check the log files under RDS02 C:\ProgramData\FSlogix\Logs\Profile, I found the below every time the user fails to login.Ġ001d664] D:\agent_01_work\2\s\libraries\Frx.ServiceLib\(452): (452): Could not acquire an exclusive lock for vhd(x): C:\ProgramData\FSLogix\Proxy\SID_Username\Profile_Username.VHDX User logs onto RDS farm again, user connects to RDS02 and receives a profile attachment error. User logs onto RDS farm, user connects to RDS01.ģ.
SYMANTEC ENDPOINT PROTECTION 14 UNLOCK ADMIN ACCOUNT CODE
Occasionally, when a user logs in, they will receive a user profile failed to attach error, with error code 21.ġ. I setup a new FSLogix environment for a three session hosts RDS farm recently.
0 kommentar(er)
