Thread Info
  • State Verified Answer
  • +2 person also asked this people also asked this
  • Locked Locked
  • Replies 3 replies
  • Subscribers 7 subscribers
  • Views 6425 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Workgroup User not Registering on Windows 10 Pro

Chris Shipley

The policies I have set work for Windows 7 and other Windows 10 Workgroup systems, but this system will not auto register it's username.  Similar to this post https://community.sophos.com/products/safeguard-encryption/f/sophos-safeguard-products/9891/why-is-my-user-status-stuck-in-sgn-guest - but looks like he never got resolution.

Yes, I have the machine settings policy set correctly for "Allow registration of new SGN users" to Everybody.  And I do not use a Service Accounts List policy.  The system registered fine in the WORKGROUP connector, but it has no Owner associated with it.

Again, this worked in my test environment with a Windows 10 Pro system in WORKGROUP.  If it matters, the user is using an MS Surface Pro 4 (it shouldn't matter, but maybe it does).



This thread was automatically locked due to age.
Parents Reply Children
  • 0 in reply to MichaelMcLannahan

    Not a stupid question - yes and thanks for confirming that step as well.  We did log in with the Sophos cog.  It's definitely doing the initial machine registration, but no the initial user registration so I can't assign keys.

  • +2 in reply to Chris Shipley

    I was able to get support to help on this one.  In my case, the user's Windows 10 system was connected to a Microsoft Account, which in the release notes is a known issue.  We were able to determine this because the Client Status (right click client icon in system tray, select status) said the user was SGN guest (Microsoft Account).  Adding a new user account that wasn't associated with an online Microsoft account resolved the problem.

Unfiltered HTML