Changes

Jump to: navigation, search

Firefox Deployment Kit

1,247 bytes added, 18:18, 19 April 2008
→‎Builds
* http://www.frontmotion.com/ - A company that has developed a .msi install file for pushing through AD
 
* Add MSI to Firefox https://bugzilla.mozilla.org/show_bug.cgi?id=231062
== Documentation of Research ==
Jan 24th - I've done some research on pushing an install through active directory. With Microsoft's Server 2003 it is possible to push an install to clients using group policy and a .msi file. Since most Firefox installers are .exe I had to do some looking for a .msi file. I was able to find one from a company called FrontMotion. They develop .msi files for the very reason of pushing them through AD (active directory). To read more about this, read my Jan 25th build statement.
 
Jan 26th - Successful remote install of Firefox over a network using the .msi file from FrontMotion.
 
Jan 28th - I've done some research into customizing a push of Firefox over the network. I'd ideally like to create a tool like Mkaply's CCK tool which exports an .xpi file to customize
Firefox.
 
Feb 1st - Turns out there could be an easier way of customizing Firefox. There are server admin files (also known as .adm) files that allow an admin to customize and install of Firefox over a network. Such settings include install directory and default browser settings.
 
Feb 4th - I've been successful in using a .adm file to customize a push of Firefox over the network. After doing so, I'd like to do some more research into figuring out how this .adm file interacts with the install.
 
Feb 6th - Today I've started to get a little lost again. Not only do I have to create an .msi I am actually attempting to create a program that can create and customize .msi files. I figure the most important thing is to understand more about .msi files so I can edit/create them.
 
Feb 8th - So I did some research on .msi files. There are tons of tutorials on the internet on how to use automated tools to create .msi files. I need to manually do it so that I can customize it. I found a Microsoft SDK on the internet for it. I am currently downloading it and will begin my work with it tomorrow.
 
Feb 9th - Knowing that I must produce some tangible code for this week I have been really stressing about my project. I feel somewhat lost. I've used a tool called Orca (included in the SDK) that has allowed me open some .msi files and edit them. I still know very little about creating .msi files.
 
Feb 10th - After speaking with David Humphrey I feel much better about my work. He has pointed me at a project know as Wix. Which seems to be an OS SDK for developing .msi files. Since I'm at work I can't write more yet.
 
Feb 14th - I've spent a ton of time trying to get the Wix toolset to build in a Vista environment. This has turned out to be nothing but annoying and I've decieded to move my project to a Windows XP platform.
 
Feb 17th - After trying to get the Wix source files to build for hours I've realized that I forgot to install the Windows SDK which is not listed as a prerequist to building the source code on the Wix website.
 
Feb 18th - I was able to build the source code finally. I also realized I could have just downloaded the binaries. I'm not to impressed with myself.
 
Feb 20th - Today I was able to actually build something with the Wix toolset. I had to read a small tutorial on building .msi files but after that I was able to build a very basic .msi. I will try to attach both the .msi and the script.
 
Feb 24th -> March 2nd - During this time I've been working closely with the Wix toolset. I downloaded a script from the internet for build 1.5.0.4. This script doesn't work though and I'll have to make some modifications to get it working.
 
March 3rd - By removing some lines in the script I have been able to get it to build however there still seems to be some bugs.
 
March 10th- After not receiving a very good grade on my last build I have to really step it up. I've been concentrating on getting my 1.5.0.4 script up to 2.0.0.12 and building a program that will package everything together.
== Project Goals ==
By the end of this semester I hope to have a program that can deploy Firefox over a network or work environment. My build will include all the add-ons that I personally like as well as being fully customized for a work environment (ie. setting default homepage).
*Updated Feb 13th*
 
I realize my goals have been somewhat vague. For that reason I will clarify. By the end of the semester I hope to create a program that can customize and create .msi files. Whether I succeed or fail in my goal, I hope to pave the road for other developers to pick-up where I left off.
== Builds ==
[[Dec 25th) This is my first real build for my project and it only really includes documentation. I am still not sure if this the right approach for my project however even if it isn't I'm sure that this is useful information. In this 25]] - Documentation of inital research build I was successful in pushing an install of Firefox over the network. The following includes documentation on how this process was completed.1
Installing Firefox over the network with Microsoft Server 2003 and Active Directory[[0.2]] - My .adm file for Group Policy Objects.
Assuming that Server 2003 is set [[0.3]] - I realize I havn't put up much lately, and that there it is a domain running on it, there are a couple things one must do before attempting because I havn't been struggling with the remote installdirection of my project. Firstly there must be a mapped drive on the server, this must also be accessible from the user(s) you are planning to push the install to.Once that This build is completed, create a folder in the mapped drive where you want to put your installer. In actually my case I downloaded the latest build from www.frontmotion.com. You can’t simply put a .exe file in this directory, it must be a first Wix toolset script and .msi file or this won’t work. After that is done, a user account must be created (if not already) to push the install to. You may also create a group so that the install can be pushed to all the users in that group. Lastly a group policy object or GPO must be createdresulted from it. The following instructs on how to create a GPO: Create a Group Policy Object
To create a Group Policy object (GPO) to use to distribute the software package: 1[[0. Start the Active Directory Users and Computers snap8]] -inI have been able to update my . To do this, click Start, point Wix script to Administrative Tools, and then click Active Directory Users and Computers.2. In the console tree, right-click your domain, and then click Properties0. 30. Click the Group Policy tab, 12 and then click New.4. Type a name for this new policy (for example, Office XP distribution), and then press ENTER.5. Click Properties, and then click the Security tab.6. Click to clear the Apply Group Policy check box for the security groups that you want to prevent from having this policy applied. 7. Click to select I've completed the Apply Group Policy check box for the groups that you want this policy to apply to.8. When you are finished, click OK.* The above was taken from Microsoft Documentation, see referenced (A)first build of my packaging program.
Next, you must Assign a package to the GPO[[0. In my case the Microsoft documentation differed greatly from how I did it, so I will document 9]] - Since my process.1. Select the GPO created in the steps above and click edit.2. Under either ‘Computer Configuration’ or ‘User Configuration’ (depending on where you want to push the software) click new and then click package. 3. A dialog box will open, navigate to the .msi package you want to push (in this case firefox) and select it. 4last build much has changed. Click Assigned, then navigate the tabs to ensure the package will be pushed to the proper computers/users.5. Exit AD. When the user/computer is logged on Please follow the install will commencelink for details.
That is all I did to remotely install the package[[1. 0]] - My next build will be using CCK to customize the package I decide Final Build. Click to push over and documenting different types of remote installssee details.
Final Report - http://daven.ca/ffp.doc
References
A) Microsoft’s “How to use Group Policy to remotely install software in Windows Server 2003”
http://support.microsoft.com/kb/816102
Davenrathh
1
edit
Retrieved from "https://wiki.cdot.senecapolytechnic.ca/wiki/Special:MobileDiff/14565...15472"

Navigation menu