I have two seperate installs. One is a prerequisite for the other. I have the first running as SYSTEM to bypass all the UAC prompts. The other has to be installed as local admin. This will not install any other way, not even domain admin. The reason for two installs.

Is there a better way to have Kace call the other to save the users from not having to click both. It's currently working the way I have it set, but if a user forgets to install at that time then the software will not function properly. I have a popup at the end of the first install reminding them to click the other. That doesn't always work though.

I understand this will probably be a feature request, but thought I would ask here first.

Answer Summary:
Cancel
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Community Chosen Answer

2

Would it work to add to the end of the first script a batch command to run psexec pointed at the local machine with the local admin username and password and run the second install?  I know it's ugly, but it might manage to get you over to local admin.

Answered 06/01/2012 by: philologist
Red Belt

  • I was just about to try copying a bat file plus the exe to a temp dir, and then call the bat from the first install. So basically the same thing. I would think that would work. I guess a little more curious if there was a cleaner way.
Please log in to comment

Answers

0

>This will not install any other way

There's no magic to this. There is either a LaunchCondition set or possibly a Custom Action being executed which controls this behaviour. All you need to do is find it and work around it, either by removing the LaunchCondition or conditioing-out the CA.

Answered 06/06/2012 by: VBScab
Red Belt

  • There is a LaunchCondition. I was also told not to mess with the vendors software in order to keep the support. If I do remove it, and we run into a problem six months from now it will somehow be because "I removed the LaunchCondition". Since this software is a HUGE part of our enviroment I chose to find other ways. The vendor is "supposed" to be releasing an update in August that will repair this.
Please log in to comment
0

>it will somehow be because "I removed the LaunchCondition"


Don't remove it in his MSI. Use a transform.

Answered 06/06/2012 by: VBScab
Red Belt

  • It's actually a weird situation. I do have a working version that will install as SYSTEM. We have to go through a testing phase to verify that if will not affect anything later down the road. That could take a month. Since we are a hospital everything has to work perfect since patients could be affected.
    I asked this question so that I could bypass this in the meantime. This is one of the pieces of software slowing our Windows 7 migration. So it's either wait for them to test, wait until August for the update, or call from another. I chose call from another because it would take the least time.
Please log in to comment
Answer this question or Comment on this question for clarity