Assigned and Published apps - tangled OU's

justmark · Guest

I'm looking for advice/tips on assigning and publishing apps through AD. I
have a single domain with two sites (different cities) and under those cities
I have OU's for servers and workstations. I have several GPO's that are used
for various tasks in those OU's.
Anyway, I have been testing an assigned deployment of Adobe Acrobat Std. and
all is well, but I'm beginning to realize how complicated things can get down
the road if I don't plan well now - for instance, if I assign new apps in the
future and need to remove some of them while keeping others.
With a test assigned deployment of Acrobat, I created an OU under the
workstations OU in my city. I moved a test workstation to that OU and linked
the GPO for this project to that OU. Acrobat installed just fine. Then I
tested uninstalling it by first removing the workstation from the GPO's
security tab. It didn't uninstall... I had to actually unlink the GPO from
that OU before it was uninstalled.
This got me to thinking that If I deploy Acrobat to a few dozen
workstations, then decide to deploy something else through a GPO, then have
to uninstall some of these, things will start to get chaotic. Having a
cascading OU structure with deeper and deeper levels that are linked to each
of the assigned apps doesn't sound like a good idea. Particularly since
uninstalling seems to require unlinking GPO's that may need to remain linked
to retain other users' installations.
It could be that I'm not approaching this concept with the right ideas, but
I wanted to ask if anybody here can offer some guidance?

Thanks,
Mark