Manitou
Version 2.1.39
Release Date: ??????
Special Upgrade / Install Instructions
Customers should be aware that the Legacy BoldNet Silverlight Client will no longer be supported with Manitou 2.1., We will continue to support the SOAP web services but the Silverlight interface is being retired.
The Distributer will not update the Manitou Web Server and BoldNet NEO web files.
You will need to run the ManitouWeb_setup.exe on each of the Manitou Servers running the web service, (IIS), to update the Manitou Web Server and BoldNet NEO web sites.
As of January 23rd, 2020 you can find the 2018 Census cartographic boundary files available in shapefile format for DBManager at this URL: https://www.census.gov/geographies/mapping-files/time-series/geo/carto-boundary-file.html
Important change to updating customers with accounting!
Accounting files will no longer be included in the patch and will need to be updated using packages. Package 90 has been added that has the x32 Router and RouterConfig. The individual files based on the customer accounting type will need to be updated from their respective packages. Package 91, Sedona Cloud (x64). Package 92, Sedona (x32). Package 93, Navision. Package 94, Quickbooks.
Updated install information for VCC
Patch 20 includes the new VCC and only distributes the BASE VCC. The old VCC will need to be completely uninstalled and the VCC folder under Manitou will need to be deleted BEFORE the new VCC is installed. Support will need to be contacted for updating individual device type drivers according to what the customer is using and has paid for. Please see additional VCC documentation in the BoldWiki BEFORE upgrading a customer that is using VCC.
There is a database migration for the PSIM changes. This took approx 2 sec to run on our large test system.
VCC VERSION 3.0 is now available in release. If a customer chooses to go to VCC 3.0 they will need to re-install the base and every single video driver they use so that the version for all their VCC is 3.0
Download Files
Contact the Support team
Supported Environments:
Minimum System Requirements:
- Windows Server 2012 R2
- 8 GB Memory
- Dual Core Processor
- MS SQL Express 2012 / MS SQL Server 2012
- 50 GB of Free Space for Database
- Windows 10 for Operator Workstations
TLS 1.2 is now supported and ALL servers should be configured to support this. The Nartac IIS Crypto tool is very useful for verifying this is supported.
NET 4.8 is required for full compatibility with current updates of the PBX server and several other Manitou components.
https://docs.microsoft.com/en-us/dotnet/framework/get-started/system-requirements
If you are updating Media Gateway, PBX Server, or LocationServer please make sure that the latest Microsoft OLEDB drivers are installed. This should just be done on ALL servers. https://docs.microsoft.com/en-us/sql/connect/oledb/download-oledb-driver-for-sql-server?view=sql-server-ver15.
.Net 4.8 is needed for VCC on workstations that use ONVIF and/or Avigilon 7 drivers
Manitou Web Clients and BoldNet requires the use of a certificate issued by a valid certificate authority. We do not support the use of invalid self-signed certificates in a production environment.
End-of-Support:
Microsoft periodically ends support for some products. Due to this we can no longer support the following:
- Windows Server 2008 or older
- MS SQL Server 2008 R2 or older
- Windows 7
- Windows XP
Features and Enhancements:
(E) [] ()
Product:
Issue:
Change:
Fixes:
(F) Updated SedonaCloud integration to retrieve all items [] (36722)
Product: SedonaCloud
Issue: SedonaWeb 2.0 has limit of 500 records in a response. When Manitou is retrieving A/R items, there can be more than that. Must change retrieval so it gets all of them when more than 500.
Solution: Retrieves items in batches now until complete.
Known Issues:
Older custom reports show From/To dates as 1/1/1900
Product: Manitou Web Client
Issue: Custom Templates built against existing reports before 2.1 show the From/To date as 1/1/1900
Solution: Current work around is to delete the existing custom template and re-create it.
Reference Chart (Legend)
Bold will be introducing some terms and abbreviations in these release notes. Some of them will be familiar, but some are new. Please refer to the table below to reference the description of the abbreviation or term.
|
Term/Abbreviation |
Description |
|
BNN |
BoldNetNEO |
|
BNM |
BoldNet Mobile |
|
BNS |
BoldNet Silverlight (legacy) |
|
Card |
A boxed area on any of the Manitou Web Client/BoldNetNEO screens which contains data |
|
IGW |
Integration Gateway |
|
MDK |
Manitou Developer Kit (REST API for integration development) |
|
MGW |
Bold MediaGateway |
|
MWC |
Manitou Web Client |
|
NFM |
Bold NotifyMe |
|
OWS |
Operator Workstation Visual Basic (legacy) Client |
|
PBX |
Bold PBX Server or PBX Enterprise |
|
SWS |
Supervisor Workstation Visual Basic (legacy) Client |
|
UC |
Bold UniversalConnector |
|
VCC |
Video Control Center |
|
N |
New Feature included in this release (may include a set of ITEMS) |
|
E |
Enhancement to an existing feature updated in this release |
|
F |
Fix for an issue reported in previous releases (commonly referred to as a “bug.”) |
|
C |
Clarification on how an item should function |
|
CAS |
Support Case (ticket) number related to reported issue |
|
ITEM |
Product Backlog Item, Feature, User Story, or Bug - Internal tracking number used by Bold in our development management environment (DevOps) |
All items will have a header and format as follows:
Category (N, E, F, or C) Description [CAS/ITEM] (if applicable)
Product:
Issue:
Solution:
