Index  | Recent Threads  | Unanswered Threads  | Who's Active  | Guidelines  | Search
 

Quick Go ยป
No member browsing this thread
Thread Status: Active
Total posts in this thread: 80
Posts: 80   Pages: 8   [ Previous Page | 1 2 3 4 5 6 7 8 | Next Page ]
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 7258 times and has 79 replies Next Thread
depriens
Senior Cruncher
The Netherlands
Joined: Jul 29, 2005
Post Count: 350
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Automating the deployment of BOINC Agent.

Great! I will try it out as soon as I find some spare time. Thanks a lot. cool
----------------------------------------

[Feb 23, 2006 9:41:05 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Automating the deployment of BOINC Agent.

Here is another way how to create MSI package:

- download FREEWARE WinINSTALL LE 2003
- install WinINSTALL LE 2003 on some computer (for example SERVERX)
- install clear system (Windows XP on PC) - find and run disco32.exe on SERVERX from PC and make SNAPSHOT (disco32.exe)
- install BOINC (DO NOT RUN BOINC SERVICE), set all your settings you want (delete shotcuts, set project, it is possible change BOINC service run as LOCAL SYSTEM ACCOUNT, ...)
- run disco32.exe again (it will create MSI package on SERVERX)

I tired to use it and it is working fine, no problem. I prefer create it by ORCA, but I am not able do it as I wish. This solved my problem.
[Feb 24, 2006 11:40:02 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Automating the deployment of BOINC Agent.

[EDIT] New version available 25 Feb 06 9:15AM GMT - Now allows the BOINC service to be deployed and run under the Local System user account. See updated notes below. [/EDIT]

[EDIT] New version available 28 Feb 06 7:06AM GMT - Corrects BOINC folder permissions when deployed and run under the Local System user account. (Permissions on the BOINC installation folder are set to 'SYSTEM' and 'Administrators'). [/EDIT]

Morning All

Sorry for the delay, but here is the updated version of the script to generate the MST for BOINC installs.
This version has a simple HTML interface to allow you to specify all of the options that I can think of at the moment. (Please post if you can think of any others.)

IMPORTANT NOTE.
As security has been tightened up in Internet Explorer, the code runs best as a HTML Application (HTA) as you now can not access files on your local PC without warnings popping up everywhere (If you wondering what HTA is, you can read more about it here .)

The bottom line is that it allows you to run any HTML code (including scripts) without any security settings problems and is a simple matter of renaming any .htm or .html file to .hta (That really is all there is to it!)

Instructions (Sorry, but the file grew so much, that a download seemed a better idea, rather than a 439 line post!)
1. Right click on the file link below and select 'Save Target As...' to download it to your PC (It's just a text file incase your browser/antivirus would otherwise throw a wobbly!) WCG_BOINC_MST_Creator.hta
2. Double click it to start.

Notes.
Hopefully everything is pretty straight forward, but here are some notes on each item anyway.
1. Path to BOINC.MSI file - Providing you're using Windows XP, you can click the little button at the end of the text box to select the extracted BOINC.msi file. Otherwise you have to manually type it in. (The full path and file are required.)
2. Your BOINC Account Key - Click the link to get your BOINC Account key from the WCG website and copy it in to the text box.
3. Device Profile - Allows you set the profile that the PC will use when running BOINC. This can always be changed using the Device Manager on the WCG website.
4. Install Method - best described here on the official BOINC website
5. Remove 'Programs Menu' Shortcut - Removes the folder 'BOINC' and shortcuts from the Programs menu.
6. Removes BOINC from the 'Add/Remove Programs' list - I would only suggest using this with a service installation otherwise it can be a bit of a pain trying to uninstall or repair the application.
7. Location to install BOINC to - Any path you like. The normal path will be displayed by default.
8. Automatically enable the screensaver - Ditto 4. above, but of no use with service installations
9. Automatically start BOINC when users sign on - Ditto 4. above. It just removes the 'Startup Menu' shortcut.
10.Launch BOINC Manager after setup completes - Ditto 4. above.
11.User account for the service (optional) - Ditto 4. above. Only available when a Service Installation is selected. The existance of the username is checked, so if you are using a username for you domain, (eg MYDOMAIN\Fred.Bloggs) you have to run this program on a PC that is attached to the domain. If you do not enter a username the service runs using the Local System account.
12.Password for the user account - Ditto 11. above. The password need confirming in the second textbox. NB. The Password is unfortunately stored in clear text in the mst.
13.Allowed Remote Hosts (one per line) - Checkout this page on the Unofficial BOINC website. Remember that you may have to adjust your firewall settings if you're considering using this over the internet.
14.Remote Access password - Again, look at this page on the Unofficial BOINC website. Please note that a password is only optional and is stored in clear text in the gui_rpc_auth.cfg file.

Items 13 and 14 allow you to see up all of your PC on your network, so that you can use just one PC to monitor the lot. Whilst BOINC Manager allows you access remote computers individually, you might want to try BoincView (It's nice to see all of the PCs crunching away at once, plus is great way of spotting problems.)

Have fun with this and let me know of any problems you may have.

Regards Slug
----------------------------------------
[Edit 6 times, last edit by Former Member at Mar 13, 2006 9:26:32 AM]
[Feb 24, 2006 1:25:09 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Automating the deployment of BOINC Agent.

Hi michalsx
Here is another way how to create MSI package:
- download FREEWARE WinINSTALL LE 2003
- install WinINSTALL LE 2003 on some computer (for example SERVERX)
- install clear system (Windows XP on PC) - find and run disco32.exe on SERVERX from PC and make SNAPSHOT (disco32.exe)
- install BOINC (DO NOT RUN BOINC SERVICE), set all your settings you want (delete shotcuts, set project, it is possible change BOINC service run as LOCAL SYSTEM ACCOUNT, ...)
- run disco32.exe again (it will create MSI package on SERVERX)

I tired to use it and it is working fine, no problem. I prefer create it by ORCA, but I am not able do it as I wish. This solved my problem.


We're actually quite lucky that BOINC is a simple install (I won't even start on QuickTime....Grrrrrrrr!!!!!)

The upside to using the MST though is that
a) You don't have to bother with the above. (Clean machines are a pain, but are really the way to go with repackaging. You might want to try Microsoft's Virtual PC Trial - very handy for this sort of thing)
b) The same MST can be used for minor upgrades (BOINC had 4 such upgrades in about a week a couple of months back.)
c)The MST creation is now much quicker (See above post biggrin )

Is the Local System Account for the service the only reason for the custom packaging ???? (I quite agree it's a pain)

Regards Slug
[Feb 24, 2006 3:22:57 PM]   Link   Report threatening or abusive post: please login first  Go to top 
depriens
Senior Cruncher
The Netherlands
Joined: Jul 29, 2005
Post Count: 350
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Automating the deployment of BOINC Agent.

Sorry for my ignorance, but I really don't understand it. Please help! blushing blushing blushing

This is what I did so far:

- Created the BOINC.msi and modified it with Orca.
- Saved the BOINC Modifications.mst

All this according to the information on the first page.

Now I would like to use our server to install the BOINC onto various workstations without actually working on those workstations.
So I would like to carry out the install from the server. Is this possible? If so, please help me a little! blushing



@michalsx, the "Deny Taskmanager" works great! cool
----------------------------------------

[Feb 24, 2006 9:18:15 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Automating the deployment of BOINC Agent.

Morning depriens

Here is how to deploy BOINC on your network with Windows 2003 SBS Server. I thought It would be a good idea to start from the begining again. (I do not know how good you are with computers, so I have made the instructions very detailed.)

1. Logon to your Windows 2003 Server with the Administrator username and password.
2. Download the latest version of BOINC from here and save it to your desktop.
3. Download the file WCG_BOINC_MST_Creator.hta by clicking this link
4. Click 'Start' > 'Run', delete any text that maybe in the box and drag the file boinc_5.2.13_windows_intelx86.exe from your Desktop into it. Go to the end of the text in the box and add a space then /a. You should end up with something like this.
"C:\Documents and Settings\Administrator\Desktop\boinc_5.2.13_windows_intelx86.exe" /a
Click the OK button to start the creation of the Administration package. (If you get a security warning, just click the 'Run' button.)
5. Click Next once and you will be asked for a 'Network Location'. In this box you want to enter your server's name and the network location where SBS stores applications (this is called 'ClientApps') and a 'BOINC' folder. So, if your server is called MYSERVER you should enter
\\MYSERVER\ClientApps\BOINC
Click the 'Install' button. After the files have been processed, Untick the 'Launch BOINC' checkbox in the final window and click 'Finish'
6. Rename the file WCG_BOINC_MST_Creator.htm to WCG_BOINC_MST_Creator.hta Click 'Yes' when you get the warning about changing file extensions.
7. Double click the WCG_BOINC_MST_Creator.hta file. In the window that appears, fill in the information as I have in the example below. Don't forget to use your own BOINC account key and use you own server name rather than MYSERVER.

You can change any of the checkboxes, Default Profile and 'Location to install BOINC to', but, personally, I would not add a username/password for the service and would not have BOINC automatically start when a user logs on. If you want to use the BOINC Manager or BoincView to view the state of BOINC on the PCs with your server, add the IP address of your server's 'Server Local Area Connection' network connection in the Allow Remote Access box. (You can get that by running IPconfig in a command window. The Default on SBS is 192.168.0.1) As you will be running on an internal network, I would not bother with a password.
7. Click the 'Generate MST' button and after a few moments a message should appear saying that the MST has been created. Close the message and the window. You can now delete WCG_BOINC_MST_Creator.hta and boinc_5.2.13_windows_intelx86.exe from your Desktop.

Now to deploy BOINC to your PCs (As you're using SBS, we'll use some of the built in wizards to make things a bit easier!)
1. Click Start > Server Management.
2. In the left panel, click Security Groups. (The right panel will list all of the individual security groups that have been created on the server)
3. In the right panel click Add a Security Group. In the 'Welcome' window, click Next.
4. In the 'Name of the Security group:' textbox, enter the following

(You can change the name and description if you want to) Click Next.
5. In the Group Membership window you will find that only users are shown, not individual computers, so we will do nothing here. Just click Next and then Finish. Close the window that shows that the group being created when it has finished. Close Server management.
6. Open Active Directory and in the left panel select YOURDOMAIN.local > MyBusiness > Security Groups. In the right panel, double click the security group called 'World Community Grid' and click the 'Members' tab
7. Click 'Add' and in new window, click 'Object Types'. In this new window, make sure that 'Computers' are ticked and the rest unticked. Click OK. Now Click 'Advanced' and then 'Find Now'. All of your computers will now appear in the bottom of the window.
8. Select all of the computer that you want to run BOINC on (NOT THE SERVER) and then click OK. Click OK again and you should be back on the members tab which will now show all of the computers you have selected. (You can change your selection at any time if you get new computers or need to remove BOINC from one.) Click Ok to close the security group properties window.
9. Open Group Policy Management and navigate to Forest: YOURDOMAIN.local > Domains > YOURDOMAIN.local > MyBusiness. Right click MyBusiness and select 'Create and Link a GPO Here...'
10. Name the GPO 'World Community Grid (BOINC)'. Click OK and the new item will listed under MyBusiness.
11. Left click the new GPO and in the right panel, at the bottom, you will see 'Authenticated Users'. Click the 'Add Button' below and in the window that appears enter the name of the security group created earlier (you only need to type the first few letters as the server will work it out !). Click OK. Select 'Authenticated Users' and then click the 'Remove' button. (Click Ok to confirm the removal.)
12. Right click the new GPO in the left panel and select 'Edit'. In the Group Policy Object Editor window that will open, navigate to Computer Configuration > Software Settings > Software installation. As this is the first time you have used this GPO, right click 'Software installation' and select properties. In the window as shown below. Again, do not forget to use your server's name

Click OK.
13. Right click the new GPO again and select New > Package... In this window, select the folder BOINC and then the BOINC.msi file. Click Open
14. In the next window, click the 'Advanced 'option and then OK (This is important as you can not add an mst to an msi later)
15. In the BOINC properties window, click the 'Modifications' tab. Click the 'Add' button, select the BOINC folder and then the BOINC.mst file. Click 'Open' and now click OK. (After a moment, an item called 'BOINC' will appear. If you ever need to remove it because of an upgrade, right click BOINC and select All Tasks > Remove... Accept the default option and click OK.)

If you decided to use the Allow Remote Access in the MST creation bit, you will have to modify the windows firewall if it is running on the local domain. Fortunately, you can also do this with the GPO.
16. In the Group Policy, Navigate to Computer Configuration, Administrative Templates > Network > Network Connections > Windows Firewall > Domain Profile. In the right panel open the option 'Windows Firewall: Define port exceptions.' Select the 'Enable' Option and then the 'Show' button. Click 'Add' and in the textbox put
1043:TCP:192.168.0.1:Enabled:BOINC
(Obviously, use your servers IP address, which maybe differerent from the 192.168.0.1 that I have used in the example above.) Click OK > OK > OK

17. Close all of the windows on your server and then restart your workstations. BOINC will now be installed on all of the ones you added to the security group.
----------------------------------------
[Edit 2 times, last edit by Former Member at Mar 13, 2006 9:28:20 AM]
[Feb 25, 2006 12:56:27 PM]   Link   Report threatening or abusive post: please login first  Go to top 
depriens
Senior Cruncher
The Netherlands
Joined: Jul 29, 2005
Post Count: 350
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Automating the deployment of BOINC Agent.

Hi The Lazy Slug,

Thank you so much for this detailed explanation! All the steps were really easy to complete!

Unfortunately it still doesn't work. crying crying crying
Everything went fine. All the required steps were okay, I could find all the things you asked for.
Created the msi
Created the mst
Created the security group
Created the GPO
Changed everything in how it should be.

Rebooted the workstation on which BOINC should be installed --> no result.
Rebooted the server and the workstation --> no result
Changed the Security Group into Distribution Group and rebooted the Workstation again --> no result

I checked in C:\Program Files but there was no BOINC directory. In taskmanager there is no BOINC process and the CPU is used for 0%. crying


I don't know if there are any options left to try and sort it out??
Anyway, thanks a lot for all the effort which you have put into helping me so far!!


BTW: I'm doing all this from my home address with external access to the Server and the Workstations. I hope this doesn't make any difference...
----------------------------------------

[Feb 25, 2006 7:02:25 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Automating the deployment of BOINC Agent.

Evening depreins
I'm doing all this from my home address with external access to the Server and the Workstations. I hope this doesn't make any difference...
I'm doing exactly the same - it is the best feature of SBS !

Back to your problem...

Just for your info, when the workstation is restarted and you are sitting in front of the screen (not remote desktop, I'm afraid), you will see the information window that displays 'Starting Windows...', 'Applying Security settings...', etc. You should also see 'Apply Software...' followed by 'Installing BOINC...'. The login windows will then appear.

To find out the problem, can you post the event viewer log for the applications section for the workstation you are installing BOINC to. The errors in question will be marked 'Application Management' and will appear just after the workstation is restarted.

Changed the Security Group into Distribution Group and rebooted the Workstation again
Change it back, A distribution group does not distribute software. (Not a very helpful name, I know !!! smile )
[Feb 25, 2006 10:42:00 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Automating the deployment of BOINC Agent.

Ah...Of Course....PERMISSIONS !!!! (Just remembered I had this problem as well!!!!)

As mentioned previously, when SBS is setup, a network share called 'ClientApps' is created for storing applications. This is setup with permissions to allow 'Domain Users' to 'Read' the share. Unfortunately it does not setup permissions for 'Domain Computers' to 'Read' the share as well. (If you deploy applications using the 'Computer Configuration' section of a GPO, as we have done, this permission needs to be added.)

So, using Explorer, browse to 'ClientApps' By default it will be found at C:\ClientApps If it has been moved by who ever installed your server, you may have to do a search for the folder. (Just as a precaution, if the folder has been moved, check that it has been done correctly as per this document from Microsoft otherwise you could have problems with service packs in the future.)

Once you have found 'ClientApps', right click it and select 'Properties'. Click the 'Sharing' tab (Not 'Security') and you should see this display

Click the 'Permissions' button. In the window that appears, you should see that permissions will have been set for 'Domain Users' and 'Administrators'. Click the 'Add' button and in the new window that pops up enter
Domain Computers
Click OK and you should have a display looking like this (I have removed my domain name from the image)

Click 'OK' on all of the open windows and close Explorer.

One final thing I forgot in my instructions was that 'Windows Installer' has to have two settings changed in the Group Policy you created.
Open the Group Policy and navigate to Computer Configuration > Administrative Templates > Windows Components > Windows Installer. In the right panel, you will see the policy 'Always Install with elevated privileges'. Open it and enable it. As you may notice, the policy also has to be set in User Configuration > Administrative Templates > Windows Components > Windows Installer too, so do that as well.

Close all of your open windows and on the workstation run GPUPDATE /FORCE (Thanks michalsx for the reminder on that!) and when prompted, restart the workstation.

Hopefully this should sort out the problem.

Regards Slug
[Feb 26, 2006 9:24:04 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Automating the deployment of BOINC Agent.

Hi Lazy, I just want to thank you. For snapshot I need about 2 hours to prepare MSI package. With you script it takes about 5 minutes? wink
[Feb 26, 2006 10:48:41 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Posts: 80   Pages: 8   [ Previous Page | 1 2 3 4 5 6 7 8 | Next Page ]
[ Jump to Last Post ]
Post new Thread