[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1824
  • Last Modified:

In Group Policy, can "remove managed software" be disabled once it has been implemented?

Windows 2003 Server R2
Windows XP workstations

Using the Group Policy Management console, I used group policy's 'software installation' to push software to the client computers.  As the software is now no longer in use, I removed the software package from Group Policy and chose the option to delete the software from the workstations.  Now, every time a computer starts up, they receive the message "Removing Managed Software XYX."  This occurs on every workstation, even those from which the software has definitely already been moved.  If this were the only issue, I wouldn't mind so much.  However, some workstations actually hang on the "Removing Managed Software" screen and can't be logged into as a result.

Ideally, I'd like to go back into Group Policy and tell it to stop trying to remove the managed software, but since I deleted the software package, there is nothing for me to configure.  How can I stop Group Policy from trying to remove the software?

Thanks for any help you can give!
- jdono89
0
jdono89
Asked:
jdono89
  • 6
  • 6
1 Solution
 
KromptonCommented:
I'm guessing that you logged onto some or all of the machines locally and verified the program is not showing in the Add/Remove Control Panel.
A simple guess here is that the uninstaller failed to do it's job properly.
Have you looked in the Registry to make sure all referances were properly removed by the uninstaller?
Do you still have the software? Try installing and un installing it on one of the machines. See if that helps
0
 
jdono89Author Commented:
This behavior happens even on a brand new machine that has never even had the software on it.

Honestly, I don't care if the software is there at this point, I just want to remove all references to it in Group Policy.  I'd like to tell Group Policy to stop pushing out the software, but leave it alone if it still exists.  
0
 
KromptonCommented:
I see.
Do you have seperate GPOs for each peice of software you manage?
Or just one GPO with multiple packages being installed?
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
jdono89Author Commented:
In this case, it is just one GPO with one software installation package.
0
 
KromptonCommented:
How many computers are we talking about?
0
 
jdono89Author Commented:
around 200 computers.
0
 
KromptonCommented:
Is the GPO currently linked anywhere in your Domain?
0
 
jdono89Author Commented:
This is my default domain policy so it is linked to the root of the domain.
0
 
KromptonCommented:
On simple thing to try is to run a GPUpdate /Force one one of the problem machines. Just to see if it helps. It's probably a long shot but easy either way. Failing that...

I suggest creating a test OU if you do not already have one and place a few problem machines into it then attempt the following before going Domain wide.

1) Make a new empty GPO and add the software to it this time with the uninstall when out of scope checked.
2) After all computers have accepted this new GPO you should be able to delete the link to it and the software should uninstall. Without the problem you have now.

If the above steps fix the problem you can use them Domain wide.

If you still have the problem....
These two steps should relieve your current problem of locking up while trying to uninstall.

1) Add the package back into the Default GPO Making sure the uninstall if out of scope option is un-checked and allow it to install.
2) After all deployments are updated delete the package from the Default GPO as you did before. This should leave the software but remove any referance to it from your Default GPO.

then apply the steps from the top.

Personally I try to keep software installs in their own GPO but this is not really necessary for anything except my sainity. And it is always a good thing to make the absolute minimum number of changes to the Default Doman Policy as you can get away with.

Good luck
Krompton
0
 
jdono89Author Commented:
Never mind.  I ended up recreating the GPO from scratch minus the software installation package.
0
 
KromptonCommented:
I'm glad you got it fixed. Since you did not use the suggestions I provided you may want to ask for your points to be refunded.

Thanks and Cheers.
0
 
jdono89Author Commented:
That's ok.  I unfortunately re-created my GPO before seeing your post.  Hopefully it well help somebody else with a similar problem.
0

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 6
  • 6
Tackle projects and never again get stuck behind a technical roadblock.
Join Now