This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 64%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EC%3C/text%3E%3C/svg%3E)
Current trying to use FSLogix but want to limit users to a single session (one profile), configured PreventLoginWithTempProfile and PreventLoginWithFailure with value 1. On the users first login the FRXShell displays error message with only option is to Sign Off. If user logins in a second time, the user picks up a temporary local profile, no error. This is the same machine, so have to assume a profile was created during the first login and was not deleted. If the user logs off after the second login, the third login will give the FRXShell error message.
Reviewed the FSLogix Profile logs, the error indicates there is a local profile so FSLogix skips loading the VHD. But we want system to error with FRXShell message anytime the profile is in use on another system. Seems as if FRXShell does not remove the initial profile after a FRXShell error message is displayed.
Hello
1.Could you be more clarified :
we want system to error with FRXShell message anytime the profile is in use on another system
2.Even you configured PreventLoginWithTempProfile , the user can still log on with a temporary local profile?
3.what happened to the third log in ? is it using temporary profile or the profile created when first log in ?
Thanks
Karlie
I have posted the error message an user receives when the FSLogix VHD is locked (RW mode). Here is the scenario, profile (file) creation was monitored during login.
User A is already logged into a desktop and has the FSLogix VHD locked (RW mode). User A attempts to log into another desktop, User A receives the error screen posted and the only option is Signoff. I can see a profile was created, for User A but not removed at Signoff. User A attempts second login to same machine, this time no error and user gets the profile created at first login. The FSLogix log indicates a local profile and does attempt to attach VHD. When User A logs off second login, the profile is removed. If a User A attempts a third login, the error screen is presented and cycle repeats.
Question, why is the first login when error is presented not removing that profile?