Uninstalling GPO distributed package - installing newer version via SMS 2003

myITforum.com Community Forum

Home Forums Blogs Live Support chat Search Articles Wiki FAQ Email Lists Register Login My Profile Inbox Address Book My Subscription My Forums

Photo Gallery Member List Search Calendars FAQ Ticket List Log Out

All Forums RSS Feed Subscription:

Uninstalling GPO distributed package - installing newer version via SMS 2003

View related threads: (in this forum | in all forums)

Logged in as: Guest

Printable Version

All Forums >> [Management Products] >> Application Deployment >> Uninstalling GPO distributed package - installing newer version via SMS 2003

Page: [1]

Message

<< Older Topic Newer Topic >>

Uninstalling GPO distributed package - installing newer... - 9/4/2008 5:36:37 AM

JacobSaaby

Posts: 4
Score: 0
Joined: 9/3/2008
From: Århus C, Denmark
Status: offline

Hey all,

I have a problem and my situation is this:

Predecessor distributed a repackaged version of Python. This package does not have the ALLUSERS property set, so I'm guessing it installs in the user context.

However, I need to remove that package, and do a clean up, and then distribute new versions of the same programs - but via SMS.

So my original strategy was to:

- Disable that software gpo
- Use SMS 2003 to uninstall those particular packages
- Install the new packages

... and we'd all be happy campers.

However, I then find out, that because (is my guess) the packages are installed in user context, when the SMS client tries to uninstall them - it can't (it doesn't see them as published). Because it tries to uninstall them in another user context than the package was originally installed.

How do I solve this ?

I thought of one way so far: Add the ALLUSERS=1 property to the package, link the distribution GPO to our Workstations OU, and redeploy the package to all workstations.

That should, is my theory, reinstall the package on all machines, as published to all users, not just that specific user.

That would enable me to uninstall it via SMS 2003.

Can anyone tell me if I'm correct in assuming this ?

I also tried using an SMS job that ran msizap, then deleted the folders, but I can't seem to get that working somehow.

Any other takes on how to resolve the situation ?

Timing is important, since we're a development heavy business, and our users need that particular application, and the supporting packages.

So I HAVE to time the uninstall of GPO distributed packages, with the install of SMS 2003 distributed packages.

And sorry about the double post to the Windows Installer - MSI forum ;)

Post #: 1

RE: Uninstalling GPO distributed package - installing n... - 9/9/2008 6:18:10 PM

rbennett806

Posts: 825
Score: 13
Joined: 6/14/2006
Status: offline

Have you checked the GPO settings for that application deployment? There's a configuration setting to remove it when the GPO is no longer applied - so if it's been configured, maybe you can use that to remove the existing client automatically. And usually you'll need to tets your install/uninstall process because even if it worked for someone else, it may not work for you (everyone's environment is different). So I'd suggest setting up a test box, deploy your old Python to it, then try to remove it...

(in reply to JacobSaaby)

Post #: 2

RE: Uninstalling GPO distributed package - installing n... - 9/10/2008 2:53:36 AM

JacobSaaby

Posts: 4
Score: 0
Joined: 9/3/2008
From: Århus C, Denmark
Status: offline

Yup, I know all about that. I'm sorry if I didn't mention it, but the issue is, that there are 3 other packages connected to this, and we have to be able to uninstall the GPO based packages so we can time it with installing the new version via SMS 2003.

I think I "solved" it though. The solution is to alter the package the package to include the ALLUSERS=1 property, then redeploy the package on all clients.

Then I can uninstall it via SMS, since the SMS account can see the pacakge then.

(in reply to rbennett806)

Post #: 3

RE: Uninstalling GPO distributed package - installing n... - 9/11/2008 9:58:56 AM

JacobSaaby

Posts: 4
Score: 0
Joined: 9/3/2008
From: Århus C, Denmark
Status: offline

Right. To answer my own question:

1. Create a copy of the package on the fileshare
2. Modify the package with e.g. SuperOrca or Orca, to include the property ALLUSERS=1 (NB: Verify that the package keeps its GUID, this is essential)
3. Create a new GPO software install, based on the new package
4. Link the new GPO to the relevant OU
5. Redeploy the new package/GPO

The next time your users reboot, the package will be reinstalled. Because the GUID is the same, you basically just get the same package, but published to all users.
This enables you to uninstall it via SMS 2003 (or other deployment platforms), as the application is now available outside the installusers context (in other words, it's published on the machine, so the SMS client account can also see that the application is installed, and therefore it can trigger an uninstall).

Bugger, what a pain in the behind. I now have to redeploy it to 3-400 clients, to enable the uninstall.

(in reply to JacobSaaby)

Post #: 4