Create a Software Distribution Point

To deploy software across a network, you need to first create a file share on the server that will be used as the software distribution point for all the software packages you want to install now or later. Log on to the server as an administrator and create a shared folder (e.g. Software Deployment) with the following permissions:

Everyone (Authenticated Users) = Read
Domain Computers = Read
Administrators = Full Control, Read

Create additional folders for each application you wish to install as well as the .Net Framework, e.g. Math3, Vocab3, DotNet2. You can always add more at another time. Please note that the Microsoft .Net Framework 2.0 is required for all Schoolhouse Technologies software (except Map Worksheet Factory) and must also be installed to each workstation. This can be accomplished using Group Policy software deployment. The .Net Framework 2.0 Redistributable Package (x86) (dotnetfx.exe) can be downloaded from the Microsoft website here.

Install each application to its matching folder using an administrative install with the command line switch /a. An administrative install will extract and create the required folder and file structure for the network installation.

The .Net Framework can be extracted using the /c switch.

One way to accomplish the administrative install is to copy the application or .Net Framework setup file to the appropriate folder then browse to that same folder using the DOS command window (Start/Run and enter cmd).

Then type the name of the application executable at the command prompt (e.g., D:\Software Deployment>AppName.exe /a).

That will start the administrative installation. Follow the install instructions and ensure that the application installs to the correct folder.

The installation will extract the msi (Windows Installer) file and all the program and supporting files and folders. The folder structure will look something like this:

Create a Software Deployment Group Policy Object

Go to Administrative Tools and open the Group Policy Management console. If the Group Policy Management console is not installed, see the Initial Steps for Working without a Group Policy Management Console below.

NOTE: If there is no Group Policy Management console, you may want to consider downloading and installing it as it makes the management of group policy a little easier. You can download it from Microsoft Downloads here.

 

Initial Steps for Working WITH a Group Policy Management Console

With the Group Policy Management console open, open the Domains folder and right-click the name of the domain that wish to install the software to and select Create and Link a GPO Here... Type a name (e.g. Software Deployment) for the new GPO and click OK. A link to your Software Deployment GPO will appear under the domain name and the actual GPO can be found under the list of Group Policy Objects.

Select your new GPO in the left window to open the settings window.

Use the Security Filtering section to control to which groups and users you want to apply the policy. Authenticated Users is the default and will do for most installations.

Right-click the GPO in the left window and select Edit to open the Group Policy Object Editor.

 

Initial Steps for Working WITHOUT a Group Policy Management Console

Go to Administrative Tools and open the Active Directory Users and Computers snap-in and right-click the site (or domain) you want to install the software across, choose Properties and then select the Group Policy Tab.

Click New to create a new GPO (Group Policy Object) and give it a name such as Software Deployment.

Click the Properties button and then click the Security tab to control to which groups and users you want to apply the policy. Authenticated Users is the default and will do for most installations. Click OK.

Now select your new software deployment GPO and click Edit to open the Group Policy Object Editor.

 

Working with the Group Policy Object Editor

Whether working with the Group Policy Management Console or not, from this point on, once you are working with Group Policy Object Editor, both methods converge.

Select the type of assignment. If you have a group license for the software, in most cases you will want to assign the software to computers (Computer Configuration) rather than users so that the applications are available to anyone who logs on to the computer. Applications assigned to computers will be automatically installed with the next reboot of the assigned computers. The software cannot be uninstalled except by local administrators. If the software is only for a department or particular users you will want to select the User Configuration option. Applications assigned to users will be installed after the next valid logon event or on first use (icons are placed on the Start Menu or desktop) by the selected users. The software can be uninstalled by the user but will be installed again after the next logon.

For the purposes of this tutorial, we will select Computer Configuration, and then select Software Installation in the Software Settings folder in the left window. Right-click Software Installation and select Properties to open the Software Installation Properties dialog.

In the Default Package Location, enter or browse to the UNC path of the file share. This is the shared root folder where you stored all the software packages for installation. In our example, this would be the Software Deployment folder.

In the New Packages section, if it's not selected already, select Display the Deploy Software dialog box.

Click OK.

Right-click on Software Installation again, and select New and then Package. An Open dialog should open to the applications shared network folder that you selected in the Software Installation Properties dialog.

Browse to the package you want to install and select the MSI (Windows Installer) file and click Open.

Select the deployment method, normally Assigned, and click OK.

If you want to edit any of your settings, simply double-click the software package and modify the settings.

Now test your network installation by rebooting one of the computers in the network. On reboot, you should be notified the installation is taking place and when the reboot is complete, the application should be installed and ready to use.