Packages Deployed Via AD/GPO removal

  • Thread starter Thread starter Mike
  • Start date Start date
M

Mike

We have recently began deploying software packages through
Active Directory. The package deploys successfully to all
machines. After the deployment we remove the assigned
package from the GPO. Is there a way to go in and verify
the size of the GPO has reverted back to its original size
or close to it once the package has been removed?
 
Mike said:
We have recently began deploying software packages through
Active Directory. The package deploys successfully to all
machines. After the deployment we remove the assigned
package from the GPO. Is there a way to go in and verify
the size of the GPO has reverted back to its original size
or close to it once the package has been removed?
Click to expand...

I'm not sure what you are referring to. The application package itself does
not reside within the GPO. The GPO just points to the network share
containing the package.

What do you mean by 'revert back to its original size'?
 
Mike,

I am really confused by your question.

Are you saying that you created a GPO that deploys a certain software
application to the computer configuration side of things and once this GPO
was successfully deployed that you removed the GPO ( did you simply remove
the link to that specific OU - or to whatever you linked this GPO - or did
you remove the link and the GPO )?

If I am understanding this correctly I am not sure why you did this. What
was your thought process with this? If I am not understanding this
correctly ( and that has often been the case ) then could you explain a
little more what you are asking please?

HTH,

Cary
 
I realize only the AAS resides in the GPO itself. It
grows from 1.7m to 6.9m. Central office is trying to stop
us from using AD/GPO to distribute software. Their
complaint is that over time if it continues to grow each
time we deploy software replication will fail over the WAN
links.

So what I'm trying to prove is that once the package is no
longer assigned, the gpo will drop back to roughly the
same size. Does that make more sense?
 
This does not make sense.

I have never seen the .aas file grow. I am not saying that it does not, I
just have never seen it grow. I will admit that I have not paid great
attention to the specific size of the .aas file so....I would not think that
it would grow, though.

I am sorry but I do not follow the logic to your statement "So what I am
trying to prove is that once the package is no longer assigned, the GPO will
drop back to roughly the same size". If you remove the GPO ( either by
removing the link to the OU(s) to which that GPO is linked or by removing
the GPO itself ) then the benefits of the GPO ( such as the self healing )
will no longer be available. It is extremely poor practice to deploy
software via GPO to a specific OU and then move the user account
object/computer account object to another OU. The account object is no
longer subject to the GPO in either case. And all of the benefits of
deploying software via GPO are lost.

What software are you deploying via GPO? Why are you trying to deploy
software over a WAN link in the first place? This is usually a bad idea -
especially if that particular software deployment is something like Office
XP or Office 2003! You might want to reconsider this!!!!

HTH,

Cary
 
Back
Top