EPO 3.0.1 Auto synching domains

[NickFerrar]

I'm in the process of setting up an EPO 3.0.1/VS 7.1 environment in our company. I'm still trying to decide the best way to organise and populate the EPO though.

Doing it as a domain and having a synch task set up looks good, in that any new PC that's added into the AD will get added into the EPO (at next synch), is this true?

If so is it possible not to force an agent install, I can't see an option for this. I'd like stuff to get added to the EPO but until they are dropped into the right group they don't get the agent pushed, this way if someone builds a server or something it's not automatically going to get an agent installed (which we don't always want to happen). There just don't seem to be many options available on the synch domain task Is there a way around this?

 

[qtin]

The term domain sync is a little misleading. ePo 3.0.x doesn't actually integrate w/ AD like SMS does. If you really want that you are going to have to wait for 3.5 which should go into beta at the end of next month.

We also don't want the agent on our servers. We have our desktop group as local admins on the desktop machines and just use a service account that is in the desktop group to push out the clients.

 

[NickFerrar]

Thanks for the info. I'm curious if the domain synch scheduled task processes and agent install based on the deployment task in the top level of the directory or if it just installs the agent regardless of any settings elsewhere.

I could test this, it's just a hassle as we don't really have a test domain and I don't want to monkey aorund on our production domains (especially as there is an existing EPO 2.5.1/VS 4.5.1 deployment)!

 

[AVChap]

There's no AUTOMATIC sync with the NT domain/AD but you can schedule this with a server task. I've done this at work and (pardon the pun) works like a charm.

AVChap

“I have not failed 700 times. I have not failed once.
I have succeeded in proving that those 700 ways will not work.
When I have eliminated the ways that will not work,
I will find the way that will work.”
--Thomas Edison

 

[NickFerrar]

Does anyone know how the Domain synching works in conjunction with IP Address sorting?

We have a couple of main domains at my company and it's possible for both domains to be on the same subnet. Within the EPO I'm dividing things first by domain then by physical site, I have subnets against these sites and they are duplicated within each domain. I'm wondering if I do IP Address sorts will the systems get picked up purely by the IP address and therefore sorted into the site with the matching subnet in the alphabetically first domain or does it also check the domain during the sort and put into into the matching subnet within the correct domain?

 

[simonjcook]

Regarding the Update Domain task or Domain Sync scheduled task... No it doesn't integrate with subgroups.

If you use update domain on a particular site it only considers the nodes located at that level and not those located in sub-groups.

I have a call in with NAI regarding that particular issue which has been around since ePO 1.0 and they have raised an FMR.