Remote Windows Software Installation Guide
Automating Software Deployment with Group Policy in Windows Domains
Recently, methods for establishing a Windows domain and implementing group policy for domain computers were discussed. This article details the process of remotely installing Windows software across your domain computers utilizing group policy features.
Previously, application installation involved direct intervention on each user’s computer, a process that proved exceptionally time-consuming. Initial attempts to streamline this involved tools like Dameware for Windows 2000, which facilitated remote installations, but came with cost and usability drawbacks.
The introduction of Remote Desktop with Windows XP Professional allowed for remote login and manual application installation. While an improvement, it remained a laborious task. Now, applications can be automatically assigned to computers, or even to users, ensuring software availability regardless of their location within the domain.
Deploying Microsoft Office via Group Policy
This guide will demonstrate a remote installation of Microsoft Office software. To proceed, the application must be packaged as an MSI file – a Microsoft Installer package. If an MSI file is unavailable, methods exist for creating one.
Once the MSI file is obtained, answer templates can be created to predefine installation options, enabling customized and automated deployments. This is particularly crucial when managing numerous computers with diverse requirements.
Organizational Units (OUs) are then utilized to target application deployments effectively.
Accessing Group Policy Management
Begin by opening Active Directory Users and Accounts.
Select the OU containing the target computers or users. Right-click on the chosen OU and select "Properties".
Navigate to the group policy tab and click open to access the group policy management interface.
All computers or users within the selected OU will be affected by the deployment. This means the software will be installed on their respective systems.
Creating a New Group Policy Object
You will then be presented with the group policy management screen.
The selected OU will be highlighted on the left, and any existing policies assigned to it will appear in the right pane. An example is a GPO named "OfcStd", representing Office Standard.
To create a new policy, right-click on the OU and choose create and link a GPO here.
A dialog box will appear, prompting you to name the new GPO.
Choose a descriptive name, such as test software installation. This will add the new, blank GPO to the screen. Right-click on it and select edit.
Configuring Software Installation
Clicking edit opens the group policy object editor. Expand either computer configuration then software settings, or user configuration then software settings, depending on whether you want the software assigned to a specific computer or to follow the user.
Clicking on "Software installation" reveals the following interface:
Right-click in the right pane and select new then package.
Select the MSI file for the application. For example, STD11.msi for Office 2003 Standard. This completes the initial software package deployment. The time savings potential with proper implementation are significant!
Testing and Verification
To test the deployment, log in as a user within the targeted OU (if user configuration was selected). If computer configuration was chosen, use a computer within that OU. A reboot may be required, and in some cases two, for the installation to begin.
Upon successful deployment, a notification will appear after login indicating the application installation is in progress.
What methods do you employ for remote software installation? Do you have any additional tips or techniques to share?
