Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations MikeeOK on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

EPO Subgroups

Status
Not open for further replies.

theboyhope

IS-IT--Management
Jul 11, 2001
772
GB
You know the old subgroups problem with EPO? ... Create a subgroup, add some machines to it and then the domain update task lists those machines as needing added again.

In other words, EPO only checks the top level to see if a machine is already being managed.

One of the support guys told me last week that this behaviour is by design. We both had a good laugh at that and I've submitted a development request for it to be fixed.

Even if they do fix this problem I'd bet it won't be any time soon. Can anyone think of a clever workaround?
 
Yeah this issue really annoys me as we can't take advantage of automatic domain updates so have to remember each time a build is done to install McAfee afterwards (it's not part of our build image for a couple of reasons...). Unfortunately I don't know of any work-around.
 
is that for 3.0.2? and/or 3.5? does 3.5 have problems with updating from AD?

Doh!!
 
Well, I'm using 3.02 but McAfee tell me 3.5 has the same problem.

They also told me a development request was submitted last week. I checked today and now it's being submitted today. For some reason I can't get these guys to do anything without having to hassle them. :eek:/
 
Yeah, they're on the permanent hot seat...

Doesn't 3.5 have a AD tie in so you can point OU's to specific sites and have them update that way? or am I talking about something totally different?

Doh!!
 
3.5 does have the AD tie in, but I also ran into issues with it. Whenever the task ran to check the AD, it would recreate my OUs in the Lost and Found folder at each designated site.

Eg. I have a Head Office site and inside are Servers and Workstations groups to match my OU. Everytime the task runs, the Workstations and Servers OU are created within the Lost and Found folder inside the Head Office site and not reusing the existing groups I created to match the OU.

 
That's not good, We've got a test server running 3.5, but haven't tested the AD tie in yet.

A days work is never done...


Doh!!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top