It turned out to be the DisableLockWorkstation policy. We removed that and it's worked perfectly.
↧
It turned out to be the DisableLockWorkstation policy. We removed that and it's worked perfectly.