For ISVs
White Papers
Video Garden

Setup Applications OU

It is becoming quite common for enterprises to use Active Directory as a central repository to define which users should have the right to use which applications. In this step, we will set up an Organizational Unit (OU) inside of our Active Directory domain.

One huge advantage to using AD for user/application assignment is that it allows the more premium tallent to worry about creating the back end of operations and not get bogged down with the daily personnel changes and needs. They virtualize the app, deploy it to the golden image, and create an empty group in Active Directory.

After that, other personnel -- potentially within the business units themselves -- can take responsibility for maintining the list of users (and user groups) that should have access to the application. These other personnel only need a very simple training in Active Directory to do there function. No need to learn any of the other back-end management consoles!

We will use a simple naming strategy when we create the user groups in the OU. The name of the group must exactly match that of the App-V package. Our publishing engine (AppV_PublishApp) will depend upon that match to determine which application packages to publish to the user.

So here is a screenshot of our Active Directory Domain. You can see that we have an Organizational Unit called "Applications". This OU has three user groups established. As shown in the view, these groups may be either Security or Distribution groups as would be appropriate in your organization.

The image below, shows the membership in one of those groups, CamtasiaStudio6_1. This is a test domain with test users named "User001", "User002", etc. So the "OddUserGroup" shown is simply those test users with a name ending with an odd number.

For this test I populated the "Intuit_QuickBooks2009_qb09x86t01" application group using the "EvenUserGroup", and for "TMurgent_Solman41_solman41t01" application to all test users.

You will need to establish an OU for your applications. The OU may have any name you like, but the name of the OU will be entered when you install the AppV_DeployNPublish tools in the next step. It is not necessary that the OU exist prior to installation, only that it exists with the configured name before the user VDI sessions begin.

NOTE: If you deploy to both 32-bit and x64 operating system clients, you may want to consider establishing two Application OUs. There will be some applications that you will need to sequence twice, because the application wants to install a 64-bit version on the x64 OS. This may be to utilize the additional memory space, or, such as with my ATM tool, it might integrate tightly with the kernel. Such a situation would involve two Golden Images and two OUs, however a single SFT cache containing all application packages could be used.

Return to Preparation of Golden Image