I'm doing the same as you; specifics in OU's and distinct policies applied.  
I've no real issue with it beyond chasing peeps to get things in the right 
place........

From: [email protected] [mailto:[email protected]] On 
Behalf Of [email protected]
Sent: 22 January 2014 20:31
To: [email protected]
Subject: [mssms] RE: What is everyone doing for Antimalware Polices for servers?

For endpoint that's fine, since the policies will happily merge.

Christopher Catlett
Consultant | Detroit
[MCTS_2013_small]

Sogeti USA
Office 248-876-9738 |Fax 877.406.9647
26957 Northwestern Highway, Suite 130, Southfield, MI 48033-8456
www.us.sogeti.com<http://www.us.sogeti.com/>

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Marcum, John
Sent: Wednesday, January 22, 2014 1:00 PM
To: [email protected]<mailto:[email protected]>
Subject: [mssms] RE: What is everyone doing for Antimalware Polices for servers?

The problem with query based collections is that you end up with many servers 
in multiple collections.

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Dzikowski, Michael
Sent: Wednesday, January 22, 2014 9:48 AM
To: [email protected]<mailto:[email protected]>
Subject: [mssms] RE: What is everyone doing for Antimalware Polices for servers?

You could have query based collections and End Point policies applied to them 
as applicable.

Domain Controllers get Domain Controller policies
Exchange Servers get Exchange Server policies
Base Server policy all servers get.

That's how I've done it in the past.

Michael Dzikowski
Senior Systems Engineer |  Ally Technical Infrastructure - Windows Hosting
[cid:[email protected]]

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Marcum, John
Sent: Wednesday, January 22, 2014 12:34 PM
To: [email protected]<mailto:[email protected]>
Subject: [mssms] RE: What is everyone doing for Antimalware Polices for servers?

After beating my head against the wall trying to figure that out I just applied 
them all to the same collection. Not the best way I'm sure but I couldn't see 
any other reasonable solution.


________________________________
John Marcum
Sr. Desktop Architect
Bradley Arant Boult Cummings LLP
________________________________

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Wood, Sandy
Sent: Wednesday, January 22, 2014 10:45 AM
To: [email protected]<mailto:[email protected]>
Subject: [mssms] What is everyone doing for Antimalware Polices for servers?

We've been looking over our Endpoint Protection polices for our servers and 
wonder how everyone else handles things. We currently have about 10 separate 
server policies for most of the basic server roles, SCCM, SCOM, Exchange, SQL, 
etc. which we deploy to collections tied to OUs in AD. I've been wondering what 
would be the downside to combining all the server policies into one big policy. 
Does anyone do this?

Sandy Wood
Network Engineer
Orange County District Attorney
(714) 347-8775


________________________________

CONFIDENTIALITY NOTICE: This communication with its contents may contain 
confidential and/or legally privileged information. It is solely for the use of 
the intended recipient(s). Unauthorized interception, review, use or disclosure 
is prohibited and may violate applicable laws including the Electronic 
Communications Privacy Act. If you are not the intended recipient, please 
contact the sender and destroy all copies of the communication.
________________________________

Confidentiality Notice: This e-mail is from a law firm and may be protected by 
the attorney-client or work product privileges. If you have received this 
message in error, please notify the sender by replying to this e-mail and then 
delete it from your computer.

________________________________

Confidentiality Notice: This e-mail is from a law firm and may be protected by 
the attorney-client or work product privileges. If you have received this 
message in error, please notify the sender by replying to this e-mail and then 
delete it from your computer.



________________________________

CONFIDENTIALITY NOTICE: This communication with its contents may contain 
confidential and/or legally privileged information. It is solely for the use of 
the intended recipient(s). Unauthorized interception, review, use or disclosure 
is prohibited and may violate applicable laws including the Electronic 
Communications Privacy Act. If you are not the intended recipient, please 
contact the sender and destroy all copies of the communication.


________________________________

Confidentiality Notice: This e-mail is from a law firm and may be protected by 
the attorney-client or work product privileges. If you have received this 
message in error, please notify the sender by replying to this e-mail and then 
delete it from your computer.

________________________________

Confidentiality Notice: This e-mail is from a law firm and may be protected by 
the attorney-client or work product privileges. If you have received this 
message in error, please notify the sender by replying to this e-mail and then 
delete it from your computer.





<<inline: image001.jpg>>

<<inline: image002.png>>

Reply via email to