Endpoint Agent not starting on Windows

Issue

Occasionally the endpoint agent service MBEndpointAgent may not start when the computer is booted up. This article provides options to ensure reliable startup by a Nebula policy setting and additionally a GPO setting.

Resolution

Allow services additional time to startup

This setting gives all Windows services more time to startup and thereby avoiding service timeouts.

Health monitoring

This setting adds a new Endpoint Agent Monitor Service EAServiceMonitor.exe that monitors and restarts the Endpoint Agent Service MBCloudEA.exe if it goes offline or is stopped.

Group policy setup

1. Download the StartMB.zip and extract the file inside StartMB.bat. Save it somewhere where it won’t be interacted with by users.
2. Open Local Group Policy Editor as administrator.
   • Type in gpedit.msc into the search bar on Windows and right-click > Run as Administator
     
3. Expand Windows Settings under Computer Configuration
   
   • You’ll find Scripts (Startup/Shutdown)
     
4. Double-click Startup on the left side
5. In Startup Properties under the Scripts tab, click Add
   • Select Browse and find the script that was saved in step 1 of these instructions
   • Hit OK
   • Hit Apply on the Startup Properties window
   • Hit OK to exit
     
     
6. Exit Group Policy Editor

Now on reboot, the Endpoint Agent service will start without any issues. If you have any questions or still have issues, contact Support.