This message was deleted.
# microsoft-fslogixs
Slackbot
10/18/2019, 1:52 PMThis message was deleted.
n
Nick Panaccio
10/18/2019, 3:53 PMI didn't enable that setting because I'd rather the user get a local profile and be able to work as opposed to them being bumped out.
t
Tim Riegler
10/18/2019, 4:02 PMWe are having problems with users logging off, then logging back in immediately, and the profile hasn't finished unmounting from the first server, so they get a temp profile. I would rather it not let them on at all, and then they will retry, and get their normal profile. However, I'm not 100% sold on that, and wanted to talk it through. Just because it makes sense to me, doesn't mean it makes sense!
n
Nick Casagrande
10/18/2019, 4:40 PMLots of things don’t make sense with FSL. hehe
d
David Ott
10/18/2019, 6:05 PMHKLM:\Software\FSlogix\Profiles
David Ott
10/18/2019, 6:07 PMput that stuff in your registry and if the profile is locked it (notice the retry count and such)... it will prompt the user with a box with your specified message/title... the only option they will have is to hit ok and it logs them off
👍 2
t
Tim Riegler
10/21/2019, 12:12 PMThanks @David Ott! Going to implement in Test this week.
d
Dennis
10/21/2019, 6:26 PMWe do it exactly like @David Ott described from the beginning of fsl. Works like a charm. I always want to know if there is a problem with the user profile, otherwise maybe the user works with a non fsl profile for weeks and nobody notices that.