On-Premise Endpoint

Sophos Endpoint Software Install Endpoint on unassigned/non joined to domain but manage it via console

On-Premise Endpoint requires membership for participation - click to join

Thread Info

State Suggested Answer
Locked Locked
Replies 6 replies
Answers 1 answer
Subscribers 3 subscribers
Views 9829 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

Install Endpoint on unassigned/non joined to domain but manage it via console

Ben@ryehills over 6 years ago

Hi,

I have a sign in system that I need to install Sophos Endpoint on. What is the best way to achieve this?

At the moment it is not part of the domain (so not managed) and currently appears in the unassigned area of Sophos console.

Thanks

This thread was automatically locked due to age.

Parents

0 QC over 6 years ago

Hello Ben@ryehills,

currently appears in the unassigned area of Sophos console
how did it get there? By using Discover or Import and it appears unmanaged (grey)? Please note that unmanaged in terms of SEC means that the computer is "known" to SEC for some reason but Sophos has not yet been installed on it. Whether it's part of a domain or not has no relevance.

Christian
Cancel
Vote Up 0 Vote Down

Cancel
0 Ben@ryehills over 6 years ago in reply to QC

Hi Christian,

Not sure really but it must of appeared by using Discover somehow or when the console refreshers. I have created a group in SE Console and moved the workstation in to that folder to give me the "Protect Computers" option. But this will not work because (I'm guessing) it needs matching local / network account to let the install work correctly.

Ben
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 Ben@ryehills over 6 years ago in reply to QC

Hi Christian,

Not sure really but it must of appeared by using Discover somehow or when the console refreshers. I have created a group in SE Console and moved the workstation in to that folder to give me the "Protect Computers" option. But this will not work because (I'm guessing) it needs matching local / network account to let the install work correctly.

Ben
Cancel
Vote Up 0 Vote Down

Cancel

Children

0 QC over 6 years ago in reply to Ben@ryehills

Hello Ben,

it needs matching local / network account
correct. The credentials you enter are used for accessing the share and for install, either this is a domain account with the necessary rights or matching local accounts on the SEC server and the endpoint.
If this isn't possible then you have to log in to the endpoint and install manually from the CID.

Christian
Cancel
Vote Up 0 Vote Down

Cancel
0 Ben@ryehills over 6 years ago in reply to QC

Thanks Christian,

I will try the manually install and report back. Should it automaticity find the Sophos server or do I need to add access information to allow to talk to the console.
Cancel
Vote Up 0 Vote Down

Cancel
0 QC over 6 years ago in reply to Ben@ryehills

Hello Ben,

the necessary information is in the CID (in mrinit.conf) so the endpoint should be able to talk to the console when you run setup.exe from there (or a package built from the CID). Of course the endpoint must be able to resolve the path in the updating policy (if using UNC it's normally \\ServerNetBIOS\SophosUpdate\).

Christian
Cancel
Vote Up 0 Vote Down

Cancel
0 Ben@ryehills over 6 years ago in reply to QC

Hi Christian,

Sorry for the delay, thanks for you help I got it working with a few tweaks to the windows 10 firewall.

Ben
Cancel
Vote Up 0 Vote Down

Cancel