Solution:

When a managed device downloads its initial policy following installation, this policy will include a link to the schedule that this device should follow.

If the ndschedag output only shows a single ‘Daily Heartbeat’ event, then this indicates that the agent has not yet received its schedule as part of the initial policy download.

Expected output for ndschedag -e should show timings for the following four events:

Generate Inventory

Update Machine Policy

Update Client Settings

Upload Client Files

To diagnose the specific errors causing the policy download to fail, consult the installation.log file, available in the following default directories:

Windows: C:\Windows\Temp\ManageSoft

Unix: /var/opt/managesoft/log

N.B: If you cannot locate the installation.log in either of the above directories, then it is possible that you have custom log locations configured in your environment. See below for steps to determine if this is the case:

Windows: Check the ‘LogFile’ value within the following registry key: [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\ManageSoft Corp\ManageSoft\Launcher\CurrentVersion]

Unix: Check the config.ini file within /var/opt/managesoft/etc, to see if there is a custom value specified for ‘LogFile’ under the section [ManageSoft\Launcher\CurrentVersion]