Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
![]() |
World Community Grid Forums
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
No member browsing this thread |
Thread Status: Active Total posts in this thread: 2
|
![]() |
Author |
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
It would be sensible to support administrators in deploying to significant numbers of workstations. The FAQs suggest that this 'is not a supported configuration' due to the requirement to log in on each machine individually to create the device profile. Surely the device profile can be created dynamically if one does not exist for that user/device combination.
I administer around 350 p4 3.2GHz machines and 70 p4 EM64T 3.6's and would love to be able to deploy the agent to all of these via group policy/msi. Unfortunately, the restrictions on this type of deployment make it a throughly impractial exercise. Ultimately, I would like to see the installer understand a couple of MSI properties which I could provide values for either by making an MST or by directly editing the MSI. I am guessing that the following would need to be set: - proxy address - proxy username - proxy password - WCG username - WCG password (hashed, if possible - though this is little consolation) Until this issue is rectified, you'll only see a measly one or two workstations contributing from my area. |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I agree... I would also like to see the app run as a system service (in a non-GUI mode). If it is only loaded as the user then the hundreds of thousands of hours our machines sit at the login box are wasted. I know SETI@Home did this. We have a few thousand machines here and I could use every one of them if I could batch delpoy it. I can tell you right now that I can't send our techs out to install this all over the hospital but if I could spend 20 min setting up an object then I would.
My holiday wish list: A non-GUI version that runs as the system account via a system service and starts with the machine (not when an user logs in) deployed through a silent .MSI that I could push through a Windows Group Policy Object. -Mark |
||
|
|
![]() |