Icon--AD-black-48x48Icon--address-consumer-data-black-48x48Icon--appointment-black-48x48Icon--back-left-black-48x48Icon--calendar-black-48x48Icon--center-alignedIcon--Checkbox-checkIcon--clock-black-48x48Icon--close-black-48x48Icon--compare-black-48x48Icon--confirmation-black-48x48Icon--dealer-details-black-48x48Icon--delete-black-48x48Icon--delivery-black-48x48Icon--down-black-48x48Icon--download-black-48x48Ic-OverlayAlertIcon--externallink-black-48x48Icon-Filledforward-right_adjustedIcon--grid-view-black-48x48IC_gd_Check-Circle170821_Icons_Community170823_Bosch_Icons170823_Bosch_Icons170821_Icons_CommunityIC-logout170821_Icons_Community170825_Bosch_Icons170821_Icons_CommunityIC-shopping-cart2170821_Icons_CommunityIC-upIC_UserIcon--imageIcon--info-i-black-48x48Icon--left-alignedIcon--Less-minimize-black-48x48Icon-FilledIcon--List-Check-grennIcon--List-Check-blackIcon--List-Cross-blackIcon--list-view-mobile-black-48x48Icon--list-view-black-48x48Icon--More-Maximize-black-48x48Icon--my-product-black-48x48Icon--newsletter-black-48x48Icon--payment-black-48x48Icon--print-black-48x48Icon--promotion-black-48x48Icon--registration-black-48x48Icon--Reset-black-48x48Icon--right-alignedshare-circle1Icon--share-black-48x48Icon--shopping-bag-black-48x48Icon-shopping-cartIcon--start-play-black-48x48Icon--store-locator-black-48x48Ic-OverlayAlertIcon--summary-black-48x48tumblrIcon-FilledvineIc-OverlayAlertwhishlist

Important Cookie Information

This website uses absolutely necessary cookies. If you consent to the use of convenience cookies, please click “Yes, I agree.” By clicking on “Privacy Settings.” you can change this setting at any time and withdraw your given consent. Icon down see more You can find detailled information in our Privacy Policy Icon forward-right
Icon up see less

Bosch Building Technologies Community

    cancel
    Showing results for 
    Search instead for 
    Did you mean: 

    Security: Video

    Sort by:
    Friday
     BOSCH and NetApp are partners and BOSCH is offering NetApp E2800 Simplex and Full-Duplex iSCSI Storage device variants. The controller Frimware is no longer a special OEM branded BOSCH unique firmware but the regular firmware offered from NetApp NOW page https://mysupport.netapp.com/NOW/download/software/eseries_cfw/11.40.3/download.shtml can be used by BOSCH customes for E-Series with the BOSCH submodel ID (356). The controller Firmware version is not released by BOSCH, but BOSCH is testing offered Firmware form NetApp from time to time. Whenever there are important bug-fix or for operation relefant fixes, NetApp will inform BOSCH. Whenever a newer E2800 contorller firmware is ranked as tested, BOSCH will announce that here in the Knowledge Base as well. Right now (status 2018-12-14) BOSCH can confirm that the E-Series SANtricity ® OS 11.40.3 package can be used which includes:  
    View full article
    2 weeks ago
    +++ Update Project Assistant 1.2: Step 4 - Option B +++ Intro: The Project Assistant offers two ways of importing existing project data: Option 1) Importing a .bpassist file, which was exported from the app at some point and which contains all information and data ever created/entered inside the app for that specific project. Simply select the "Project Assistant" mode >> click "continue" >> and press "import". Option 2) Importing from a tab-separated text file. This option may be useful, if you have existing project data, e.g. in an Excel spreadsheet, which you want to transfer into the Project Assistant for further use. This article deals with option 2 and explains the steps potentially needed before you can refer to the steps explained in the following Youtube video ("Import from file"). Let's assume you already have existing project data prepared in an Excel spreadsheet and you want to transfer that data into a format that can be imported to the Project Assistant Go to the Bosch Security Systems DownloadStore and download the provided template file "example_project_import_report_template.txt" Import the template file into Excel by opening the template file with Excel and following these steps:  Select "delimited" as well as "My data has headers." Select "Tab" in the Delimiters section and finish up the Excel import by pressing "Finish". [Option A] According to the provided data columns, copy and paste your existing data from your initial spreadsheet file into the template file (you do not need to populate every column of the template) [Option B] This option works the other way around. Use the Project Assistant header tags, e.g. [ip], [mac], etc., which you can find in the template file and add these tags to the column headers in your initial Excel spreadsheet (cf. screenshot below). The Project Assistant is capable of searching the .txt import file for these tags and of filtering out the corresponding columns (no matter the order of the columns). Go to "Save As" in Excel and save the newly populated template file as a "Unicode Text (*.txt")" file   Transfer the file to where you can find it with the Project Assistant and start the app Create a new project Set a password for the project itself as well as default passwords for the cameras that you would like to assign That's it - Now it is time to refer to the Youtube video mentioned above Enjoy using the Project Assistant and feel free to share your feedback with us!  
    View full article
    a week ago
    For larger projects, where many cameras need to be commissioned, the question might come up on how to tackle it in the most efficient way using the Project Assistant. In the end, a Project Assistant file can comprise up to 500 cameras. Especially if multiple contributors perform the commissioning step in parallel, you need an appropriate approach. For visualization reasons, let's use a simple example. Let's imagine we have a project that comprises 500 new cameras in total. 250 cameras for building A and another 250 cameras for building B. Here are two options: Creating multiple (sub-) projects and merge them in Configuation Manager If you cannot use Dropbox for synchronisation via the cloud, you can simply create 2 projects - one for building A and one for building B. Both projects can be prepared ahead of time, e.g. in the office, and exported in order to share them. Sharing the exported as well as encrypted project files can be done via E-mail, thumb drive, any of the major cloud storage services, etc.*. Now let's assume that there is one contributor working on building A and one working on building B. After each contributor has commissioned his or her 250 cameras each, they can themselves export the project files. To re-combine or merge both sub-projects, we have introduced a Project Assistant project file import feature in our Bosch Configuration Manager 6.10. This feature allows you to conveniently import multiple project files at once and to easily integrate them into your existing system structure. Please, check out the corresponding "How to import project files into Configuration Manager 6.10" article in this community. * Restrictions due to project file size might apply depending on the sharing medium. The synchronization functionality is only available for Dropbox. Using the Dropbox Synchronization feature This feature let's you plan and preprare a project ahead of time, e.g. in the office, which can then be shared via Dropbox with multiple other contributors as needed. That means everyone that was "invited" to work on this project has access to the same project file, where there is only one "master" version residing in the cloud that is accessed and synchronized via Dropbox. Consequently, you can avoid managing multiple versions of the same project file. Therefore, depending on the internet connectivity of all contributor's devices, you can see the real-time progress of the project, no matter if you are in building A, building B or even in the office. All updates to the project are immediately synced via Dropbox among all contributors. If you want to know how to setup it up, please check out the following videos:   Of course, the Project Assistant project file import feature in our Bosch Configuration Manager 6.10 is also available for futher configuration and system integration for this option, as well.
    View full article
    3 weeks ago
     In August 2018 (10-08-2018) the VRM version 03.71.0029 was released. The Video Recording Manager 03.71.0029 is fully supported with BVMS 8.0 and Product Management of BVMS and VRM recommend to use this VRM version instead of the former Release version of VRM 03.70.0056. Changes / Bug Fixes: One of the main bugfix reasons to use VRM 03.71.0029 is a fix in regards to correct display and replay of recorded clips in continous and alarm recording mode. This fix is listed on page 2 of hte attached Relase Letter. For Troubleshooting and support reasons it is essential to double-check a reported gap in recording and to analyze on Level 2 and Level 3 support side what circoumstanced could lead to a video gap. See in the following chapter what kind of data a trained BOSCH partner, Installer or Video expert should provide to the BOSCH Technical Support to advise on next steps. The data described here below can and should be collected before the software VRM is changed and updated to a latger version. Note: Video Recording Manager version 03.71.0029 is not the latest available version of VRM, but in combination with other 3rd party implemantation or usage of special BOSCH VMS software version (e.g. BVMS 8.0) this VRM version 03.71.0029 may be required. VRM logging to collect for in depth expert troubleshooting In certain situations and troubleshooting scenarios extended logfiles might be required. The BOSCH Level 1 and BOSCH Level 2 team will assist all users on how to collect these data and cooperate with the BOSCH Level 3 Support where needed. Backup the configuration of BVMS and VRM (BVMS elements and VRM config.xml file) Enable debug logging of the VRM Depending on the used Configuraiton Software the debug logging need to be enabled to get an extended logging informaiton. In case a gap in recording happened in the past it is anyhow helpful to enable the debug logging for a defined time for future incidents. To analyze the already occured video recording gap the available VRM logging must be collected. Depending on 32-Bit or 64-Bit version of the VRM software, the loggings are found in the "primary" or "secondary" sub-directory structure. Surch for     ...\Bosch\Video Recording Manager\VRM Server   folder at your VRM server to find a similar directory view like shown in the screenshot here below: Inside the directory "log" the standard logging data of the VRM are found and need to bre collected. In addition to the standard logfiles of the relevant day, the debug logging from a defined time period need to be provided in case debug logging was enabled prior to an incident. Here the "debug" logfiles are found: The debug loggins are saved in a special directory "debug". The Spanhistory logging does provide details of the storage usage. It describes which internal "storage block" was used. It describes the IP of the target, the LUN and the block used for a recording. The Spanhistory of the day where the recording was done and shows issues (e.g. the video reocriding gap), the related spanhistory logfiles is required. As seen in an earlier screenshot above the VRM configuration file is found in the directory:     ...\Bosch\Video Recording Manager\VRM Server\primaryAll versions of the config.xml need to be provided to the Technical Support.  
    View full article
    3 weeks ago
      Issue: The Bosch VRM Monitor page does not open correctly, but instead displays an Error. Any Replay client requesting video from the  Bosch Video Recording Manager service, only receives the Time-Line but the video is alway Black. Bosch VRM by default uses Ports 80 & 443. In most cases the problem is caused by another web server (e.g. IIS) that is installed on the same machine and is also making use of the default web ports 80 & 443. Related product: Bosch Video Recording Manager (VRM) Bosch Video Managment System (BVMS) Bosch Video Client (BVC) Bosch Video Security Client (VSC) Any Replay Client/ Managment System which accesses recorded video data via HTTP/HTTPS Solution: Disable any of the other web services or change the default Ports they are using.
    View full article
    3 weeks ago
     This article explains how to exchange the battery on the DIVAR Hybrid and Network in a safe way.
    View full article
    ‎10-10-2018 03:08 PM
    rectrieve live video with Video Security Client Software for Windows version 2.2
    View full article
    100% helpful (1/1)
    ‎11-07-2018 08:31 PM
    MTU and MSS     MTU stands for "Maximum Transmission Unit." MTU is a networking term that defines the largest packet size that can be sent over a network connection. The MTU is typically limited by the type of connection, but may sometimes be adjusted IT network settings. The typical value of the Network MTU is 1514 Byte. If a system sends packets over an Ethernet network that are larger than this size, the data will be fragmented into smaller packets. When referring to Ethernet MTU this includes 4 Byte checksum. The  1514 Byte is the interface MTU without the Ethernet Checksum. In cae there are limitations by the type of connection, the packets will then need to be reassembled on the receiving side (e.g. Bosch video management software or Bosch hardware decoder). However, it can be beneficial to optimize the packet size on the sender side (e.g. IP camera) to the exisitng network infrastructure. As MTU maximum packet size is layer 1 related, the IP MTU that you can be adjusted at the BOSCH device configuration (Configuration Webpages or with the help fo BOSCH configuraiton software like "Configuraiton Manager"). The BOSCH GUI refers to this as “Network MTU”. BOSCH products can manage fragmented data. MSS stands for "Maximum Segment Size" The MSS value is calculated from the MTU. MSS = MTU – (layer 3 TCP header [20 Byte] + Layer 2 IP header [20 Byte]+ Layer Ethernet 1 [6+6+2 = 14 Byte]) For example looking at CPP 6 Platform – like FLEXIDOME IP panoramic 7000 MP in Firmware version 6.50.0128 you can adjust and find the following values: Network MSS (in Byte) - default value = 1460 iSCSI MSS (in Byte) – default = 1460 Network MTU (in Byte) – default = 1514   MTU and MSS can be adjusted at all released firmware versions 4.x and later. CPP-ENC CPP3 CPP4 CPP5 CPP6 CPP7 CPP7.3 yes x x x x x x x No               Here some screenshots as example based on Firmware 06.50.0128  
    View full article
    100% helpful (1/1)
    ‎11-06-2018 12:51 PM
    Symptoms When scanning a QR or Data Matrix code on a label using the Project Assistant app, it can happen that you get an error message that the MAC address cannot be found (1) or that only part of the address is correctly extracted (2). Diagnosis  First of all, there are different types of labels: product labels (on the device) box labels (on the outside of the box/packaging) installer / UX labels (inside the box /packaging) Symptom (1) can only happen when scanning a product label because some QR or Data Matrix codes do not contain a MAC address, depending on the product, even though the MAC address is available in plain text right next to the code.   The box and installer label codes, however, always contain the MAC address information. Symptom (2) can happen when scanning certain installer labels due to legacy formatting. Solution We have further standardized the labels so that the symptoms mentioned above will be resolved. There will be a transition period, however. As an alternative for symptom 1, you will have smooth experience when preferably scanning the box label. If you encounter symptom 2, we ask you to enter the MAC address manually or use the December 2018 release of the Project Assistant (version 1.2) PS: For full transparancy on QR code / Data Matrix content and/or troubleshooting purposes, you can use conventional code scanning apps available in the resepective app stores.
    View full article
    ‎11-05-2018 11:35 AM
    The attached technical notes give a short introduction to scripting alarm and counter tasks with Intelligent and Essential Video Analytics. It also provides a broad selection of example scripts for explanation as well as including real world application examples.
    View full article
    100% helpful (1/1)
    ‎10-31-2018 02:34 PM
    Combined firmware package 6.50 – applicable to all platforms The Release Letter of the combined firmware package for all platforms 6.50.0620 provides information about the dependencies between firmware versions for a better understanding of the upgrade process of devices with older firmware. CCP4 and CPP6 devices: Due to an internal file system being introduced to CPP4 and CPP6 since firmware 6.10 and architectural changes thereof, a direct upgrade from firmware below version 6.10 to latest firmware is only possible via intermediate firmware 6.1x. CPP4 cameras with firmware versions below 6.10 need to upload this package twice. For example, when having firmware 5.92 on a CPP4 device, you need to load the CPP all common firmware file two times: >  First time this is loaded the device will be updated to the 6.11.0021 which is part of the common file. >  Second time you load the common firmware file, the update to 06.50.0128 will be performed. CPP6 cameras with firmware versions below 6.10 need to upload the separate firmware version 6.1x first to receive the latest firmware version. This means that intermediate firmware version 6.1x for CPP6 needs to be requested from your technical support. A support ticket to Level 3 team at MKP PRM group via the support ticket system is needed. In case we see a high demand for that a new combined firmware file might be created by PRM. Only after receiving and uploading firmware 6.1x, you can upload combined firmware package for all platforms 6.50.0620 or CPP6 specific firmware  6.50.0128.  CPP5 devices: This combined firmware cannot be applied to CPP5 products with firmware version older than 5.91. It is required to upgrade to intermediate firmware 5.91 first This means that intermediate firmware version 5.91 for CPP5 needs to be requested from your technical support. Only after receiving and uploading firmware 5.91, you can upload combined firmware package for all platforms 6.50.0620 or CPP5 specific firmware  6.30.0059. Note: Upgrading from versions lower than 5.5x To upgrade to a newer firmware version using this combined firmware package, firmware versions before 5.5x require an intermediate update cycle using the respective platform firmware version mentioned above. Restrictions: This firmware and its included platform firmware builds are not applicable to MPEG-4 products. The final firmware version for VIP-X1600-XFM4 modules is FW 5.53. No newer firmware will be provided for these modules. Configuration Manager cannot upload this Combined Firmware file to VIP-X1600-XFM4 modules. Use the module’s web page instead for uploading; or use the separate firmware file. The final firmware version for CPP3 devices is FW 5.74. No newer firmware will be provided for these products. The Combined Firmware file does not load onto VG4 AUTODOME or AUTODOME Easy II via the browser when running a firmware version before 5.52.0017. The specific platform file should be used instead. (Note: In case any link might not work to the current DownloadStore, see attached a copy PDF of the Release Letter.) How to get and request a BOSCH Legacy Firmware: The procedure to request and get an legacy firmware that is no longer online in the web is as follows: Customers are kindly requested to reach out to the local BOSCH Support (L1 and L2 team). Bosch Level 2 will ask for the exact BOSCH Commercial Type Number (CTN). The local BOSCH team can check the Global End of service date. The project background (How many of these devices/cameras) need to be collected.  The relevant BOSCH Technical Support (e.g. Level 2) can explain and check if there is the chance to update the project and included management software in order to be able to use the latest BOSCH device firmware as the goal is to have a non-vulnerable product in productive environments. In case there is no newer firmware available (hardware was discontinued), a commercial hardware upsell can be recommended. In general all firmware that is not available on the product catalog, and for all firmware files that are ranked to have vulnerabilities, this need to be documented in a Technical Support case. In case legacy firmware is anyhow needed and requested by our customers, the Bosch Technical support will start an approval flow. The BOSCH Level 3 Technical Support will provide a form/document that must be signed by the installer/endcustomer. See an example PDF (empty) "Example_Aged_Software_Release_form.pdf" attached to this article. Such a form will be prepared by the BOSCH Level 3 Technical support team and provided to our customer/installer in order to confirm that legacy firmware is then used on the risk of the installer and customer (See text and legal note in the PDF). In the future BOSCH plan to introduce and setup a self-service portal for all customers to simplify this process. ___________________________________________________________________________ The above mentioned combined firmware 6.50 supports: CPP7.3 HD and UHD cameras update from FW 6.40 or newer to latest FW 6.50 CPP7 UHD cameras update from FW 6.30 or newer to latest FW 6.50 CPP6 UHD cameras update from FW 6.10 or newer to latest FW 6.50 CPP5 encoders update from FW 5.91 or newer to latest FW 6.30 CPP4 HD cameras update from FW < 6.10 to intermediate FW 6.11 update from FW 6.10 or newer to latest FW 6.50 CPP3 cameras and encoders update from FW 4.54.0026 or newer to latest FW 5.74 CPP-ENC VIP-X1600-XFM4 encoders: update from FW 4.2x or newer to latest FW 5.53 VJT XF and VJD-3000 update to latest FW 5.97 The combined firmware package includes the following build versions: CPP7.3 FW 6.50.0128 CPP7 H.264 6.50.0128 CPP6 H.264 6.50.0128 CPP5 H.264 6.30.0059 CPP4 H.264 6.50.0128 CPP4 H.264 6.11.0021 CPP3 H.264 5.74.0010 CPP-ENC H.264 5.97.0005 for VJT XF family, VJD-3000 and VJC-7000 CPP-ENC H.264 5.53.0004 for VIP X1600 XFM4 For detailed description please refer to the separate release letters. Customers can upload such combined firmware packages by using multi-select in the Configuration tool "BOSCH Configuration Manager" (currently available in version 06.01.0157 at the BOSCH DownloadStore or Product catalog > Video Software > Video Management Systems > Configuration Manager) When using the multi-select option in Configuration Manager, please make sure this combined firmware package for all platforms can be uploaded to all the devices selected and there are no additional requirements or intermediate steps needed for any of the devices in question. This article has status of 31st of October 2018 and changes in this procedure might be introduced. When changes are done, then this article will be updated. Therefore check this article from time to time.
    View full article
    100% helpful (2/2)
    ‎10-29-2018 04:58 PM
    Possible Communication Issue between BVMS 8.0 Central Server and Video Recording Manager (VRM) 3.70 and 3.71 with BVMS 8.0 installed on different Servers. Problem Identification Communication can get interrupted and configuraiton might fail if the below desribed actions are not performed. If your system is affected or not is described here as follows: There can be authentication issues between the BVMS Central Server and the Video Recording Manager in case they are installed on different Servers. It is possible to see reports at the BVMS 8.x system alarms that VRM reports wrong version Please check in the VRM debug logging if the following logline indications can be found CONFIG;DEBUG;SENDING XPATH /SYSTEM/DEVICES/DEVICE as well as HAS NO CONFIGURED NODE, SET TO CONFIGURED CONFIG;INTERNAL;/SYSTEM/DEVICES CHANGED IN CONFIG. DEVICEID= [DEVICE IP]\0;SYSINFO;INTERNAL;LINE 1 HAS NO CONFIGURED NODE, SET TO CONFIGURED Solution In general please keep in mind, that it is strongly recommended to use VRM 3.71.0029 with BVMS 8.0. Do not use any older VRM version like 03.71.0022. The 03.71.0029 and Releaseletter is available at the BOSCH DownloadStore (status update 2018-10-26). https://downloadstore.boschsecurity.com/FILES/Setup_VRM_03.71.0029_win32.zip Release Letter: https://downloadstore.boschsecurity.com/FILES/Bosch_Releaseletter_VRM_3.71.0029.pdf At the VRM system / server, please check and ensure that the following Microsoft software packages are pre-installed: .NET framework 4.6.2 or higher Redistributables for Visual Studio 2015 In case one component is missing, please perform the following steps: Download the missing Microsoft components. Note: When using BVMS 8.0 the VRM is typically a 32-Bit VRM software. Therefore the 32-Bit Microsoft packages are needed. Component that was seen as missing is the >>   “Visual C++ Redistributable for Visual Studio 2015”            https://www.microsoft.com/en-US/download/details.aspx?id=4814 Please choose the 32-Bit version of that when using with 32-Bit VRM and the >>  .NET framework 4.6.2 or higher (NDP462-KB3151800-x86-x64-AllOS-ENU.exe)       https://www.microsoft.com/en-US/download/details.aspx?id=53344 Stop the VRM (rms.exe) service in Windows services  Install those components with Administrator rights at the VRM server Reboot the server after installation of the Microsoft components Check if the VRM service is running and if needed Re-Start the VRM (rms.exe) service Check that the combination of messages are not longer seen in the VRM debug logging The VRM package is enhanced and useres should no longer run into this issue with VRM 3.81 and newer versions. Please be aware that BVMS releases are tested with certain VRM verions. This still can offer to install a newer VRM than originally rolled-out in the BVMS overall installer. For all VRM versions 3.7x and below 3.81 it is needed to add this packages.
    View full article
    ‎10-29-2018 09:18 AM
    The attached file explains how BVMS can be configured to connect to an LDAP (or Microsoft Active Directory) and use it as a base for user authentication.
    View full article
    ‎10-29-2018 07:34 AM
    Do you want to know more about designing a BVMS system?
    View full article
    ‎10-22-2018 05:03 PM
    Learn how to design a network on which BVMS can run comfortably.
    View full article
    100% helpful (2/2)
    ‎10-16-2018 06:35 PM
    Introduced Firmware signature and firmware file encryption to protect IP cameras
    View full article
    100% helpful (1/1)
    ‎10-10-2018 03:42 PM
     Bosch software is distributed via the Bosch website, but can also be re-distributed by Bosch partners. It is important for the system-installer to check if the installation file he or she has received, matches exactly with the output of the engineering process. There are several risks that, in the distribution path, changes are made to the installation file. Keyloggers or other spyware could be added to the installation, or in theory video surveillance footage could be routed to external resources. The attached document describes how the integrity of software can be checked.
    View full article
    ‎10-09-2018 03:50 PM
     BVMS customers can download camera updates free of charge, in order to integrate approved, third-party cameras. BVMS scans for third-party cameras, automatically configuring motion and other key events; it also enables installers to configure the most important settings for third-party cameras from a single user interface, without the hassle of having to access the websites of other camera manufacturers. The attached files include a list of compatible cameras and the ONVIF mapping files for each specific BVMS version.
    View full article
    ‎10-05-2018 07:00 AM
      The attached document describes the different components that Bosch Video Management System offers to to establish a connection between Bosch Video Management System and a 3rd party management system. This description helps you in writing your own commands for controlling Bosch VMS from inside your management system.   
    View full article
    100% helpful (3/3)
    ‎10-02-2018 01:55 PM
    The BVMS Operator Cliet can be automatically logged in by using parameterized startup. For this, a new shortcut to the OperatorClient.exe needs to be created, and the target of the shortcut needs to be adjusted. The text between ** needs to be adjusted to the specific situation. "*BVMS installation directory*\bin\OperatorClient.exe" /user="*username*" /password="*password*" /connection="*ip address*" For example: "C:\Program Files\BOSCH\VMS\bin\OperatorClient.exe" /user="Admin" /password="password123" /connection="192.168.20.120" The connection parameter works with BVMS 9.0 and newer. The username and password parameters are working from BVMS 5.0 onwards. The username and password are stored as cleartext in the target of the shortcut, which could be considered a security risk.
    View full article