Endpoint Protection

Question is

How do i make DC a GUP without making it have the same security policies as the client computers?

     - I know that I MUST have the GUP in the same client folder as rest of the clients that want to speak to the GUP. If I move the GUP computer out of the client folder it no longer reports as a GUP. I've tested this.

   -Is there a way to manually change the servers' policy even though it is supposed to be recieving a certain policy within this clients' folder

  -If the DC does become a GUP and it has a 256K connection to 4 other branches that want to use this DC as their GUP. What will the bandwidth be like?

It doesn't need to be in the same folder, it just needs to have the same LU policy specifying that it is a GUP than apply it to the groups which you want to use that GUP.

You would use location awareness to set this up. So that all PCs that are in IP range 10.1.1.x use this GUP.

You might run into bandwidth issues. You should setup a GUP at each branch, if you can.

May be its a DC or normal server.

They all can be GUP, any normal SEP client can be GUP..

You can use this  to check the band width

http://www.symantec.com/connect/downloads/new-sep-content-distribution-monitor-gup-health-checking

If i was in your place i would not make a DC a GUP, as DC as an important roll to play. So it is not advisable to add more roles to it.

It may happen that a time would come that your DC would run out of resouces and in turn you may have different issue.

So a good practice would be to make a client a GUP that has a server OS running

You can also have a non-server machine (xp, vista, win7) be a GUP. Just be aware that there is a connect limit whereas servers don't have this limit.

I would recommend against this too.  You dont want to add that much disk IO and you could risk corupting your AD.    As a general rule advoid using AD to do anything but AD functions.

Hi,

as far as I know you, since RU5, or even earlier, you can have the GUP in a different group than the one that should be served. Of course, in both groups you have to set the LU policy with that GUP.

One other thougth on making a DC a gup I am going to amend my prior statement of not recommending it.   I would add that if it is a RODC then I would consider doing it as the likely hood of something bad happending to the database would be reduced.