Hidden operation installation

[SCHHCC Tech]

Reference: ticket #393 ?

Environment: public PC with admin account. Upon windows logoff; machine is 're-imaged'.

Requirement: No public person is to have access to Boinc via the Boinc tray icon. Other obvious routes can be hidden; less obvious routes, oh well.

Approach: I have eliminated the MSCONFIG entry ...boincmgr.exe /a /s. This is replaced with a Task Scheduler enrty ...bioncmgr /a /m. Trigger is startup + 1 minute, running under a 2nd hidden admin account. This avoids the tray icon.

results: Mostly works, however at times no processing is kick off. May well not be due to my approach.

Question-1: Is boinctray.exe needed in MSCONFIG to launch under the active / logon admin account? Gossip says it is needed to honer the PC-in-use constraints.

Question-2: Is it or was it ever true that the install option to run in protected mode requires a non-admin account to host the session, and does that account have to be non-batch?

Question-3: The approach of 'protected mode' is known to corrupt the gpu for other apps?

apologizes: As an old mainframe guy; I realize a trouble ticket system is not the place to ask questions.

bottom line: Provide a concise step by step doc to allow a 'hidden' approach to running Boinc.

[Christian Beer]

You're right this would be better on the boinc_dev mailing list or the dev Forums. But let me try to answer some of your questions here: If the PC gets re-Imaged it would be good to include the Client in this image and have the data directory on a server storage so the client can pick up where it left. I heard of this on the mailing list one time.

Some options for a mass deployment are here: creating custom installers (This is mainly for 6.x Clients so you may ask in the mailing list about some newer information

With a service install you an also restrict who can control the client on this machine (must be a member of the boinc_master group I think)