Thread Info
  • State Verified Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 2 replies
  • Subscribers 7 subscribers
  • Views 3123 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

Installing Safeguard on Laptop not on Domain

JohnMintz

I am currently running Sophos Safeguard Enterprise 8.  All of the users that I have completed up to now have been traditional users in the office with PCs on the domain.  I now have one user that currently has an AD account but is assigned a PC that is not on the domain and has a generic local login.  When I installed Safeguard, its prompts him for his AD credentials.  

 

Is it possible to use Safeguard enterprise on a pc not on the domain with generic credentials?



This thread was automatically locked due to age.
Parents
  • +2

    Yes it is -

    I would create a Workgroup within Sophos SG console. Right click the "Root" and select New - Create new workgroup (auto registration) Call this WG the same as the WG the PC is in. My top tip is DON'T call it Workgroup! Windows will not mind what you call it really so if it's currently WorkGroup on his laptop I'd rename it to mydomainWG. Reboot his PC if you've changed the name. It'll be easier and neater to figure out in Sophos SG rather than management of a WorkGroup called Workgroup... :)

    You'll then need to "confirm" the local user (right click the user that'll be below the computer object within the console) This will then mean the user can "authenticate" against this standalone user.

     

    Hope this helps? Give me a shout if you'd like more detail - I have it setup this way on my pre-prod testing server!

     

    Michael

Reply
  • +2

    Yes it is -

    I would create a Workgroup within Sophos SG console. Right click the "Root" and select New - Create new workgroup (auto registration) Call this WG the same as the WG the PC is in. My top tip is DON'T call it Workgroup! Windows will not mind what you call it really so if it's currently WorkGroup on his laptop I'd rename it to mydomainWG. Reboot his PC if you've changed the name. It'll be easier and neater to figure out in Sophos SG rather than management of a WorkGroup called Workgroup... :)

    You'll then need to "confirm" the local user (right click the user that'll be below the computer object within the console) This will then mean the user can "authenticate" against this standalone user.

     

    Hope this helps? Give me a shout if you'd like more detail - I have it setup this way on my pre-prod testing server!

     

    Michael

Children
No Data
Unfiltered HTML