NEW Software will not install as System account. What do you do?

[dragonfligh]

I am trying(and trying, and trying some more) to install a piece of software that will not install as system.

I have confirmed by running psexec64.exe -i -s setup.exe it produces an error saying it cant overwrite the file that already exists in C:\windows\temp

The software will install all day if you run as administrator under user context.

It's an Installaware package. I have tried /s, ALLUSERS=TRUE, OVERRIDECACHE

SCCM is our deployment tool (miss my K1000 from a previous life).

Ideas?

 

[Garth]

Did you create a log file during the setup? And exactly which file does it say it can't overwrite?

 

[dragonfligh]

Garth,
I do not know the switch to output a log file.

It's trying to overwrite the files it puts into C:\Windows\temp, i.e., C:\Windows\temp\mia.tmp\setup.exe

Paul

 

[Garth]

You need to talk to the vendor and find out what the log switch is. Does that file exist in that temp folder? What folder are you running the setup from?

 

[dragonfligh]

Yes, the file exists in that temp folder.
Doesn't matter what folder the install is run from, it will extract to that temp folder.
Vendor is not an option.
Looking for creative solution to run this setup.exe outside of the system context with elevated privileges via SCCM Software Center.
That's all. Not too much to ask.

 

[Garth]

And why can't you talk to the vendor? They are the ones that can tell you how their program works and how to make it work in an enterprise. Without talking to them you and everyone else will be guessing at the problem and therefore the solutions.

Having said that the my guess at the problem is profiles, most likely environment variable within the profiles. Maybe %Appdata% / %programdata%; maybe path, etc.

 

[dragonfligh]

Thank you Garth. I'm not necessarily looking for the solution from the community(though it would be nice), I'm looking for folks who have run into this same challenge and what they did. Sharing thoughts and ideas.

I am sure there is someone that has run into this and has a creative solution for installing software elevated for the end user, without running as system. Psexec or similar tool? Powershell?

With the Quest K1000 there was the ability to choose to run as a different user(domain\adminuser), I don't see that option with SCCM. Closest thing I can find in SCCM is running a task sequence with a run as.

 

[Garth]

Thank you Garth. I'm not necessarily looking for the solution from the community(though it would be nice), I'm looking for folks who have run into this same challenge and what they did. Sharing thoughts and ideas.

I am sure there is someone that has run into this and has a creative solution for installing software elevated for the end user, without running as system. Psexec or similar tool? Powershell?

With the Quest K1000 there was the ability to choose to run as a different user(domain\adminuser), I don't see that option with SCCM. Closest thing I can find in SCCM is running a task sequence with a run as.

You will not see an option to run a a particular user (admin) as this is a security risk. a TS is your only options in this case, which will require the account to be admins on each computer that you want to install this SW.

 

[dragonfligh]

Thanks Garth.
I'll be patient, interested in what others in the community are doing as well.

 

[MJ-Tech]

Are you using adminstudio for packaging?

Please check below options, [Source : Wisescript or VBscript)

• Prior to installing the setup.exe, create a script to delete the temp folder (I guess the exe name might change randomly on each installation. if not, you can delete the exe alone before installation)
• Enable userinterface (Deployment types -> edit -> User Experience tab -> check "allow users to view and interact with the program installation")