1. Supporting and Maintaining Desktop Applications Lesson 13

2. Skills Matrix Technology SkillObjective Domain SkillDomain # Software Deployment Overview Support deployed applications 5.1 SMS Advanced ClientSupport deployed applications 5.1 Using Group Policy to Deploy Software Support deployed applications 5.1 Creating a Network Share for Distributing Software via Group Policy Support deployed applications 5.1

3. Skills Matrix Technology SkillObjective Domain SkillDomain # Using Group Policy to Assign and Publish Packages Support deployed applications 5.1 Deploying Software By Using Systems Management Server 2003 Support deployed applications 5.1 Installing Systems Management Server 2003 Support deployed applications 5.1 Assigning the SMS Client to Windows Vista by Using Group Policy Support deployed applications 5.1

4. Skills Matrix Technology SkillObjective Domain SkillDomain # Using Group Policy to Upgrade or Replace an Existing Application Maintain desktop applications 5.3 Upgrading ApplicationsMaintain desktop applications 5.3 Troubleshooting Group Policy Software Deployment Maintain desktop applications 5.3

5. Microsoft offers two technologies for the purposes of installing and maintaining software on a Windows-based network.  Group Policy  Systems Management Server 2003 (SMS 2003) Software Deployment Overview

6. Group Policy – Freely available as part of Windows Server 2003 when Microsoft Active Directory directory service is installed. Group Policy offers simple software deployment features and management using Windows Installer technology. Group Policy lacks the sophisticated deployment, reporting, and scheduling features offered by Systems Management Server 2003 (SMS 2003). Software Deployment Overview (cont.) Software Deployment Overview

7. Group Policy supports the following features:  Software distribution using Microsoft Installer  Distribution of legacy applications using zap files  Removal of managed software  Customization of MSI-based application packages using transform files Software Deployment Overview (cont.) Software Deployment Overview

8. Group Policy supports the following features (cont.):  Upgrading of managed applications  Ability to assign or publish applications to specific users or computers Software Deployment Overview (cont.) Software Deployment Overview

9. You should consider using SMS Server under the following circumstances:  Software distribution needs to be managed for a large network with many physically dispersed sites.  Software deployments/upgrades need to be scheduled. Software Deployment Overview (cont.) Software Deployment Overview

10. You should consider using SMS Server under the following circumstances (cont.):  Reporting and inventory capabilities are required.  Packages are frequently deployed, removed, or upgraded. Software Deployment Overview (cont.) Software Deployment Overview

11. SMS Advanced Client 2.5 – Supports all operating systems from Windows 2000 to Windows Vista. Advanced Client has a number of benefits over IntelliMirror and Group Policy, especially in the area of supporting remote users on slow network links. SMS Advanced Client Software Deployment Overview

12. The SMS Advanced Client makes use of the BITS (Background Intelligent Transfer Service). The rate at which software is transferred from a DP (Distribution Point) to a client is adjusted according to the available bandwidth. BITS also makes it possible to restart an interrupted software download from the point at which it stopped. Background Intelligent Transfer Service (BITS) Software Deployment Overview

13. Microsoft Installer – Proprietary Microsoft system for installing applications on Windows operating systems. The file extension for Windows Installer packages is.msi. Microsoft Installer Using Group Policy to Deploy Software

14. IntelliMirror – Group of technologies that allows users’ data and programs to follow them around a network IntelliMirror Using Group Policy to Deploy Software

15. Scope of Management – Refers to the Active Directory objects to which a Group Policy Object applies Scope of Management (SOM) Using Group Policy to Deploy Software

16. Distributed File System (DFS) – Provides replication of files across multiple servers and the ability to route users transparently to the nearest available replicated copy of a given file Distributed File System (DFS) Using Group Policy to Deploy Software

17. To use Group Policy to deploy software, create an NTFS or DFS network share for use as a software distribution point. Add Microsoft Installer packages to the share. Create an Organizational Unit (OU; optional). Creating a Share for Distributing Software via Group Policy Using Group Policy to Deploy Software

18. Create a new Group Policy object and link it to an Organizational Unit. Configure a new Software Installation in the Group Policy Object (GPO). Test the configuration. Creating a Share for Distributing Software via Group Policy (cont.) Using Group Policy to Deploy Software

19. Log on to a file server in the contoso.com domain as an administrator. Create a folder named Software in a suitable location on a file server that’s a member of your Active Directory domain. Right-click the new folder, and then select Properties. Select the Security tab, and then click Add. Creating a Folder for Distributing Software via Group Policy Using Group Policy to Deploy Software

20. Key authenticated users in the Enter object names to select list box, and then click Check Names. Click OK to close the Select Users, Computers, or Groups dialog box. Make sure that Authenticated Users is highlighted on the Security tab and that the following permissions are selected: Read & Execute, List Folder Contents, and Read. Creating a Folder for Distributing Software via Group Policy (cont.) Using Group Policy to Deploy Software

21. Log on to a file server in the contoso.com domain as an administrator. From the Start Menu, select Administrative Tools and then Distributed File System. Right-click Distributed File System in the Distributed File System console, and then select New Root. Click Next. Creating a DFS Root Using Group Policy to Deploy Software

22. Ensure that Domain Root is selected before clicking Next. Select your domain to host the new root (in this case, contoso.com), and then click Next. Next to the Server name text box, click Browse to locate the server to host the new DFS root. Select the server in the Search results list box, and then click OK. Creating a DFS Root (cont.) Using Group Policy to Deploy Software

23. The server you selected should appear in the Server name text box. Click Next. In the Root name text box, give the new DFS root a name. You need to key only software. The full path for the new DFS root, which is \\contoso.com\software, appears in the Preview of UNC path to the root preview box. Click Next. Creating a DFS Root (cont.) Using Group Policy to Deploy Software

24. Click Browse to browse for the folder called Software that you created in the previous procedure. Highlight the folder name, and then click OK. In the Root Share page, the folder name you selected should appear in the Folder to share text box. Click Next. Creating a DFS Root (cont.) Using Group Policy to Deploy Software

25. Click Next. The Completing the New Root Wizard page appears. Review the settings, and then click Finish. Test the new DFS root by opening Windows Explorer, keying the path of the DFS root into the Address Box, and then clicking Enter. You should see the shared folder appear under Folders on the left side of the window. Creating a DFS Root (cont.) Using Group Policy to Deploy Software

26. Creating a DFS Root (cont.) Using Group Policy to Deploy Software Configured DFS root \\contoso.com\software in the DFS console

27. User Assignments – Software packages that are assigned to users via Group Policy and are advertised to a user via the Start menu when a user logs on to a computer Computer Assignments – Windows Vista installs any packages assigned to computers the next time the user reboots the machine. Using Group Policy to Assign and Publish Packages Using Group Policy to Deploy Software

28. Packages Published to Users – Appears only in the Add/Remove Programs control panel and not in the Start menu Using Group Policy to Assign and Publish Packages (cont.) Using Group Policy to Deploy Software

29. Using Group Policy to Assign and Publish Packages (cont.) Using Group Policy to Deploy Software Published (Users Only) Assigned (User Accounts) Assigned (Computer Accounts) Where can the user find the application? Add/Remove Programs Control Panel Start menu When or where is the application installed? Add/Remove Programs Control Panel At logonAt reboot How is the application installed? Full installationAs neededFull installation

30. Log on to your Windows Vista machine with your standard user account. Click Start. In the Start Search text box, key mmc, and then press Enter. A User Account Control dialog box appears. Provide administrator credentials, and then click OK. An MMC console appears. Creating a New Group Policy Object Using Group Policy to Deploy Software

31. Click File, and then click Add/Remove Snap-in. In the Available snap-ins list box, select Group Policy Management, and then click Add. Click OK to close the Add or Remove Snap-ins dialog box. In the console tree, expand Group Policy Management > Forest: contoso.com > Domains > contoso.com. Creating a New Group Policy Object (cont.) Using Group Policy to Deploy Software

32. Right-click Group Policy Objects, and then select New. Key SharedView in the Name text box, and then click OK. Creating a New Group Policy Object (cont.) Using Group Policy to Deploy Software

33. Creating a New Group Policy Object (cont.) Using Group Policy to Deploy Software SharedView GPO listed in the details pane

34. To save the console you just created, click File and then click Save. Under the Save in column, click Desktop. In the File name text box, key GPMC SharedView. Click Save. The icon for this console now appears on the desktop. Creating a New Group Policy Object (cont.) Using Group Policy to Deploy Software

35. Creating Software Categories Using Group Policy to Deploy Software Software Categories allow users to locate programs easily in the Add/Remove Programs control panel.

36. Log on to your Windows Vista machine with your standard user account. Double-click the GPMC SharedView icon on the desktop. Provide administrator credentials, and then click OK. Publishing Application Packages to Users via Group Policy Using Group Policy to Deploy Software

37. In the details pane under Group Policy Objects in contoso.com, right-click SharedView, and then select Edit. Expand User Configuration > Software Settings. Right-click Software installation, and then select New > Package. Publishing Application Packages to Users via Group Policy (cont.) Using Group Policy to Deploy Software

38. When selecting the MSI package to publish, it’s important to use the DFS share that we created earlier. In the File name box, key \\contoso.com\software, and then click Open. Select SharedView folder, and then click Open. Select SharedView MSI package, and then click Open. Publishing Application Packages to Users via Group Policy (cont.) Using Group Policy to Deploy Software

39. Verify that Published is selected as the default, and then click OK. Let’s assign this published application to a software category. Make sure that Software installation is highlighted under User Configuration, and right-click the Microsoft SharedView package in the details pane. Publishing Application Packages to Users via Group Policy (cont.) Using Group Policy to Deploy Software

40. Select Properties. The Microsoft SharedView (Beta) Properties dialog box appears. Select the Categories tab.  In the Available categories list box, select Collaboration, and then click Select. Collaboration now appears under the Selected categories list box. Publishing Application Packages to Users via Group Policy (cont.) Using Group Policy to Deploy Software

41. Click OK. Close Group Policy Object Editor. Link the new GPO to the Managed Users OU by right-clicking the Managed Users OU in the console tree and then selecting Link an Existing GPO. Publishing Application Packages to Users via Group Policy (cont.) Using Group Policy to Deploy Software

42. In the Group Policy objects list box, select SharedView, and then click OK. For the sake of simplicity, we’ll leave the security filtering set to Authenticated Users. Expand the Managed Users OU, and then select the SharedView GPO. Publishing Application Packages to Users via Group Policy (cont.) Using Group Policy to Deploy Software

43. Publishing Application Packages to Users via Group Policy (cont.) Using Group Policy to Deploy Software Links and security filtering for the SharedView GPO in the details pane

44. Log on to Windows Vista with a user account that is located in the Managed Users OU. From the Start menu, click Control Panel. Click Programs. Under Get Programs, select Install a program from the network. You should see Microsoft SharedView listed. Highlight the application, and then click Install. Testing a Published Application Using Group Policy to Deploy Software

45. Log on to a Windows 2003 server in the contoso.com domain as an administrator. From the Start menu, open Administrative Tools > Active Directory Users and Computers. Under contoso.com, right-click Users, and then select New > Group. In the Group Name text box, key Accounts Application, and then click OK. Creating an Active Directory Security Group Using Group Policy to Deploy Software

46. Expand Users in the console tree, right-click Accounts Application, and then click Properties. Click the Members tab, and then click Add. Click Object Types. The Object Types dialog box appears. Select the Computers check box, and then click OK. Creating an Active Directory Security Group (cont.) Using Group Policy to Deploy Software

47. In the Select Users, Contacts, or Computers dialog box, key the name of your computer account, and then click Check Names. Verify that the computer name is underlined, and then click OK. Click OK to close the Accounts Application Properties dialog box. Creating an Active Directory Security Group (cont.) Using Group Policy to Deploy Software

48. Filtering a Group Policy Object by Security Group Using Group Policy to Deploy Software Security Filtering for a Group Policy Object

49. Group Policy can upgrade a previously assigned or published application in two ways.  The existing application can be uninstalled and replaced with the upgrade package.  The upgrade package can be installed without removing the previously deployed version of the application. Using Group Policy to Upgrade or Replace an Existing Application Using Group Policy to Deploy Software

50. Upgrading an Application Using Group Policy to Deploy Software Group Policy already understands that this new package will upgrade an existing package configured in this policy.

51. Log on to a Windows Server 2003 machine in the contoso.com domain as an administrator. Open Group Policy Object Editor. Expand Computer Configuration > Software Settings or User Configuration > Software Settings. Redeploying an Application Using Group Policy to Deploy Software

52. Click Software installation. Right-click the installation package in the details pane, and then select All tasks > Redeploy application. Redeploying an Application (cont.) Using Group Policy to Deploy Software

53. Identifying Packages by Product Code Using Group Policy to Deploy Software Microsoft Installer Packages can be identified by their Global Unique Identifier (GUID).

54. Before running RSoP, let’s “create” a problem for a Windows Vista workstation. Log on to a file server in the contoso.com domain as an administrator. Use Windows Explorer to browse to the folder called Software that you created earlier in this lesson. Removing Authenticated Users from an ACL Using Group Policy to Deploy Software

55. Right-click the Software folder, and then select Properties. Select the Security tab, and then click Authenticated Users in the Group or user names list box. Click Remove, and then click OK. Removing Authenticated Users from an ACL (cont.) Using Group Policy to Deploy Software

56. Running RSoP Against a Windows Vista Workstation Using Group Policy to Deploy Software RSoP component status

57. Systems Management Server 2003 offers more flexible and comprehensive deployment and management options for larger organizations. Deploying Software Using Systems Management Server 2003 Deploying Software by Using Systems Management Server 2003

58. Management Point (MP) – Advanced Clients communicate with Systems Management Server Management Points to retrieve Advanced Client Policy and check for advertisements Distribution Point (DP) – A Systems Management Server where software packages are stored for SMS Clients to download Deploying Software Using Systems Management Server 2003 (cont.) Deploying Software by Using Systems Management Server 2003

59. Systems Management Server 2003 should be installed on a member server in the contoso.com domain. Systems Management Server 2003 requires SQL Server 2000/2005 to be installed on either the same or preferably a different member server. Installing Systems Management Server 2003 Deploying Software by Using Systems Management Server 2003

60. Installing Systems Management Server 2003 (cont.) Deploying Software by Using Systems Management Server 2003 Install an SMS primary site.

61. Installing Systems Management Server 2003 (cont.) Deploying Software by Using Systems Management Server 2003 SMS Site Information

62. Installing Systems Management Server 2003 (cont.) Deploying Software by Using Systems Management Server 2003 SQL Server Information for the SMS Site Database

63. Installing Systems Management Server 2003 (cont.) Deploying Software by Using Systems Management Server 2003 SMS Administrator Consoles

64. Upgrading Systems Management Server 2003 to SP3 Deploying Software by Using Systems Management Server 2003 Asset Intelligence Installation options

65. Upgrading Systems Management Server 2003 to SP3 (cont.) Deploying Software by Using Systems Management Server 2003 SMS 2003 Deployment Readiness Wizard

66. Upgrading Systems Management Server 2003 to SP3 (cont.) Deploying Software by Using Systems Management Server 2003 Do not accept unsigned data

67. Configuring the SMS Client Deploying Software by Using Systems Management Server 2003 You must configure the Advanced Client to communicate with a specified SMS Site.

68. Log on to SMS with Domain Administrator credentials, and open the SMS Administrator console. Expand Site Database > Site Hierarchy > Site Settings, and then click Discovery Methods. In the details pane, right-click Active Directory System Discovery, and then select Properties. Populating the SMS Server Database with Client Information Deploying Software by Using Systems Management Server 2003

69. Select the Enable Active Directory System Discovery option. Click Add on the right side of Active Directory Containers, and then select Local Domain or Forest for Location. Select Recursive for Search options to ensure that objects in child containers are also discovered. Populating the SMS Server Database with Client Information Deploying Software by Using Systems Management Server 2003

70. Click OK. Select a container or domain/forest, and then click OK. Click the Polling Schedule tab. Click Schedule under the Recurrence pattern section, and then change the polling interval to every five minutes. Populating the SMS Server Database with Client Information (cont.) Deploying Software by Using Systems Management Server 2003

71. Click OK. Select the Run discovery as soon as possible check box, and then click OK. Populating the SMS Server Database with Client Information (cont.) Deploying Software by Using Systems Management Server 2003

72. Log on to SMS with Domain Administrator credentials. Open the SMS Administrator console, and then expand your site. Right-click Packages, and then select New > Package From Definition. Creating an SMS Package Deploying Software by Using Systems Management Server 2003

73. Browse for the Microsoft SharedView MSI package, click it, and then click Next. On the Source Files screen, select This package does not contain any files, and then click Next. Click Finish. Creating an SMS Package (cont.) Deploying Software by Using Systems Management Server 2003

74. Log on to SMS with Domain Administrator credentials. In the SMS Administrator console, expand Packages > Microsoft Corporation Microsoft SharedView. Right-click Distribution Points, click New, and then click Distribution Points. Assigning a Package to an SMS Distribution Point Deploying Software by Using Systems Management Server 2003

75. Click Next on the Welcome page. Click Next on the Copy package page. Select all of the DPs (Distribution Points) where you want the package to be made available. Click Finish to close the wizard. Assigning a Package to an SMS Distribution Point (cont.) Deploying Software by Using Systems Management Server 2003

76. Log on to SMS with Domain Administrator credentials. Right-click the collection to which you want to advertise a package in the SMS Administrator console, and select All Tasks > Distribute Software. On the Welcome page, click Next. Advertising a Package to a Collection Deploying Software by Using Systems Management Server 2003

77. Select the Select an existing package option, and then highlight the required package under the Packages list box. Click Next. Select the install method. In this case, let’s choose to install the package on every system in the collection without user interaction. Advertising a Package to a Collection (cont.) Deploying Software by Using Systems Management Server 2003

78. Highlight Per-system unattended, and then click Next. Modify the Advertisement name and comment if required, and click Next. Choose whether to advertise the package to just this collection or to sub-collections as well, and click Next. Advertising a Package to a Collection (cont.) Deploying Software by Using Systems Management Server 2003

79. On the Advertisement Schedule page, set the time from which the package will be advertised and whether the advertisement should expire, and then click Next. Let’s choose to assign the package because it’s mandatory for our organization. Select Yes. Assign the program. Advertising a Package to a Collection (cont.) Deploying Software by Using Systems Management Server 2003

80. Set a date and time, and then click Next. Review the details, and then click Finish. Expand System Status > Package Status, and you’ll see the SharedView package listed. Advertising a Package to a Collection (cont.) Deploying Software by Using Systems Management Server 2003

81. Reports in SMS Server 2003 Deploying Software by Using Systems Management Server 2003 Report in Systems Management Server 2003

82. Summary You learned how to create new assigned and published packages using Group Policy. You learned how to create packages and advertisements by using Systems Management Server. You learned how to deploy and configure the SMS Advanced Client. You Learned

83. Summary You learned how to run reports by using Systems Management Server. You learned how to upgrade packages by using Group Policy. You learned how to remove and redeploy packages by using Group Policy. You learned that legacy applications can be deployed by Group Policy using zap files. You Learned (cont.)

84. Summary You learned how to identify MSI packages by product code. You learned how to assign packages to Distribution Points in Systems Management Server. You learned how to use software categories in Group Policy. You Learned (cont.)