Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 1 subscriber
  • Views 1419 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

Is there a way to tell EM to protect more computers in bulk?

nduda78

Say you highlight 100 computers and protect them, it does then in batches of how many, like 5? Basically, the 100th computer on the list gets protected last and it can take a long time for that to happen. 


Maybe we are impatient, but deploying globally at once, we rely on some offices to complete first. I've been staring at a system with the orange hourglass for a couple hours now just waiting for it to get its place in queue.

Anyway to tell EM or the SUM to open up more install threads?

:20503


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

    Thanks, I'll play with these.

    Our official stance is to not use AD for anything Sophos related, even GPO installs, for a couple reasons.

    Sophos using AD syncing is only good if your AD structure (OU's) and administration is clean. I know, it's a sysadmin training thing, but we have 14 sites globally, and New OU's pop up (which get default policies base on sync folder, which isnt always good), and new systems are added to the domain where they are never put into OU's or the correct OU's, which would get wrong policies.


    If we use GPO to put Sophos to an endpoint that isnt in a group (instead unassigned) it gets no policies. Helpdesk staff has this issue where if they see the white/purple shield on a client they "assume" sophos is installed and getting the right policies.

    By not using AD (except for computer discovery) the only way to install SEPP is manually through the EC or from the CID share (which is not broadcasted as the proper way of installing). By manually installing SEPP in the console, the admin is also required to move it to the correct folder for policies.

    This menthod is allowing us to have a cleaner dashboard, and truly track who has and doesnt have sophos installed. It's working well for 9000 systems in 14 sites so far.

    :20543
Reply
  • 0

    Thanks, I'll play with these.

    Our official stance is to not use AD for anything Sophos related, even GPO installs, for a couple reasons.

    Sophos using AD syncing is only good if your AD structure (OU's) and administration is clean. I know, it's a sysadmin training thing, but we have 14 sites globally, and New OU's pop up (which get default policies base on sync folder, which isnt always good), and new systems are added to the domain where they are never put into OU's or the correct OU's, which would get wrong policies.


    If we use GPO to put Sophos to an endpoint that isnt in a group (instead unassigned) it gets no policies. Helpdesk staff has this issue where if they see the white/purple shield on a client they "assume" sophos is installed and getting the right policies.

    By not using AD (except for computer discovery) the only way to install SEPP is manually through the EC or from the CID share (which is not broadcasted as the proper way of installing). By manually installing SEPP in the console, the admin is also required to move it to the correct folder for policies.

    This menthod is allowing us to have a cleaner dashboard, and truly track who has and doesnt have sophos installed. It's working well for 9000 systems in 14 sites so far.

    :20543
Children
No Data