Use Group Policy To Deploy Applications In Windows Server 2003 Part I
- 1
- Add a Comment
Through the Microsoft Management Console (MMC) and group policies you can configure a Windows Server 2003 server to automatically distribute software to Windows clients by either assigning or publishing applications. Although the basics of this process are fairly straightforward, there are situations that will require you to use advanced publish and assign options.
For example, if you were installing Office XP onto a system that already had Office 2000, you would probably want Office XP to replace Office 2000 rather than keeping both versions. Advanced publish and assign options allow you to do this and more.
Getting started
To access the advanced publishing and assigning options, open the MMC, add the Group Policy snap-in, and navigate to the Software Installation container. Right-click on the Software Installation container to access the Software Installation properties sheet. Select the default location of the Windows installer package that you wish to push to your client machines, select the Advanced radio button and click OK. Doing so will return you to the main Group Policy screen.
Then, right-click on the Software Installation container and select New | Package from the resulting menu to display the Open dialog box which lists the contents of default locations that you selected. Next, select the exact Windows Installer (.msi) file you wish to push and click OK. The installation properties window for your chosen .msi file will then be displayed. You can then configure the advanced publish or assign options for your installation through the series of tabs at the top of the window.
The Deployment tab
On this properties sheet you will find the Deployment tab, where you can select whether you want to assign or publish the application. There are also three check boxes that control auto installation by file extension activation, automatic uninstallation, and whether or not the package is visible in the Add/Remove Programs dialog box.
At the bottom of the Deployment tab, you’ll notice an Advanced button. If you click this button, you’ll see a dialog box that contains some advanced diagnostic information, such as the name of the automatic installation script that you’re creating. This dialog box also contains a check box you can select to ignore language options when deploying the package.
The Upgrades tab
The Upgrades tab contains Add and Remove buttons that you can use to build a list of applications that the new application should replace. Once you’ve created the list, select the check box to make the new package a mandatory upgrade to the previously existing package.
When you click the Add button you’ll have the option to select a package from the current group policy object or from another specific group policy object. You can also decide whether Windows should uninstall the old package prior to installing the new package or if Windows can perform an upgrade by installing the new package on top of the previously existing application.
- Windows Group Policy Administrator’s Pocket Consultant
- MapPoint 2009
- Pro Tools M Powered Recording Software 8
- Guitar Tracks Pro 4 USB - Windows
- MapPoint 2010
- Music Creator 5 - Windows
- City Navigator North America Volume 6
- Streets and Trips 2008 w/ GPS Locator
- MapPoint 2010 with GPS
- SONAR Home Studio 7 Software Production
- Streets + Trips (GPS) 2009 x32 English DVD
- Beyond Bullet Points: Using Office PowerPoint 2007…
- Office Word 2003 Inside Out
- Guitar Tracks Pro 4 - Windows
- Office Access 2007 Inside Out
- Office Word Plain & Simple
- SONAR Home Studio 7 XL
- Street USA Plus 2009
- TECHNET Plus 1U Multi-Lang SA ACAD-6.0
- PLWII14 What It Is! ’70s Analog Funk - Windows
- Berlitz English Premier
- Windows Server 2008 Inside Out
- Office SharePoint Server 2007 Best Practices
- Office Excel 2007 Step by Step
- Office System Step by Step - 2003 eLearning Edition

One Comment
myadds
November 6th, 2009
at 2:18pm
Hi, Can we upgrade office 2003 to 2007 with GP, then how to set up answer file for silent instalation.