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.
== Project Goals ==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.
By Feb 8th - So I did some research on .msi files. There are tons of tutorials on the end of this semester internet on how to use automated tools to create .msi files. I hope need to have a program manually do it so that I can deploy Firefox over customize it. I found a network or work environmentMicrosoft SDK on the internet for it. My build I am currently downloading it and will include all the add-ons that I personally like as well as being fully customized for a begin my work environment (ie. setting default homepage)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.
== Builds ==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.
Dec 25th) Feb 14th - I've spent a ton of time trying to get the Wix toolset to build in a Vista environment. This is my first real build for my project has turned out to be nothing but annoying and it only really includes documentation. I am still not sure if this the right approach for 've decieded to move my project however even if it isn't I'm sure that this is useful information. In this build I was successful in pushing an install of Firefox over the network. The following includes documentation on how this process was completedto a Windows XP platform.
Installing Firefox over Feb 17th - After trying to get the network with Microsoft Server 2003 and Active DirectoryWix 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.
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 Feb 18th - I was able to build the remote installsource code finally. Firstly there must be a mapped drive on the server, this must I also be accessible from the user(s) you are planning to push the install to.Once that is completed, create a folder in the mapped drive where you want to put your installer. In my case realized I could have just downloaded the latest build from [[http://wwwbinaries.frontmotion.com FrontMotion]]. You can’t simply put a .exe file in this directory, it must be a .msi file or this won’t work. After that is done, a user account must be created (if I'm not already) to push the install toimpressed with myself. 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 created. The following instructs on how to create a GPO: Create a Group Policy Object
To create Feb 20th - Today I was able to actually build something with the Wix toolset. I had to read a Group Policy object (GPO) small tutorial on building .msi files but after that I was able to use build a very basic .msi. I will try to distribute attach both the software package: 1. Start msi and the Active Directory Users and Computers snap-in. To do this, click Start, point to Administrative Tools, and then click Active Directory Users and Computersscript.
2Feb 24th -> March 2nd - During this time I've been working closely with the Wix toolset. In I downloaded a script from the console tree, right-click your domain, internet for build 1.5.0.4. This script doesn't work though and then click PropertiesI'll have to make some modifications to get it working.
3. Click March 3rd - By removing some lines in the Group Policy tab, and then click Newscript 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.4script up to 2. Type 0.0.12 and building a name for this new policy (for example, Office XP distribution), and then press ENTERprogram that will package everything together.
5. Click Properties, and then click the Security tab.== Project Goals ==
6By the end of this semester I hope to have a program that can deploy Firefox over a network or work environment. Click to clear 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 security groups that you want to prevent from having this policy applieda work environment (ie. setting default homepage).
7. Click to select the Apply Group Policy check box for the groups that you want this policy to apply to.*Updated Feb 13th*
8I realize my goals have been somewhat vague. When you are finishedFor 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, click OKI hope to pave the road for other developers to pick-up where I left off.
* The above was taken from Microsoft Documentation, see referenced (A). 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
