The Meeting Application does not provide all the options it did before and the application does not request any log-in credentials when first started and simply starts.
It was found that the “automatic login” feature in the configuration file was set to ‘true’ so the application logged in automatically. The user that was logged in automatically did not have all required permissions.
Details on the automatic login feature (from Dicentis Software Manual):
By default, the Meeting Application will automatically log in when the windows login username is the same as a username in the Dicentis system. In this case, the authorization rights of this user will be used for the Dicentis Meeting Application.
The default Username is “admin” and the password is empty. The default language is the language of the operating system; if the default language is not available, English is automatically selected.
Disable/enable automatic login to Meeting Application
The automatic login feature can be disabled and enabled as follows:
In Windows explorer, select: C:\Programs (x86)\Bosch\DICENTIS.
To disable automatic login, set the key from true to false.
<add key="ENABLE_AUTOMATIC_WINDOWS_AUTHENTICATION_TO_LOGIN" value="false"/>
To enable automatic login, set the key from false to true.
<add key="ENABLE_AUTOMATIC_WINDOWS_AUTHENTICATION_TO_LOGIN" value="true"/>
... View more
"More information on XML style sheets (XSLT) is available on the web. This is what the voting results template uses.
In order to change the layout, the StyleSheet needs to be changed. Default it is located in C:\ProgramData\Bosch\DICENTIS\VotingResult.xslt, this file can be opened in any text editor, Notepad++ is recommended as it is very versatile.
In order to change the title: Find the line , edit the yellow marked text. E.g. 你好世界'" />.
Changing the image is also possible, but requires a bit more work. The image inside the XSLT file is Base64 encoded (in order to include it as a piece of text), so any image in png or jpg can be transcoded to a Base64 string. There are websites that can do this for you. One of them is https://www.base64-image.de/
Drag an image in the drag & drop field:
Image is automatically converted, click on the “show code” button.
In the pop-up that comes up, hit copy to clipboard (In the section for <img> elements)
Look for <img src= in the stylesheet and replace the existing block of data (The Bosch logo) by the base 64 encoded data.
Be sure the datablock start with a double quote “. So it will look something like this:
And it has to end with a “/>
... View more
When using a fixed IP addresses in a multi-subnet Dicentis system, certain settings need to be made for the system to function well. If the settings are not made correctly, the system can stop functioning & disconnect from the server.
The IP address of the server should lie outside the DHCP scope for the rest of the system, otherwise IP address conflicts may occur.
When using a multi-subnet, a DNS suffix needs to be added to the IP settings of the server in order for the devices in the system to find the server.
In order to use a computer in a Dicentis system to which you want to assign a fixed IP you should make the settings similar to below. The settings should of course match the definitions made for your network.
Start > type “Network Connections” & select
Right-click the network interface, select “Properties”, select “Internet Protocol Version 4” and select “Properties”.
Make sure the fixed IP settings in the next pane are appropriate for the used network configuration.
Select “Advanced”, select the “DNS” tab.
Make sure “Append primary and connection specific DNS suffixes” and “Append parent suffixes of the primary DNS suffix” are selected.
Fill in “DNS suffix for this connection:”. What needs to be filled in here depends on the domain suffix created for this subnet.
For instance, the main DICENTIS subnet is always “parent.bosch.omneo”, but if a device is connected to any subsequent subnets, names can vary.
Make sure the suffix corresponds with the suffix given during the setup for the ARNI for the specific subnet.
Select “Register the connection’s addresses in DNS” and “Use the connection’s DNS suffix in DNS registration.”. Select “OK” to finalise the settings.
A quick test to verify if the settings are correct, is to run the command as in the screen capture below. If you see a list of DICENTIS devices registered in the domain parent.bosch.omneo (and/or other domains in the multi-subnet system) then it is fine. The Bosch-arni is registered twice, once in the “local” domain and a second time in the “parent.bosch.omneo” domain, this is normal.
Start Command Prompt
Change directory to “C:\Program Files\Bosch\DNS-SD\”
Run “BoschDNSSDClient.exe –b _ocasec“ (or “BoschDNSSDClient.exe –B _ocasec”)
Results should look similar to the screenshot below:
If you only see the Bosch-arni registered in “local” domain, the DNS settings are wrong.
... View more
The time on the MMD2's is not the same as the time on the Server PC/Meeting Application and will drift further away over time.
Version(s): all, workaround for always-on systems not needed after v3.00
Explanation & troubleshooting:
In a Dicentis system there is one time server, this is the Dicentis server. It runs a 3 rd party program called “NetTime” which acts as an NTP server for the Dicentis system.
It is possible that the system time is off because there are two or more time servers in the network. Make sure there are no other devices that have a time server running besides the main server PC in the same network.
Time will drift if along with the "Net Time" service, the "Windows Time" service is also running. This service should be turned off on a Dicentis Server:
On the Dicentis server, check if the program "Net Time" is running.
To investigate and troubleshoot NetTime:
Check the settings of the program & make a screenshot of the program's window and the program's Settings window.
Check the logs of the program (Network Time > Settings > Logging level > View - copy the text to a file).
If the system is in no way connected to the internet, the time on the server PC will drift, but the PC should provide NTP information to the MMD2s at start-up prior to v3.00 and periodically after with > v3.00 so Server PC/Meeting Application and MMDs remain in sync.
Make sure that the firewall does not block traffic to & from NetTime.
If the system is connected to the internet, NetTime should be able to connect to 0.pool.ntp.org which is the NTP server configured by default, you can check this is OK by pinging it.
Behaviour prior to version 3.00:
Prior to version 3.00, the Dicentis system only synced with the server during boot-up. The Server will not sync the discussion devices periodically. With version 3.00 and later a periodic sync is added.
This meant that if you keep the system running for a prolonged time, the time will drift on the discussion devices and will most likely be slightly different on each MMD due to variation in the devices' internal clock.
Therefore, it would be advised to periodically power off the system through the Meeting Application & power it on again before the meeting. This is in fact standard advice to spare the devices' screens and limit power consumption.
Workaround for always-on systems prior to version 3.00:
The best way of preventing time drift is to switch off the MMDs. Either by switching off the (A)PS or PoE switches. Once they turn on again they connect to the SW services and the MMD clock will be synchronized with the server.
In this system the MMDs are always on. This will have a negative impact on the product lifetime expectations.
A workaround for the MMD time drift problem is to create a task that is started every day, week, month (whatever the need) that automatically restarts the Dicentis services. Use windows Task Manager to do this.
This task should run the program:
With the argument: RestartServices
Note: The user account that is used to runs the task, requires administrative rights
... View more
Version: <=1.12 but also applicable to other older versions
The APS in question was running on v1.12 and needed to be upgraded to v2.60 and any firmware updates would continually fail (even other intermediate versions). The below procedure is not specific to this update and can also be used for updating from other older versions.
Install the 2.60 release on the Server PC and connect the PC to the APS directly (no network router or switch in-between).
Make sure nothing else is connected to the APS. Make sure the Dicentis services on the server PC are stopped.
When downloading the firmware to the APS it will fail the first time because of the change in name on the APS between version 1.12 and 2.60. Download the firmware again and then it will be fine.
If the update fails a second time, please check the LED behaviour of the APS:
Front LED should show alternating Green/Amber.
If not; switch the APS off and on again and re-try the update.
If the update keeps failing, the problem could also be caused by the PC used in the updating process, try a different PC and connecting cabling and follow the above steps once more.
... View more