* 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.
== Project Goals ==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.
By the end of this semester Feb 6th - Today I hope '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 deploy Firefox over a network or work environmentcreate and customize .msi files. My build will include all I figure the add-ons that most important thing is to understand more about .msi files so I personally like as well as being fully customized for a work environment (ie. setting default homepage)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.
== Builds ==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.
Dec 25th) This is my first real build for Feb 10th - After speaking with David Humphrey I feel much better about my work. He has pointed me at a project and it only really includes documentationknow as Wix. I am still not sure if this the right approach Which seems to be an OS SDK for my project however even if it isn't developing .msi files. Since I'm sure that this is useful information. In this build at work I was successful in pushing an install of Firefox over the network. The following includes documentation on how this process was completedcan't write more yet.
Installing Firefox over Feb 14th - I've spent a ton of time trying to get the network with Microsoft Server 2003 Wix toolset to build in a Vista environment. This has turned out to be nothing but annoying and Active DirectoryI've decieded to move my project to a Windows XP platform.
Assuming that Server 2003 is set up and that there is a domain running on it, there are a couple things one must do before attempting the remote install. Firstly there must be a mapped drive on the server, this must also be accessible from the user(s) you are planning Feb 17th - After trying to push get the install Wix source files to.Once build for hours I've realized that is completed, create a folder in the mapped drive where you want I forgot to put your installer. In my case I downloaded install the latest build from [[FrontMotion:http://www.frontmotion.com]]. You can’t simply put a .exe file in this directory, it must be a .msi file or this won’t work. After that Windows SDK which is done, not listed as a user account must be created (if not already) prerequist to push building the install to. You may also create a group so that source code on the install can be pushed to all the users in that groupWix website. Lastly a group policy object or GPO must be created. The following instructs on how to create a GPO: Create a Group Policy Object
To create a Group Policy object (GPO) Feb 18th - I was able to use to distribute build the software package: 1source code finally. Start I also realized I could have just downloaded the Active Directory Users and Computers snap-inbinaries. To do this, click Start, point I'm not to Administrative Tools, and then click Active Directory Users and Computersimpressed with myself.
2Feb 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. In I will try to attach both the console tree, right-click your domain, .msi and then click Propertiesthe script.
3Feb 24th -> March 2nd - During this time I've been working closely with the Wix toolset. Click I downloaded a script from the Group Policy tab, internet for build 1.5.0.4. This script doesn't work though and then click NewI'll have to make some modifications to get it working.
4. Type a name for this new policy (for example, Office XP distribution), and then press ENTERMarch 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. Click Properties, 0.4 script up to 2.0.0.12 and then click the Security tabbuilding a program that will package everything together.
6. Click to clear the Apply Group Policy check box for the security groups that you want to prevent from having this policy applied. == Project Goals ==
7By the end of this semester I hope to have a program that can deploy Firefox over a network or work environment. Click to select My build will include all the Apply Group Policy check box add-ons that I personally like as well as being fully customized for the groups that you want this policy to apply toa work environment (ie. setting default homepage).
8. When you are finished, click OK.*Updated Feb 13th*
* The above was taken from Microsoft DocumentationI 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, see referenced (A)I hope to pave the road for other developers to pick-up where I left off.
Next, you must Assign a package to the GPO. In my case the Microsoft documentation differed greatly from how I did it, so I will document my process.== Builds ==
[[Dec 25]] - Documentation of inital research build .1. Select the GPO created in the steps above and click edit.
[[0.2]] - My . Under either ‘Computer Configuration’ or ‘User Configuration’ (depending on where you want to push the software) click new and then click packageadm file for Group Policy Objects.
[[0.3. A dialog box will open]] - I realize I havn't put up much lately, navigate to and it is because I havn't been struggling with the direction of my project. This build is actually my first Wix toolset script and .msi package you want to push (in this case firefox) and select file that resulted from it.
4[[0. Click Assigned, then navigate the tabs 8]] - I have been able to ensure the package will be pushed update my .Wix script to 2.0.0.12 and I've completed the proper computers/usersfirst build of my packaging program.
5[[0. Exit AD9]] - Since my last build much has changed. When Please follow the user/computer is logged on 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
