DeskView 5.33 Client Management Software. October 2003

DeskView 5.33 Client Management Software October 2003

Microsoft, MS, MS-DOS, Windows, Windows 2000, Windows NT and Windows XP are registered trademarks of Microsoft Corporation. Alert on LAN is a registered trademark of IBM Corporation. Intel is a registered trademark of Intel Corporation, USA. Magic Packet is a registered trademark of Advanced Micro Devices, Inc. OpenView is a registered trademark of Hewlett Packard. Unicenter and AMO are registered trademarks of Computer Associates. ServerView is a registered trademark of Siemens AG. Copyright Fujitsu Siemens Computers GmbH 2003. All rights, including rights of translation, reproduction by printing, copying, or similar methods, in part or in whole, are reserved. Offenders will be liable for damages. All rights, including rights created by patent grant or registration of a utility model or design, are reserved. Delivery subject to availability. The right to technical modification is reserved.

Contents Client Management with DeskView...1 What is client management with DeskView?...1 DeskView components overview...2 Network capability...4 SMS and SNMP integration...4 Calling from the command line...4 DeskView Browser/Agent concept...4 What you must know about DeskView...7 DeskView installation, uninstallation and upgrade...7 Tips on installation...8 Network drives...8 Installing DeskView on Windows for Business PCs...8 Installation variants...8 DeskView administrator...9 DMI 2.0 or WMI/CIM...9 License number DeskView License Pack...11 You want to migrate to a different operating system?...11 Migration to Windows XP / Migration from Windows NT 4.0 to Windows 2000...11 Upgrading from Windows 2000 to Windows XP...12 Earlier DeskView versions...13 Where can I find additional information?...13 DeskView components...14 DeskAlert...14 Brief description...14 Conditions in a network with Windows for Home Use Client-PCs and Windows for Business administrator PC...14 Calling from the command line...15 Troubleshooting and tips...17 DeskFlash...17 Brief description...17 Calling from the command line...17 DeskFlash Administration...20 Brief description...20 Calling from the command line...21 DeskInfo...24 Brief description...24 Calling from the command line...25 Troubleshooting and tips...27 DeskOff and DeskOff Admin...28 Brief description...28 Calling from the command line...29 DeskView 5.33 Client Management Software

Contents DeskSettings...31 Brief description...31 Calling from the command line...32 DeskWOL Admin Wake On LAN...33 Brief description...33 Calling from the command line...34 Network installation of DeskView components by the administrator...37 Installation procedure...37 Brief overview of installation procedure...37 Create SNISADM.INI control file...37 Admin Password Utility...38 Make installation files available for client PCs...39 Login script with running of installation program...39 Integration in Management Systems...42 ServerView...42 Microsoft SMS...43 SMS administrator console...43 SMS client...44 CA Unicenter and CA AMO...44 SNMP...44 SNMP administrator...44 SNMP client...45 Timeout for SNMP request for DeskInfo data...47 Appendix result file and error numbers...48 DeskView Setup result file...48 Error numbers...49

Client Management with DeskView This description provides an overview of DeskView, the individual components and their functions. In addition, it also contains important information and tips on installation and on integration in the management systems. For information on operating the program of the individual components, check the respective online help. What is client management with DeskView? DeskView supports you as a PC user, PC administrator or service during the administration of both local and networked PCs provides access to system information and to BIOS Setup even from a remote PC increases system security and reliability with proactive alarms that you can configure yourself provides information on changes to the hardware and opening the case provides the basis for reducing TCO (total cost of ownership) DeskView is a family of software components that can also be installed individually if necessary. DeskView can easily be installed, updated and uninstalled via an unattended setup. Network capability DeskView is network-capable in networks with TCP/IP protocol only. Depending on the DeskView components, these can operate via the network: via the DeskView Browser/Agent concept via command line call (for example, in login scripts) can be integrated into global system management software like Microsoft SMS or SNMP-based management software Naturally, you can run the DeskView components, where reasonable, also locally on your PC. Operating Systems DeskView is available for the following operating systems: Windows 2000 with Service Pack 1 to 3 Windows XP Home Edition and Windows XP Professional, also with Service Pack 1 Windows NT 4.0, Service Pack 5 or 6a In the following, the operating systems Windows NT, Windows 2000 and Windows XP Professional are referred to as Windows for Business. Windows XP Home Edition is referred to as Windows for Home Use. DeskView 5.33 Client Management Software 1

Client Management with DeskView Base memory For an administrator PC, at least 128 Mbyte of RAM is recommended, for a client PC at least 64 Mbyte. BIOS From DeskView 4.25 only system boards with BIOS version 4.05 or higher are supported. When booting the system the BIOS version is displayed. DeskView components overview Currently, DeskView client management software consists of the following components: DeskView component DeskAlert Brief description With DeskAlert changes to the system state of the PCs can be reported and their monitoring configured. Network capability DeskView Browser/Agent DeskFlash DeskFlash Administration Offers the following functions: Update the BIOS Update BIOS settings Archive the BIOS and BIOS settings Update installed processor microcode patches Offers the administrator the following functions in the network: Query BIOS information Archive the BIOS and BIOS settings Check the BIOS update file(s) Update the BIOS Update BIOS settings Update processor microcodes Calling from the command line SNMP integration Calling from the command line DeskView Browser/Agent Calling from the command line Launch integration from SMS 2.0 2 DeskView 5.33 Client Management Software

Client Management with DeskView DeskView component DeskInfo Brief description Provides information on the hardware and software and displays the current status of the PCs. Network capability DeskView Browser/Agent DeskOff DeskOff Admin Switches off the PC, ends the current session or changes into a supported energysaving mode. DeskOff Admin allows the administrator to configure and activate the local DeskOff of the client PC. Calling from the command line SMS and SNMP integration Calling from the command line Launch integration from SMS 2.0 DeskView Browser/Agent DeskSettings Makes settings in the BIOS Setup under Windows. line Calling from the command DeskView Browser/Agent DeskWOL Admin Enables a PC to be switched on via the network (Wake on LAN). line Calling from the command The magic packets are transmitted via the network. line Calling from the command DeskView 5.33 Client Management Software 3

Client Management with DeskView Network capability SMS and SNMP integration Detailed information can be found in chapter "Integration in Management Systems". Calling from the command line DeskAlert, DeskInfo, DeskFlash, DeskFlash Administration, DeskSettings, DeskOff, DeskOff Admin and DeskWOL can be run via the command line. This can, for example, be used for administration via SMS or login scripts. You can find information on the parameters in this manual in the sections for the corresponding DeskView components or in the online Help. DeskView Browser/Agent concept The following DeskView components can be run remotely via the DeskView Browser from an administrator PC: DeskAlert DeskInfo DeskFlash Administration DeskOff Admin DeskSettings DeskView Browser is automatically installed during the administrator installation of these components. For communication in the network these components require the DeskView Agent. DeskView Agent The DeskView Agent receives requests from the administrator PC, checks the access rights for the PCs, and returns the information to the administrator PC. The DeskView Agent is also installed during every installation of DeskAlert, DeskInfo, DeskOffAdmin, DeskFlash (Administration) and DeskSettings. 4 DeskView 5.33 Client Management Software

Client Management with DeskView Under Windows for Home Use the DeskView Agent symbol is displayed in the task bar. By double-clicking on this symbol, you can assign a password for accessing this PC. In addition, you can activate and deactivate the password protection. Under Windows for Business the DeskView Agent is not displayed. The password is not needed since the Windows security concept is used. DeskView Browser The DeskView Browser is an administrator tool, primarily for use in smaller networks. If you use Microsoft SMS or CA Unicenter, you can run the DeskView components directly. Then you do not require the DeskView Browser. The DeskView Browser checks on which PCs the DeskView Agent has been installed and uses it to communicate with the client PCs. The DeskView Browser offers an overview of the PCs in the network and indicates which DeskView components are available on the PCs. To do this, checks are necessary, which may take several minutes for large domains. For the client PCs on which at least DeskView 5.10 is installed, the version of each related DeskView version is displayed. Thus being an administrator you can see on which client PCs DeskView versions even older than 5.10 are installed. With the DeskView Browser you can group the PCs on the network into so-called user-defined domains. You can create these groups temporarily or permanently, independent of the real domain setup. This enables you to arrange PCs in the network individually and simply. For detailed information, see the DeskView Browser online help. In the DeskView Browser, you start the DeskView components that are network-capable on these groups or individual network PCs via the DeskView Browser. If you start a component for a large group of PCs, this procedure might take several minutes. Through the DeskView Browser you also enter the passwords for those PCs on the network for which passwords were assigned with DeskView Agent. These passwords are only important under Windows for Home Use, as under Windows for Business the Windows security concept is used. The DeskView Browser within a DeskView network requires the TCP/IP network protocol. For performance reasons you should not manage more than 100 client PCs with the DeskView Browser. Windows 2000 or Windows XP Professional should be installed on the administrator PC. Otherwise not all PCs of a domain may be checked successfully. Operation Ê Start the DeskView Browser on the administrator PC with Start DeskView or Start Programs DeskView. Ê Select the PCs in the DeskView Browser and start the corresponding DeskView-component for these PCs. DeskView 5.33 Client Management Software 5

Client Management with DeskView Launch integrations In the DeskView Browser, you can use menu item "Call Integrations" to launch integrations that are entered in the DeskView Browser and installed on the PC. For example, Scout el is entered by default in the DeskView Browser. The DeskView Browser checks at each startup whether Scout el is installed on the PC. If Scout el is installed, it is displayed in the "Call Integration" menu and you can start the program from within the browser. Scout el is a program for managing thin clients from a central workstation. These thin clients must have elux as their operating system and be linked into a server-based computing environment. Security concept To gain access to other PCs on the network via the DeskView Browser, the following conditions must be fulfilled depending on the configuration: Access via DeskView Browser in network Windows for Business client with domain registration Windows for Business-Client, not registered in domain Windows for Home Use client The account under which the DeskView Browser is run must be entered in the local administrator group of the client. Domain administrators are normally members of this group. Otherwise, the PC is displayed as locked and cannot be accessed. Access is only possible if the password and user name for the client PC are identical on the client PC and the administrator PC. If a password is set for the client PC (with ADMINPWD or directly on the client PC) and the password protection on the client PC is not deactivated, the DeskView Agent password of the client must be entered in the DeskView Browser. If the password is wrong, the PC is displayed as locked and cannot be accessed. The password on the client PC is not set by default. The password protection can be activated or deactivated on the client PC using the DeskView Agent symbol in the task bar. Also observe the notes provided in the online help for DeskView Browser. 6 DeskView 5.33 Client Management Software

What you must know about DeskView What you must know about DeskView DeskView installation, uninstallation and upgrade You can get the DeskView software from the "Drivers & Utilities" CD in the directory DeskView\Current\Install, from our bulletin board system (+49 821/804-3333, +49 821/814-007, +49 821/814-008, +49 821/829-71) or on the Internet under http://www.fsc-pc.de. To install, uninstall, and upgrade DeskView components use the SETUP533.EXE program. Before calling SETUP533.EXE all open DeskView components should have been closed. You can install DeskView directly on the PC on which you run the program SETUP533.EXE or create a control file for network installation with SETUP533.EXE. As a network administrator you can install, uninstall or update the DeskView components on the client PCs via a login script with this control file (SNISADM.INI) (unattended setup). With this you need not carry out the installation, uninstallation or update on each individual PC. Detailed information can be found in "Network installation of DeskView components by the administrator" chapter. Important note for the installation of DeskView using software distribution systems Always use the DVSETUP.EXE program and the SNISADM.INI control file for software distribution on client PCs in the network. Please do not use any DeskView installations that were recorded with software distribution programs, as the DeskView installation depends on the hardware of the PCs and on the DeskView components already installed. Otherwise, this could lead to incalculable "mixed installations and undefined states. SETUP533.EXE: Access to Windows components SETUP533.EXE accesses the REGEDIT.EXE and REGSVR32.EXE Windows programs. For this purpose the REGEDIT.EXE path must be added to the ambient variable PATH, and REGSVR32.EXE must be located in the Windows System directory. With a default installation of Windows these conditions are met. Installation of an older DeskView Version on top of a newer version If you have installed DeskView, then you cannot install an older version again until you have completely uninstalled ALL installed DeskView components. Should the installation of a lower DeskView version fail, delete the following entry in the Windows registry: HKEY_LOCAL_MACHINE\SOFTWARE\Siemens Nixdorf\DeskView\DeskViewVersion DeskView 5.33 Client Management Software 7

What you must know about DeskView Tips on installation If possible end all other running programs before running SETUP533.EXE. The installation can take some minutes. Do not turn off your PC during the installation and do not reboot. Network drives DeskView may not be installed on a network drive. The entry DeskView\System must be entered before the references to network drives in the environment variable PATH that contains the search path. Check the entries after installing DeskView and if need be after installing any other software, that writes into the PATH environment variable. Installing DeskView on Windows for Business PCs To install DeskView on a PC under Windows for Business, you must be logged on with administrator rights. Installation variants During installation you will be offered the installation variants "Local", "Administrator PC", "Client PC with User Interface" and "Client PC without User Interface". Local no network Select this variant if the PC is not connected to a network or if the administrator should have no access to information or system states of a PC. Administrator in network Select this setup variant if you are a network administrator and want to monitor information, system states, and any changes of these on clients in the network. Client in network with user interface Select this option if a PC is to be accessed both locally and via the network for information and system states. Client in network with user interface Select this type of setup if the PC should be integrated into an enterprise management system (for example SMS or a SNMP based enterprise management system as CA Unicenter) or for example if only the administrator (not the client) should have access to information or system states of a PC. (You must select SMS or SNMP support from an options dialog in the DeskView setup for DeskInfo and DeskAlert.) 8 DeskView 5.33 Client Management Software

What you must know about DeskView It is always only possible to use one installation variant on a PC. If you have selected the installation variant "Client with User Interface" during the initial installation of DeskView, this will automatically be retained for the installation of each additional DeskView component. The only way to change the installation variant is to uninstall DeskView and reinstall it with a different installation variant. DeskView administrator The DeskView administrator PC need not be identical to the administrator PC of the Windows network. For example, you can also install several PCs as DeskView administrator PCs. To be able to use the full functionality of DeskView, install one of the following operating systems on the administrator PC: Microsoft Windows XP Professional Microsoft Windows 2000 Microsoft Windows NT 4.0 DMI 2.0 or WMI/CIM When you install DeskInfo, under Options... you can choose whether you wish to install DMI or WMI instrumentation. Only use DMI or WMI instrumentation without the DeskView interface or DeskView agent On client PCs with local or client installation and without the user interface, you can only install the DMI or WMI instrumentation. You should make this selection, for example if the only DeskView component you use as administrator is DeskInfo and you only want to receive the PC data via DMI or WMI and not via the DeskView network. Ê Ê Ê Select the program DeskInfo in the selection dialog box during the installation of DeskView. Click Options... Select the desired instrumentation DMI or WMI under Instrumentation. DeskView 5.33 Client Management Software 9

What you must know about DeskView Information and tips on DMI and WMI If an older DMI version is already installed If you install DeskInfo with DMI instrumentation, a DMI Service Layer as per DMI 2.0S will be installed with all components. If a DMI installation already exists, older DMI Service Layer files in the Windows System directories will be replaced with new ones. The older files will be copied to the directory...\deskview\dmi\win32\backup. Problems may result in other applications that use DMI when the files are replaced. After uninstalling DeskInfo the directory...\deskview\dmi\win32\backup is retained. DMI files that may be renewed when installing DeskInfo: AUDCAT.DLL, AUDDETL.DLL, DMIAPI32.DLL, GROUPS16.DLL, GROUPS32.DLL, NTEVENT.DLL, WCDMI.DLL, WCDMIDCE.DLL, WDMI2API.DLL, WDMIUTIL.DLL, WIN32SL.EXE, WSAIMON.DLL, WSDMIAUD.DLL, WSDMIDCE.DLL, WSSSP.DLL. DeskInfo/DeskAlert and WMI language version During a DeskAlert or DeskInfo installation with WMI instrumentation, either an already installed, compatible WMI core is used or updated, or a WMI core is automatically installed. DeskView contains one WMI core each in English and German. As a result, a WMI core may be installed in a different language than the operating system. This basically does not affect the operability and is only apparent in the language of the WMI configuration programs. You can avoid this by installing a current WMI core in the desired language prior to the DeskView installation. WMI cores are available from Microsoft. DeskInfo data compatibility with regard to DMI or WMI instrumentation Depending on whether the DMI or WMI instrumentation has been selected during DeskInfo installation, the same date may be displayed with a different format under DeskInfo (but also under SMS and SNMP if SMS/SNMP support has been installed). DeskInfo with DMI instrumentation and "foreign" WMI installation If WMI with a DMI provider is installed separately on a PC with DeskInfo with DMI instrumentation, DeskInfo may access the DMI data of the "foreign" WMI DMI provider. This can cause DeskInfo to display "incorrect" data or if the data are completely incompatible to the DeskInfo DMI instrumentation can cause DeskInfo to abort with the error message "No instrumentation is available on the client PC". Ê or Ê In this case, add the path to the DMI files in the environment variable PATH at the very front (e.g. PATH=C:\Programme\DeskView\DMI\Win32\bin;...) copy the corresponding files from the DeskView directory into the corresponding WMI directory, thus overwriting them. 10 DeskView 5.33 Client Management Software

What you must know about DeskView License number DeskView License Pack If you install DeskView on a Business Line PC, you will be asked to enter a license number during installation. When the control file SNISADM.INI is generated, you are always prompted to enter a license number. If you want to install DeskView on Premium Line PCs only in your network, you can leave the field blank. You can obtain licenses for the DeskView remote functionality from your sales partner. You want to migrate to a different operating system? If you have installed DeskView and want to migrate to a different operating system, please note the following. Migration to Windows XP / Migration from Windows NT 4.0 to Windows 2000 If you are using DeskView and want to migrate from Windows NT 4.0 or Windows 2000 to Windows XP or from Windows NT 4.0 to Windows 2000, proceed as follows. If you update Windows 2000 to Windows XP, i.e., you do not completely reinstall Windows XP, you can use a shortcut (see "Upgrading from Windows 2000 to Windows XP"). Ê Ê Ê Ê Ê Make sure that at least DeskView version 5.10 is installed. Save the user-specific data from DeskInfo and DeskAlert. You can save the configuration for DeskAlert in a file. You can find more information on this procedure in the online help information for DeskAlert. The user-specific DeskInfo data (in the user folder) is dependent on the data instrumentation (DMI or WMI). You can only restore the data if you continue to use the instrumentation. With DMI instrumentation, export the path: HKLM\SOFTWARE\Siemens Nixdorf\DMI\MIF\SNIDESK\CustomerService\Daten from the Windows validation file. With WMI instrumentation, export the path: HKLM\SOFTWARE\Siemens Nixdorf\WMI\UserTab. Uninstall DeskView (only when upgrading to Windows XP). Install Windows XP (new installation or upgrade). If upgrading the operating system fails after uninstallation of DeskView, delete the following entry in the Windows registry: HKEY_LOCAL_MACHINE\SOFTWARE\Siemens Nixdorf\DeskView\DeskViewVersion Install DeskView version 5.10 or a later version. DeskView 5.33 Client Management Software 11

What you must know about DeskView Ê Restore the saved DeskInfo and DeskAlert data. You can find information on loading the configuration for DeskAlert in the online help information for DeskAlert. Import the previously exported path once again into the validation file in order to restore the user-specific DeskInfo data. Have you already migrated to Windows XP without following these instructions? If you have already migrated to Windows XP without following these instructions, then neither the installation path nor the installation mode (Administrator, Client-PC,..) will be available for selection when reinstalling DeskView. If this is the case, delete the validation file entry: HKLM\Software\Siemens Nixdorf\DeskView whenever DeskView has been completely uninstalled. Upgrading from Windows 2000 to Windows XP If DeskView version 5.00 or higher is installed on a Windows 2000 PC and you upgrade this PC to Windows XP, please observe the following: DeskAlert and DeskInfo Ê On PCs on which DeskAlert or DeskInfo is installed, run the program WMIFIX.EXE after upgrading the operating system. WMIFIX.EXE is located, for example, on the "Drivers and Utilities" CD. After upgrading to Windows XP and then again after running WMIFIX.EXE, DeskAlert may incorrectly detect a processor replacement, as the processor data stored in the operating system may change. DeskAlert Alert on LAN Client PC While upgrading to Windows XP, the Platapnp.sys file is requested. Ê Specify the path in which the file is located (on the "Drivers & Utilities" CD in the DeskView\Current\Support directory) and click OK. Ê After upgrading to Windows XP, start NETALRT.REG (on the "Drivers & Utilities" CD in the DeskView directory). Ê Then reboot the system. If the Alert on LAN client PC is not operable following these actions, you must uninstall DeskAlert and then reinstall it. 12 DeskView 5.33 Client Management Software

What you must know about DeskView Earlier DeskView versions Since DeskView version 5.00 the components DeskSeal, DeskOn, DeskWOL Client, PowerSaver and Watchdog are no longer supported. If you have installed one or more of these components using an older version of DeskView, they will automatically be uninstalled during the installation of DeskView version 5.00 or higher. Where can I find additional information? In this manual the individual DeskView components and the network installation and integration in management systems are described in detail. Additional information on all DeskView components can be found in their text and/or Help files, such *.TXT, *.HTML, *.HLP, and *.PDF files. More detailed information about using the individual DeskView components is located in their respective online Help files (*.HLP or Help menu) and in the additional program information (e.g., Info button). Many DeskView functions are dependent on the hardware and software equipment of the PC. Generally only components that satisfy the requirements are available for installation. Please see the Operating Manual or Technical Manual for the PC for a list of the functions your PC supports. DeskView 5.33 Client Management Software 13

DeskView components DeskAlert Brief description With DeskAlert you can have the system state checked regularly automatically according to specified criteria. As a DeskView administrator you check selected client PCs in the network with DeskAlert. With DeskAlert you can set the following: The system conditions that will be monitored on one client PC or a group of client PCs. In what time intervals do the monitoring take place. To which recipients (for example, DeskInfo, EventLog etc.) the system status changes will be sent. Will these system status changes be sent across the network to the administrator PC? Due to a change in the defined system state, an alarm is generated and output on the affected PC and/or on the administrator PC (depending on the configuration). To enable the transmission of these alarms to the DeskView administrator PC via the network, at least DeskView 4.00 should be installed on the client PCs. The latest DeskView version should always be installed on the administrator PC, however at least the version that is also installed on the client PCs. Conditions in a network with Windows for Home Use Client-PCs and Windows for Business administrator PC The following conditions must be fulfilled in a network with Windows for Home Use client PCs and a Windows for Business administrator PC. DeskAlert (without Alert on LAN) So that communication between a Windows for Business administrator PC and Windows for Home Use client PCs registered in a Windows Workgroup functions properly, the guest account on the administrator PC must be activated, (the setting Deactivate account in the user properties of guest must be deactivated). DeskView 5.33 Client Management Software 14

DeskAlert DeskView components Under Windows NT the setting can be found at Start Programs Administration (General) User Manager. Ê Double-click on Guest and select the setting. Under Windows 2000/Windows XP, click with the right mouse button on My computer and select Administer. Ê Under Administration click on local Users and Groups, then on Users. Ê Right-click on Guest and select Properties. Ê Deactivate the field Disable Account. DeskAlert with Alert on LAN/ASF So that the Alert on LAN/ASF communication between a Windows for Business administrator PC and Windows for Home Use client PCs functions properly, the Windows for Home Use client PCs must be registered on a domain. Client PCs with Windows XP Home Edition cannot be registered on a domain. Calling from the command line Display of the DeskAlert interface DACONFIG.EXE [\\<client>][/i: <file.cfg>] Load the saved configuration for a PC without DeskAlert interface DACONFIG.EXE [\\<client>] /S [/I: <file.cfg>] Parameters /H or /? Indicates the syntax. /I: <file.cfg> Specifies the import file. The configuration saved in the import file is transferred to the PC for which you start DeskAlert with this parameter. /S Starts DAConfig without graphic interface (batch mode). The parameter /S is permissible only in connection with the parameter /I: <file.cfg>. DeskView 5.33 Client Management Software 15

DeskView components DeskAlert Variables \\<client> /I: <file.cfg> Name of the PC for which DAConfig is started. The default is the PC on which DeskAlert is started. Specifies the import file. The configuration stored in the import file is transferred to the PC for which you start DeskAlert with this parameter. Return values DACONFIG.EXE provides the following feedback values that you can request via ERRORLEVEL. 0 DACONFIG.EXE was run without errors. 1 Unknown error. 2 Client PC or WMI service of client PC is currently not available. 3 Access to client PC impossible. 4 Timeout after mail to the client PC. 5 AOL/ASF Agent: Access to client PC impossible. 6 DeskAlert is started already for this PC. 7 DeskAlert is installed without user interface and must be started with the parameter /S. 8 Reserved 9 Reserved 10 Invalid import file or import file not found. 11 Reserved 12 Syntax error 13 DeskAlert must not be started at the moment, e.g. because the DeskView setup is running. 14 DeskAlert is already opened for this PC or this domain. 15 DeskAlert is already opened in another session (only under Windows XP with "fast user switching"). 16 Temporary file cannot be saved, e.g. because of insufficient memory or missing write access permissions. 16 DeskView 5.33 Client Management Software

DeskFlash DeskView components Troubleshooting and tips Error message "Client PC or the WMI service of the client is currently not available" When DeskAlert is started very quickly after the operating system is booted, an error message may be output. This behavior can also occur with integrations when DeskAlert is started (for example from the SMS administrator console or the CA Unicenter Manager). Ê Try again after a few seconds. DeskFlash Brief description DeskFlash offers the following functions: Update the BIOS Update BIOS settings Archive the BIOS and BIOS settings Update installed processor microcode patches With DeskFlash, you can update and archive the BIOS under Windows. DeskFlash supports the file formats OMF, OCF, and BUP for BIOS files. To run DeskFlash under Windows NT, Windows 2000, Windows XP Professional and Windows XP Home Edition, you need to have administrator privileges. Calling from the command line Viewing command line parameters DskFlash /h /help Displays the command line parameters. Updating the BIOS DskFlash /upd [/wd=<dir>] [/o=<dospat> /o=<file>] [/s [/w]] [/lf[=<logfile>]] [/ov] [/arb] [/frb] The changes to the BIOS are enabled after the next system startup. DeskView 5.33 Client Management Software 17

DeskView components DeskFlash Updating BIOS settings DskFlash /nvu [/wd=<dir>] [/o=<dospat> /o=<file>] [/s [/w]] [/lf[=<logfile>]] [/frb] [/arb] [/afu] The changes to the BIOS settings are enabled after the next system startup. Archiving the BIOS and BIOS settings DskFlash /ar [/wd=<dir>] [/o=<pattern> /o=<file>] [/s [/w]] [/lf[=<logfile>]] [/ov] Updating installed processor microcode patches DskFlash /mcu /s [/w] [/wd=<dir>] [/lf[=<logfile>]] [/arb] [/frb] The changes to the BIOS are enabled after the next system startup. Parameters /afu, /allowfullupdate /ar, /archive /arb, /allowreboot /frb, /forcereboot /h, /help /lf[=],/logfile[=], /mcu, /microcodeupdate /nvu, /nvramupdate /o= /ov, /overwrite /s, /silent /upd, /update /w, /warningoff /wd=, If the BIOS versions of the target system and the update file(s) are not the same, a complete BIOS update is performed during update of the BIOS settings. Archives the BIOS including BIOS settings. The DeskFlash kernel can reboot the system if required. Forces a system reboot after the action is completed. Displays the command line parameters. Creates a log file in the working directory, with optional specification of the file name. Updates the processor microcode patches. Updates the BIOS settings. The BIOS versions of the target system and the update file(s) must be the same. File name of the archive. The BIOS may also be overwritten even though a newer version may not be available. Dialog is not displayed. The warning dialog is displayed instead. Updates the BIOS, the BIOS settings and the processor microcode patches. Disables the warning dialog if /s was specified. Specifies the working directory. If the parameter is not specified, the current working 18 DeskView 5.33 Client Management Software

DeskFlash DeskView components /workingdirectory= directory is selected. Variables <dir> <file> <logfile> <pattern> <dospat> The directory name conforms to the DOS naming conventions (e. g. C:\BIOS) or takes a UNC name (e. g. \\Server\BIOS). Name of the file for archiving or updating. Name of the log file. Specify a pattern for the name under which the archive files are stored. You can use the following variables: #domain# = System domain #name# = Computer name #system# = System board (mainboard) #date# = Current date #time# = Current time in the format HHMMSS #no# = Automatically generated serial number You can mix fixed name components and variables, e. g. MyArch_#system#_#date#.bup File name with placeholder (e. g. D1332*.bup). DeskView 5.33 Client Management Software 19

DeskView components DeskFlash Administration Return values DSKFLASH.EXE provides the following return values that you can request via ERRORLEVEL. 0 DSKFLASH.EXE was run without errors. 1 The action has been completed, but the log file contains warnings. 2 General error. 4 Syntax error, incorrect parameters on callup. 8 On one or more target systems, the temporary directory is either missing or does not have enough free space. 16 On the administrator system, the temporary directory is either missing or does not have enough free space. 32 The target system cannot be reached. 64 On one or more target systems, there is no valid file available for updating the BIOS. 128 Insufficient disk space. 256 Mandatory settings are not defined (e. g. Allow reboot). There may be a combination of error levels. The resulting error level consists of a bitwise addition of the single error levels. DeskFlash Administration Brief description DeskFlash Administration provides you with the following functions in the network as administrator: Query BIOS information Archive the BIOS including BIOS settings Check the BIOS update file(s) Update the BIOS Update BIOS settings Update processor microcodes Update the index file Convert OMF and OCF files into BUP files 20 DeskView 5.33 Client Management Software

DeskFlash Administration DeskView components To have the same BIOS with uniform settings on all systems in the network, you can, for example, archive a BIOS together with all BIOS setup settings and then distribute it to all systems in the network. To run DeskFlash Administration under Windows NT, Windows 2000, Windows XP Professional and Windows XP Home Edition, you need to have administrator privileges. Calling from the command line Viewing command line parameters DfAdmin /h /help Displays the command line parameters. Starting DeskFlash Administration with the program interface, for a system or a domain DfAdmin <sysdomname> Querying BIOS information DfAdmin /qsi [/target=<sysdomname>] [/s /lf[=<logfile>]] [/lf[=<logfile>]] Archiving the BIOS and BIOS settings DfAdmin /ar [/target=<sysdomname>] [/wd=<dir>] [/o=<pattern> /o=<file>] [/s [/w]] [/lf[=<logfile>]] Checking the BIOS update file(s) DfAdmin /chk [/target=<sysdomname>] [/wd=<dir>] [/o=<file>] [/lf[=<logfile>]] Updating the BIOS DfAdmin /upd [/target=<sysdomname>] [/wd=<dir>] [/o=<file>] [/s [/w]] [/lf[=<logfile>]] [/ov] [/arb] [/frb] The changes to the BIOS are enabled after the next system startup. Updating BIOS settings DfAdmin /nvu [/target=<sysdomname>] [/wd=<dir>] [/o=<file>] [/s [/w]] [/lf[=<logfile>]] [/frb] [/arb] [/afu] The changes to the BIOS settings are enanbled after the next system startup. DeskView 5.33 Client Management Software 21

DeskView components DeskFlash Administration Updating processor microcodes DfAdmin /mcu [/target=<sysdomname>] [/wd=<dir>] [/s [/w]] [/lf[=<logfile>]] [/arb] [/frb] The changes to the BIOS are enabled after the next system startup. Updating the index file DfAdmin /indexupdate [/wd=<dir>] Converting OMF and OCF files into BUP files DfAdmin /omfocf2bup [/wd=<dir>] Parameters /afu, /allowfullupdate /ar, /archive /arb, /allowreboot /chk, /checkforupdate /frb, /forcereboot /h, /help /indexupdate /lf[=],/logfile[=] /mcu, /microcodeupdate /nvu, /nvramupdate /o= If the BIOS version of the target system and the update file(s) are not the same, a complete BIOS update is performed during update of the BIOS settings. Archives the BIOS including BIOS settings. DeskFlash Administration reboots the system if required. Checks the file for usability to update the BIOS. If a directory is specified, all *.BUP files it contains are checked. Forces a system reboot after the action is completed. Displays the command line parameters. Creates an index file "index.bup" from the BUP files in the specified directory. Before creating an index file, you can convert OMF and OCF files into BUP files with the parameter /omfocf2bup so that they are also included. We recommend creating an index file if you want to update a number of client systems individually with files from one directory. When you create the index file, this disables the internal indexing by DfAdmin. After the update, you must therefore either delete the index file to re-enable the internal indexing or update the index file if you delete files or copy new files to the directory. Creates a log file in the working directory, with optional specification of the file name. Updates the processor microcodes. Updates the BIOS settings. The BIOS version of the target system and the update file(s) must be the same. File name of the archive. 22 DeskView 5.33 Client Management Software

DeskFlash Administration DeskView components /omfocf2bup /ov, /overwrite /qsi /s, /silent /target= /upd, /update /w, /warningoff /wd=, /workingdirectory= Converts the OMF and OCF files in the working directory into BUP files. The BIOS may be overwritten even though a newer version may not be available respectively an existing archive file may be overwritten. Queries the system information. Dialog is not displayed on the administrator system. Specifies the target system or the domain known by DvProxy. If the parameter is not specified, the local system is assumed as the target system. Updates the BIOS, the BIOS settings and the processor microcodes. Disables the warning dialog on the target system. Specifies the working directory. If the parameter is not specified, the current working directory is selected. Variables <dir> <file> <logfile> <pattern> <sysdomname> The directory name conforms to the DOS naming conventions (e. g. C:\BIOS) or takes a UNC name (e. g. \\Server\BIOS). Name of the file for archiving or updating. Name of the log file. Specify a pattern for the name under which the archive files are stored here. You can use the following variables for this: #domain# = System domain #name# = Computer name #system# = System board (mainboard) #date# = Current date #time# = Current time in the format HHMMSS #no# = Automatically generated serial number You can mix fixed name components and variables, e. g. MyArch_#system#_#date#.bup System name (begins with \\) or domain name of the temporary or user-defined domain known by DvProxy. DeskView 5.33 Client Management Software 23

DeskView components DeskInfo Return values DFADMIN.EXE provides the following return values that you can request via ERRORLEVEL. 0 DFADMIN.EXE was run without errors. 1 The action has been completed, but the log file contains warnings. 2 General error. 4 Syntax error, incorrect parameters on callup. 8 On one or more target systems, the temporary directory is either missing or does not have enough free space. 16 On the administrator system, the temporary directory is either missing or does not have enough free space. 32 One or more target systems cannot be reached. 64 On one or more target systems, there is no valid file available for updating the BIOS. 128 Insufficient diskspace. 256 Mandatory settings are not defined (e. g. Allow reboot). There may be a combination of error levels. The resulting error level consists of a bitwise addition of the single error levels. DeskInfo Brief description DeskInfo lets you detect PC-related information and display it on the screen, save it in a file or print it. Available information includes: General information like PC type, system name, video card, serial number, and system equipment. Technical information like hard disk installed, amount of RAM, RAM usage, processor, system board, local and network drives, peripherals. Service and dealer information. Integration in the network. User-defined information like inventory number or system location. 24 DeskView 5.33 Client Management Software

DeskInfo DeskView components Calling from the command line Display of the DeskInfo interface DESKINFO.EXE [/d] [/s] [\\<client pc>] [/csva] [/csvopt <xxx>] Creating a log file *.log in INI format without DeskInfo interface DESKINFO.EXE /b [<path>\ <path>\<file>.log <file>.log] [/s] [\\<client pc>] Creating a log file *.log and a log file *.csv in Excel or Access format without DeskInfo interface DESKINFO.EXE /csv [<path>\[<file>.log]] [/csvopt <xxx>] [/csva] [/s] [\\<client pc>] or DESKINFO.EXE <path>\[<file>.log] [/csvopt <xxx>] [/csva] [/s] [\\<client pc>] or DESKINFO.EXE <file>.log [/csvopt <xxx>] [/csva [/s] [\\<client pc>] DeskInfo is always started without a user interface, when one of the following parameters has been specified: /b, /csv, <path>\ or <file>.log. Parameters /b DeskInfo creates a log file *.LOG in the INI file format. /csv Creates two log files: *.LOG contains the DeskInfo data in INI file format, *.CSV contains the DeskInfo data in CSV format. The DeskInfo data includes the computer name, the name of the tab in the DeskInfo interface, the field and the value. /csva The DeskInfo data in the *.CSV file are saved in Access format i.e. separated by semicolons. When displaying the DeskInfo interface, this parameter causes the *.CSV log file to be stored in Access format, as soon as a *.CSV log file is created in the DeskInfo interface. /csve Causes the DeskInfo data to be saved in the *.CSV log file in Excel format separated by commas. As this is the default setting, the parameter is unnecessary. /csvopt <xxx> /csvopt replaces the computer name entered in the log file with the specified text <xxx>. There must be at least one space between /csvopt and <xxx>. If there are blanks in the specified text, it must be placed in inverted commas. DeskView 5.33 Client Management Software 25

DeskView components DeskInfo /d Collects the DeskInfo data during the start-up of DeskInfo (precollect mode), and not when the tab is opened. /s Prevents displaying the DeskView logo before the desired action. Variables \\<client pc> <file>.log <path>\ The client PC (PC name or IP address) for which DeskInfo is to be started or for which a log file is to be created. If no client PC is specified, the DeskInfo call will apply to the local PC. Name of the log file *.LOG. The *.CSV file is created under the same name as the *.LOG file. Default file name is DI_<pcname>.LOG or DI_<pcname>.CSV. Specifies which directory the log file(s) are to be stored in. Default setting is the directory currently active. The path must already exist. Tip For the administrator to collect the data of all client PCs in the network, the call in the login file being started for all client PCs when the system boots could look as follows: DESKINFO.EXE \\ADMINPC\LOGFILES\ /csv /csva /s The directory must already have been created and the client PCs must have write access permissions to this directory. DeskInfo is started without a user interface. The *.LOG and *.CSV log files are saved on the ADMINPC in the LOGFILES directory with the corresponding client PC name in the file name (DI_<pcname>.LOG or DI_<pcname>.CSV). The *.CSV log files can be imported into an Access database. Return values DESKINFO.EXE provides the following return values that you can request via ERRORLEVEL. 0 DESKINFO.EXE was run without errors. 1 DeskInfo is already running on the PC and cannot be run twice. 2 Insufficient memory 3 The RICHED32.DLL library file could not be loaded. 4 Syntax error: The /b and /csv parameters must not be used together. 5 Syntax error: Several PC names have been specified. 26 DeskView 5.33 Client Management Software

DeskInfo DeskView components 6 Syntax error: Unexpected command line parameter, e.g. unknown parameter or parameters entered without spaces next to each other ("/d/s"). 7 DeskInfo has been installed without a user interface. Only the parameters for creating a protocol file without DeskInfo interface should be used. 8 Reserved 9 Syntax error: /csve and /csva must not be used together. 10 Syntax error: Error in the file name. 11 The log file could not be created, e.g. because of insufficient memory or missing write access permissions or because the directory does not exist. 12 Syntax error: An option for a parameter is missing, e.g. /csvopt without specifying <xxx>. 13 DeskInfo must not be started at the moment, e.g. because the DeskView Setup is running. 14 Syntax error: Several log files have been specified. 15 Reserved 16 There is no instrumentation on the client PC. 17 The instrumentation is being used. Try again later. 18 Incorrect DMI Agent version. 19 Access to the client PC has been refused. 20 The DeskView Agent has been stopped. 21 DeskView Agent: invalid parameter. 22 Agent: insufficient memory. 23 Unknown request 24 Unknown object Troubleshooting and tips If you change from DMI to WMI support or vice versa when reinstalling DeskInfo, user-defined information such as inventory number or system location will be lost. DeskView 5.33 Client Management Software 27

DeskView components DeskOff and DeskOff Admin DeskOff and DeskOff Admin Brief description With DeskOff you can switch the PC or the operating system on a PC into different operating modes. If supported by the PC, the following modes are possible: Switch off the PC Shutdown the operating system Reboot the PC Switch into the energy-saving mode (Standby) Switch into hibernate mode under Windows 2000 and Windows XP only Log off the user PCs with the operating system Windows NT 4.0 can also be shut down with DeskOff. Switching to different modes is only possible when no running application prevents Windows from being exited (see parameter /i). DeskOff Admin DeskOff Admin allows you to access the local DeskOff of a client PC via the DeskView network. It is required that on the client PC DeskOff is installed with the DeskView version 5.21 or superior. DeskOff Admin allows you to configure and activate the local DeskOff of the client PC and thus perform the DeskOff actions on the client PC that are supported by the client PC. DeskOff Admin thereby supports all DeskOff actions apart from logoff and shutdown. With DeskOff Admin you can access only to one client PC, you cannot start DeskOff Admin for a group of client PCs. DeskOff states As long as you have not yet terminated the settings in DeskOff or DeskOff Admin with Run, DeskOff will be available e.g. in the quick start toolbar but will not be activated. DeskOff can be considered as being activated only when you click on the command button Run and time is running. You realize the state is active when the DeskOff icon is blinking in the quick start toolbar. Clicking on the command button Apply only saves your settings, DeskOff will not be activated. DeskOff under Windows 2000 After adjusting the time zone under Windows 2000 you have to close DeskOff completely (in the task bar as well) and then restart. 28 DeskView 5.33 Client Management Software

DeskOff and DeskOff Admin DeskView components Calling from the command line DeskOff Start DeskOff action DESKOFF.EXE /hib /sby /sd /l /r /t<sek> /t<hh:mm:ss> [/s] [/pmd] [/i] Stop started DeskOff action DESKOFF.EXE /stop [/s] Output call syntax and program parameters DESKOFF.EXE /h /? Start DeskOff in the Windows fast start bar DESKOFF.EXE /tna DeskOff Admin Start DeskOff admin action DESKOFFADMIN.EXE /hib /sby /sd /r /t<sek> /t<hh:mm:ss> [/s] [/pmd] [/i] [/warntime<sek>] [\\<pc-name> \\<ip-address>] Stop started DeskOff admin action DESKOFFADMIN.EXE /stop [\\<pc-name> \\<ip-address>] [/s] Output call syntax and program parameters DESKOFFADMIN.EXE /h /? DeskView 5.33 Client Management Software 29

DeskView components DeskOff and DeskOff Admin Parameters /? Displays the callup syntax and the program parameters. /h Displays the callup syntax and the program parameters. /hib The PC is switched into the Hibernation mode. /i The selected action is forced. All open applications are closed without data being saved. Data may be lost! /l The user is logged off the system (Logoff). The parameter is only valid for the local DeskOff (DESKOFF.EXE). /pmd Ignores system energy-saving modes as long as DeskOff is active. While your system is in the energy-saving mode, the set DeskOff action is not carried out. If you set the parameter /pmd, the set DeskOff action will always be carried out. As long as DeskOff is active, set system energy-saving modes are ignored, and the system does not switch into the energy-saving mode. /r The PC is rebooted instead of shut off. /s Automatic execution of actions without the user interface (Silent Execution). If the specified action (/hib Hibernate, /sby Standby, /sd Shutdown, /r Reboot, /l Logoff) is to be carried out without user interface, the parameter /s (Silent Execution), must be entered in the command line. /sby /sd /stop /t<hh:mm:ss> /tna /t<sek> /warntime<sec> If the parameter /s is not specified, the specified command line parameters will be adopted in the DeskOff interface, but the action you want will not be carried out yet. Execution then may take place via the DeskOff user interface. The PC is switched into the Standby mode. The user is logged off the system and the PC is shut down. Stops an active DeskOff process, i.e. a started DeskOff action is not executed. The selected action is carried out at the time entered. Valid maximum values are "23" for hh, "59" for mm and "59" for ss. If you specify an invalid time, the action is not executed. Starts DeskOff in the quick start toolbar The selected action is carried out after <sec> seconds The maximum value is 86399 seconds. If you specify a higher value, the maximum value is taken automatically. Specifies how many seconds before performing the action a warning is to be output on the PC. 30 DeskView 5.33 Client Management Software

DeskSettings DeskView components Return values of DeskOff Admin DESKOFFADMIN.EXE provides the following return values that you can request via ERRORLEVEL. 0 DESKOFFADMIN.EXE was run without errors. 1 Unknown error 2 DeskOff Admin may only be started for one client PC. 3 Wrong PC name or the PC is not available. 4 Communication error: network error or the PC is not available. 5 The client PC does not support DeskOff. 6 The client PC has been configured incorrectly. 7 The action is not supported. 8 Incorrect parameters in the command line. 9 No action or time is indicated. Example DESKOFFADMIN /sd /t120 /s /warntime30 \\192.168.10.4 The system with IP address 192.168.10.4 will be switched off in 120 seconds. A warning is output on the system concerned 30 seconds before switchoff. DeskSettings Brief description DeskSettings enables you to make BIOS setup adjustments under Windows both for the local PC and via the network. The condition for this is that the system board and the BIOS support this function. Via DeskSettings it is not possible to access PCs with a BIOS Setup which is SmartCard-protected. SmartCardprotected means that the access check on the BIOS-Setup is carried out by a correspondingly coded chip card (SmartCard). DeskView 5.33 Client Management Software 31

DeskView components DeskSettings Calling from the command line DeskSettings enables BIOS Setup settings on the PC to be distributed in the network without additional user entries (Silent mode). To do this, a *.DSM control file which contains all necessary information is required. This control file is created with DeskSettings. Information on the content and on creating the control file is contained in the DeskSettings online help. DESKSET.EXE <client pc> DESKSET.EXE [/C <client pc>] [/P <protocol> /M <file.mif>/s <file.dsm>] All relative paths begin in the...\desksettings\usrdata directory. Parameters /C <client pc> Name or TCP/IP address of the client PC or name of the network created in DeskView Browser to which DeskSettings is to establish a connection. The TCP/IP address or the client PC name must be preceded by a double backslash (\\) (example: /c \\141.29.76.162). If you do not specify any additional parameters, you only need to specify <client pc> (without /C). If the parameter /C <client pc> is missing, DeskSettings automatically connects to the local PC. /S <file.dsm> <file.dsm> specifies the name of the control file. Without the parameter /S DeskSettings is started with the user interface. /P <protocol> <protocol> specifies the path and the name for the protocol files. The parameter /P without further specification creates the following three protocol files in the directory...\deskset\usrdata\ on the administrator PC: - The DeskSet.log$ file is only used to verify the path and is always empty. This file must always be deleted via the command line before calling up DeskSettings (see supplied example silent.bat file). - The DeskSet.log1 file is created as soon as DeskSettings has been run through error-free. This file contains the date of the successful update. - The DeskSet.log file is only stored when an error has occurred. The last actions are stored in the DeskSet.Log file with the date and comments. A directory you specify and a name for the log file are treated in the same way. /M <file.mif> With this option DeskSettings stores the result in the specified *.MIF file. The file is given the standard name DeskSet.Mif. DeskSettings takes the path for the file from the system entries of the SMS installation. 32 DeskView 5.33 Client Management Software

DeskWOL Admin Wake On LAN DeskView components Integrating in batch file DeskView network The SILENT.BAT file is supplied with DeskSettings. This file can be used as an example of how to integrate the command line in a batch file. To run the file SILENT.BAT automatically, enter it in the PC s login script in the client PC s Windows Registry. SMS The SILMIF.BAT file is supplied with DeskSettings. This file is an example of how the command line can be started in a batch file in an SMS network. If you as an SMS administrator are not sure which directory on the client PC DeskSettings is installed in, use the program DSETSM.EXE. This searches the PC for DeskSettings and starts it. DeskWOL Admin Wake On LAN Brief description DeskWOL Admin enables a PC to be switched on via the network with Wake on LAN technology. DeskWOL Admin allows you to turn on one or more PCs from an administrator workstation with a command to the LAN adapter (magic packet). If corresponding client management services are installed on the client PCs, procedures and programs can be carried out automatically via LAN after the client PCs are switched on. If a client PC is to be shut down again automatically, you can use DeskOff for this purpose. Run WOLADMIN.EXE to save the parameters relevant for "Wake on LAN" (e.g. MAC address) of the PCs to be "woken up" in a *.INI file. The information in the *.INI file conforms to the Windows standard and can therefore be edited with a text editor. With the program GETMAC.EXE you can search a specified domain for LAN adapter addresses and save these in the specified *.INI file. The programs WOLADMIN.EXE and GETMAC.EXE can be run in the dialog mode or in command line mode. The description of the command line call, the format of the *.INI file and an example of an *.INI file are contained in the DeskWOL Admin online help. DeskView 5.33 Client Management Software 33

DeskView components DeskWOL Admin Wake On LAN Requirements for client PCs Wake on LAN-ready system board with integrated network controller (LAN) or a Wake on LAN-capable network card that has been wired accordingly to the system board. In the BIOS Setup the corresponding entries for Wake on LAN must be set. The settings are dependent on the BIOS Setup. Example: In the BIOS Setup, the entry LAN under Power On Source must be set to Enabled. If the screen is to be switched on, in the BIOS Setup the Monitor entry under Advanced Power On/Off LAN Wakeup Mode, must be set to ON. If the PC is to be started through an onboard LAN controller, the fields LAN-Controller and Wake on LAN in the BIOS Setup s Peripheral Configuration menu must be set to Enabled. Only a single network controller per PC can be enabled for Wake on LAN. Since each LAN controller consumes power in standby mode but the PC s cooling fan is not running, overheating in the PC is possible. So that the PC can also be started after switch-on, start-up must be possible without user entries (no system password assigned and no chip card security software installed!). Under "ACPI-enabled" special conditions with regard to switch-on via Wake On LAN apply to PCs and operating systems. Under certain circumstances it may not be possible to switch on a system from the ACPI state "OFF" (SoftOff) via Wake On LAN. Whether the system can be woken up from one of the ACPI rest states via Wake On LAN is dependent on the BIOS, on the settings in the BIOS Setup and on the power management configuration of the operating system. Calling from the command line By starting the WOLADMIN.EXE program from the command line, you can automatically wake up all PCs that have a listing in the *.INI file. Syntax WOLADMIN.EXE <file>.ini /WAKEALL [/T <Pause>] [/L <protocol file>] Parameters <file>.ini /L <protocol file> Filename of the Windows-standard *.INI file that contains all PCs to be woken up. See section "*.INI File Format". All actions and any errors are recorded in the named log file. 34 DeskView 5.33 Client Management Software

DeskWOL Admin Wake On LAN DeskView components /T <pause> Pause (0 to 99 sec) between the wake-up commands to the PCs. /WAKEALL Wakes up all PCs that are listed in the *.INI file. *.INI File Format The PCs and their parameters that Wake on LAN" needs (most importantly the MAC address) are stored in a Windows-standard *.INI file. Each computer is defined in a separate section with its name. The information in the *.INI file conforms to the Windows standard and can therefore be edited and modified with a text editor. *.INI file example [Client1PC] MacAddr = a0b1c2d3e4f5 IpAddr = BroadCAddr = BooP = 0 [Client2PC] MacAddr = 001020304050 IpAddr = 100.10.100.10 BroadCAddr = 100.10.255.255 BooP = 1 Entries in the *.INI file For each PC the following information can be entered: PC-Name, MacAddr, and BootP are required entries. [PC name] MacAddr IpAddr Logical name of the (client) PC to be woken up (15 characters max.). The name should be the same as the PC s network name. The name serves only to identify and select the PC. It is not used for network addressing. Physical Media Access Control ("Ethernet") address of the network interface card in the PC to be woken up (12-character hexadecimal address). Internet address of the PC to be woken up. You can set this parameter, if the wake-up packet shall be sent as BOOTP request packet. The program itself does not evaluate this parameter. DeskView 5.33 Client Management Software 35

DeskView components DeskWOL Admin Wake On LAN However, if it is specified, it will be entered in the wake-up packet to create a formally valid BOOTP request packet (see parameter BootP). BroadCAddr BootP IP address where the wake-up packet ("Magic Packet") is to be sent. This may be a unicast or a subnet broadcast address. When not supplied, the limited broadcast address (255.255.255.255) is used. When a DHCP/BOOTP relay is used to forward the wake-up frame then this should be the address of the DHCP/BOOTP relay on the subnet where the client is located (not a broadcast address). Indicates whether the wake-up packet is to be transmitted as a BootP (bootstrap protocol) reply packet (BootP = 1) or not (BootP = 0). The default is BootP = 0; in this case the packet will be send to UDP port 9 (discard). If the wake-up packet is to be transmitted as a BootP (bootstrap protocol) reply packet, the destination address must be defined (see entry BroadCAddr). This option strongly depends on the configuration of the IP routers in the network. Examples: BootP = 0: The Router is configured to pass subnet broadcasts". The BroadCAddr must be provided with the subnet broadcast address of the target network (e.g. 192.168.2.255). BootP = 1: The router is configured to pass DHCP and BOOTP (subnet) broadcast packets or a DHCP/BOOTP relay is active on the router. In the latter case the IP address of the DHCP relay must be provided as the BroadCAddr (see above). In V1.51 the entry NetMask was changed to BroadCMask and also the order with entry IpAddr was changed. In V1.52 the entry BroadCMask was changed to BroadCAddr. It is not necessary to re-format old *.INI files. The program is able to process old *.INI files, too. 36 DeskView 5.33 Client Management Software

Network installation of DeskView components by the administrator As an administrator of a network you can install, uninstall or update the DeskView components on the client PCs via a login script (unattended setup). When using Unattended Setup all screen displays on the client PC are deactivated during installation (Silent Installation) in the default setting. Installation procedure For installation, uninstallation or updating via Unattended Setup, you require a login script for the client PCs. In this login script either a batch file is processed that runs the installation program DVSETUP.EXE or the installation program DVSETUP.EXE is started directly from the login script. The installation program DVSETUP.EXE requires a control file SNISADM.INI, which contains installation options. This control file SNISADM.INI is created using DeskView Setup SETUP533.EXE. Brief overview of installation procedure Ê Ê Ê Create a control file SNISADM.INI using the SETUP533.EXE program. For Windows for Home Use client PCs you run the admin password utility and assign passwords which are then entered in the control file SNISADM.INI. Provide the installation files for the client PCs on an enabled drive. Ê Create a login script for each client PC or adapt an existing login script. The installation program DVSETUP.EXE must either be run directly from the login script, or a batch file that starts the installation program. Feedback on the installation is provided via the feedback values (ERRORLEVEL) of the installation program and via the event file. The event file is created when the corresponding option is entered in the control file SNISADM.INI. Create SNISADM.INI control file Ê Start DeskView Setup SETUP533.EXE and carry out the installation selection Create control file SNISADM.INI for network installation. Ê Follow the instructions on the screen and observe the information in the online help of the DeskView Setup. All options selected in the DeskView Setup dialog are then applied in the control file SNISADM.INI. You will be asked for the license number. On some PCs the full range of DeskView functions will not be available without a license number (e.g. no network capability). If you have purchased a DeskView License Pack", please enter the license number. DeskView 5.33 Client Management Software 37

Network installation of DeskView components by the administrator Installation procedure Result file If you have specified that a result file is to be created in the Installation options dialog box during the installation of DeskView (SETUP533.EXE), a result file will be created for each client PC. In this way you can quickly check for which PCs the installation has run successfully and where errors have occurred. To simplify evaluation, we recommend saving the event files in a directory on the server. The drive must be assigned under the same drive letter for all client PCs. Tips on the event file and the entries and related explanations are contained in the Appendix of this manual. Admin Password Utility In a DeskView network, protect each Windows for Home Use client PC with a password against unauthorized access. This password must be entered when the client PC is to be accessed via the DeskView Browser. As an administrator you can assign passwords for client PCs with the program Admin Password Utility (ADMINPWD.EXE). These passwords are entered encoded in the selected control file SNISADM.INI. With the Unattended Setup these passwords are then made known to the DeskView Agent of the client PCs. DeskView Admin Password Utility is also automatically installed with the DeskView Setup installation variant Administrator in network. A description of the program and information on its operation are contained in the online help for DeskView Admin Password Utility. Ê We recommend assigning the same password to client PCs that are selected together in the DeskView Browser (for example, when they are in one group). When working with these PCs, you then have to enter the password only once for the entire group. If you carry out the installation for Windows for Home Use client PCs, you should assign passwords. To do this, run the Admin Password Utility and assign the passwords for the control file SNISADM.INI just created. Tip for password assignment If DeskView is already installed on the administrator PC, you can conveniently assign the passwords for the client PCs in the DeskView Browser and then apply them in the control file SNISADM.INI with the Admin Password Utility. 38 DeskView 5.33 Client Management Software

Installation procedure Network installation of DeskView components by the administrator Make installation files available for client PCs Ê Copy the entire directory DESKVIEW with all subdirectories from the CD to a directory on the administrator PC that is enabled for reading access of the client PCs. Ê Make sure that the control file SNISADM.INI is located in a directory to which the client PCs have read access. These drives must be available for a sufficient time so that the software can be installed on PCs that have not been started for a long time. Leave the drives enables until you are sure that all client PCs are completely installed. Ê If you have specified a directory for the event file on a network PC such as an administrator PC or server in the control file SNISADM.INI, make sure that the client PCs have write access to this directory. Login script with running of installation program The installation program DVSETUP.EXE must be run from the login script of the client PCs either directly or via a batch file. Ê Create a login script for all client PCs on which the installation is to be carried out or adapt an existing login script accordingly. Executing login script for client PCs in a workgroup With a client PC in workgroup you create an entry in the Windows registry under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run or RunOnce that runs the login script. Executing login script for client PCs in a domain On a PC in a domain you specify on the administrator PC that a login script is automatically executed during the login of the client PC. Information on this is, for example, contained in the Microsoft Windows NT Server Manual. DeskView 5.33 Client Management Software 39

Network installation of DeskView components by the administrator Installation procedure Running installation program The installation program DVSETUP.EXE installs the components as specified in the control file SNISADM.INI. To run the installation program you can use the sample file DVLogin.bat or write your own batch file or also you can also run the installation program and the parameter directly in the login script. The following parameters are required for the installation program DVSETUP.EXE: /S or /Script /Path=<path for SNISADM.INI> Silent mode installation without user entries Note: For an installation or uninstallation in the Silent mode, the parameter /S must be specified. Pure path of the SNISADM.INI file (without concluding backslash (\) and without the file name SNISADM.INI) This parameter must be listed last, however can be eliminated if the file SNISADM.INI is located in the same directory as DVSETUP.EXE. DVSETUP.EXE provides the following feedback values that can be requested via ERRORLEVEL. 0 DVSETUP.EXE was run without errors. Please check whether all DeskView components have been properly installed, uninstalled or updated in the process in the event file. The creation of the event file is an option in the control file SNISADM.INI. 1 The control file SNISADM.INI was not found. Check the parameter /Path=<Path for SNISADM.INI> 2 The DVSETUP.INI file could not be found This file must be located in the same directory as DVSETUP.EXE. 3 Syntax error (incorrect parameter) 4 Internal error 5 DeskView is already installed in a version of another manufacturer. You must uninstall this version first. 6 The necessary administrator rights are missing. 7 ServerView is installed. To integrate DeskView in ServerView, please read the documentation on ServerView. 8 Restart the PC and carry out the installation again. 9 A required restart could not be carried out. Reboot the PC before starting DeskView components. 10 There is not enough free space available on the volume. Provided example batch file for controlling installation In the directory DeskView\Current\Install\Samples you will find the example batch file DVLogin.bat. 40 DeskView 5.33 Client Management Software

Installation procedure Network installation of DeskView components by the administrator Copy the file into an enabled directory on the administrator PC (e.g. V:\DVINST from the standpoint of the client PCs), which also contains the login script and adapt this file (see comments in the file DVLogin.bat). The calling of this batch file in the login script could, for example, be as follows: IF EXIST V:\DVINST\DVLOGIN.BAT CALL V:\DVINST\DVLOGIN.BAT Drive V: corresponds to a network drive linked to the administrator PC with a released directory. This drive must be available until it is ensured that DeskView is installed on all PCs. Please control whether the path specifications are correct. If a parameter is missing or a file is not found, the installation will not be carried out. No error message will be output, however you can display the error codes via ERRORLEVEL. The path names may not yet contain UNC file names (\\MYPC\...). DeskView 5.33 Client Management Software 41

Integration in Management Systems The network-capable DeskView components are integrated in an existing network and expand, for example, the system management under Microsoft SMS (Systems Management Server), the Server-Management-Software ServerView developed by Fujitsu Siemens Computers or SNMP-based enterprise management software such as CA Unicenter (SNMP = Simple Network Management Protocol). To integrate DeskView data, alarms and program runs in a management system, certain conditions must be met and in some cases additional software must also be installed. To carry out integration, you should have a good knowledge of the management system. DeskView offers the following basic integration possibilities: Data integration (DeskInfo) Client data such as hardware and software inventory are made available in the management console. Data integration can be carried out via the file deskinfo.mif. Data integration in SNMP is also possible (desksnmp.mib) so that management systems equipped with an SNMP browser can also be provided with these data. Alarm integration (DeskAlert) With DeskAlert various events can be defined which send an alarm to the management console. Alarm integration functions SNMP-based via the files desktrap.mib and status.mib. Launch integration (via DeskView browser/agent) On the management console currently can be run the DeskView components DeskView, DeskAlert and DeskSettings for the clients. In addition, Microsoft SMS 2.0 and SMS 2003 support the launch integration for DeskFlash and DeskOff. The condition for this is that the corresponding DeskView component is installed on the management console in the "Administrator in network" installation variant and on the client in a network-capable installation variant (client with or without user interface or administrator in network). ServerView DeskView can be integrated in the Server Management ServerView. The requirements for this and the procedure are described in the ServerView documentation. DeskView 5.33 Client Management Software 42

Microsoft SMS Integration in Management Systems Microsoft SMS SMS (Systems Management Server) from Microsoft is as management solution for all companies that want to efficiently manage their Windows-based desktop systems from a central location while at the same time reducing the operating costs for change and configuration management. SMS 1.2, SMS 2.0 and SMS 2003 are supported. Possible integrations Data integration via deskinfo.mif Data integration is also possible via MOF for SMS 2.0 (from DeskView 5.31) and SMS 2003 (from DeskView 5.33). For a precise description and the software required for integrating DeskView in Microsoft SMS (MOF integration), see the Internet under www.fsc-pc.de/manageability/englisch/manageability.htm or the Drivers & Utility CD under \DeskView\sms20_mof.int (for SMS 2.0) and under \DeskView\sms2003i.int (for SMS 2003). Launch integration for DeskAlert, DeskInfo and DeskSettings; from SMS 2.0 also for DeskOff and DeskFlash. Under SMS 1.2 the results of a silent-mode call of DeskSettings can be viewed in SMS. SMS administrator console Installing DeskView Ê Install DeskView on the SMS console in the "Administrator in network" installation variant. Installing integration Ê Run the program SMSSetup.EXE and select the integration of DeskView in SMS for administrator PC. SMSSetup.EXE is included with DeskView (option: "Admin Extensions"). DeskView 5.33 Client Management Software 43

Integration in Management Systems CA Unicenter and CA AMO SMS client Installing DeskView Ê Install DeskView in a network-capable installation variant. Installing integration SMSAgent must be installed on the SMS client. SMSAgent creates the file deskinfo.mif (MIF = Management Information File). The file is recreated each time the client is rebooted. In addition, a new MIF file can be created with the runtime parameter / Refresh (SMSAgent /Refresh). Ê Activate the option "SMS support" when installing DeskInfo. or Ê Start SMSSetup.EXE and select the integration of DeskView in SMS for client PC (option: "Client"). SMSSetup.EXE is included with DeskView. CA Unicenter and CA AMO CA Unicenter is an enterprise management system based on SNMP (CA = Computer Associates). CA AMO is an add-on for CA Unicenter (AMO = Asset Management Option) for collecting and managing hardware and software inventory data. An exact description and the required software for the integration of DeskView in CA Unicenter and CA AMO is available on the Internet at www.fsc-pc.de/manageability/english/manageability.htm. You can find all the files required for the integration on the CD "Drivers & Utilities" in the directories \deskview\ca_amo.int and \deskview\ca_uni.int. SNMP SNMP administrator You must link the MIB files manually" into your management system. For more information, consult the documentation on your management system. The files DeskSnmp.mib and DeskTrap.mib are located on the CD "Drivers & Utilities" in the directory \deskview\current\install\modules\dsnmpstp. 44 DeskView 5.33 Client Management Software

SNMP Integration in Management Systems SNMP client DeskView provides SNMP support for DeskInfo data (DeskSNMP) and DeskAlert alarms (DeskTrap). You have to install and configure the SNMP support on the client PC, before you install DeskView with SNMP support. Installing and configuring the SNMP support You have to install the SNMP support and to configure the trap targets (trap receivers), before the Client PC can generate and send SNMP traps. Windows NT 4.0 You must be logged on as a member of the Administrator group. To install the SNMP support, proceed as follows: Ê Select Start Settings Control Panel Network. Ê Click Add and SNMP Service on the Services tab. Ê Click OK. Ê In the Windows NT Setup dialog box, enter the full path to the Windows NT installation files, and then choose the Continue button. The SNMP support is installed. To configure proceed as follows. Ê Select Start Settings Control Panel Network. Ê Click SNMP Service and Settings... on the Services tab. Ê On the Traps tab enter the community name and the trap targets. Ê Click OK. The SNMP service is configured. To accept the configuration, restart the SNMP service. Windows 2000/Windows XP You must be logged on as a member of the Administrator group. To install the SNMP support, proceed as follows: Ê Right-click on the desktop on My Network Places and select Properties. Ê Click on Advanced and then on Optional Network Components... in the Network and Dial-Up Connections dialog box. Ê Select Management and Monitoring Tools and click on Details... DeskView 5.33 Client Management Software 45

Integration in Management Systems SNMP Ê Within the new dialog box you select the sub-components SNMP (Simple Network Management Protocol) and click on OK. Ê For the rest of the installation click on Continue. The SNMP support is installed. To configure proceed as follows. Ê Click on My computer on the desktop with the right mouse button and select Administer. Ê Click on Services under Services and Applications. Ê Right-click on SNMP Service and select Properties. Ê Select the Traps tab and enter the community name and the trap targets. Ê Click OK. The SNMP service is configured. To accept the configuration, restart the SNMP service. Installing DeskView with SNMP support DeskSNMP Ê Select the program DeskInfo in the selection dialog box during the installation of DeskView. Ê Select the SNMP support option under Options... DeskSNMP agent will then be installed on the PC. This allows the SNMP administrator to query DeskInfo data. DeskTrap Ê Select the program DeskAlert in the selection dialog box during the installation of DeskView. Ê Select the SNMP support option under Options... and in the Alert on LAN field, enable Client PC. DeskTrap Agent will then be installed on the PC. This allows SNMP traps to be generated from the DeskView alarms which can be sent to the SNMP administrator. The required configuration is realized using the DeskAlert program via the SNMP Trap column. The SNMP trap column is only displayed when DeskView is installed on the PC in the "Administrator in network" installation type or when you access the PC from a DeskView administrator PC over the network for example via DeskView Browser. 46 DeskView 5.33 Client Management Software

SNMP Integration in Management Systems Timeout for SNMP request for DeskInfo data If DeskInfo data are requested via SNMP, the SNMP request may be aborted with a timeout. This is primarily true for "slow" data, such as mainboard or PCI information. You can solve the problem as follows: Ê Wait a few seconds and then carry out the SNMP request again. The second request is generally successful, as the SNMP data are still contained internally in the cache memory. or Ê Increase the value for the timeout (e.g. to 60 seconds) if the SNMP software used permits this. For more information, consult the documentation of your SNMP software. DeskView 5.33 Client Management Software 47

Appendix result file and error numbers DeskView Setup result file Appendix result file and error numbers DeskView Setup result file The result file is only created when you have specified the corresponding option in DeskView Setup. In the DeskView Setup you also specify the directory in which the event file is to be saved. If a directory on the administrator PC or a server is specified for the result files, the client PCs must have write access to this directory. In the result file all errors are recorded which have occurred during the installation or uninstallation. The entry OK means that no error has occurred. The result file of a client PC bears the name of the client PC (ID of the PC in the Windows network) and the extension INI, e.g. NETPC1.INI. If such a file already exists, the file contents for the individual DeskView components will be overwritten. As the administrator you should back up or delete the result files of early installations on the client PC or specify a different directory for the new result files prior to an installation. All client PCs on which an error occurred enter the text ERROR and the error number in the result file. All non-critical errors are marked with WARNING. To determine all client PCs on which an error occurred, search for all result file names containing the text ERROR or WARNING with a suitable program (e.g. Windows Explorer). The result files should only be opened with a word-processing program that permits outside access to open files, e.g. Windows Notepad. This ensures that no information is lost when the client PC is written directly into the file while it is opened by the administrator. If a DeskView component is installed for which other components are automatically installed at the same time, results from subcomponents may also be contained in the result file. Also check these entries, as they are important for error-free installation. Syntax Syntax Meaning <programname> placeholder install remove alternatively [ <date> ] optional {, <tag> } optional, can be repeated 48 DeskView 5.33 Client Management Software

DeskView Setup result file Appendix result file and error numbers <programname> = ERROR #<number> [ (<tag> {, <tag> } ) ] [ File: [<path>]<filename> ], [ <date> ], [ mode = install remove letitbe ] <programname> = WARNING #<number> [ (<tag> {, <tag> } ) ] [ File: [<path>]<filename> ], [ <date> ], [ mode = install remove letitbe ] <programname> = OK [ {<status information>}] <date>=<mm-dd-[yy]yy> <tag>= any information belonging to the text Example DVSETUP cannot load a DLL file (DLL = Dynamic Link Library) on the PC "XYZ PC". The log file may include for example: Either: [XYZ-PC] DeskSettings=ERROR #107 (DSMOD.DLL) or [XYZ-PC] DeskInfo=ERROR #107 (Could not load DIMOD.DLL) DVSETUP.EXE 01-31-2000 mode=install Error numbers Each program is equipped with its own error numbers. General errors DeskInfo DeskAlert DeskView Browser DeskView Agent SNIDMI DeskSettings DeskFlash PCDescript SMSAgent SMSAdmin SMSIntegration Alert on LAN DeskWOL WMI Core Setup 0000 to 0199 1000 to 1199 1400 to 1599 2000 to 2199 2400 to 2499 2800 to 2999 3200 to 3399 3600 to 3699 3700 to 3799 3900 to 3999 4000 to 4099 4100 to 4199 4200 to 4299 4300 to 4399 4400 to 4499 DeskView 5.33 Client Management Software 49

Appendix result file and error numbers DeskView Setup result file No. Error Error handling 0000 OK 0001 Error when calling the specified section in an INF file. DeskView Setup will be ended. 0002 Error when removing the specified file during the uninstallation. DeskView Setup will be ended. 0003 The setup program was called with incorrect command line parameters. 0004 The setup program was started with the /Remove parameter and the uninstallation routine was not found. 0005 The setup program has determined that it was not started under Windows for Home Use. 0006 The setup program has determined that it was not started under the proper Windows version. 0007 The setup program has determined that it was started on a PC of another manufacturer. 0008 The setup program has found a newer installed version on the computer. 0009 The setup program has determined that there is not enough memory available on the hard disk of the (target) computer. 0011 An installation or uninstallation was started without administrator rights. 0013 The product type is not WinNT, LanmanNT or SERVERNT, and is therefore not supported by the setup. Remove the specified file manually and repeat the uninstallation. Check the command line parameters. Install a newer Windows version. A downgrade is not permitted. If you really want to install the older version, you must uninstall the newer version first. Make memory space available and repeat the installation. Assign administrator rights to the computer. Check and repair your Windows for Business installation and then run the setup again. 0014 No component was successfully installed. This error is a follow-up error. Observe the error messages of the respective components. 0015 DeskView Setup has determined that no Windows 95 shell interface is present on the system. You have attempted installation on a Windows platform (e.g. Windows 3.1x, Windows NT 3.51) which is not permitted. 50 DeskView 5.33 Client Management Software

DeskView Setup result file Appendix result file and error numbers No. Error Error handling 0016 This version of DeskView requires Service Pack 5 under Windows NT 3.51. Install Service Pack 5 under Windows NT 3.51 or install Windows NT 4.0 and carry out the installation again. 0017 A required module cannot be installed. This error refers to a preceding error. Check which error has occurred prior to the error message 0017 and eliminate it. 0018 DeskView cannot be installed in conjunction with ServerView Agent V2.0 or a later version. 0020 The specified service could not be stopped. DeskView Setup will be ended. 0021 The specified service could not be removed. DeskView Setup will be ended. 0022 The specified service could not be set up. DeskView Setup will be ended. 0023 The specified service could not be started. DeskView Setup will be ended. 0024 The setup program has determined that DeskView is not supported by the operating system installed. 0030 The specified registry tree or key could not be deleted. 0031 The specified registry key could not be opened. Uninstall the ServerView Agent and carry out the installation again. Restart the PC and invoke the setup again. If the error occurs again, you must stop the service manually. Restart the PC and invoke the setup again. If the error occurs again, you must delete the service manually. Set up the service manually. To do this, use the program INSTSRV.EXE. Restart the PC and invoke the setup again. Delete the registry tree or key manually and then run the setup again. 0032 The specified registry key could not be created. Create the registry key yourself. 0033 The specified registry key could not be closed. Call the Setup again. 0040 The specified process could not be deleted. End the process in the Task Manager. 0041 The specified program was ended with an error Restart the PC. message. 0043 The function CheckIfValuesExists was ended with an error. 0044 GetRegistryValues() failed. DeskView 5.33 Client Management Software 51

Appendix result file and error numbers DeskView Setup result file No. Error Error handling 0045 SetRegistryValues() failed. 0046 DeleteRegistryValue() failed. 0047 The registry value (MultiSZ value) could not be deleted. The RemoveMultiSZ section in SniSubr.inf is defective. 0048 reserved 0049 reserved 0051 The setup program has determined that it was not started under Windows for Business. 0060 The callup of SniSleep() has failed. 0070 The setup program was unable to find the required files. 0071 A required restart was not carried out between two DeskView installations. Settings could be lost. 0072 A DeskView component could not be installed on this operating system. It is not or no longer envisaged for this operating system. 0073 A DeskView variant of another manufacturer is already installed on the target system. 0100 The specified DeskView Setup program was not found. 0101 An installation variant (administrator, client with user interface, client without user interface or local) is specified in the file SNISADM.INI that differs from that already installed on the PC. 0102 In file SNISADM.INI a non-permissible installation mode was entered. 0103 The Setup program fails to find the component SNISetup.DLL. SNISetup.DLL is not present in the same directory as the Setup program (%INST%). You have attempted installation on an incorrect software platform. Check whether all required files are located in the directory from which the Setup program was called. Reboot the PC and restart DeskView installation. Uninstall the existing variant completely and then repeat installation. Check whether the module is present in the corresponding directory. The installation variant cannot be changed on a PC during an update. The only way to change the installation variant is to uninstall DeskView and reinstall it with a different installation variant. Manual entries were made in the file SNISADM.INI. Create the file SNISADM.INI using DeskView Setup SETUP533.EXE. Copy the component SNISetup.DLL from the directory Common to %Source%\WinNT. 52 DeskView 5.33 Client Management Software

DeskView Setup result file Appendix result file and error numbers No. Error Error handling 0104 The setup program has determined that ACPI is active, however the program does not support ACPI. 0105 The setup program fails to find one of the following components: SNIDMI.sys, SNIDMI.dll or SNISETUP.dll The DeskView component cannot be operated with this operating system with ACPI functionality (ACPI = Advanced Configuration and Power Interface). Copy the missing file from the directory...modules\common to the installation directory. 0106 There is not enough free space on the hard disk. Select a different hard disk or delete files no longer required. 0107 It was not possible to load the *.DLL file. Copy the missing file into the installation directory. 0120 This DeskView component cannot be installed. It requires a license number. Obtain the "DeskView License Pack". 0130 The listed files could not be copied into the correct directory. Check if the directories %Temp, %Tmp and %Win are present. 0199 An unexpected, unknown error has occurred. This error number is entered in the result file at the start of every component and is overwritten on successful installation and when errors occur. If following an update installation of DeskView version 4.25 to a higher version a uninstallation is then carried out unattended, and despite successful uninstallation this error is listed in the result file, it can be ignored. 1000 OK 1002 This version of DeskInfo requires Windows NT 4.0. The installation was attempted on a PC with Windows NT version 3.51. 1003 This version of DeskInfo requires Service Pack 5 under Windows NT 3.51. The installation was attempted on a PC with Windows NT version 3.51 without Service Pack 5. Carry out an upgrade to Windows NT version 4.0 on the PC and carry out the installation again. Install Service Pack 5 and carry out the installation again. DeskView 5.33 Client Management Software 53

Appendix result file and error numbers DeskView Setup result file No. Error Error handling 1005 An error has occurred in the module SniDmi when installing DeskInfo. 1006 An error has occurred when calling the System Monitoring module while installing DeskInfo. 1008 An error has occurred during installation of SNMP Integration. 1009 The SNMP Admin installation has failed while installing DeskInfo. 1010 The registration has failed while installing DeskInfo. 1011 The deregistration has failed while uninstalling DeskInfo. 1012 A fault has occurred while removing System Monitoring while uninstalling DeskInfo. 1013 No log file was found for removing System Monitoring while uninstalling DeskInfo. 1014 An error has occurred while removing SNMP Integration while uninstalling DeskInfo. 1015 No log file was found for removing SNMP Integration while uninstalling DeskInfo. Check whether all files (e.g. SETUP533.EXE) are present under %Source%\WinNT\SniDmi. Check whether the file SniDmi.inf exists under %Source%\WinNT. Check whether all files (e.g. SETUP533.EXE) are present under %Source%\WinNT\DeskInfo\SysMon. Check the error message under System\CurrentControlSet\Control\Siemens_Nixdorf\ DeskView\System_Monitoring\Setup. See Error No. 1005 Check whether the file DSNMPSTP.EXE exists in the Common directory. 1016 The specified file was not found. Copy the file C:\NTDetect.COM to C:\NTDetect.BAK (do not rename!). 1017 While uninstalling DeskInfo, a fault has occurred when removing SniDMI. 1018 During local installation, neither SMS/SNMP nor SMS Administrator installation can be carried out. Check whether the file SNIDMI.INF is contained in the directory %Source%\WINNT. Select either the installation mode local or additional options such as SMS, SNMP or SMS Admin. 54 DeskView 5.33 Client Management Software

DeskView Setup result file Appendix result file and error numbers No. Error Error handling 1021 An old DeskInfo version (< 2.50.008) was found from which no update is possible. 1022 SNMP Integration was selected and the SNMP Install the SNMP Service. Service is not installed on the system. 1400 OK 1401 SNMP Integration was selected and the SNMP Install the SNMP Service. Service is not installed on the system. 2000 OK 2400 OK 2800 OK 2803 An error occurred while installing SniDMI The error could not be entered in the Windows registry. 2806 Function SniFindStrInPhysMem () failed. 3200 While installing DeskSettings an installed DeskInfo version lower than or equal to 3.10 was found. 3201 While installing DeskSettings an installed DeskInfo version lower than or equal to 2.33.010 was found. 3202 When installing the update no already present DeskSettings was found. 3210 The BIOS on this PC does not support DeskSettings. Check whether all files (e.g. SETUP533.EXE) are contained in %Source%\WINNT\SNIDMI. No DeskSettings is installed on the PC. Therefore, no update is possible. If your system board supports DeskSettings, perform a BIOS update. 3230 Defective access to the registry Check whether the required rights for the registry are present. 3600 OK 3601 The mainboard of the PC does not support DeskFlash. 3602 DeskFlash is already running. DeskView 5.33 Client Management Software 55

Appendix result file and error numbers DeskView Setup result file No. Error Error handling 3700 OK 3701 It was not possible to install all images and board Check whether all files have been copied to the PC. specifications. 3900 OK 3901 You must select either DeskView or ServerView. 3902 ServerView can only be installed under Windows for Business. 3903 ServerView SMS Client cannot be installed together with DeskView Client. 4000 OK 4001 You must select either DeskView or ServerView or both. 4002 No SMS Administrator installation was found. 4100 OK 4101 SMS Integration is not possible due to the installed software. Install the correct version of DeskView or ServerView. 4102 SMS Integration cannot be installed. Check the installation. 4103 No integration has been selected. 4200 OK 4201 Alert On LAN can only be installed when DeskInfo and DeskAlert from the DeskView version 4.15 are installed. Install a newer version of DeskInfo and DeskAlert. 4202 A newer Alert on LAN version is already installed. Install a newer version of DeskInfo and DeskAlert. 4203 Neither a client nor an administrator installation is Install DeskAlert again. specified in the SNISADM.INI. 4204 You have tried to carry out an administrator installation under Windows for Home Use. 4205 Before you install Alert on LAN under Windows 95, DCOM95 version 1.3 (or higher) must be installed. Install Windows for Business or carry out a client installation. Install DCOM95 version 1.3 (or higher) before you run the installation program. 56 DeskView 5.33 Client Management Software

DeskView Setup result file Appendix result file and error numbers No. Error Error handling 4206 The PC's hardware does not support Alert On LAN or ASF. Check that the necessary hardware and software requirements are fulfilled. 4207 No valid setup for Alert on LAN/ASF Agent. Download the current setup for Alert on LAN/ASF Agent from the internet at http://www.fsc-pc.de. 4208 No valid setup for ASF Proxy. Download the current setup for ASF Proxy from the internet at http://www.fsc-pc.de. 4209 The installation or deinstallation of ASF Proxy during the installation of DeskAlert with AoL Admin option has not functioned properly. 4210 The installation or deinstalltion of AoL/ASF Agent during installation of DeskAlert with AoL Client option has not functioned properly. 4211 No valid MSI software package for ASF Proxy (ASFProxy.msi). File not found as expected. ASF Proxy will not be installed. 4212 To install ASF Proxy under Windows XP, you need Service Pack 1. Check that the necessary hardware and software requirements are fulfilled. Check that the necessary hardware and software requirements are fulfilled. Download the current MSI software package for ASF Proxy (ASFProxy.msi) from the internet at http://www.fsc-pc.de. Install Service Pack 1 under Windows XP and carry out the installation again. 4213 Microsoft Installer service not installed. Install Microsoft Installer (1.0 or higher) and carry out the installation again. 4214 Microsoft Installer service is not up to date. You need version 1.0 or higher. ASF Proxy will not be installed. Install Microsoft Installer (1.0 or higher) and carry out the installation again. 4215 No valid setup for ASF Agent. Download the current setup for ASF Agent from the internet at http://www.fsc-pc.de. 4216 To install ASF Agent or Proxy under Windows NT4, you need Service Pack 4 or higher. 4217 To install ASF Agent or Proxy under Windows 2000, Service Pack 2 or higher is required. Install Service Pack 4 under Windows NT4 and carry out the installation again. Install Service Pack 2 under Windows 2000 and carry out the installation again. DeskView 5.33 Client Management Software 57

Appendix result file and error numbers DeskView Setup result file No. Error Error handling 4218 The SNMP Service is not installed on the system. To install AoL/ASF Proxy, the SNMP Service is required. 4219 During installation, the configuration of DeskAlert with the ASF Client option did not function correctly. 4300 OK 4400 OK 4401 No or the old WMI version is installed and no WMI Core Setup is available. 4402 An attempt was made to install or update WMI but Microsoft Setup failed. Install the SNMP Service. Detailed information can be found in chapter "Installing and configuring the SNMP support". Check that the necessary hardware and software requirements are fulfilled. Install the current version of WMI. Install the current version of WMI manually. 58 DeskView 5.33 Client Management Software