wIntegrate Deployment Nightmare
Hello All,
I'm having difficulties deploying some software called wIntegrate. It's an old terminal emulation software originally developed by IBM and it is shit.
However, I can't get rid of it now since it is integrated so conveniently into our network. This piece of software is a constant headache that I would like to fix through GPOs.
The software requires local admin rights to install and must be installed in each users profile who access the computer separately by installing over the original install. You can not install this software under the admin account and expect it to work in a user profile as you will get registry and permission errors.
I'm not looking for help on distributing the software (yet), I'm just looking for assistance on where I can start to help get this software working for all users by installing the software using the runas and using an administrator account. I'm trying to avoid everyone having local admin rights all the time.
Where can I start?
I'm having difficulties deploying some software called wIntegrate. It's an old terminal emulation software originally developed by IBM and it is shit.
However, I can't get rid of it now since it is integrated so conveniently into our network. This piece of software is a constant headache that I would like to fix through GPOs.
The software requires local admin rights to install and must be installed in each users profile who access the computer separately by installing over the original install. You can not install this software under the admin account and expect it to work in a user profile as you will get registry and permission errors.
I'm not looking for help on distributing the software (yet), I'm just looking for assistance on where I can start to help get this software working for all users by installing the software using the runas and using an administrator account. I'm trying to avoid everyone having local admin rights all the time.
Where can I start?
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
anonymous_9363
14 years ago
Sounds to me like a straightforward per-user GPO deployment. That is, you add the MSI and MST to the 'User configuration' instead of 'Computer configuration'. Make users members of a group scoped to the GPO link. After they're added to the group (and a suitable wait for AD replication), they'll receive the deployment when they log in. Removing them from the group triggers the package's removal when they log in.
For good measure, explicitly set ALLUSERS={} (i.e. set it to null, NOT an empty string!) in the MST to make sure you get a per-user install.
EDIT:
Don't forget to advise the idiot vendor that his brain-dead configuration means that the license terms of the application are probably violated (most licenses restrict installs to "one package, one machine"). Clearly, per-user installs present the likelihood that a user's apps get installed onto whichever machine they log in to. Equally clearly, these apps don't get removed when said user returns to his/her regular machine.
For good measure, explicitly set ALLUSERS={} (i.e. set it to null, NOT an empty string!) in the MST to make sure you get a per-user install.
EDIT:
Don't forget to advise the idiot vendor that his brain-dead configuration means that the license terms of the application are probably violated (most licenses restrict installs to "one package, one machine"). Clearly, per-user installs present the likelihood that a user's apps get installed onto whichever machine they log in to. Equally clearly, these apps don't get removed when said user returns to his/her regular machine.
Posted by:
morrty
14 years ago
Thank you, I'll give that a shot and let you know whether it worked or not.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.