Nomad integration with WakeUp is available if you enable this feature when installing NightWatchman Management Center. You should install ActiveEfficiency Server first and then install NightWatchman Management Center. Both servers require Windows Message Queuing feature (MSMQ) to be enabled.
In summary, you require the following:
Please refer to Integrating with WakeUp.
See below for pre-installation checks, architecture and ports.
Nomad Download Pause is available if you implement a Tachyon server infrastructure, including enabling the Tachyon client features in 1E Client in addition to the Nomad client. It also requires Single-site download and ActiveEfficiency.
If you are also implementing a PXE Everywhere solution using Nomad, ensure you meets its prerequisites. Please refer to PXE Everywhere 4.0 - Requirements.
To install Nomad, you will need:
The Nomad Dashboard and dynamic pre-cache features require ActiveEfficiency to synchronize with the Configuration Manager database. For standalone primary site environments, permissions are assigned to the ActiveEfficiency service account automatically using the ConfigMgr_DViewAccess localgroup native to Configuration Manager. For a CAS, this group is not created natively therefore additional steps are required to allow access. Please refer to ActiveEfficiency Server 1.10 - Preparation: Granting access to the Configuration Manager site database.
Ensure local broadcasts are enabled on each subnet that Nomad operates in
|Some wireless access points may be configured to prevent broadcasts, which will prevent Nomad peer-sharing features from working. See the Wireless Access Points prerequisite below for details on WAP configuration.|
StatusMsgEvents = 0x1000000064set in the registry to enable them to send data to the dashboard. Currently the default is 0 and no status messages will be sent.
You will need a valid NightWatchman Enterprise license to use these components.
To support enhanced package consistency checking, the Nomad client must be installed on each Configuration Manager DP. This client enables file-level consistency checking by creating a manifest file on the DP for every version of each package created enabling Nomad to verify that each file it downloads is consistent with the version available on the DP.
You can use digital certificates to certify the identity of entities in your network. We support the use of Public key infrastructure (PKI) based certificates or self-signed certificates. If you are using PKIs to digitally sign entities from the outset, ensure that they are deployed to all agents. Alternatively, you can deploy PKIs post-installation. Things to bear in mind when using the HTTPS protocol:
When self-signed is enabled, a self-signed certificate is created by the installer and stored in