Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 4 replies
  • Subscribers 0 subscribers
  • Views 14174 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

How can we protect and manage Windows Home OS machines from Enterprise console (in Domain)

Yugandhar

Hi,

We have Windows domain environment and installed Sophos Enterprise console on one of the member server. We have Windows laptops which have Windows home editions and we would like to protect and manage those Home editions from enterprise console.

We have done the following procedure to achieve this but still getting error i.e. either dont have administrator permissions on the client machine

1. Created same local admin user account in both the server and client machines

2. Given permissions to Everyone on UNC path folder

3. Started the services Task schedular, Remote registry and Windows installer on the client machine

4. While doing Protect computer from the Enterprise console, providing local admin account of the client machine

But still getting the dont have administartor permissions on the client machine, 

Anyone please help me on this issue.

Regards,

Yugandhar

:57207


This thread was automatically locked due to age.
Parents
  • 0

    Hello Yugandhar,

    location for installer package

    an installer package doesn't reside in the CID, put it somewhere else from where it can be downloaded (not recommended but with Everyone permissions on the SophosUpdate share you could put it there (say ...\SophosUpdate\Packages\SAVWinHome.exe).

    whatever policies we apply

    If you use the Deployment Packager you could build the package like this:

    For the -G in Additional setup parameters please see Command line parameters used by Setup.exe.

    It would then work like this: An administrator downloads and runs the SAVWinHome.exe which installs AutoUpdate and RMS. RMS will then fetch the updating policy, AutoUpdate will update from there (and install the remaining components) then the other applicable policies will be fetched.

    HTH

    Christian

    :57212
Reply
  • 0

    Hello Yugandhar,

    location for installer package

    an installer package doesn't reside in the CID, put it somewhere else from where it can be downloaded (not recommended but with Everyone permissions on the SophosUpdate share you could put it there (say ...\SophosUpdate\Packages\SAVWinHome.exe).

    whatever policies we apply

    If you use the Deployment Packager you could build the package like this:

    For the -G in Additional setup parameters please see Command line parameters used by Setup.exe.

    It would then work like this: An administrator downloads and runs the SAVWinHome.exe which installs AutoUpdate and RMS. RMS will then fetch the updating policy, AutoUpdate will update from there (and install the remaining components) then the other applicable policies will be fetched.

    HTH

    Christian

    :57212
Children
No Data
Unfiltered HTML