| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: Boinc installation using normal User type (NO Admin Right) |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 9
|
|
| Author |
|
|
IT067015
Cruncher Joined: May 10, 2007 Post Count: 11 Status: Offline |
Boinc agent for Windows. A potential partner with thousands of PC has more than 50% of users with USER rights on the PC. This is stopping the mass install in their intranet.
The Admin right is required by the msi file. We modified the msi file and removed the Admin check pre installation property. The installation Single User starts but we have 2 error messages: 1. The Boinc.scr cannot be copied in C:\winnt (Admin right required) 2. The Boinc.dll cannot be registered (Admin right required) I need suggestions what to modify in the msi file in order to avoid these 2 actions that I suppose are not necessary (the client installs and runs) The shared users install doesn't start, but I suppose it is due to the access to All Users Startup directory restricted to Admin users. Thanks for your help |
|||
|
||||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Boinc agent for Windows. A potential partner with thousands of PC has more than 50% of users with USER rights on the PC. This is stopping the mass install in their intranet. The Admin right is required by the msi file. We modified the msi file and removed the Admin check pre installation property. The installation Single User starts but we have 2 error messages: 1. The Boinc.scr cannot be copied in C:\winnt (Admin right required) 2. The Boinc.dll cannot be registered (Admin right required) I need suggestions what to modify in the msi file in order to avoid these 2 actions that I suppose are not necessary (the client installs and runs) The shared users install doesn't start, but I suppose it is due to the access to All Users Startup directory restricted to Admin users. Thanks for your help I use this sites tools to create a transform for mass installation using Zenworks, Active Directory ect... (any push technology). http://www.thelazyslug.com/boinc.htm It's very helpful. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I strongly advise you to do an elevated install, and to choose the service option. This will let BOINC run no matter who is logged on (or not).
Please ask if you need further help with this. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I strongly advise you to do an elevated install, and to choose the service option. This will let BOINC run no matter who is logged on (or not). Please ask if you need further help with this. Oh yes. That is the only way I install boinc here. Good catch. |
||
|
|
IT067015
Cruncher Joined: May 10, 2007 Post Count: 11 Status: Offline |
May you explain it a little bit more?
Elevated install is with an Admin user? We want to leave installation choice to the user. We have a network drive with the personalized install directory. From the Intranet Portal they select and launch the install on their PC. Multiple device on a single registered user. That's why we want to leave normal User to install but the 2 error messages are not nice. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
If you have a domain (as I assume you do) you can deploy using Active Directory. You can either push the installation to all the users or computers you want, or you can allow your users to pull the installation from the server - either automatically using advertised shortcuts, or manually using Add or Remove Programs.
Assuming you want to go with this last option: From the user's perspective, all they need to do is go to Add or Remove Programs, and go to the Add New Programs tab. Here will be a list of pre-approved (published) applications. When the user starts the installation, it is automatically elevated. That is, the installation runs as though it has full system rights. From the system administrator's point of view, things are a little more complicated. There is a brilliant guide on how to set things up here: http://www.thelazyslug.com/boinc.htm For complete details of Active Directory software deployment, read this: http://www.microsoft.com/technet/prodtechnol/...0serv/howto/instmain.mspx You will want to publish to users, although the more common option for BOINC is to assign to computers. If you need more help, or if you want to try an easier option, please ask again. The BOINC installer is currently being redesigned, and all the input we can get is immeasurably useful. |
||
|
|
IT067015
Cruncher Joined: May 10, 2007 Post Count: 11 Status: Offline |
Thanks. some details:
we have a domain (as I assume you do) and we deploy using Active Directory. we allow our users to pull the installation from the server manually using Add or Remove Programs. From the user's perspective, all they need to do is go to Add or Remove Programs, and go to the Add New Programs tab. Here will be a list of pre-approved (published) applications. When the user starts the installation, it is automatically elevated. That is, the installation runs as though it has full system rights. This is the pont. The installation runs only with Admin rights and 50% of users has only USER rights. No way to change permissions, either on write permissions on c:\winnt. So we are trying to let install the client to ALL users using the lower rights possible. Remove the Admin check brings to the 2 little errors we found. Is it possible to remove easily these 2 actions (register the boinc.dll and copy the boinc.scr) in the msi? If not, we can try different ways. But I want to focus on this. Suggestions where and how to change the CURRENT msi are welcome |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
You can probably remove those safely.
However, I strongly recommend an elevated Active Directory installation. |
||
|
|
IT067015
Cruncher Joined: May 10, 2007 Post Count: 11 Status: Offline |
update.
we managed to have a correct packaged procedure with: a modified .msi (5.8.16) without Admin check a .mst file created with the utility in http://www.thelazyslug.com/boinc.htm with the Remove Boinc from the ADD/REMOVE programs list unchecked. a distribution to the client via Active directory and group policy. The installation run perfectly but the SYSTEMCOMPONENT registry entry for BOINC is set to 1 instead to 0 so the Boinc icon IS NOT LISTED in the ADD REMOVE Programs (while the Boinc program is registered properly). Any idea where we have to check the .mst file in order to avoid this problem? The .mst file contains a property called ARPSYSTEMCOMPONENT=0 Thanks |
||
|
|
|