Guest User!

You are not Sophos Staff.

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

New to SGN and it's driving me nuts

Hello All,

     This past summer Sophos SGN was thrown at me.  I am so lost.  Called tech support twice and I believe I got the same guy both times that wasn't very helpful, nor could I understand him.  Anyway....so we are running 5.60 and I have a device (laptop) that the wrong person was the first to log into it (why do I bother trying to educate people?), thus the the wrong user is currently the owner on the laptop.  I was able to use recovery and both users can now login through the POA, however Management Console still shows the wrong user as owner.  I would THINK that I could just uncheck the current owner and check the proper one, then maybe right-click and delete the user that shouldn't even be on that laptop, but no.  No such thing seems to work.  What am I doing wrong?  It looks straight forward and easy, but not so much.

     Another thing driving me nuts is I can no longer WOL a device and log into it remotely.  It, obviously, boots up and hangs out at the POA waiting to be logged in through, but none of my remote control methods work until Windows is loaded.  Anyone have a way they deal with this?

     Last...when I AM forced to visit a PC to correct it's issue...if the user isn't around and it's off...I can't log in through the POA without hunting them down and getting their password.  There's GOT to be an easy way to globally set one of our network admin accounts to all SGN protected devices so I can log in through POA with said username.  Any guidance there, and on any of my other issues/gripes, would be ENORMOUSLY appreciated.

    I want to like SGN, but so far it's done nothing but make my job harder and cause me grief.  I'm not ready to even think about what happens when it's time to image all these devices and what's going to happen there...

Take Care

Rick

:17935


This thread was automatically locked due to age.
Parents
  • 2. WOL is a policy setting in SafeGuard Enterprise. Create a new Specific Machine Settings policy and set time and date when the policy should be active, define the number of automatic log on's and before shutting down the machine use "sgnstate.exe -WOLStart" on the client >> at the next reboot the machine will be in auto log on.

    In reference to this issue...I don't understand what I'm setting time and date for in the policy.  Prior to SGN I could WOL any of our computers, any time of the day, from my couch at home if I wanted and it would allow me in.  What you're describing to me sounds like more of a ... well gives me the ability to reboot and machine that's already on and will bypass the POA, but doesn't allow me to WOL the machine from a down state as it would have been "Shutdown" by the user via Windows shutdown rather than me issueing the command you specified.  If that makes sense...cause I'm not sure it'll make sense to me if I re-read it.  

    I guess I understand I can set it so that I have the option to reboot it via Start/Run and using the command you gave...still not sure what I'm setting time/date for though...

    :18239
Reply
  • 2. WOL is a policy setting in SafeGuard Enterprise. Create a new Specific Machine Settings policy and set time and date when the policy should be active, define the number of automatic log on's and before shutting down the machine use "sgnstate.exe -WOLStart" on the client >> at the next reboot the machine will be in auto log on.

    In reference to this issue...I don't understand what I'm setting time and date for in the policy.  Prior to SGN I could WOL any of our computers, any time of the day, from my couch at home if I wanted and it would allow me in.  What you're describing to me sounds like more of a ... well gives me the ability to reboot and machine that's already on and will bypass the POA, but doesn't allow me to WOL the machine from a down state as it would have been "Shutdown" by the user via Windows shutdown rather than me issueing the command you specified.  If that makes sense...cause I'm not sure it'll make sense to me if I re-read it.  

    I guess I understand I can set it so that I have the option to reboot it via Start/Run and using the command you gave...still not sure what I'm setting time/date for though...

    :18239
Children
No Data