¶ Maintenance
¶ General Maintenance
To get the best possible performance from the server, MOG recommends performing a few basic actions:
- Restart the server periodically: MOG recommends that the server is restarted at least once each week, with the best practice being, doing it every five days;
- This operation can be done manually, or through a scheduled automatic restart from our software. Please check the user manual on how to configure this feature;
- To accelerate the reboot process, there is the option of configuring an “Auto Log-On” script, which allows the services to be started without any user input;
- You can run this script by navigating to “C:\MOG\Tools\AutoLogon_Lock” and click on “AutoLogon_Lock.cmd”. If you have not changed the server’s password, please insert “admin”. Otherwise, input the user password correspondent to the MOG user.
- If you experience difficulties on how to perform these operations, please contact our support team.
- Back-up the database: to be cautious in case of a database corruption, it is recommended that you perform a database back-up at least once every two weeks, or every time that a major configuration change is executed. You can also import / export the dashboards in case you need to use your previous dashboard setup;
- To perform a database or dashboard back-up, please check our user manual.
- Restart MOG Control Panel’s services: MOG recommends restarting the control panel’s services regularly. This operation does not have a fixed schedule for the best time to do this, however, it is good practice to execute this operation when the server is idle (not performing any operation);
- Log clean-up: MOG recommends that you perform this operation once every two weeks. To do this:
- Stop all services;
- Click “Open Log Folder” on MOG Control Panel;
- Delete every file and folder present in that folder;
- Restart the services.
- Clean-up assets, flows, and notifications: to improve the user experience, and avoid unnecessary data build-ups, perform a data usage clean-up (which will delete all assets, flows and notifications) every once in a while.
Note: when performing this procedure, data from assets, flows, and notifications will be permanently deleted. Information from assets indexed in collections and from archived ones will also be deleted.
If you wish to completely reset the system, and uninstall / re-install every software component, you should first perform a factory data reset, which will erase all data. Please check the user manual on how to perform this action.
¶ Restore Image
After downloading the recovery image provided by FTP by MOG, follow the instructions in the sections below to create and restore the image.
Note: if you do not have the credentials to log in, please contact our support team.
¶ Create Restore Pen-Drive
-
Run Rufus.exe;
-
Click on the “Select” button to add a recovery image;
-
Click the “Start” button to create the recovery pen.
¶ How to Restore Images on Dell Servers
-
Boot the server and click F11;
-
Select the option “One-shot BIOS Boot Menu” and click “Enter”;
-
Select the pen drive and click “Enter”;
-
On the main screen, click on “Browse for an image file”;
-
Double-click to enter the pen drive;
-
Double-click on the folder where the image is located;
-
Select the first file of the recovery image and click the “OK” button;
-
Click on the “Restore Image” option;
-
Click on the “Next” button;
-
Click on the “Finish” button to start the image restore process;
-
Check the option highlighted below to confirm that the volume data will be overwritten and click on the “Continue…” button;
The restore process will start:
-
At the end of the process, click on the “OK” button;
-
Click the red button to restart the server;
-
A dialog box will appear to reboot or shut down the server. Please, reboot the server.
IMPORTANT NOTE: MOG does not recommend the use of Sysprep under any circumstances, as it will revert the entire operating system configuration, including disabling the pre-installed Windows license by MOG. In case of use, perform the image reset procedure again.
¶ How to Restore Images on Densu Servers
-
Boot the server and click F7;
-
Select the pen drive;
-
On the main screen, click on “Browse for an image file”;
-
Double-click to enter the pen drive;
-
Double-click on the folder where the image is located;
-
Select the first file of the recovery image and click the “OK” button;
-
Click on the “Restore Image” option;
-
Click on the “Next” button;
-
Click on the “Finish” button to start the image restore process;
-
Check the option highlighted below to confirm that the volume data will be overwritten and click on the “Continue…” button;
The restore process will start:
-
At the end of the process, click on the “OK” button;
-
Click the red button to restart the server;
-
A dialog box will appear to reboot or shut down the server. Please, reboot the server.
IMPORTANT NOTE: MOG does not recommend the use of Sysprep under any circumstances, as it will revert the entire operating system configuration, including disabling the pre-installed Windows license by MOG. In case of use, perform the image reset procedure again.
¶ Ecosystem
MOG’s servers and software are part of a bigger ecosystem that makes use of a few specific components that work together in order to deliver the best solution.
¶ Third-Party Apps
MOG’s ecosystem makes use of some third-party apps to execute some of the necessary tasks. These components are:
- Bonjour: allows the creation of groups and is responsible for identifying MOG services broadcasted in the network. It makes use of the mDNS protocol (Multicast DNS), which creates the requirement for Multicast, and for CPUs with an architecture with the SSE3 instruction set;
- RabbitMQ: allows notifications inside MOG products. If the connection to RabbitMQ is lost, a pop-up will appear in the GUI warning the user about it. If you have this issue, please contact MOG support;
- Sentinel License Manager: manages MOG licenses. More in Licensing section;
- Visual Studio Redistributables:
a. 2010 v10.0.30319.01;
b. 2013 v12.0.30501.0;
c. 2015 v14.0.23026.0;
d. 2015 v.14.0.24215.1. - .NET 4.7.2 version or above.
¶ Network
MOG’s services have a few network requirements in order to work correctly.
¶ Network Ports
MOG product’s use a few different network ports for its services and as such, these should be open both on the server’s OS firewall and on your company’s network. (The ports suffered alterations since version 2023.01.00). These ports and its specific uses are:
General Internal Communication
| Port(s) | Protocol | Rule |
|---|---|---|
| 53 | UDP | MOG Network (DNS) |
| 80, 81, 82 | TCP | MOG Services (Web Interfaces) |
| 137 | UDP | MOG Network Discovery (NetBIOS) |
| 427 | UDP | MOG Service Discovery (Service Location Protocol) |
| 808 | TCP | MOG Services (Remote Operation Proxy) |
| 843 | TCP | MOG Services (Policy File Server) |
| 1900, 2869, 5000 | UDP | MOG Network Discovery (SSDP) |
| 1935 | TCP | MOG External Services (Nginx Web Server TCP) |
| 1935 | UDP | MOG External Services (Nginx Web Server UDP) |
| 1947 | TCP | MOG Services (License Manager TCP) |
| 1947 | UDP | MOG Services (License Manager UDP) |
| 3389 | TCP | MOG Network (Remote Desktop TCP) |
| 3389 | UDP | MOG Network (Remote Desktop UDP) |
| 5350, 5351, 5353 | UDP | MOG Service Discovery (Bonjour mDNS) |
| 5355 | UDP | MOG Network Discovery (LLMNR) |
| 5672 | UDP | MOG External Services (RabbitMQ Message Broker) |
| 8741 | TCP | MOG Network (WebSocket Server) |
| 15672 | UDP | MOG External Services (RabbitMQ Message Broker Management Interface) |
| 21000 | TCP | MOG Services (Control Panel) |
| 27017 | TCP | MOG Services (MongoDB Database Server) |
External Communication via Browser
| Port(s) | Rule |
|---|---|
| 8741* | WebSocket |
| 80* | Web Interfaces |
| 40140* | mCore |
| 40160* | mWeb |
| 40080 –40100** | sCapture |
| 40200** | rPlayerWeb |
| 40180** | rPlayout |
| 40060** | rPlayerSDI |
| 40220** | mProxyFileServer |
* Mandatory
** Only need to open in accordance with the active services
Ports per Services
| Port(s) | Rule |
|---|---|
| 40000 | mAnnouncer |
| 40020 | hOperation* |
| 40041 | mExtractor #1* |
| 40042 | mExtractor #2* |
| 40043 | mExtractor #3* |
| 40060 | rPlayerSDI* |
| 40080 | sCapture* |
| 40100 | sCapture* |
| 40120 | PeripheralBoardServer |
| 40140 | mCore |
| 40160 | mWeb |
| 40180 | rPlayout |
| 40200 | rPlayerWeb* |
| 40220 | mProxyFileServer |
| 40240 | WebServicesProxy |
* Scalable service - Services that vary according to the number of operations contracted. For these cases, it will be possible to add up to 40 new instances, each of which will require the subsequent ports to be open. For example, if hOperation uses port 40020 for one instance, subsequent instances on the system will use sequential ports such as 40021 and beyond.
DNS
Furthermore, if your infrastructure does not support auto-assigning on your DNS, a few MOG services (including the Dash preview of captured signals or assets) will not work. As a workaround, you can add the IP address and hostname of your server to the C:\Windows\System32\drivers\etc\hosts file so that MOG services are recognized on the network.
Multicast
Your IT infrastructure must support multicast so that services like mDNS, NDI, and MPEG-TS protocols work as intended.
¶ Operating System
To optimize the OS to run your MOG system, MOGOS presents a few changes to the base version of Windows 10 Enterprise, comprising of:
- Disabled Windows Defragmentation service;
- Disabled UAC;
- Disabled Windows Defender:
- Real-Time Protection;
- Security Center;
- Controlled Folder Access;
- Notifications;
- Hide Tray Icon.
- Disabled Windows SmartScreen;
- Notifications.
- Disabled Windows Action Center;
- Disabled Windows Firewall;
- Disabled FIPS-compliant Encryption;
- Disabled Memory Compression;
- Removed and Disabled Windows Pagefile.
If any of these changes do not comply with your IT infrastructure rules and you need to revert them, please be aware of what might occur some issues:
- During the installation of the licensing software Hasp and RUS 8.13;
- During the first MOG software installation;
- If the server has an SDI Capture Card, popups will appear related to the following services:
- MOG sCapture;
- MOG sCapture.DeckLinkCaptureProducer;
- MOG sCapture.GeneratorHost - when performing a capture operation (Firewall requests access to the network);
- MOG sCapture - when performing a capture operation (Firewall requests access to the network).
Web Browsers
MOG recommends using Google Chrome, Mozilla Firefox, or Microsoft Edge browsers.
Antivirus Software
If you choose to implement antivirus protection, we recommend adhering to the following best practices:
-
Schedule File Scanning Outside Work Hours: it is advisable to schedule file scanning processes during non-operational hours. Simultaneous execution of virus scanning processes and recording/ingesting operations can affect performance and may lead to the degradation of resulting assets;
-
Disable Device Scanning for Specific Card Readers: to mitigate potential issues, consider disabling device scanning specifically for card readers. This precautionary measure helps ensure smoother operations and prevents any adverse effects on performance;
-
Ensure Unblocked Services: make sure that none of the services used by MOG are blocked by the antivirus software. Blocking essential services may hinder the proper functioning of MOG products and services.
By following these practices, users can enhance the compatibility of antivirus software with MOG services and minimize the risk of performance issues and asset degradation.
Note: MOG products use a few different network ports for their services and as such, these should be open both on the server’s OS firewall and on your company’s network. Please check these ports and their specific uses here.
¶ Licensing
As aforementioned, MOG uses Sentinel License Manager (Gemalto) for licensing its services and products. When buying a new MOG server, it will arrive fully licensed and ready to work. However, there may be a few occasions where you would have to perform an operation regarding the product licenses.
Support & Maintenance Update
Your Support & Maintenance expiration dates are embedded in your licenses. This expiration dates have nothing to do with the product functioning, but they do signal the date up until which you have bought Support from us. To keep track of these dates, when updating your Support & Maintenance, it is required to perform a license update.
To execute this update, MOG will send you a “.V2C” file after you made your order. After receiving these files, you must follow this procedure, in order to update your license:
- Go to “Gemalto Admin Control Center” locally on the server to be updated:
http://localhost:1947/_int_/ACC_help_index.html; - Select the option “Update / Attach” and apply the provided “V2C” file. Please make sure to apply the “V2C” with the correct Key Id;
- Select the option “Sentinel Keys”. On the right corner you will have a “C2V” icon, press it and a “C2V” file will be created;
- Return the “C2V” files to MOG by replying to the corresponding e-mail.
After that, the license update procedure will be complete.
OS Image re-installation
Before performing an OS Image reinstall, please contact our support team so we can first extract your license. If the license is not extracted before performing a Windows re-installation, you will lose your license and the ability to perform media operations.
¶ Troubleshooting
¶ SxS devices may not be correctly detected on Densu server-based products
If an SxS device fails to be detected by the operating system, it may be due to the lack of consistent power being provided to the USB ports.
This will cause the operating system to enter an inconsistent state while trying to detect the SxS device, which will prevent users from having the device available for use.
To overcome this issue, it is necessary to use a USB 3.0 HUB with external A/C power.
Note that the USB ports and other devices will work well under the USB 2.0 specification.