United Kingdom Endpoint Management User Group

Hi all,

at the moment we are going through an AD migration and re-design. Id like to know is there any best practice for Active directory OU/group design for Altiris?

e.g. Create a seperate OU structure exclusively for ALtiris with UAT/Pilot/Production containers etc, can anyone point me to any documentation on this?

Thanks

Eugene

and keep in mind, I have done implementations as part of an AD switch over and those with AD already in place, is to keep the AD design separate. Active Directory is the backbone of the Network\Company design and organizational structure. Whatever tool you implement, Altiris for example, needs to be molded to fit those organanizational structures.

The hierarchy and design document, I think provided to you eariler, gives some examples of how to place Altiris based on the type of organization, but it's not exhaustive, nor should it be.

One of the main feature of NS 7.x is the abiltiy to create filters that can be used repeatedly against many groups to acheive the desired results. So, you can import your organziational structure as is, and then have pilot, production, etc targets as desired.

There are no best practices around this.  You may want to have Altiris in mind--I have when reorganizing messy AD designs--but nothing specific is required.  Consider that with Altiris, you can use the AD Organizational View, or you can use the Default View, or you can create your own organizational views.  Other systems aren't so forgiving, and either let you synchronize for your only view or not synchronize for your custom view.  Altiris doesn't mind if you do both.

I hope this helps.