Distributing SMS and SCCM Packages

Transcription

1 Technical Brief Distributing SMS and SCCM Packages Overview Distributing Microsoft Systems Management Server (SMS), and Microsoft System Center Configuration Manager (SCCM) packages to Persystent Suite clients requires integrating Persystent Suite cleanup and capture into the SMS package program sequence at the beginning and end, respectively. This integration requires configuration of the Suite environment and the creation of SMS/SCCM packages: Configuring Persystent for Package Distribution (page 1) Configuring SMS/SCCM Server and Creating Packages (page 4) See Also PS Technical Brief: Configuring PS for Software Distribution Solutions PS Technical Brief: Configuring WSUS Interoperation PS Technical Brief: Resetting SusClientId Requirements SCCM 2007, SCCM 2007 SP1, SCCM 2007 SP2, SMS 2003, SMS 2003 SP1, or SMS 2003 SP2 Configuring Persystent for Package Distribution Procedure Overview Configuring Persystent for SMS package distribution to clients only needs to be performed once for each repair file filter, repair registry filter, and pre boot policy that you are using for client computers. 1

2 The procedure to configure Persystent for SMS package distribution to clients is as follows: Add to client s repair file filter Add to client s repair registry filter Configure client s pre boot policy to enable SMS (Optional) Force client to download updated policies To Configure PS for Package Distribution 1. Add the Windows\system32\ccm folder to the repair file filter that you are using for client computers (for example, Exclude from Repair) to ensure that the downloaded updates are not removed during the repair process. A. In the WebUI, in the left pane, click Filters and in the right pane the File Filter Filters subtab appears. B. On the File Filter Filters subtab, in the File Filters area under Name, click the repair filter that you are using for client computers (for example, click Exclude from Repair), and the File Filter Manage subtab appears. 2. On the File Filter Manage subtab, in the New File Filter Path area, in the File Path box, type Windows\system32\ccm, and then click Add. TIP When typing file paths in Persystent Suite, it is not necessary to type C:\, the paths are not case sensitive, and for slashes it does not matter if you type a forward slash ( / ) or backward slash ( \ ). (Persystent changes all typed backward slashes to forward slashes) 3. Notice that the typed file path appears in the File Filters area under Path. 2

3 4. Add the HKEY_LOCAL_MACHINE\Software\Microsoft\CCM path and HKEY_LOCAL_MACHINE\Software\Microsoft\SMS path to the repair registry filter that you are using for client computers (for example, Registry Repair Filter Exclude from Repair) to ensure that registry changes are not removed during the repair process. 5. In the WebUI, in the left pane click Filters, and in the right pane click the Registry Filter tab and the Filters subtab appears. 6. On the Registry Filter Filters subtab, in the Registry Filters area under Name, click the repair filter that you are using for client computers (for example, click Registry Repair Filter Exclude from Repair), and the Registry Filter Manage subtab appears. 7. On the Registry Filter Manage subtab, in the New Registry Path area, in the leftmost Path box, select HKEY_LOCAL_MACHINE/Software/. 8. On the Registry Filter Manage subtab, in the New Registry Path area, in the rightmost Path box, type Microsoft\CCM and then click Add. 9. On the Registry Filter Manage subtab, in the New Registry Path area, in the leftmost Path box, select HKEY_LOCAL_MACHINE/Software/. 10. On the Registry Filter Manage subtab, in the New Registry Path area, in the rightmost Path box, type Microsoft\SMS and then click Add. 11. Notice that the typed registry paths appear in the Registry File Path area under Path. Configure pre boot policies to enable SMS/SCCM 1. In the WebUI, in the left pane, expand Policy, click Pre Boot, and in the right pane the Pre Boot Manage subtab appears. 2. On the Pre Boot Manage subtab, in the Available Pre Boot Policies area under Name, click a Pre Boot Policy that you are using for client computers (for example, click Standard Unicast), and the Policy area on the Pre Boot Manage subtab appears. 3. On the Pre Boot Manage subtab, in the Policy area: A. In the Patch Services CleanUp Task list, select SMS/SCCM Cleanup Task. B. In the Patch Services Capture Task list, select SMS/SCCM Capture Task. C. Click Save. NOTE The updated policies will download at the next polling interval specified in the client s active post boot policy. 4. (Optional) Force the download of the updated policies from the server to the client by: A. PXE booting the client computer. or B. Restarting the Persystent Client service on the client computer by clicking Start Control Panel Administrative Tools Services, and right click Persystent Client and click Restart, and then exit Services console. 3

4 Configuring SMS/SCCM Server and Creating Packages Bits Configuration Requirement In order to integrate with Persystent Suite, the following BITS setting must be enabled. 1. In the SMS/SCCM Administrator s console, navigate to Systems Management. (Server Site Database Site Hierarchy <SITENAME> Site Settings Site Systems <SITE SYSTEM NAME>). 2. Right click <SITE SYSTEM NAME>and select Properties. 3. In the Distribution Point tab, ensure that Enable Background Intelligent Transfer Service (BITS) is checked. Persystent Collection Configuration You must create a Persystent Collection in SMS/SCCM in order to integrate with Persystent. You must create a Persystent Collection in SMS/SCCM in order to integrate with Persystent called Persystent Migrated, with the following criterion in the screenshot. 4

5 TECHNICAL BRIEF: DISTRIBUTING SMS AND SCCM PACKAGES 4 Advertisement Configuration Wizard 1. In addition to proper Distribution Point configuration, Advertisements must be properly configured in order to work with Persystent. 2. The following two settings are mandatory for advertisements to work with Persystent during Distribute Package Wizard : A. Advertise the program to Persystent collection only B. Make the Program Mandatory and assign it a date in the future, for example, one year in the future. 3. Here is an example of a sample advertisement setup using Distribute Package Wizard 5

6 A. Screen 1 B. Screen 2 6

7 C. Screen 3 D. Screen 4 7

8 E. Screen 5 F. Screen 6 8

9 G. Screen 7 H. Screen 8 9

10 I. Screen 9 J. Screen 10 10

11 Advertisement Configuration Once the advertisement is created, the following changes need to be made to the Advertisement in order to work with Persystent. 1. Right click on the advertisement previously created. 2. Select Properties. 3. Select Schedule tab. 4. Check Allow users to run the program independently of assignments. 5. Select Advanced Client tab. 6. Select Download program from distribution point. 7. Select Download program from remote distribution point. 8. Click Apply to save all the changes. Client Requirements Client must have.net Framework installed. User must be logged on. Logged on user must have administrative privilege. SMS Advanced client/sccm Client must be installed. It is advised to hide Run Advertised Programs from control panel. This can be done using Global policy in AD. Utopic Software 1215 East 6 th Ave. Tampa, FL Phone: (813) Fax: (813) Sales@UtopicSoftware.com Web Site: Copyright 2011 Utopic Software, LLC. All rights reserved. Printed in the United States of America. Information in this document is subject to change without notice. Utopic Software makes no warranties, express, implied, or statutory, as to the information in this document. This document contains proprietary information protected by copyright. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, without written permission of Utopic Software, LLC 1215 East 6 th Ave., Tampa, FL 33605, except as specified in the Product Warranty and License Terms. Utopic Software, LLC logos are registered trademarks; Persystent Suite is a trademark of Utopic Software, LLC. Microsoft, Windows Server 2008, Windows Server 2003, Windows XP, Windows Vista, Windows 7, Active Directory, SQL Server, SQL Express, and.net are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. All other registered trademarks and service marks mentioned are the property of their respective owner. 11