User Guide - English. ServerView Suite. DeskView and ServerView Integration Pack for Microsoft SCCM

User Guide - English ServerView Suite DeskView and ServerView Integration Pack for Microsoft SCCM Edition June 2010

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 e-mail to manuals@ts.fujitsu.com. 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 www.cognitas.de Copyright and Trademarks Copyright 2010 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.

Contents 1 Introduction............................ 5 1.1 Target groups........................... 6 1.2 Documentation for ServerView Suite.............. 6 1.3 Notational conventions..................... 6 2 Integration pack......................... 7 2.1 Integration requirements.................... 7 2.2 Installing and uninstalling the integration pack........ 8 2.2.1 Installing the integration pack................... 8 2.2.2 Uninstalling the integration pack.................. 9 3 ServerView integration..................... 11 3.1 Updating the scan program.................. 11 3.2 Initial steps after installation................. 12 3.3 Integrating the update process into SCCM.......... 13 3.4 Specific actions for PRIMERGY servers........... 18 3.4.1 Start irmc Console....................... 18 3.4.2 Start ServerView Operations Manager............. 19 4 DeskView Integration..................... 21 4.1 Installing DeskView Integration................ 22 4.1.1 Installing DeskView enhancements on the SCCM console... 22 4.1.2 Integrating system data..................... 23 4.1.2.1 Copy DeskView.dll...................... 24 4.1.2.2 Customize MOF files..................... 25 4.1.2.3 Compile MOF files...................... 26 4.1.3 Installing DeskView Client.................... 27 4.1.4 Uninstalling DeskView Integration................ 28 4.1.5 Troubleshooting......................... 29 DeskView and ServerView Integration Pack for Microsoft SCCM

Contents 4.2 Configuring DeskView Integration............... 29 4.2.1 DeskView functions........................ 29 4.2.2 Event indicators.......................... 30 4.2.3 Reports.............................. 30 4.3 Using DeskView Integration.................. 31 4.3.1 Collections............................ 31 4.3.2 System data............................ 32 4.3.3 Reporting............................. 34 4.3.4 Displaying status changes on the client via event indicators... 35 4.3.5 DeskView functions........................ 35 4.3.5.1 Settings before running.................... 41 4.3.5.2 Executing packages...................... 42 5 Appendix: Integrating the update process into SCE..... 43 Index.................................... 55 DeskView and ServerView Integration Pack

1 Introduction This manual describes the product DeskView and ServerView Integration Pack for Microsoft SCCM, which can be used to manage the hardware and software of clients (business clients, workstations, PCs, notebooks and PRIMERGY servers) from Fujitsu with a Windows operating system in the Microsoft System Center Configuration Manager (SCCM). I In the Japanese market the product DeskView and ServerView Integration Pack for Microsoft SCCM supports only ServerView. Please skip all the relevant descriptions for DeskView in this manual. The manual is organized into the following sections: Integration pack This section describes the integration requirements, and explains how to install and uninstall the integration pack. ServerView integration (PRIMERGY servers only) 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. DeskView integration This section provides information about DeskView integration. DeskView integration allows you to query and manage system data, BIOS settings and reports in the SCCM. Appendix: Integrating the update process into SCE (PRIMERGY servers only) Microsoft System Center Essentials (SCE), like SCCM, is autonomous system management software which is based on SCOM 2007 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. DeskView and ServerView Integration Pack for Microsoft SCCM 5

Target groups 1.1 Target groups This manual is aimed at administrators and service professionals who already have a sound knowledge of SCCM, ServerView Update Manager and DeskView. 1.2 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 http://manuals.ts.fujitsu.com under the link Industry standard servers. 1.3 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. 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. 6 DeskView and ServerView Integration Pack

2 Integration pack 2.1 Integration requirements The site server (also known as the configuration management server ) on which the integration pack is to be installed must be configured as a management point. At least Windows 2003 SP2 must be installed on this server. ServerView: Microsoft Windows Update Service (WSUS) 3.0 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. DeskView: Windows 2000 SP4, Windows XP Home Edition and Windows XP Professional must be installed on the clients, with SP1 and SP2 or Windows XP Professional x64 Edition. DeskView 6.00 or higher must be installed on the clients. DeskView and ServerView Integration Pack for Microsoft SCCM 7

Installing and uninstalling the integration pack 2.2 Installing and uninstalling the integration pack 2.2.1 Installing the integration pack The DeskView and ServerView Integration Pack for Microsoft SCCM integration pack 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: DeskView and 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 aera under http://support.ts.fujitsu.com/com/support/downloads.html full text search DeskView and 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 DeskView and 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 pack is visible to all system users. Without this option, the pack is only visible to the user who installs it. /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: 8 DeskView and ServerView Integration Pack

Installing and uninstalling the integration pack 2.2.2 Uninstalling the integration pack You can use one of the following three options to uninstall the integration pack: Windows uninstall program In the Windows Control Panel, select Add or Remove Programs. Then choose Remove to start the uninstall program for the DeskView and 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 DeskView and ServerView Integration Pack for Microsoft SCCM.msi DeskView and ServerView Integration Pack for Microsoft SCCM 9

3 ServerView integration 3.1 Updating the scan program The SVUMScanTool.msi scan program is delivered with the DeskView and ServerView Integration Pack for Microsoft SCCM integration pack. 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 12) 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. If you are integrating software updates and SVUMScanTool.msi has the status required (see Point 5 on page 17), you should initially only distribute this program to the PRIMERGY servers, and then distribute the actual software updates in a second step. 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. DeskView and ServerView Integration Pack for Microsoft SCCM 11

Initial steps after installation Uninstall the scan program If you no longer want to use the DeskView and ServerView Integration Pack for Microsoft SCCM integration pack 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 PRIMERGY server concerned in the SCCM Resource Explorer under Hardware - ServerView: ServerView Update The SCCM Inventory is listed in the Description column of the UpdMgmt Scan Tool in the table contained there. Local deletion on each individual PRIMERGY server using the Windows uninstall program 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. 12 DeskView and ServerView Integration Pack

Integrating the update process into SCCM You can do this under Install Update Management Scan Tool with the objectspecific action Distribute > Software, or under Advertisements with the objectspecific action New > Software. 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. DeskView and ServerView Integration Pack for Microsoft SCCM 13

Integrating the update process into SCCM 1. The Software Update Catalog must be imported into the SCUP. To do this, start the SCUP and import the catalog manually with the objectspecific action Import Update(s), or add the catalog to the import list (menu bar: Action > Settings > Import List). If you import the catalog manually with the Import Update(s) action, you must trigger an "on-spec" update of the catalog at intervals of your own choosing. If you add it to the import list, the import is based on the settings made there. You can, for example, make a setting to ensure that the catalog in the import list is checked each time the SCUP is started, and is imported automatically if it needs to be updated. You will find the catalog at: http://support.ts.fujitsu.com/gfsms/globalflash/fjsvumcatalogforsccm.cab The catalog contains the descriptions of PRIMERGY software updates which are available in the PRIMERGY Support Package or Autonomous Support Package format. After the import, the updates are displayed in the SCUP under Fujitsu. 14 DeskView and ServerView Integration Pack

Integrating the update process into SCCM 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 Update(s) to transfer them. 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 Update Repository with the object-specific action Run Synchronization. DeskView and ServerView Integration Pack for Microsoft SCCM 15

Integrating the update process into SCCM Alternatively, define the cycle in which synchronization is to be automatically executed under Component Configuration by selecting the object-specific action Properties. 16 DeskView and ServerView Integration Pack

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 Software Updates. 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. DeskView and ServerView Integration Pack for Microsoft SCCM 17

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. 3.4.1 Start irmc Console This action, which is only available after you select a PRIMERGY server, starts the ServerView Remote Management irmc S2 Web Server for the selected PRIMERGY server. 18 DeskView and ServerView Integration Pack

Specific actions for PRIMERGY servers 3.4.2 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. DeskView and ServerView Integration Pack for Microsoft SCCM 19

4 DeskView Integration The Fujitsu DeskView Integration in Microsoft System Center Configuration Manager (SCCM) - DeskView Integration for short - offers the following functions: Grouping DeskView systems into collections Displaying system data Setting a customer-specific serial number Generating reports Displaying status changes on the client via event indicators Configuring the system monitoring on the client Changing the operating status Configuring the 0 watt/maintenance operating status BIOS management Update BIOS Archive BIOS Update processor microcodes Configure individual BIOS settings Change BIOS password Reset BIOS to default values Set boot order During the installation, DeskView Integration extends the existing SCCM system data. The enhancements required for this are described below. For this installation to be performed, Microsoft SCCM must already be installed. To install DeskView, the following steps are required: Install the DeskView enhancements on the SCCM console (see section Installing DeskView Integration on page 22, section Installing DeskView enhancements on the SCCM console on page 22. Integrate the data (see section Integrating system data on page 23) Install DeskView Client on the client computers (see section Installing DeskView Client on page 27) DeskView and ServerView Integration Pack for Microsoft SCCM 21

Installing DeskView Integration 4.1 Installing DeskView Integration 4.1.1 Installing DeskView enhancements on the SCCM console I If you do not use the standard directory during installation of the DeskView enhancements, you must make sure that the complete path statement of this directory does not exceed 70 characters. Otherwise the installation will not be fully performed. This is how you install DeskView on the SCCM console: 1. Start the program DeskView and ServerView Integration Pack for Microsoft SCCM.msi on the SCCM site server. The SCCM console enhancements which are required for the integration of DeskView will be installed. The standard installation directory is C:\%ProgramFilesFolder%\Fujitsu\SCCM. During installation, the program DVSMSSiteserverInstall.exe is run, to expand the user interface of SCCM. I FJSCCMSiteserverInstall.exe uses the output file FJ_SCCM.xml. The file FJ_SCCM_IntegrationUninstallFile.xml is also created during installation. Both files are absolutely vital for the uninstall procedure (see section Uninstalling DeskView Integration on page 28). They must not be edited. By installing DeskView you have integrated the DeskView functions into Microsoft SCCM and enhanced the user interface of the SCCM console with DeskView-specific features. The DeskView Integration is only fully operational after you have installed DeskView Client on the target system and have correctly integrated the data. 22 DeskView and ServerView Integration Pack

Installing DeskView Integration 4.1.2 Integrating system data DeskView uses MOF based data integration, in order to offer additional system data in Microsoft SCCM. The following files are required for the MOF integration: DeskView.dll FJ_SCCM_addon_to_sms_def_mof.txt with the additional class definitions for DeskView FJ_SCCM_addon_to_sms_schm_mof.txt with the SCCM schema for the additional classes FJ_SCCM_recommended_enhancements_to_sms_def_mof.txt with the description of how the changes must be carried out and recommendations concerning which MOF classes and properties should be activated for reports You will find all the necessary files for the data integration at http://www.ts.fujitsu.com/manageability Under DeskView Downloads, select the download package (.zip). You will find the TXT files for the relevant language in the subdirectory \de or \en after you unzip the package. DeskView and ServerView Integration Pack for Microsoft SCCM 23

Installing DeskView Integration To integrate the DeskView-specific system data, you must edit the sms_def.mof file on the SCCM site server. The file is located on the SCCM site server in the directory <Installation_directory>\inboxes\clifiles.src\hinv. The associated schema file sms_schm.mof must also be edited. The file is located in the directory <Installation_directory>\bin\i386. I You can display and edit the MOF files with any text editor. 4.1.2.1 Copy DeskView.dll Copy the file DeskView.dll into the SCCM directory <SCCM_installation_directory>\bin\i386. 24 DeskView and ServerView Integration Pack

Installing DeskView Integration 4.1.2.2 Customize MOF files I In the MOF files you will find more information about changing the classes and attributes. To customize the MOF files: 1. Before you make any changes, make a back-up copy of the files sms_def.mof and sms_schm.mof. 2. Copy the contents of the supplied MOF files in sections into the existing MOF files. In doing this, you must bear in mind that already existing classes and attributes must not be inserted. 3. Insert the DeskView-specific classes at the end of the sms_def.mof file, as indicated in the file FJ_SCCM_addon_to_sms_def_mof.txt. 4. In the file sms_def.mof, change the value of the report attribute of the corresponding class properties to True and insert the standard classes as indicated in the file FJ_SCCM_recommended_enhancements_to_sms_def_mof.txt. Once this is done you can display this data in the SCCM console as inventory data and use it in reports. 5. Check the syntax of your changes with the command mofcomp -check sms_def.mof. 6. Copy the contents of the file FJ_SCCM_addon_to_sms_schm_mof.txt and insert it at the end of the file sms_schm.mof. The schema files are used to configure SCCM for language-relevant terms, which, through the file FJ_SCCM_addon_to_sms_def_mof.txt, are additionally included in the SCCM inventory 7. Check the syntax of your changes with the command mofcomp -check sms_schm.mof. DeskView and ServerView Integration Pack for Microsoft SCCM 25

Installing DeskView Integration 4.1.2.3 Compile MOF files 1. Compile the file sms_def.mof using the command mofcomp -N:root\cimv2<SCCM Installationsverzeichnis>\inboxes\clifiles.src\hinv\sms_def.mof. If there are errors, correct them and compile the file again. I You can run the compilation of Microsoft SCCM automatically, but with a time delay. 2. Mark the following line of the sms_schm.mof file with the comment characters: //#pragma autorecover. This is recommended because otherwise, compilation of the file cannot be performed correctly in some circumstances. The changes will be automatically evaluated during the next run of the hardware inventory agents on the SCCM clients. 3. Compile the file sms_schm.mof using the command mofcomp <SCCM_installation_directory>\SCCM\bin\i386\sms_schm.mof. If there are errors, correct them and compile the file again. 4. Once the compilation has run without errors, remove the commenting-out characters from operation step 2. I The changes to the MOF files will be automatically evaluated during the next inventory cycle on the clients. After installation it may take up to three inventory cycles, before the new system data can be displayed in Microsoft SCCM. 26 DeskView and ServerView Integration Pack

Installing DeskView Integration 4.1.3 Installing DeskView Client DeskView Client is installed as follows: 1. In Microsoft SCCM, create a new package for the program DeskView Client. The program package with all the associated files can be stored on an approved network drive or locally. 2. Select the option Package from definition and select the package DeskViewClient.msi. I The control file DeskViewClient.sms must be located in the same directory as the file DeskViewClient.msi. 3. If necessary, configure a distribution point for the package (e.g. in larger networks). 4. Under Advertisements, create a new task for software distribution for the new package. 5. Make the desired settings in the Advertisement properties window (e.g. time, computer groups, collections). 6. Start the distribution of the software. You can check the status of the client installation later using the System status function. DeskView and ServerView Integration Pack for Microsoft SCCM 27

Installing DeskView Integration An example of software distribution: 4.1.4 Uninstalling DeskView Integration During installation, the file FJ_SCCM_IntegrationUninstallFile.xml is stored in the installation directory of DeskView Integration (default installation directory: C:\%ProgramFilesFolder%\Fujitsu\SCCM). You must not change this file or the file FJ_SCCM.xml. Otherwise uninstall cannot be run correctly. DeskView SCCM is uninstalled as follows 1. Uninstall DeskView SCCM using the Windows Start menu (Settings > Control Panel > Software). For more information, see the Windows documentation. 2. If you installed DeskView Client on the client computers using Microsoft SCCM, you must also use Microsoft SCCM to uninstall the program again. 28 DeskView and ServerView Integration Pack

Configuring DeskView Integration 4.1.5 Troubleshooting If not all the WMI classes and attributes are displayed in Microsoft SCCM, check whether the correct language version of the file DeskView.dll is stored in the directory \bin\i386. 4.2 Configuring DeskView Integration This section provides an overview of how to configure the DeskView functions, the event indicators and the reports in Microsoft SCCM. I For more detailed information on using the DeskView functions, see the manual "DeskView Client 6". 4.2.1 DeskView functions Each DeskView function is provided as an SCCM program and they are arranged in function groups in packages in Microsoft SCCM. They are run in batch files or VB scripts, which must be distributed on the clients before being run. You distribute the DeskView tasks using the SCCM function Advertisements. I In Microsoft SCCM under Advertisements, always select the setting Download the program from the distribution point. Never change the setting Run with administrator rights, because these rights are needed to run the DeskView Client components. You will find the setting in the Environment tab in the Properties window. Before running, the batch files are downloaded together with their associated files into the SCCM client storage. The batch files or VB scripts are started from this storage. DeskView and ServerView Integration Pack for Microsoft SCCM 29

Configuring DeskView Integration 4.2.2 Event indicators Microsoft SCCM only shows event indicators if a corresponding event occurred before the system data was last updated and you have not reset the indicators using the function Reset all values for event indicators. In this case the WMI instances for the first occurrence of the event are meant. 4.2.3 Reports The DeskView reports can be found under Reporting > Reports > Fujitsu > DeskView. Some of these reports work with MOF components which are not covered by the standard file SCCM_def.mof from Microsoft SCCM. The database tables are generated on the basis of the first occurrence of information for these classes or their properties. For this reason, during production of the reports, errors may occur in the following cases: The MOF file was not upgraded with the recommended add-on of DeskView. The system data of this upgrade has not yet been stored in the central SCCM database. 30 DeskView and ServerView Integration Pack

Using DeskView Integration 4.3 Using DeskView Integration This section explains how you can use DeskView functions and data in SCCM. I For more detailed information on using the DeskView functions, see the manual "DeskView Client 6". 4.3.1 Collections Figure 1: Example Collections Under Collections, systems are combined in groups with special attributes. This grouping is done according to various criteria, e.g. operating systems. DeskView and ServerView Integration Pack for Microsoft SCCM 31

Using DeskView Integration 4.3.2 System data The following DeskView system data is administered in Microsoft SCCM: DeskView: Installation information DeskView: Computer system product DeskView: BIOS settings DeskView: Latest received device status DeskView: Mainboard DeskView: Physical hard disk DeskView: Problem indicator DeskView: Memory controller DeskView: Physical memory DeskView: Monitor casing You will find a detailed description of the system data in the manual DeskView functions in Microsoft SCCM. Furthermore, you can enhance the standard system data of Microsoft SCCM with additional properties for DeskView. You will find a description of the enhancements in the file FJ_SCCM_recommended_enhancements_to_sms_def_mof.txt. 1. Select a system in your chosen collection. In the navigation on the right you will see the link to the Resource Explorer. 2. In Microsoft SCCM start the Resource Explorer. 3. Open the Hardware folder. All system data is shown. 4. Select the system data class whose data you want to display. 32 DeskView and ServerView Integration Pack

Using DeskView Integration Figure 2: Example Inventory data DeskView and ServerView Integration Pack for Microsoft SCCM 33

Using DeskView Integration 4.3.3 Reporting Figure 3: Example Reports You can use Reporting > Reports to report information about the resources managed by SCCM. In the subfolder DeskView of the folder Fujitsu you will find the following DeskViewspecific reports: All different mainboards Shows all the different mainboard types from Fujitsu All different system type Shows all the different system types from Fujitsu All mainboards Shows the mainboard types for all the systems from Fujitsu All system types Shows the system types for all systems from Fujitsu Number of different mainboards Shows all the different mainboard types and their number 34 DeskView and ServerView Integration Pack

Using DeskView Integration Number of different system types Shows all the different system types and their number Version of DeskView SCCM Integration Shows the installed version of DeskView SCCM as a title caption 4.3.4 Displaying status changes on the client via event indicators Status changes on the client are shown in the Resource Explorer. 1. Select a system in your chosen collection. In the navigation on the right you will see the link to the Resource Explorer. 2. In Microsoft SCCM start the Resource Explorer. 3. Select Hardware > DeskView: Event Indicator. 4.3.5 DeskView functions The following functions cannot be called directly in SCCM, but must be executed via functions: Setting a customer-specific serial number Configuring the system monitoring on the client Changing the operating status Configuring the 0 watt/maintenance operating status BIOS management Update BIOS Archive BIOS Update processor microcodes Configure individual BIOS settings Change BIOS password Reset BIOS to default values Set boot order DeskView and ServerView Integration Pack for Microsoft SCCM 35

Using DeskView Integration The execution of the functions is controlled via packages, which group together related DeskView functions. Figure 4: DeskView Advanced and Basic Packages The DeskView functions can be found in the Packages folder in the subfolders DeskView Basic Packages and DeskView Advanced Packages. Advanced packages differ from basic packages in that they require adjustment of call-up parameters and variables. 36 DeskView and ServerView Integration Pack

Using DeskView Integration Figure 5: DeskView Basic Packages DeskView Basic Packages Activate Specific BIOS Settings Enable 0 Watt Mode Enable Bluetooth Enable Diskette Controller Enable Flash Write Right Enable Infrared Enable Maintenance Mode Enable Parallel Port Enable Remote Boot Enable USB Host Controller Enable USB Mass Storage Devices Enable Wake on LAN Enable WLAN DeskView and ServerView Integration Pack for Microsoft SCCM 37

Using DeskView Integration Archive BIOS Archive BIOS in Local File Archive BIOS in Remote File Change System Mode (at once) Log Off Current User Log Off Current User (forced) Restart Computer Restart Computer (forced) Shutdown and Switch Off Computer Shutdown and Switch Off Computer (forced) Switch Computer into Hibernate Mode Switch Computer into Hibernate Mode (forced) Switch Computer into Standby Mode Switch Computer into Standby Mode (forced) Deactivate Specific BIOS Settings Disable Bluetooth Disable Diskette Controller Disable Flash Write Right Disable Infrared Disable Parallel Port Disable Remote Boot Disable USB Host Controller Disable USB Mass Storage Devices Disable Wake on LAN Disable WLAN Reset BIOS to Default Reset BIOS to Default Values 38 DeskView and ServerView Integration Pack

Using DeskView Integration Update BIOS Update BIOS from Distributed Update File Update from Local Archive File Update from Remote Update File Update with Automatic File Detection Update Microcode Patch from Distributed File Update Microcode Patch from remote Update File Update Boot Order Boot from CD-ROM Boot from Floppy Boot from Hard Disk Boot from LAN Boot from Legacy Network Card Update Boot Order to CD_HD_Diskette_LAN Update Boot Order to Diskette_CD_LAN_HD Update Boot Order to HD_CD_Diskette_LAN Update Boot Order to LAN_HD_CD_Diskette DeskView and ServerView Integration Pack for Microsoft SCCM 39

Using DeskView Integration Figure 6: DeskView Advanced Packages DeskView Advanced Packages BIOS Access Right Change BIOS Password BIOS Settings Update Update BIOS Settings from Distributed Update File Update BIOS Settings from Local Archive File Update BIOS Settings from Remote Update File Update BIOS Settings with Automatic File Selection Change System Mode (time controlled) Log Off Current User Log Off Current User (forced) Restart Computer Restart Computer (forced) Shutdown and Switch Off Computer 40 DeskView and ServerView Integration Pack

Using DeskView Integration Shutdown and Switch Off Computer (forced) Switch Computer into Hibernate Mode Switch Computer into Hibernate Mode (forced) Switch Computer into Standby Mode Switch Computer into Standby Mode (forced) General Client Settings Configure Notification E-mail Forwarding on Client Disable Problem Monitoring on Client Enable Problem Monitoring on Client Reset All Problem Indicator Values Schedule Maintenance Mode Set Customer-Specific Serial Number Security Functions Enhance BOOT Security Secure PC Set USB Mass Storage Devices to Read-only 4.3.5.1 Settings before running Some programs contain command line parameters which you must update before distribution. The current values must also be entered for the variables. Special settings must be made for the following programs before running: BIOS - change access privileges BIOS - update with distributed update file BIOS - update with remote update file Update processor microcode with distributed update file Update processor microcode with remote update file I For a detailed description of the settings, see the manual "DeskView Client 6. DeskView and ServerView Integration Pack for Microsoft SCCM 41

Using DeskView Integration 4.3.5.2 Executing packages The New Advertisement Wizard is intended for executing packages (Computer Management > Software Distribution > Advertisements). 1. Select under Advertisements the New Advertisement action. The New Advertisement Wizard opens. 2. Follow the steps of the wizard to select and execute a package. Figure 7: Example: Select a Package 42 DeskView and ServerView Integration Pack

5 Appendix: Integrating the update process into SCE This chapter describes what steps are required to integrate Update Management - as in SCCM - into 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 http://support.ts.fujitsu.com/gfsms/globalflash/svumscantool.msi 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. DeskView and ServerView Integration Pack for Microsoft SCCM 43

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. 44 DeskView and ServerView Integration Pack

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

In the next step you must enter the installation and uninstallation properties. 46 DeskView and ServerView Integration Pack

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. DeskView and ServerView Integration Pack for Microsoft SCCM 47

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. 48 DeskView and ServerView Integration Pack

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

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. 50 DeskView and ServerView Integration Pack

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: http://support.ts.fujitsu.com/gfsms/globalflash/fjsvumcatalogforsccm.cab DeskView and ServerView Integration Pack for Microsoft SCCM 51

After downloading the catalog the available update packages are listed. You can import them into SCE using the Import button. 52 DeskView and ServerView Integration Pack

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. DeskView and ServerView Integration Pack for Microsoft SCCM 53

Index D DeskView functions 29 installing DeskView Client 27 installing enhancements 22 integrating system data 23 integration 21 troubleshooting 29 uninstall 28 documentation for ServerView Suite 6 I installation 8, 11 installation,initial steps after 12 integration requirements 7 irmc console,starting 18 P PRIMERGY server,specific actions 18 S scan program 11 SCE, integrating the update process 43 ServerView Operations Manager,starting 19 SVUMScanTool.msi 11 U uninstallation 8 update process, integration into SCCM 13 DeskView and ServerView Integration Pack for Microsoft SCCM 55

56 DeskView and ServerView Integration Pack