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.
== Project Goals ==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.
By Feb 17th - After trying to get the end of this semester I hope Wix source files to have a program that can deploy Firefox over a network or work environment. My build will include all the add-ons for hours I've realized that I personally like as well forgot to install the Windows SDK which is not listed as being fully customized for a work environment (ie. setting default homepage)prerequist to building the source code on the Wix website.
*Updated Feb 13th*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 realize my goals have been somewhat vaguewas able to actually build something with the Wix toolset. For that reason I will clarifyhad to read a small tutorial on building . By the end of the semester msi files but after that I hope was able to create build a program that can customize and create very basic .msi files. Whether I succeed or fail in my goal, I hope will try to pave attach both the .msi and the road for other developers to pick-up where I left offscript.
== Builds ==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.
Dec 25th) This is my first real build for my project and it only really includes documentation. March 3rd - By removing some lines in the script I am still not sure if this the right approach for my project however even if have been able to get it isn't I'm sure that this is useful information. In this to build I was successful in pushing an install of Firefox over the network. The following includes documentation on how this process was completedhowever there still seems to be some bugs.
Installing Firefox over the network with Microsoft Server 2003 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 Active Directorybuilding a program that will package everything together.
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 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 I downloaded the latest build from [[http://www.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 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 created. The following instructs on how to create a GPO: Create a Group Policy Object== Project Goals ==
To create By the end of this semester I hope to have a Group Policy object (GPO) to use to distribute the software package: 1program that can deploy Firefox over a network or work environment. Start My build will include all the Active Directory Users and Computers snapadd-inons that I personally like as well as being fully customized for a work environment (ie. To do this, click Start, point to Administrative Tools, and then click Active Directory Users and Computerssetting default homepage).
2. In the console tree, right-click your domain, and then click Properties. *Updated Feb 13th*
3I realize my goals have been somewhat vague. Click For that reason I will clarify. By the end of the Group Policy tabsemester I hope to create a program that can customize and create .msi files. Whether I succeed or fail in my goal, and then click NewI hope to pave the road for other developers to pick-up where I left off.
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 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). 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