Page 1 of 1
Active Directory Relationship - Sub-OR Management
Published: October 15, 2015 - 5:36 PM
by Floflobel
Good morning,
I am currently in the testing phase with your software, which is very good.
I would like to assign a computer to several groups but this does not seem possible.
Let me explain:
Code: Select all
OU
-> OU1
-> PC1
-> PC2
-> OU2
-> PC1
-> PC2
-> OU3
-> PC1
-> PC2
I would like PC1 in wapt to be the OU1 group as well as the OU group in order to manage the installation of software according to the different OUs.
Thank you
Sincerely
Re: AD Relationship - Sub-OU Management
Published: October 19, 2015 - 10:08 AM
by htouvet
In WAPT, there isn't strictly speaking a "group" belonging to a group, but rather packages that describe a workstation profile. A machine depends on one or more group (or software) "packages," which themselves depend on one or more other packages (groups or software) recursively. A "group" package can therefore represent a workstation "profile."
So what you describe is possible. You simply need to assign several groups to the same machine, and in that case, the machine will install the dependencies of all its groups.
WAPT has a mechanism to then attempt to assign (i.e., make dependents of) all the corresponding "group packages" (i.e., those with the same name) to a machine in Active Directory (AD) to which it belongs. This avoids duplicating the work of categorizing machines (AD for GPOs, for example, plus WAPT).
Re: AD Relationship - Sub-OU Management
Published: October 21, 2015 - 5:54 PM
by Floflobel
Thank you for your reply.
Unfortunately, after several attempts, I'm unable to define multiple groups on WAPT based on the user's group. I did manage to assign a group to each user. Another problem arises if the computer is turned off; it's impossible to assign a group to it, which could cause issues when the software is deployed via GPO.
Sincerely
Re: AD Relationship - Sub-OU Management
Published: October 21, 2015 - 6:25 PM
by htouvet
Adding one or more groups as dependencies to a machine technically involves modifying the machine package.
The machine package is edited by the management console, signed on the console, and then uploaded to the server.
The machine does not need to be powered on or accessible.
When the machine later consults the WAPT package repository, it will detect that its relevant machine package (named after the machine's DNS name) has changed version, download it, and install the dependencies of that package, including the software groups it contains.