|
| | | Junior Member
 
Group: Forum Members
Last Login: 12/19/2006 11:05:57 AM
Posts: 16, Visits: 29 |
| | ** No i haven't received point 5.1 yet, been waiting for ever and a day!! BUT WHEN I DO...* I Understand if i install workstations with run.exe , all updates will be pushed to the workstations. But if the user logged into the workstation is a "limited user" , who can't install applications. it will just error out. What is a way around this? |
| |
| | | 
Supreme Being
Group: Moderators
Last Login: 12/21/2008 11:16:31 PM
Posts: 837, Visits: 1,901 |
| | I understand it's far from secure to grant Local Admin rights on each computer across a domain. However, the InstallShield Wizard used by Point requires Administrator rights to run. During a typical software installation, some system files may be added that are needed by the application, and you wouldn't want "limited users" to have that ability all the time. Hopefully, Calyx will move to using a Windows Installer package (*.msi file) for installing Point. This would have some flexibility to allow an user that is not an Administrator to install software, but still protects the system from unauthorized changes. One other thought: It might be possible with Group Policy Editor to change install rights for non-administrator users, but I haven't tried it.
Bryan
Point Product Manager |
| |
| | | 
Forum Member
Group: Moderators
Last Login: 10/2/2006 4:26:56 PM
Posts: 33, Visits: 118 |
| | realized - What are the target operating systems you need to do the upgrades on? Advanced ideas that might lead to a solution: - Startup script that the clients have to run at boot time applied by the Domain (via gpedit.msc Group Policy Editor, or Active Directory). This script could run the Point setup when the clients boot with the elevated privileges needed. Some organizations will already have startup scripts in use.
- Scheduled task created by the administrator that runs the Point setup regularly at an hour when no-one is working or has Point open.
- Runas using a special locked down account just for installing Point. Requires the users to manually do the runas login and very careful configuration of the locked down account with testing... The account could be restricted as to what programs it is allowed to run and other restrictions.
|
| |
| | | Junior Member
Group: Forum Members
Last Login: 12/19/2006 11:05:57 AM
Posts: 16, Visits: 29 |
| | I think i will try group policy to give acess to run the run.exe file as admin at all times, hopefully no lo will get smart and rename everything to run.exe ! Or the idea of a script at startup.. I think a mmc package would be good, a central location where i can see all my workstations, see what version of point they have etc, see what needs to be upgraded if any, and so on. Lots of companies are starting to use this. Microsoft Management Console works great for things like this  I hope calyx sees this post! |
| |
| | | 
Sepal
Group: Moderators
Last Login: Today @ 6:19:09 AM
Posts: 1,183, Visits: 9,259 |
| run.exe is just around for nostalgia. Our process uses setup.exe so that is what you will have to give the rights to.
Disclaimer: This post carries no explicit or implied warranty. Nor is there any guarantee that the information contained in this post is accurate. It is offered in the hopes of helping others, but you use it at your own risk. The author will not be liable for any damages that occur as a result of using this post.  |
| |
| | |
Supreme Being
Group: Moderators
Last Login: 12/21/2008 11:16:31 PM
Posts: 837, Visits: 1,901 |
| | "Run.exe" is a launcher application. It just launches an instance of InstallShield Wizard, and the wizard is still going to check for Admin rights. You may get more success with the startup script method. Great suggestion on using MMC. Thanks!
Bryan
Point Product Manager |
| |
| | |
Forum Member
Group: Moderators
Last Login: 10/2/2006 4:26:56 PM
Posts: 33, Visits: 118 |
| | |
| | | Forum Newbie
Group: Forum Members
Last Login: 9/7/2005 2:19:40 PM
Posts: 1, Visits: 1 |
| | I use WSH for my logon scripts. This is the code that i added to execute the install at logon If Fso.FileExists ("c:\point51.txt") thenelse wshshell.Run "\\stateetsetup\setup.exe",3, trueFSO.CreateTextFile "c:\point51.txt", trueEnd If Checks to see if installed if not, it installs it and creates the check so it doesn't reinstall it. |
| |
| | | Forum Newbie
Group: Forum Members
Last Login: 12/21/2005 6:13:32 PM
Posts: 1, Visits: 3 |
| | There is an easy solution. Once you have copied the shortcut "run.exe" to the desktop, right click on it the click properties. A dialog box will open. About halfway down on the right will be a check box labeled "run as different user" check that box then click apply and then ok. Then click on "run.exe" and it will give you the option to enter the user name and password of the user you want to run the program Steve Marchbanks AmTrust Funding |
| |
|
|