We have recently removed local admin from all users and are now in the process of removing unapproved software from users PC's. The users installed the software themselves whilst they had local admin.

We use SMS2003 as our deployment tool.

I use the following command line (in an .exe file so that SMS can run it) to uninstall a package. This was taken from the registry and then modified with a response file so that it can run silently.

"C:\Program Files\Common Files\InstallShield\Driver\8\Intel 32\IDriver.exe" /M{3CB41017-F5CA-4C56-934C-ED02156251E6} /s /f1"c:\windows\uninstall.iss" (Under testing I have removed the /s so that I can see any error messages)

The problem is that when I run this .exe file from SMS it runs with SYSTEM rights. The package has a check in it to check if the account that is running it has admin rights. The SYSTEM account doesn't have local admin and I get the message "You do not have sufficient privileges... Please log on as an administrator."

The SYSTEM account has enough rights to uninstall, the problem is the package has a check built into it to check for admin rights.

Does anyone have any ideas on how I can get around this?
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity



I don't use SMS, so forgive me if this is gibberish - I'll just say how I remotely install things. I use a KIX script, combined with PSEXEC.

You could have a BAT file with your uninstall syntax, copy it over to a folder on the remote workstation (the one you want to uninstall the app), and run it from a workstation/server using
PSEXEC -s -d \\workstation -u username -p password pathtobatchfile.bat

where -u and -p are optional extras if the user running the psexec is NOT an administrator of the target workstation.

SO for example, you would have something like..

XCOPY "uninstall_driver.bat" "\\workstation\c$\temp"
PSEXEC -s -d -u Administrator -p Adminpass c:\temp\uninstall_driver.bat

(-u and -p wouldn't be needed if the user ID running this script had Admin rights on the target workstation)

I hope this makes some kind of sense? I'm not terribly good at explaining my thought processes :-)

I also apologise if this isn't anything close to the answer you were looking for.

Answered 03/08/2005 by: sirclive
Senior Yellow Belt

Please log in to comment
Are you dropping the response file on the machine, or is it already there when you run this command?

Usually necessary permissions are set there.

Also, why is the account SMS uses on all machines not a local admin? It would save you numerous headaches.
Answered 03/08/2005 by: Bladerun
Green Belt

Please log in to comment
I have the same SMS 2003 problem during a package installation (BlackBerry Desktop Software 4.0) if the user haven't admin right.

I'm not sure if it could help because I can't try this fix:
Answered 03/31/2005 by: auroauro
Yellow Belt

Please log in to comment