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.
|
Printable Version
Uninstalling GPO distributed package - installing newer... - 
New Messages
No New Messages
Hot Topic w/ New Messages
Hot Topic w/o New Messages
Locked w/ New Messages
Locked w/o New Messages
Post New Thread