ServerView Integration Pack for Microsoft SCCM

Transcription

1 User Guide - English FUJITSU Software ServerView Suite ServerView Integration Pack for Microsoft SCCM Edition July 2012

2 Comments Suggestions Corrections The User Documentation Department would like to know your opinion of this manual. Your feedback helps us optimize our documentation to suit your individual needs. Feel free to send us your comments by to Certified documentation according to DIN EN ISO 9001:2000 To ensure a consistently high quality standard and user-friendliness, this documentation was created to meet the regulations of a quality management system which complies with the requirements of the standard DIN EN ISO 9001:2000. cognitas. Gesellschaft für Technik-Dokumentation mbh Copyright and Trademarks Copyright 2012 Fujitsu Technology Solutions GmbH. All rights reserved. Delivery subject to availability; right of technical modifications reserved. All hardware and software names used are trademarks of their respective manufacturers.

3 Contents 1 Introduction Target groups Changes since the previous version ServerView Suite link collection Documentation for ServerView Suite Notational conventions Integration package Integration requirements Installing and uninstalling the integration package Installing the integration package Uninstalling the integration package ServerView integration Updating the scan program Initial steps after installation Integrating the update process into SCCM Specific actions for PRIMERGY servers Start irmc Console Start ServerView Operations Manager Offline update repository Appendix: Integrating the update process into SCE ServerView Integration Pack for Microsoft SCCM 3

4 Contents 4 ServerView Integration Pack for Microsoft SCCM

5 1 Introduction This manual describes the product ServerView Integration Pack for Microsoft SCCM, which can be used to manage the hardware and software of PRIMERGY servers from Fujitsu with a Windows operating system in the Microsoft System Center Configuration Manager (SCCM). The manual is organized into the following sections: Integration package This section describes the integration requirements, and explains how to install and uninstall the integration package. ServerView integration This section provides information about ServerView integration. ServerView integration allows you to use the SCCM to manage execution of the update process of the ServerView Update Manager for PRIMERGY servers. Appendix: Integrating the update process into SCE Microsoft System Center Essentials (SCE), like SCCM, is autonomous system management software which is based on SCOM and WSUS. Up to 30 Windows servers and approx. 500 clients are supported in SCE. I For basic information about using the Windows software mentioned in this manual, refer to the relevant Microsoft documentation. ServerView Integration Pack for Microsoft SCCM 5

6 Target groups 1.1 Target groups This manual is aimed at administrators and service professionals who already have a sound knowledge of SCCM and ServerView Update Manager. 1.2 Changes since the previous version This edition of the manual applies to ServerView Integration Pack for Microsoft SCCM and replaces the following online manual: ServerView Suite, DeskView and ServerView Integration Pack for Microsoft SCCM, December 2010 edition. The manual features the following changes and enhancements: DeskView has been removed from the manual. The chapter Offline Update Repository has been extended to include the partial download and the type specification of the update components.. Screenshots have been updated. 1.3 ServerView Suite link collection Via the link collection, Fujitsu Technology Solutions provides you with numerous downloads and further information on the ServerView Suite and PRIMERGY servers. For ServerView Suite, links are offered on the following topics: Forum Service Desk Manuals Product information Security information Software downloads Training 6 ServerView Integration Pack for Microsoft SCCM

7 ServerView Suite link collection I The downloads include the following: Current software versions for the ServerView Suite as well as additional Readme files. Information files and update sets for system software components (BIOS, firmware, drivers, ServerView agents and ServerView update agents) for updating the PRIMERGY servers via ServerView Update Manager or for locally updating individual servers via ServerView Update Manager Express. The current versions of all documentation on the ServerView Suite. You can retrieve the downloads free of charge from the Fujitsu Technology Solutions Web server. For PRIMERGY servers, links are offered on the following topics: Service Desk Manuals Product information Spare parts catalogue Access to the ServerView link collection You can reach the link collection of the ServerView Suite in various ways: 1. Via ServerView Operations Manager. Ê Select Help Links on the start page or on the menu bar. After this selection the start page of the ServerView link collection opens. 2. Via the ServerView Suite DVD 2 or via the start page of the online documentation for the ServerView Suite on the Fujitsu Technology Solutions manual server. I You access the start page of the online documentation via the following link: Ê Ê In the selection list on the left, select Industry standard servers. Click the menu item PRIMERGY ServerView Links. After this selection the start page of the ServerView link collection opens. ServerView Integration Pack for Microsoft SCCM 7

8 Documentation for ServerView Suite 3. Via the ServerView Suite DVD 1 Ê Ê Ê In the start window of the ServerView Suite DVD 1, select the option Select ServerView Software Products. Click Start. This takes you to the page with the software products of the ServerView Suite. On the menu bar select Links. After this selection the start page of the ServerView link collection opens. 1.4 Documentation for ServerView Suite The documentation for the ServerView Suite can be found on the ServerView Suite DVD 2 supplied with each server system. The documentation can also be downloaded free of charge from the Internet. You will find the online documentation at under the link Industry standard servers. 1.5 Notational conventions The following notational conventions are used in this manual: VCaution I Italics Fixed width <variable> Reference to hazards that can lead to personal injury, loss of data or damage to equipment. This symbol highlights important information and tips. Commands, menu items, names of buttons, options, variables, file names and path names are shown in italics. Commands and options in syntax descriptions are shown in fixed width type. Angle brackets are used to indicate variables that are to be replaced by actual values. 8 ServerView Integration Pack for Microsoft SCCM

9 Notational conventions Screen outputs Please note that some of the screen outputs are system-dependent and therefore may not be identical to the screens in your system. Similarly, some of the menu items available depend on the system used. ServerView Integration Pack for Microsoft SCCM 9

10 Notational conventions 10 ServerView Integration Pack for Microsoft SCCM

11 2 Integration package 2.1 Integration requirements The integration package only supports the integration into SCCM SCCM 2012 thus determines the requirements for installing the integration package. The site server (also known as the configuration management server ) on which the integration package is to be installed must be configured as a management point. Windows 2008 must be installed on this server. ServerView: At least Microsoft Windows Update Service (WSUS) 3.0 SP2 must be installed on the site server that is to be used as a software update point. Windows 2000 SP4 (or higher) and ServerView Agents Version 4.7 (or higher) must be installed on the PRIMERGY servers that are managed by the SCCM and on which the SCCM configuration management agents run. ServerView Integration Pack for Microsoft SCCM 11

12 Installing and uninstalling the integration package 2.2 Installing and uninstalling the integration package Installing the integration package The ServerView Integration Pack for Microsoft SCCM is installed on the configuration management server. The following program allows you to install the pack automatically or to be guided through the installation by a wizard: ServerView Integration Pack for Microsoft SCCM.msi You will find this program on the PRIMERGY ServerView Suite DVD 1 under: ServerView Suite - Integration Solutions or in the Fujitsu download area under full text search ServerView Integration Pack for Microsoft SCCM I The pack must be uninstalled before it can be reinstalled. An update is not possible. Use the following command in the Windows command prompt to start the installation: msiexec [/qn] /i ServerView Integration Pack for Microsoft SCCM.msi [<options>] An automatic installation is started if you specify the qn parameter. You can specify the following options (among others) in the command call: ALLUSERS=1 1 = The integration package is visible to all system users. Without this option, the pack is only visible to the user who installs it. TRANSFORMS=<language ID>.mst With TRANSFORMS you can supply installations in different languages. The default language is English. For an installation with a German user interface use TRANSFORMS=de.mst. For an installation with a Japanese user interface use TRANSFORMS=ja.mst. 12 ServerView Integration Pack for Microsoft SCCM

13 Installing and uninstalling the integration package /l*v <file name> An installation log file is generated in the current directory if you specify the /l option. After a successful installation, the clients detected after a discovery run are listed by type under Collections in the Configuration Manager Console of the SCCM: ServerView Integration Pack for Microsoft SCCM 13

14 Installing and uninstalling the integration package Uninstalling the integration package You can use one of the following three options to uninstall the integration package: Windows uninstall program In the Windows Control Panel, select Add or Remove Programs. Then choose Remove to start the uninstall program for the ServerView Integration Pack for Microsoft SCCM. Restart the installation wizard If the pack is already installed, it can only be uninstalled when you restart the installation wizard. In this case, the Remove option is automatically preselected, and can only be confirmed by choosing Next. Call the following command: msiexec [/qn] /x ServerView Integration Pack for Microsoft SCCM.msi 14 ServerView Integration Pack for Microsoft SCCM

15 3 ServerView integration 3.1 Updating the scan program Updating the scan program To provide the ServerView update process in SCCM, you require the scan program SVUMScanTool.msi. The scan program is not part of the ServerView Integration Pack for Microsoft SCCM, but is available on the Fujitsu Technology Solutions support server and as an SCCM update package. The ServerView Agents (Version 4.70 and higher) installed on the PRIMERGY servers automatically call this program on the servers on a cyclical basis. It finds all Update Manager components installed on the machine and enters their data in the Windows Registry. A Registry Provider assigns this data to the FJSV_UMComponents WMI class. The data is then available to SCCM in the Software Updates Scan Cycle and as inventory data in the SCCM Resource Explorer. Distribute the scan program This program must be distributed to the PRIMERGY servers in SCCM: 1. after SCCM is installed for the first time (see chapter Initial steps after installation on page 17) 2. after an update of the scan program itself (see below) Update the scan program The latest version of the scan program is contained in the current software update catalog and can consequently be updated in the context of a software update. Additionally the newest version of the scan program is available on the Fujitsu Technology Solutions support server at If you are integrating software updates and SVUMScanTool.msi has the status required (see Point 5 on page 21), you should initially only distribute this program to the PRIMERGY servers, and then distribute the actual software updates in a second step. ServerView Integration Pack for Microsoft SCCM 15

16 Updating the scan program I If you have installed a new hardware component on your SCCMmanaged PRIMERGY servers, or added new PRIMERGY models to SCCM Update Management, you should also install the latest version of the scan program on these systems. The new version ensures that updates for the new components can also be correctly detected and updated. Uninstall the scan program If you no longer want to use the ServerView Integration Pack for Microsoft SCCM integration package and wish to uninstall it, note that the scan program is not automatically uninstalled with the pack. In such a scenario, you must explicitly delete the scan program using one of the following methods: Global deletion on all PRIMERGY servers using a distribution package you create yourself in SCCM. This distribution package must contain the following command: msiexec /qn /X {<product code>} ALLUSERS=1 The product code changes each time the scan program is updated. You can determine the current product code in two ways: You take the valid product code from the registry on the PRIMERGY servers: HKLM\SOFTWARE\Fujitsu\ServerView Suite\Update ScanTool\Setup\ProductCode If the SCCM Inventory has been extended and a hardware scan cycle has been executed, you will find the product code of the ServerView Update Management Scan Tool for the PRIMERGY server concerned in the SCCM Resource Explorer. Local deletion on each individual PRIMERGY server using the Windows uninstall program 16 ServerView Integration Pack for Microsoft SCCM

17 Initial steps after installation 3.2 Initial steps after installation 1. You must begin by doing the following (if you have not done so already): Define the distribution point and the software update point in SCCM. Define the software update point as an update server in the Microsoft System Center Updates Publisher (SCUP). 2. The scan program for determining which Update Manager components are installed on a machine must be distributed to (installed on) the PRIMERGY servers in SCCM. You can do this in the Software Library panel under the Application Management folder with the action Create Application. Requirement for this is that the latest scan program package SVUMScanTool.msi has been downloaded from the Fujitsu Technology Solutions support server ( onto a network drive or local drive of the site server. ServerView Integration Pack for Microsoft SCCM 17

18 Integrating the update process into SCCM I The scan program is part of the SVUMScanTool.msi package. Since this pack is also part of Update Management, the cyclical call option (here: a cyclical re-installation, if not yet installed) should not be used the first time it is distributed with SCCM. 3.3 Integrating the update process into SCCM The steps described below are required in order to integrate the required software updates of the ServerView Update Manager into SCCM. I These steps are necessary whenever you upgrade the Update Catalog version. 1. The Software Update Catalog must be imported into the SCUP. To do this, start the SCUP and add the software update catalog as a Microsoft partner catalog. You can then import the catalog with the function Import Software Updates Catalogs. You will find the catalog at: The catalog contains the descriptions of PRIMERGY software updates which are available in the PRIMERGY Support Package or Autonomous Support Package format. 18 ServerView Integration Pack for Microsoft SCCM

19 Integrating the update process into SCCM After the import, the updates are displayed in the SCUP under Fujitsu. 2. The updates must then be transferred to the WSUS server (software update point). To do this, select the relevant updates in the SCUP and execute the objectspecific action Publish to transfer them. ServerView Integration Pack for Microsoft SCCM 19

20 Integrating the update process into SCCM 3. Next, the updates must be imported from the WSUS server into SCCM (synchronization). To do this, start SCCM and import the updates manually under Software Library All Software Updates with the object-specific action Synchronize Software Updates. 20 ServerView Integration Pack for Microsoft SCCM

21 Integrating the update process into SCCM 4. After synchronization, each of the specified updates is displayed, together with its status, in SCCM: 5. As a final step, the updates are distributed to the relevant PRIMERGY servers with the status required when you execute the object-specific action Deploy. I A distribution executed in this way currently always returns the value 0. As a result, the only indication that it has actually been successful is if an update has the status (Installed). The return value 0 is also entered for each update as Pending Reboot Code. ServerView Integration Pack for Microsoft SCCM 21

22 Specific actions for PRIMERGY servers 3.4 Specific actions for PRIMERGY servers The first time you call the actions specified below, you are asked to specify the connection-relevant values, namely: the IP address of the irmc or ServerView Operation Manager, the port number and the protocol security level (SSL on/off). The values entered are stored in the irmc.ini and SVS2.ini files, so that they do not have to be entered again the next time the action is called. You will find these files in the SCCM installation path Start irmc Console This action, which is only available after you select a PRIMERGY server, starts the ServerView Remote Management irmc Web Server for the selected PRIMERGY server. 22 ServerView Integration Pack for Microsoft SCCM

23 Specific actions for PRIMERGY servers Start ServerView Operations Manager This action, which is only available after you select a PRIMERGY server, starts the ServerView Operations Manager for the selected PRIMERGY server. ServerView Integration Pack for Microsoft SCCM 23

24 Offline update repository 3.5 Offline update repository For security reasons, computers in a productive environment do not normally have an Internet connection. To allow updates to be distributed via SCCM resources in this scenario, an offline update repository is required, i.e. there must be local access to a locally stored copy of the Fujitsu Technology Solutions update repository Such an offline repository is created with the BuildLocalRep tool. With the help of this tool you can download the entire Fujitsu Technology Solutions update repository or part of it (option- p) into the specified directory (option -d). With the partial download, the following arguments are permitted: Relative path name of an update component or of update components within the repository (including * as wildcard). Example: -p SystemBoard/D21*TX* Type specification of the update components. The following types are allowed: Firmware, Driver, Application. In the process, the scan program SVUMScanTool.msi and the update catalog FJSVUMCatalogForSCCM.cab are always downloaded. If necessary, the update catalog FJSVUMCatalogForSCCM.cab will be saved with a new name (-n option). Afterwards the download URL details within the update catalog FJSVUMCatalogForSCCM.cab are adjusted to the new local directory. The call syntax is as follows: BuildLocalRep -d <Local Share Folder> [-p <Partial Repos Specification>] [-n <Name of Catalog>] [-u] [-t] [-v] -h -d <Local Share Folder> The Local Share Folder must be specified in UNC format, i.e. in the syntax \\<server_name>\<release_name> (e.g.: BuildLocalRep -v -d \\ \SCCM_LocalRepository ). -p <Partial Repos Specification> Partial download of the Fujitsu Technology Solutions update repository. -n <Name of Catalog> New name of the update catalog FJSVUMCatalogForSCCM.cab. 24 ServerView Integration Pack for Microsoft SCCM

25 Offline update repository -u -t -v Use http for downloading (default is https). Use the file %TMP%/BuildLocalRep.log for logging. Show progress on the screen. -h Output the command syntax. This catalog is thus ready to be imported into the SCUP. Once there, the relevant updates can be transferred to the WSUS server ('published') and are then finally available to SCCM for distribution. BuildLocalRep is not part of the ServerView Integration Pack for Microsoft SCCM, but is available on the Fujitsu Technology Solutions support server at ServerView Integration Pack for Microsoft SCCM 25

26 Offline update repository 26 ServerView Integration Pack for Microsoft SCCM

27 4 Appendix: Integrating the update process into SCE This chapter describes what steps are required to integrate Update Management - as in SCCM - into System Center Essentials (SCE). If they have not already been carried out, the following tasks must first of all be performed once on the SCE console: Computer Discovery using the Computer and Device Management Wizard Configuration of Update Management using the Update Management Configuration Wizard The steps described below are needed to subsequently integrate the required software updates of the ServerView Update Manager into SCE. I You must always perform these steps when a new version of the Software Update Catalog is available. 1. The scan program for ascertaining the Update Manager components installed on a computer must be loaded onto a network drive or local drive of the site server and a software package must be created from this which must be distributed to the clients. I The distribution of this software package is a prerequisite for permitting the updates of the ServerView Update Manager to be assigned the correct status information. You will find the scan program at To create the software package, start the SCE console, switch to the Software folder and start the New Software Package Wizard (see the figures below) using the Create New Package... task. ServerView Integration Pack for Microsoft SCCM 27

28 In the first step you must specify the absolute path name of the scan program - which was saved locally beforehand - in the Package setup file field. 28 ServerView Integration Pack for Microsoft SCCM

29 In the Package details step the fields are then filled automatically with the package information of the scan program. ServerView Integration Pack for Microsoft SCCM 29

30 In the next step you must enter the installation and uninstallation properties. 30 ServerView Integration Pack for Microsoft SCCM

31 In the next step you create the package by pressing the Create button. In the last step you confirm the steps and terminate the wizard. ServerView Integration Pack for Microsoft SCCM 31

32 After the New Software Package Wizard has terminated, the following dialog box appears. Here you can add or remove computer groups or set deadlines for the installation of the just created software package. 32 ServerView Integration Pack for Microsoft SCCM

33 The new software package is displayed on the SCE console and can be distributed to the clients using the Add and Remove Approvals... task. ServerView Integration Pack for Microsoft SCCM 33

34 2. The Software Update Catalog must be imported into SCE. On the SCE console switch to the Updates folder and there select the Import updates from partner catalogs task. 34 ServerView Integration Pack for Microsoft SCCM

35 This task opens the Update Catalog Import Wizard with the Welcome step. In the next step you must enter the following URL of the Software Update Catalog: ServerView Integration Pack for Microsoft SCCM 35

36 After downloading the catalog the available update packages are listed. You can import the update packages into SCE using the Import button. 36 ServerView Integration Pack for Microsoft SCCM

37 After a successful import, the updates are displayed on the SCE console with the status Unapproved and can be distributed to the clients using the Add and Remove Approvals task. ServerView Integration Pack for Microsoft SCCM 37

38 38 ServerView Integration Pack for Microsoft SCCM