The Server shutdowns can occur due to different reasons/errors. In this scenario, I would enable Denodo Monitor to track the server activities. I would also [monitor](https://community.denodo.com/docs/html/browse/7.0/vdp/dmt/monitoring/monitoring) the servers using Diagnostic & Monitoring Tool to check if they are working as expected.
You could take a look at [Denodo Monitor](https://community.denodo.com/docs/html/browse/7.0/vdp/administration/monitoring_the_virtual_dataport_server/denodo_monitor/denodo_monitor) section under the Virtual DataPort Administration Guide and [Creating Diagnostics](https://community.denodo.com/docs/html/browse/latest/vdp/dmt/creating_diagnostics_and_diagnostic_intervals/creating_diagnostics/creating_diagnostics) section under the Diagnostic & Monitoring Tool Guide for more information.
In case if it is a license issue, then I would check the 'solution-manager' and 'license-manager' logs present under '<SOLUTION_MANAGER_HOME>/logs' folder for more details.
Regarding starting the Denodo servers (like Virtual DataPort, Scheduler server, etc.) automatically in Windows, I would follow the steps from [Configure Windows Services](https://community.denodo.com/docs/html/browse/latest/platform/installation/postinstallation_tasks/configure_windows_services/configure_windows_services#configure-windows-services) section of the Denodo Platform Installation Guide which explains how to start these services in an automatic fashion.
Hope this helps!