1 / 21

Office of Education Technology (OET)

Office of Education Technology (OET). Using Group Policy Objects to Deploy Software. KTLC March 11, 2006. Preparing for Software Deployment!. Review the white paper or software vendor’s support documentation. Bandwidth and Network Utilization.

ayanna
Télécharger la présentation

Office of Education Technology (OET)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Office of Education Technology (OET) Using Group Policy Objects to Deploy Software KTLC March 11, 2006

  2. Preparing for Software Deployment! • Review the white paper or software vendor’s support documentation. • Bandwidth and Network Utilization. • Plan your installation according to your network. Fiber, Point to Point, Frame Relay, and slower links. • Verify the availability of free space on workstations selected for the software install.

  3. Preparing for Software Deployment! • Thoroughly test the application before installing it on a large number of workstations. Also test service packs or updates for the software. • You can create a Test OU and move some computer accounts into the OU to verify that the software install works properly.

  4. Configuring the Installation Files • Creating the Office 2003 Installation files with the Volume License Key and Service Pack 2 embedded. • You will need 2 directories 1 for Office 2003 service pack 2 and the other for the Office 2003 installation files that will be copied from the Office 2003 cd-rom.

  5. Configuring the Installation Files • Run D:\setuppro.exe /a from the command line. This option will allow you to install the Office 2003 suite to a specified directory. You will also need to enter the volume license key or product key. The most important part of this step is entering the product or volume license key. Once the key is entered it will no longer be required when the application is installed from the source files on your hard drive.

  6. Configuring the Installation Files • Now that the Office 2003 source files and Service Pack 2 have been copied to the hard drive the following 3 commands will need to be ran. • E:\sp2\office2003sp2-kb887616-fullfile-enu.exe /Q /C /T:E:\Office2003_temp • This command will extract the contents of the service pack 2 executable file into the directory with the Office 2003 source files.

  7. Configuring the Installation Files • Msiexec /p e:\office2003_temp\mainsp2ff.msp /a e:\office2003_temp\pro11.msi SHORTFILENAMES=TRUE /qb • This command uses msiexec to combine the mainsp2ff.msp package with the pro11.msi windows installer package.

  8. Configuring the Installation Files • Msiexec /p e:\office2003_temp\owc11sp2ff.msp /a e:\office2003_temp\owc11.msi SHORTFILENAMES=TRUE /qb • Like the previous command this command uses msiexec to combine the owc11sp2ff.msp package with the owc11.msi windows installer package.

  9. Configuring the Installation Files • Now that Service Pack 2 and the Product or Volume License key have been embedded in the Office 2003 source files rename the temp directory to Office2003sp2. • Copy the directory with the source files to a file sever or servers where the files will be hosted and share the directory. You can add a $ symbol after the share name to make the share hidden. Leave the default share permission, read only on Windows server 2003

  10. Configuring the Installation Files • Add Domain Computers with default NTFS permissions (Read, Read and Execute, and List folder Contents) to the security tab. • The Domain Computers group needs to have read permissions to the source files because Office 2003 will be installed by the system before a user can logon.

  11. Creating a New Group Policy Object • Using the Group Policy Management console, right click on Group Policy Objects and click new. Give the group policy a descriptive name (Office2003sp2_Install) or if you will have multiple locations (school_Office2k3sp2_Install). Right click the new group policy and go to GPO status then select All Settings disabled before modifying the GPO. (Doing this will help make sure the policy does not get applied before it is ready).

  12. Creating a New Group Policy Object • Right click the group policy and click edit to begin creating the Software Settings GPO. Under Computer Configuration select software settings – Right click Software Installation then select new package. • You will be prompted to select the MSI windows installer package from the share location. For this example it will be \\edtestrd1\Office2003sp2$\pro11.msi

  13. Creating a New Group Policy Object • There are 3 software deployment options. You can assign the software package to computers. (The application will be installed at startup the next time it is rebooted). You can assign the software package to Users (The application will be installed on demand or at user logon on Windows XP). You can publish the software package for users. (Users can install the software from Add/Remove programs).

  14. Creating a New Group Policy Object • For this example we will assign the software package to Computers. On the deploy software dialogue box choose the default deployment method (assigned). Advanced options can be selected if you are updating an existing software installation. • Close the group policy object editor!

  15. Creating a New Group Policy Object • If you want to apply the group policy to all workstation drag and drop the Office2003sp2_install policy from the Group Policy Objects container to the workstations OU. • Click ok when prompted to link the selected GPO to the organizational unit.

  16. Creating a New Group Policy Object • After the group policy has been configured and linked properly right click the GPO and select GPO Status, then choose User Configuration Settings Disabled. Since user configuration settings are not used in this group policy choosing to disable User configuration settings will allow faster group policy processing.

  17. Creating a New Group Policy Object • The group policy should refresh for all the workstations within 2 hours. The next time a workstation is rebooted the automated software installation will begin before the user logon prompt is displayed with the message installing managed software. • After the software installation is complete, the newly installed application will be listed under start – all programs – Microsoft office, and should not require the user to enter a product or volume license key the first time they run an Office 2003 application.

  18. Removing Software with the Install GPO • If you need to remove software previously installed by GPO you will need to have the original GPO used to install the software. • Using the Group Policy Management Console right click the Office2003sp2_Install GPO and click edit. Under Computer Configuration select software settings – Select Software Installation then right click the software package in the right window pane, and select remove.

  19. Removing Software with the Install GPO • When you select remove you will have 2 options. Remove the installed software package and allow users to continue using the software. • Select remove the installed software package to remove the software the next time the computer is rebooted. • Close the Group Policy Object Editor and make sure the group policy is linked to the correct OU, and select disable user configuration settings.

  20. Resources • Office 2003 Service Pack 2: http://www.microsoft.com/downloads/details.aspx?FamilyId=57E27A97-2DB6-4654-9DB6-EC7D5B4DD867&displaylang=en • Group Policy Management Console: ftp://ketsftp.k12.ky.us/WindowsServer2003/gpmc.msi • More information about Slip Streaming: http://www.microsoft.com/technet/prodtechnol/windowsserver2003/deployment/winupdte.mspx • More information about msiexec and command line options: http://www.microsoft.com/technet/prodtechnol/windows2000serv/maintain/featusability/winmsi.mspx

  21. Demo • Live Demonstration

More Related