Difference between revisions of "Active Directory/Software Distribution"

From WolfTech
Jump to: navigation, search
Line 1: Line 1:
 
{{Active_Directory_toc}}
 
{{Active_Directory_toc}}
The WOLTECH domain was designed to ease, automate, and monitor the distribution of software to computers. We have an extensive list of software that has been packaged and configured for distribution via the domain, and new packages are being added everyday. To see the complete, up-to-date list of available [[Packaged Software]], click here.
+
The WOLTECH domain was designed to ease, automate, and monitor the distribution of software to computers. We have an extensive list of software that has been packaged and configured for distribution via the domain, and new packages are being added everyday. To see the complete, up-to-date list of available [[../Packaged Software]], click here.
  
Each departmental organizational unit (OU) contains a Software Packages OU. This OU is automatically populated with groups to install all software that the department is licensed to use (via NCSU, your college, freeware, etc). OU Admins can also create their own departmentally licensed software packages. To learn more, see [[Publishing Departmental Software]] (coming soon).
+
Each departmental organizational unit (OU) contains a Software Packages OU. This OU is automatically populated with groups to install all software that the department is licensed to use (via NCSU, your college, freeware, etc). OU Admins can also create their own departmentally licensed software packages.
  
 
==Software Distribution Architecture==
 
==Software Distribution Architecture==

Revision as of 17:45, 27 February 2006

The WOLTECH domain was designed to ease, automate, and monitor the distribution of software to computers. We have an extensive list of software that has been packaged and configured for distribution via the domain, and new packages are being added everyday. To see the complete, up-to-date list of available [[../Packaged Software]], click here.

Each departmental organizational unit (OU) contains a Software Packages OU. This OU is automatically populated with groups to install all software that the department is licensed to use (via NCSU, your college, freeware, etc). OU Admins can also create their own departmentally licensed software packages.

Software Distribution Architecture

The following process and diagram explain how group policies, groups, and OUs come together to distribute software on the WOLFTECH domain. The diagram shows a University licensed package (MATLAB), college licensed package (OPNET Modeler), and departmentally license package (Microsoft Office).

For each software package:

  1. A domain local group is created in the Software Packages OU of the OU in the hierarchy that the software is licensed.
  2. A group policy is created and linked to the OU. The group policy is filtered to apply only to the domain local group.
  3. Global groups are created in each sub-OU's Software Packages OU. These groups are added as members of the domain local group.
  4. To configure software to be installed a machine, an OU Admin simply adds the machine as a member of the group that was created in his/her OU's Software Packages OU.

It's important to note that there is a rigid naming standard in place for all domain objects. This is necessary to promote organization, prevent conflicts, ease delegation, and allow for future automation. Before creating domain objects, please thoroughly read the Naming Standards page.

University Licensed Software - Group Memberships

University licensed software is distributed through a series of nested groups.

  1. A domain local group is created in the NCSU Software Packages OU (wolftech.ad.ncsu.edu/NCSU/Software Packages).
  2. A group policy is created and linked to the NCSU OU. The group policy is filtered to apply only to the domain local group.
  3. Global groups are created in each college's Software Packages OU (wolftech/NCSU/[COLLEGE]/Software Packages). These groups are added as members of the domain local group.
  4. Global groups are created in each Departmental Software Packages OU (wolftech/NCSU/[COLLEGE]/[DEPT]/Software Packages). These groups are added as members of their college's group.
  5. To configure software to be installed a machine, an OU Admin simply adds the machine as a member of the group that was created in his/her OU's Software Packages OU.

College Licensed Software - Group Memberships

College licensed software is distributed through a series of nested groups.

  1. A domain local group is created in the college's Software Packages OU (wolftech/NCSU/[COLLEGE]/Software Packages).
  2. A group policy is created and linked to the college's OU. The group policy is filtered to apply only to the domain local group.
  3. Global groups are created in each of the college's departmental Software Packages OUs (wolftech/NCSU/[COLLEGE]/[DEPT]/Software Packages). These groups are added as members of their college's group.
  4. To configure software to be installed a machine, an OU Admin simply adds the machine as a member of the group that was created in his/her OU's Software Packages OU.

Departmentally Licensed Software - Group Memberships

Departmentally licensed software is distributed through a single group.

  1. A domain local group is created in the department's Software Packages OU (wolftech/NCSU/[COLLEGE]/[DEPT]/Software Packages).
  2. A group policy is created and linked to the department's OU. The group policy is filtered to apply only to the domain local group.
  3. To configure software to be installed a machine, an OU Admin simply adds the machine as a member of the group that was created in his/her OU's Software Packages OU.

Available Software Packages

See [Software Packages].