Bosch Video Management System Patch Setup



Similar documents
SharePoint Wiki Redirect Installation Instruction

Bosch Video Management System. VIDOS to Bosch VMS Migration Guide

Bosch Video Management System High availability with VMware

Sophos Enterprise Console server to server migration guide. Product version: 5.1 Document date: June 2012

VMware for Bosch VMS. en Software Manual

Sitecore Ecommerce Enterprise Edition Installation Guide Installation guide for administrators and developers

INSTALLATION GUIDE Datapolis Process System v

Upgrading MySQL from 32-bit to 64-bit

File Manager Pro User Guide. Version 3.0

Dynamics CRM 2011 Outlook Configuration Guide With Windows XP

Remote Programming Software (RPS) D5500CU

Distributing SMS v2.0

Symantec AntiVirus Corporate Edition Patch Update

ACTIVE DIRECTORY DEPLOYMENT

DocAve Upgrade Guide. From Version 4.1 to 4.5

SharePoint List Filter Favorites Installation Instruction

Data Warehouse Troubleshooting Tips

Honeywell Process Solutions Experion HS R400 Server Patch220 for PAR1-MVKSRD Software Change Notice

STATISTICA VERSION 9 STATISTICA ENTERPRISE INSTALLATION INSTRUCTIONS FOR USE WITH TERMINAL SERVER

Installing Sage Accpac ERP CGA 5.6A

How to Uninstall Manually and Upgrade the Cisco VPN Client 3.5 and Later for Windows 2000, Windows XP and Windows Vista

SAS 9.3 Foundation for Microsoft Windows

Sophos Enterprise Console server to server migration guide. Product version: 5.2

Installation and licensing Licensing method 1 Manual Activation by Serial number... 3

Enterprise Historian 3BUF D1 Version 3.2/1 Hot Fix 1 for Patch 4 Release Notes

SonicWALL CDP 5.0 Microsoft Exchange InfoStore Backup and Restore

Integrated Virtual Debugger for Visual Studio Developer s Guide VMware Workstation 8.0

USING SSL/TLS WITH TERMINAL EMULATION

Cisco TelePresence Management Suite Extension for Microsoft Exchange

User Installation Guide for SAS 9.1 Foundation for 64-bit Microsoft Windows

Pocket ESA Network Server Installation

HP Enterprise Integration module for SAP applications

Video Administration Backup and Restore Procedures

SAS 9.4 PC Files Server

All Windows Installations Guide Contents

Software Change Notice

BioWin Network Installation

TSM for Windows Installation Instructions: Download the latest TSM Client Using the following link:

GE Intelligent Platforms. Activating Licenses Online Using a Local License Server

Customizing the SSOSessionTimeout.jsp page for Kofax Front Office Server 3.5.2

Global Image Management System For epad-vision. User Manual Version 1.10

Error: "Object reference not set to an instance of an object" When Opening Any Database

This document describes the software upgrade of BRS Appliance from v8.9 to v8.10.

Reconfiguring VMware vsphere Update Manager

Item Audit Log 2.0 User Guide

How To Install Database Oasis On A Computer Or Computer (For Free)

GeneMapper Software v.4.1 Uninstall Procedure

Windows Security Scoring Tool Implementation Guide v2.0.1

Test Note Phone Manager Deployment Windows Group Policy Sever 2003 and XP SPII Clients

XMap 7 Administration Guide. Last updated on 12/13/2009

How to Back Up and Restore an ACT! Database Answer ID 19211

VeriCentre 3.0 Upgrade Pre-Installation and Post Installation Guidelines

CISCO VPN CLIENT INSTALL AND UPDATE INSTRUCTIONS

Administration guide. Host software WinCCU Installation. Complete gas volume and energy data management

Magaya Software Installation Guide

Lenovo Online Data Backup User Guide Version

CloudPortal Services Manager Version 11.0 CU2 Deployment Guide

Using Logon Agent for Transparent User Identification

Lync Server Patching Guide

Upgrade: SAP Mobile Platform Server for Windows SAP Mobile Platform 3.0 SP02

Capture Pro Software FTP Server System Output

Print Audit 6 Network Installation Guide

Sage ERP Accpac 6.0A. SageCRM 7.0 I Integration Guide

INSTALLATION INSTRUCTIONS FOR UKSSOGATEWAY

new Business Online Technical Troubleshooting Guide

MIGRATING TO AVALANCHE 5.0 WITH MS SQL SERVER

FlexSim LAN License Server

Password Manager Windows Desktop Client

Moving the Web Security Log Database

Cisco TelePresence Management Suite Extension for Microsoft Exchange

Migrating MSDE to Microsoft SQL 2008 R2 Express

Independent Operator Client. en Software Manual

Tool Tip. SyAM Management Utilities and Non-Admin Domain Users

How To Configure CU*BASE Encryption

Quick Start Guide for the SupportDesk Web Interface

Sage Intelligence Financial Reporting for Sage ERP X3 Version 6.5 Installation Guide

Upgrading Good Mobile Messaging and Good Mobile Control Servers

Installation Guide for Crossroads Software s Traffic Collision Database

SonicWALL CDP 5.0 Microsoft Exchange User Mailbox Backup and Restore

Witango Application Server 6. Installation Guide for Windows

AVG Business SSO Connecting to Active Directory

NComputing vspace Server 8.3 for Windows. Software and Firmware Upgrade Guide. Document version 1.2

Moving the TRITON Reporting Databases

ClearPass Policy Manager 6.3

Perceptive Intelligent Capture. Product Migration Guide. with Supervised Learning. Version 5.5 SP3

Inmagic ODBC Driver 8.00 Installation and Upgrade Notes

1 Minimum system requirements

Ajera 7 Installation Guide

IISADMPWD. Replacement Tool v1.2. Installation and Configuration Guide. Instructions to Install and Configure IISADMPWD. Web Active Directory, LLC

Avira Professional Security Migration to Avira Professional Security version HowTo

CloudPortal Services Manager Version 11.0 CU1 Deployment Guide

Installing, Uninstalling, and Upgrading Service Monitor

How to Install MediaWiki on Windows Server 2003

ContentWatch Auto Deployment Tool

Upgrade Guide BES12. Version 12.1

Intellicus Cluster and Load Balancing (Windows) Version: 7.3

5.6.3 Lab: Registry Backup and Recovery in Windows XP

XenClient Enterprise Synchronizer Migration

PSCAD Installation Errors

Transcription:

Bosch Video Management System Patch Setup en Technical Service Note

Bosch Video Management System Table of contents en 3 Table of contents 1 Introduction 4 2 Deliverables 5 2.1 The.msp File 5 2.2 The ReadMe.txt File 7 3 Patch Deployment Sequence 8 4 Uninstallation of Patches 13 5 Bosch VMS Diagnostics for Bosch VMS Patches 16 5.1 Control Panel 16 5.2 DLLs in Folder bin 16 5.3 Registry 17 5.4 ConfigCollection 18 5.4.1 File Listing 18 5.4.2 Registry Settings 19 5.4.3 Patch Setup Log File 19 6 Bosch VMS Patching Special Cases 21 6.1 Cumulative Patches 21 6.1.1 Patch installation 21 6.1.2 Patch uninstallation (oldest patch first) 21 6.1.3 Patch uninstallation (latest patch first) 21 6.2 Installing Bosch VMS Features on Patched Systems 21 7 Bosch VMS Patch Setup FAQ 23 Bosch Sicherheitssysteme GmbH Technical Service Note 2015.05 V1 DOC

4 en Introduction Bosch Video Management System 1 Introduction This document informs about the changed procedure for deploying Bosch VMS hotfixes. Hotfixes for Bosch VMS version 5.5.1 and later will no longer be shipped as individual batch files and DLL files, but as setup files. The underlying setup technology is the same as for Microsoft patches. The motivation for changing Bosch VMS hotfix deployment was to improve the user experience and to avoid common mistakes when applying patches. To be consistent with Microsoft terminology, all future Bosch VMS hotfixes will be called patches. The term hotfix will no longer be used. For those cases where experimental or diagnostic patches must be shipped, the deliverable will be called experimental patch or diagnostic patch. For all other cases the term Bosch VMS patch indicates that the deliverable was fully tested by QA i.e. the functionality of the patch was ensured on a test system. 2015.05 V1 DOC Technical Service Note Bosch Sicherheitssysteme GmbH

Bosch Video Management System Deliverables en 5 2 Deliverables Every Bosch VMS patch deliverable consists of a folder that contains two files: an.msp file and a ReadMe.txt file. Figure 2.1: Patch folder contents:.msp file and ReadMe.txt file The patch folder name indicates the Bosch VMS target version of the patch, a short title of the patch and the unique identifier. In the example above the target version is Bosch VMS 5.5.1.515, the short title is CameoSDK and the unique identifier is 10001. The.msp file is the setup executable that must be started to install the patch. The ReadMe.txt file contains detailed information about the patch. Both files the.msp file and the ReadMe.txt file are shipped together since the setup references the ReadMe.txt files. Note: Files InstallerInfo.txt and CustomerInfo.txt, which were formerly shipped with every Bosch VMS hotfix, are no longer required. Note: Starting with Bosch VMS Version 5.5.1, the patch setup dialog offers a Show the readme file button that opens the file ReadMe.txt. This button is not yet supported for Bosch VMS 5.5.0 patches. As a consequence, for Bosch VMS 5.5.0 patches the user must manually open file ReadMe.txt to get more information about the patch. 2.1 The.msp File The.msp file is a setup file which can be started like any other executable. The.msp file should be started on all Bosch VMS machines that are affected by the patch. Please refer to ReadMe.txt for details on which machines are affected by a patch. The.msp file name indicates the Bosch VMS target version of the patch, a short title of the patch and the unique identifier. Example.msp file name: BVMSPatch_5.5.0.348_PTZDomeIssues_109757.msp The file name indicates, that the patch is applicable for systems running Bosch VMS version 5.5.0.348 has a short title PTZDomeIssues i.e. it has something to do with PTZ and dome issues resolves TFS bug 109757 Note: If a Bosch VMS patch fixes multiple issues, then the unique identifier of the patch consists of multiple, comma separated TFS bug IDs, e.g. 109757,109196. Bosch Sicherheitssysteme GmbH Technical Service Note 2015.05 V1 DOC

6 en Deliverables Bosch Video Management System Important Note: It is no longer required to manually stop services before applying a Bosch VMS patch. The patch setup will automatically detect if services must be stopped before applying the patch. In this case, the setup program will prompt the user whether services should be automatically stopped and started. It is possible to abort the setup installation at this point. This gives the user the chance to apply the patch at a later time e.g. at a time when a short Bosch VMS server downtime is acceptable. Figure 2.1: Setup dialog informing about required service stop Note: The Bosch VMS patch setup can safely be started on Bosch VMS installations that are not affected by the patch. In this case, the setup will run through all installation stages without modifying any dlls on the system. Note: The Bosch VMS patch setup can safely be started on Bosch VMS machines with a not matching Bosch VMS version. In this case the following error dialog will pop up patch installation will be aborted after clicking OK. 2015.05 V1 DOC Technical Service Note Bosch Sicherheitssysteme GmbH

Bosch Video Management System Deliverables en 7 Figure 2.2: Error dialog when running a Bosch VMS patch setup on a system with a wrong Bosch VMS version. Note: It is no longer possible to accidentally patch a Bosch VMS machine with a patch for a different Bosch VMS version. 2.2 The ReadMe.txt File The ReadMe.txt file contains detailed information about the Bosch VMS patch: patch identifier (bug ID and short title) problem details (details on the problem that is fixed by the patch) affected Bosch VMS components (Bosch VMS machines where the patch must be applied) list of replaced files (files that are replaced by the patch) The ReadMe.txt file replaces the formerly used file CustomerInfo.txt. The ReadMe.txt file does not contain detailed instructions on how to manually apply the patch, because these steps are automatically carried out by the patch setup functionality. Important note: Always make sure that the.msp file is shipped together with the corresponding ReadMe.txt file. If the ReadMe.txt file is missing, then there is no detailed information about the Bosch VMS patch. Note: If the ReadMe.txt file is missing when running the patch setup, then a click Show the readme file opens an empty Notepad file. To avoid this, always make sure that both, the.msp file and the ReadMe.txt file are delivered and are located in the same directory. Bosch Sicherheitssysteme GmbH Technical Service Note 2015.05 V1 DOC

8 en Patch Deployment Sequence Bosch Video Management System 3 Patch Deployment Sequence Bosch VMS patches cannot detect which Bosch VMS features (Management Server, Operator Client, Configuration Client, ) are installed on a system. Therefore it is required to apply the patches to all affected system of a Bosch VMS installation. For a list of affected systems, please refer to the ReadMe.txt file that comes with every Bosch VMS patch. To apply a patch, simply start the.msp file like any other executable. Note: It is not required to manually stop services before applying a patch: see below for details on what happens if the patch setup detects that services must be stopped. In the first phase of the Setup, the required space is calculated. This process might take a while. Figure 3.1: Space calculation dialog In the next setup step, details about the patch are displayed. The setup dialog indicates the ID of the patch, the short title and a summary of the problem details. 2015.05 V1 DOC Technical Service Note Bosch Sicherheitssysteme GmbH

Bosch Video Management System Patch Deployment Sequence en 9 Figure 3.2: Patch details dialog with short patch description and Show the readme file button. Note that you can get all details about the patch by clicking the Show the readme file button. File ReadMe.txt is opened in Notepad when clicking this button. Bosch Sicherheitssysteme GmbH Technical Service Note 2015.05 V1 DOC

10 en Patch Deployment Sequence Bosch Video Management System Figure 3.3: Opened ReadMe.txt file The Bosch VMS patch details consist of The name of the patch Details on the problem being fixed by the patch A list of Bosch VMS components that are affected by the patch this list indicates on which Bosch VMS systems the patch must be installed (e.g. Management Server, Operator Client, Configuration Client, ) A list of files being replaced by the patch The installation of the Bosch VMS patch can be started by clicking Update >. If the patch requires replacing files that are used by one of the Bosch VMS services, then a dialog will prompt the user for permission to stop and restart these services. Note that patch deployment can be aborted in this case. When clicking Cancel, the patch setup will terminate without stopping services and without deploying patch files. 2015.05 V1 DOC Technical Service Note Bosch Sicherheitssysteme GmbH

Bosch Video Management System Patch Deployment Sequence en 11 Figure 3.4: Setup dialog informing about required service stop If patch deployment was confirmed, then a progress dialog will show up while the patch is installed. Figure 3.5: Patch installation progress This final dialog will be displayed after the patch was installed: Bosch Sicherheitssysteme GmbH Technical Service Note 2015.05 V1 DOC

12 en Patch Deployment Sequence Bosch Video Management System Figure 3.6: Final Patch dialog 2015.05 V1 DOC Technical Service Note Bosch Sicherheitssysteme GmbH

Bosch Video Management System Uninstallation of Patches en 13 4 Uninstallation of Patches Every Bosch VMS patch can easily be uninstalled via the Control Panel. Start Control Panel, navigate to Programs / Programs and Features and click View Installed Updates. Figure 4.1: Programs and Features dialog On patched Bosch VMS systems, the list of installed updates contains one or more Bosch VMS patch entries. Bosch Sicherheitssysteme GmbH Technical Service Note 2015.05 V1 DOC

14 en Uninstallation of Patches Bosch Video Management System Figure 4.2: List of installed updates To uninstall a Bosch VMS patch, find the entry of the Bosch VMS Patch that you want to uninstall and right-click it to open the context menu. Select Uninstall in the context menu and confirm with Yes. Figure 4.3: Context menu entry Uninstall The Bosch VMS patch setup program now performs the patch uninstallation process. 2015.05 V1 DOC Technical Service Note Bosch Sicherheitssysteme GmbH

Bosch Video Management System Uninstallation of Patches en 15 Important note: Bosch VMS services will be automatically stopped and restarted if the patch uninstallation requires stopping the services. The user will not be prompted to confirm automatic service stop/start! As soon as the uninstallation is finished, the Bosch VMS patch entry will disappear from the Programs and Features / Installed Updates dialog. The result of a patch uninstallation is that all files that were replaced by the patch are rolled back to their preceding state. Bosch Sicherheitssysteme GmbH Technical Service Note 2015.05 V1 DOC

16 en Bosch VMS Diagnostics for Bosch VMS Patches Bosch Video Management System 5 Bosch VMS Diagnostics for Bosch VMS Patches For problem investigation on Bosch VMS systems, it is important to know whether a system is patched or not. Here are a number of hints how to check whether a Bosch VMS system was patched or not. 5.1 Control Panel To find out whether a Bosch VMS system was patched, simply launch Control Panel. Then navigate to Programs / Programs and Features and click View Installed Updates on the left side of the dialog. Bosch VMS patches are indicated by entries below the Bosch Video Management System section. The name of Bosch VMS patches starts with Bosch VMS Patch. Figure 5.1: List of installed updates Note that Bosch VMS patches do not indicate information in the Version and Publisher columns of the Installed Updates dialog. Providing this information is not possible for technical reasons. 5.2 DLLs in Folder bin To find out whether a Bosch VMS system was patched, you can also check the Bosch VMS installation directory. In explorer, navigate to the <install-root-dir>\bosch\vms\bin directory and sort the files by date. Note that the file date of patched DLL files differs from the file dates of all other DLL files. Also note that the file version of patched DLL files differs: the build number part of the file version string is bigger than the build number of the original DLL files. 2015.05 V1 DOC Technical Service Note Bosch Sicherheitssysteme GmbH

Bosch Video Management System Bosch VMS Diagnostics for Bosch VMS Patches en 17 Figure 5.1: Patched dll with differing file date and file version 5.3 Registry To find out whether a Bosch VMS system was patched, you can also check the registry. Run regedit from the command shell to open the registry editor. Navigate to registry hive HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData \S-1-5-18\Products. Then run a search on registry key Products for string Bosch VMS Patch. Bosch Sicherheitssysteme GmbH Technical Service Note 2015.05 V1 DOC

18 en Bosch VMS Diagnostics for Bosch VMS Patches Bosch Video Management System Figure 5.1: Registry with Bosch VMS patch 5.4 ConfigCollection 5.4.1 File Listing It is also possible to find out the patching status of a Bosch VMS system by analyzing the file listing in a Bosch VMS ConfigCollection. Extract the ConfigCollection zip and navigate to folder \BvmsConfigCollection\Bvms\Bin. Open file FileInfo.txt and check the file dates and the file versions of the Bosch VMS DLLs. Note that the file date and file version of patched Bosch VMS files differ. 2015.05 V1 DOC Technical Service Note Bosch Sicherheitssysteme GmbH

Bosch Video Management System Bosch VMS Diagnostics for Bosch VMS Patches en 19 Figure 5.1: Contents of ConfigCollection file FileInfo.txt (folder Bin) 5.4.2 Registry Settings The patching status of a Bosch VMS system can also be found out by analyzing the collected registry hive in a Bosch VMS ConfigCollection. Extract the ConfigCollection zip and navigate to folder \BvmsConfigCollection\Bvms\Registry. Open file HKLM_SOFTWARE_Microsoft_Windows_CurrentVersion_Installer_UserData_S-1-5-18_Products.t xt and search for Bosch VMS Patch. 5.4.3 Patch Setup Log File You can also find out whether a Bosch VMS machine was patched by searching for patch setup log files. While the Bosch VMS patch setup is running, the patch setup log file is created in folder %tmp % (i.e. Folder C:\users\<user name>\appdata\local\temp). The original name of the log file is MSI*.LOG, where * stands for a random temporary string. On patch setup completion, the patch setup log file is copied to C:\Program Data\Bosch\VMS \Log and renamed to <.msp file name>.log. Example: the log file name of Bosch VMS patch setup BVMSPatch_5.5.0.348_PTZDomeIssues_109757.msp will be BVMSPatch_5.5.0.348_PTZDomeIssues_109757.log Since the patch setup log file is copied to the standard log file folder, it will also be collected by the ConfigCollector. To search for patch setup log files, extract the ConfigCollection zip and navigate to folder \BvmsConfigCollection\Bvms\Log. If the Log directory contains files named BVMSPatch_*.log, then the Bosch VMS patch setup was executed on the system. Bosch Sicherheitssysteme GmbH Technical Service Note 2015.05 V1 DOC

20 en Bosch VMS Diagnostics for Bosch VMS Patches Bosch Video Management System Note that the existence of a patch setup log file does not necessarily mean that a system is still patched. When removing the patch, the log file will still remain in the log folder. 2015.05 V1 DOC Technical Service Note Bosch Sicherheitssysteme GmbH

Bosch Video Management System Bosch VMS Patching Special Cases en 21 6 Bosch VMS Patching Special Cases 6.1 Cumulative Patches It is sometimes required to merge two individual patches into one patch. This section describes the different installation and uninstallation cases when working with cumulative patches. Consider this example: Bosch VMS patch 12345 patches file A.dll (file version 001) Bosch VMS patch 54321 patches files A.dll and B.dll (file version 002) 6.1.1 Patch installation Assume that Bosch VMS patch 12345 was already installed on a Bosch VMS system. When installing Bosch VMS patch 54321 on top of Bosch VMS patch 12345, the following changes can be observed on the patched system: Patch file A.dll (file version 001) is replaced by file patch A.dll (file version 002) Original file B.dll is replaced by patch file B.dll (version 002) A new patch entry 54321 is added to Programs / Programs and Features/Installed Updates. Note that patch entry 12345 will still be listed in Programs / Programs and Features/Installed Updates. 6.1.2 Patch uninstallation (oldest patch first) Assume that Bosch VMS patches 12345 and 54321 were installed on a Bosch VMS system. When uninstalling patch 12345, the following changes can be observed on the patched system: Patch file A.dll (file version 002) remains unchanged Patch entry 12345 is removed from Programs / Programs and Features/Installed Updates. Note that patch entry 54321 will still be listed in Programs / Programs and Features/Installed Updates. 6.1.3 Patch uninstallation (latest patch first) Assume that Bosch VMS patches 12345 and 54321 were installed on a Bosch VMS system. When uninstalling patch 54321, the following changes can be observed on the patched system: Patch file A.dll (file version 002) is replaced by patch file A.dll (file version 001) Patch entry 54321 is removed from Programs / Programs and Features/Installed Updates. Note that patch entry 12345 will still be listed in Programs / Programs and Features/Installed Updates. 6.2 Installing Bosch VMS Features on Patched Systems Assume that Bosch VMS patch 12345 consists only of dlls that affect Bosch VMS Operator Clients. When installing patch 12345 on a Bosch VMS Management Server no dlls is deployed, because there is no Bosch VMS Operator Client feature to be patched. You will still notice in this case, that patch entry 12345 is listed in Programs / Programs and Features/Installed Updates despite no dlls were deployed. Assume that you run the Bosch VMS installer again on the patched Management Server machine and assume that you install the Bosch VMS Operator Client feature. Bosch Sicherheitssysteme GmbH Technical Service Note 2015.05 V1 DOC

22 en Bosch VMS Patching Special Cases Bosch Video Management System You will notice in this case, that the Bosch VMS Operator Client is installed, and that patch 12345 is properly applied. I.e. the end result is that the dlls of patch 12345 are deployed on the machine. 2015.05 V1 DOC Technical Service Note Bosch Sicherheitssysteme GmbH

Bosch Video Management System Bosch VMS Patch Setup FAQ en 23 7 Bosch VMS Patch Setup FAQ Q: What happens if you try to install the same Bosch VMS patch setup multiple times? A: Nothing happens. When running the setup for a second time, no patch files will be deployed. Q: What happens to the Bosch VMS patches if a patched system is upgraded? A: All patched DLLs and the patch entries in Programs and Features will be removed during the upgrade process. Example: if you upgrade a patched Bosch VMS 5.5.0 system to Bosch VMS version 5.5.1, then you will get a clean Bosch VMS 5.5.1 installation without 5.5.0 patch DLLs and without Bosch VMS 5.5.0 patch entries in Programs and Features. Q: What happens to the Bosch VMS patches if a patched system is downgraded? A: All patched DLLs and the patch entries in Programs and Features will be removed when uninstalling the Bosch VMS major version. Example: if you uninstall a patched Bosch VMS 5.5.0 system, all Bosch VMS 5.5.0 patches will automatically be uninstalled. If you install Bosch VMS version 5.0 on a previously uninstalled system, then you will get a clean Bosch VMS 5.0 installation without 5.5.0 patch DLLs and without Bosch VMS 5.5.0 patch entries in Programs and Features. Q: What happens to patches when running a repair installation of the currently installed Bosch VMS major version? A: All patches will be preserved when running a repair installation i.e. a repair installation does not roll back patches. Q: What is the expected downtime when applying a Bosch VMS patch? A: The patch process takes only a couple of minutes. The actual downtime for a Bosch VMS management server patch is only a couple of seconds longer than the time required for stopping/starting the Bosch VMS server service. Bosch Sicherheitssysteme GmbH Technical Service Note 2015.05 V1 DOC

Bosch Sicherheitssysteme GmbH Robert-Bosch-Ring 5 85630 Grasbrunn Germany www.boschsecurity.com Bosch Sicherheitssysteme GmbH, 2015