What's new in version 1.3.1?
Dear users, thank you for working with the Bosch Project Assistant. Based on your feedback, we have introduced the following improvements and features to make its use even more effective and enjoyable: • Sorting option on project overview page • Easier and faster removal of cameras from a project • Time server support • Re-commissioning support for VRM-managed cameras (focus on Flexidome IP 8000i) • Configuration mismatch (between project/app and camera) resolution dialog • Integration of Bosch Portable camera installation tool (NPD-3001-WAP), i.e. automatic detection of its wireless access point, management of multiple tools, and configuration of the tool’s network settings within the app
Please check out the updated article " How-to: connect to and configure the portable camera installation tool ". Here we have added new videos that help you to get started and which explain the sepcifics of the different platforms - iOS, Android and Windows.
Your Bosch Security App Team
PS: For details, please have a look at the latest release letter in our Bosch Security Download Area.
The attached document aims to provide concerned parties, such as customers, users, operators or consultants, with an overview of data privacy and protection related features of BVMS Person Identification. Moreover, this document describes how data, as processed during the Person Identification steps, can be classified. Finally, this document lists technical measures for data protection in the context of BVMS Person Identification.
As video surveillance use grows in commercial, government and private use cases, the need for low-cost storage at scale is growing rapidly. BVMS, Bosch cameras, HPE hardware and SUSE Enterprise Storage provide a platform that is an ideal target for recording these streams.
There are numerous difficulties around storing unstructured video surveillance data at massive scale. Video surveillance data tends to be written only once or become stagnant over time. This stale data takes up valuable space on expensive block and file storage, and yet needs to be available in seconds. With this massive scale, the difficulty of keeping all the data safe and available is also growing. Many existing storage solutions are a challenge to manage and control at such scale. Management silos and user interface limitations make it harder to deploy new storage into business infrastructure.
The solution is software-defined storage (SDS). This is a storage system that delivers a full suite of persistent storage services via an autonomous software stack that can run on an industry standard, commodity hardware platform. Bosch, Hewlett Packard Enterprise (HPE) and SUSE have partnered to deliver the benefits of SDS to the video surveillance industry. Using SUSE Enterprise Storage™ on HPE ProLiant DL and Apollo servers in a Bosch video surveillance environment simplifies the management of today’s volume of data, and provides the flexibility to scale for all enterprise storage needs.
The full description can be found in the attached whitepaper.
Trying out the BVMS Lite is easy! Download BVMS Lite from the downloadstore and use the quick installation guide to set-up the system. BVMS Lite contains 8 video channels, 2 workstations, 1 DVR, 2 keyboards, and 1 intrusion panel and can be used without a time limit. BVMS Lite can be expanded to 42 channels using license extensions.
A step-by-step instruction on how to install the BVMS Lite license can also be found as an attachment to this page.
This troubleshooting guide, will guide you through the recovery steps of an DIP, without video data loss
General note: Using a Bosch DIP system without video data disks is a non supported use case, its mandatory to equip the system with data disks to recover the system.
Step 1 - Preperation
Download the attachment repair.zip and unzip the content
Prepare an USB-stick, rename it to SCRIPT
Copy the repair.txt extracted of the attachment on the USB-stick
Insert the USB-stick into an USB-slot of your machine
Insert the BOSCH r ecovery DVD into the DVD-drive
Step 2 - Create RAiD1
Boot the machine and enter the Intel RAiD MENU pressing CTRL + I
Navigate to CREATE RAiD VOLUME and hit enter
Set RAiD level to RAiD1(Mirror), navigate to CREATE VOLUME and hit enter
Exit the RAiD controller, navigate to EXIT and hit enter
Reboot the machine (e.g. press CTRL + ALT + DEL)
Step 3 - System Recovery
During the reboot, boot from DVD, press ENTER as the line will displayed
In the System Management Utility, click on CONSOLE
Type into command line "diskpart.exe" hit enter
Type into command line "list volume" hit enter and search for your USB-stick called SCRIPT, note down the assigned drive letter (LTR)
End diskpart.exe by typing on the command line "exit" hit enter
Type into the command line "diskpart.exe /s [YOUR_USB_DRIVE_LETTER]:\repair.txt" hit enter
Wait until the script has been finished and CLOSE the console
Step 4 - System Recovery
On the System Management Utililty click on SYSTEM RECOVERY (back to factory default)
NOTE: Do not select Initial Factory Setup, this will wipe all existing data!
As the recovery has been completed, click on OK to confirm and reboot
Do not eject the DVD and follow the instructions on your screen to initialize the system.
have you ever wondered how to best transition from the Project Assistant to (B)VMS?
This article aims at providing you a recommendation and the answer is quite simple: Use the Project Assistant to its full extent and once the cameras are connected to the target network, perform a network scan using the BVMS Configuration Client, to add the respective cameras to the system. The remaining fine-grained settings can then be tackled within BVMS.
For details, please check out the attached presentation.
Let us know, if you have further questions and share your comments below.
Your Bosch Security App Team
How can I combine a ISS SecureOS Auto system (providing ANPR functionality) with a BVMS system?
The attached document describes the steps how to configure BVMS and the ISS SecureOS Auto system for achieving watchlist ANPR alarms and recorded ANPR detections into the BVMS logbook.
Time is everything: meetings, public transportation, religion, transactions: the whole world is working because the concept of “time” exists. Within a security (or any other) system this is not different: recording schedules, logging, authorizations, encryption keys, timelines, all of these concepts can exist because of time. As a result, time can either make or break a system: problems can appear only due to a time difference of a couple of seconds between two system components.
The attached document describes how time services can be configured in a BVMS environment.
Workstations, Z4G4, Microsoft License
Is it possible to Activate Windows 10 by phone for Bosch Workstations?
With introduction of Windows 10, Microsoft disable the phone license activation for Bosch Workstations.
Please perform online activation over internet.
Configuration Manager does not display all camera configuration menus for cameras with fimware v7.10+
Upgrade Configuration Manager to v6.20 or higher. It is available on the Download Store
When installing Configuration Manager v6.20.0102 on Windows 10 and error message is received during installation of .NET Framework v4.7.2 that states:
The .NET Framework 4.7.2 is not supported on this operating system.
Windows 10 requires frequent updates that must be installed to keep the system compatible with new software installations. Windows 10 periodically releases a features update package that provides new features and compatibility. These are required for version of .NET framework installation.
Windows 10 release Information
Feature updates for Windows 10 are released twice a year, around March and September, via the Semi-Annual Channel and will be serviced with monthly quality updates for 18 months from the date of the release.
We recommend that you begin deployment of each Semi-Annual Channel release immediately as a targeted deployment to devices selected for early adoption and ramp up to full deployment at your discretion. This will enable you to gain access to new features, experiences, and integrated security as soon as possible.
Above except from Microsoft's Windows 10 Release information document: https://docs.microsoft.com/en-us/windows/release-information/
Option 1 - This option will require an active internet connection.
Using the windows search function (Windows key+S), search for "Windows Update Setting"
Click "Check for Updates"
Install all available updates
Option 2 - This option will not require an internet connection. It will require multiple steps be performed per the Microsoft websites guidelines to create and burn a windows update DVD using a downloadable .ISO file provided directly from Microsoft.
You can find these instructions and links on Microsoft's website here: https://www.microsoft.com/en-au/software-download/windows10
This article shows how to configure Input Alarm and later search for them in the Event search using Web Interface. There are only 3 different search parameters for Event type search, which are "All", "Motion" and "Alarm". Once can search for any alarms during the set time period and channel and in this way indirectly to filter for Input Alarm (if only Input Alarm triggers Recording for a particular channel). It is not possible to directly narrow the search for particular Alarm type (ex. Input alarm).
1.Configure the Input Alarm.
Go to: Settings - Alarm - Input Alarm.
Click Enable and Chose the respective Input (from 1 to 16), then click Record Channel and Save.
Note: The other Settings like Buzzer, Display Mon. A can also be configured but is not a must for performing Even Search.
Schedule the recording.
Settings - Schedule: Chose the days of the week, the time and enable "Alarm"
Set the recoding stream.
Settings - Storage - Recording: Chose the stream to be recorded.
2. Event Search - Chose the respective Camera (that recorded on Alarm Input) and search for "Alarm"
Can I move the BVMS Logbook database to a separate Microsoft SQL Server to ease maintenance or increase the size of the Logbook?
The BVMS Logbook database can be moved to another SQL Server. The attched guide describes the steps that are necessary to migrate the database and describes how to confirm if the migration was successful.
When using Configuration Manager, each device has a status icon.
The method below shows you how to generate an updated certificate for Bosch IP Camera's and VRM Servers
Here we are talking about Certificates, the Icon is colored Yellow with an exclamation mark.
Using the mouse over Tooltip, the device is saying exactly what is wrong with the certificate connection.
VRM on a DIVAR IP 5000:
Right click on the device to Show Certificates, if you wish to view them.
We can see that there are multiple things wrong.
The Cert is not Trusted
Cert Name mismatch.
First is inconsistent date:
All IP devices and PC’s must be synchronized on Date time page (group General)
Second is invalid certificate
First quick look on certificate requirement level, navigate to Preferences -> Configuration Manager -> Access -> Security:
The certificate must just be valid - self signed certificate matching host name/IP address will be sufficient.
We need to generate a new certificate on Certificate page.
Clicking "Generate certificate" button:
should open a certificate creation dialog - most important options are matching common name and matching validity time.
After the certificate is created correct usage must be set as shown below:
IP Camera Certificate
To apply changes VRM must be restarted.
If certificate requirement is higher, then a validatable chain of certification must be used (This would be setup by a System Integrator or IT Administrator):
Trusted - the signing entity CA (e.g. VeriSign) must be trusted on target PC
Issued by this CA - There is a Micro CA setup on this PC.
The Bosch Video Client is a 32bit application, CFM 5.50 and newer are 64bit applictions. 32bit applications can only R/W 32bit files (where as 64bit applications can R/W to both 32 & 64bit files), so in order for BVC to access the CFM database, this database also needs to be 32bit.
If you need to configure newer devices with newer FW, you will need to install the relavant CFM version (e.g. CPP 7.3 Camera with FW 7.10.xxxx would require min CFM 6.20.xxxx), by installing the new CFM this will upgrade the original database to 64bit.
Leading to an issue that BVC can not open the database!
Reinstall CFM <5.5.x once more which will cause the database to be migrated back to 32bit.
Strong database encryption must not be activated, otherwise BVC will fail to start.
Microsoft Event Logging, when an error occurs, the system administrator or Integrator must determine what caused the error. The operator can then use the event log to help determine what conditions caused the error and identify the context in which it occurred.
Starting Event Viewer
The procedure for starting Event Viewer depends on your starting point, e.g. windows key + R type in ”eventvwr.msc” hit enter.
With the decent administrative access, you can select any computer in your network to view that Microsoft system event logs.
To select computers in Event Viewer:
In the top of the console tree, right-click Event Viewer (local), and then click Connect to another computer.
Enter FQDN/NetBIOS name or browser to the regarding machine
Adjusting Event Viewer Settings
In the console tree, right-click the appropriate log file, and then click Properties. Click the General tab.
Saving Event Logs
In the console tree, right-click the appropriate log file, and then click Save Log File As. Navigate to the subfolder in which you want to save the file, type a name for the file, click the file type, and then click Save.
Clearing Event Logs
In the console tree, right-click the appropriate log file, and then click clear all Events. You are prompted for whether you want to save the log to a file before clearing it. Click “Yes” to save a log and clear all events. If you click No, the log is not saved, but all events are cleared from the selected Event log. If you click Cancel, the request to clear the log is canceled.
Viewing Event Details
In the console tree, right-click the appropriate log file. A list of events in the log file is displayed in the details pane of Event Viewer. Click a specific event in the details pane to display the Event Properties dialog box and details about the event.
In the console tree, right-click the appropriate log file, and then click Properties. Click the Filter tab. Type the appropriate information that you would like to filter.
In the console tree, right-click the appropriate log file. On the View menu, click Find. Type the appropriate information that you would like to find in the dialog box, and then click Find Next.
An event that indicates a significant problem such as loss of data or loss of functionality. For example, if a service fails to load during startup, an Error event is logged.
An event that is not necessarily significant, but may indicate a possible future problem. For example, when disk space is low, a Warning event is logged. If an application can recover from an event without loss of functionality or data, it can generally classify the event as a Warning event.
An event that describes the successful operation of an application, driver, or service. For example, when a network driver loads successfully, it may be appropriate to log an Information event. Note that it is generally inappropriate for a desktop application to log an event each time it starts.
An event that records an audited security access attempt that is successful. For example, a user's successful attempt to log on to the system is logged as a Success Audit event.
An event that records an audited security access attempt that fails. For example, if a user tries to access a network drive and fails, the attempt is logged as a Failure Audit event.
The events themselves are what we’re trying to see, of course, and their usefulness can range from really specific and obvious things that you can fix easily to the totally undefined messages that don’t make any sense and you can’t find any information on your preferred search engine. example:
The regular fields on the display contain:
Log Name – while in older versions of Windows everything got dumped into the Application or System log, in the more modern editions there are dozens or hundreds of different logs to choose from. Each Windows component will most likely have its own log.
Source – this is the name of the software that generates the log event. The name usually doesn’t directly match with a filename, of course, but it is a representation of which component did it.
Event ID – the all-important Event ID can actually be a little confusing. If you were to Google for “event ID 122” that you see in the next screenshot, you wouldn’t end up with very useful information unless you also include the Source, or application name. This is because every application can define their own unique Event IDs.
Level – This tells you how severe the event is – Information just tells you that something has changed or a component has started, or something has completed. Warning tells you that something might be going wrong, but it isn’t all that important yet. Error tells you that something happened that shouldn’t have happened, but isn’t always the end of the world. Critical, on the other hand, means something is broken somewhere, and the component that triggered this event has probably crashed.
User – this field tells you whether it was a system component or your user account that was running the process that caused the error. This can be helpful when looking through things.
OpCode – this field theoretically tells you what activity the application or component was doing when the event was triggered. In practice, however, it will almost always say “Info” and is pretty useless.
Computer – on your home desktop, this will usually just be your PC’s name, but in the IT world, you can actually forward events from one computer or server to another computer. You can also connect Event Viewer to another PC or server.
Task Category – this field is not always used, but it ends up basically being an informational field that tells you a bit more information about the event.
Keywords – this field is not usually used, and generally contains useless information.
As a rule of thumb (common way of doing), you should try searching by the general description, or the Event ID and the source, or a combination of those values. Just remember that the Event ID is unique for each application. So there is a lot of overlap and you can’t just search for “Event ID 122” only. This is because users might find the list is too large and too general, your specific search aspect might not fit your issue.