There can be multiple reasons why a Nomad peer computer is disqualified from elections (and therefore unable to provide content to the requesting computer). It can be caused by mis-matched Nomad settings or network issues (such as the client firewall not being configured correctly). 

  • Ensure the Nomad version you are using is the same for all its peers
  • Ensure the Nomad client settings are correctly matched – for example, if you have configured SpecialNetShare to hide the Nomad Share, make sure other clients use the same settings otherwise the clients won't be able to Peer-to-Peer successfully. Ensure your OSD Task Sequences have the same settings, such as the Install and Configure Nomad in Windows PE step.
  • Ensure client firewalls are configured correctly. Even though Nomad self-configures the Windows Firewall, you may have Group Policy settings that override the local settings. If you have another firewall installed, such as McAfee HIPS or Symantec Endpoint Protection, you will need to configure those settings for Nomad. Check network access. See the online help for further information. 
  • Review the following KB article for a scenario where User Rights have prevented Nomad from working correctly, and the suggested solution: https://1eportal.force.com/articles/Info/KB000001596
  • The content is in the Master might not be the latest version in the cache
  • The peer downloading the content from the elected master may disqualify it if there is something wrong with the content

Remediation:

  • For a single package, it will come out of that state in 1 hour.
  • For all packages, restarting the Nomad service will reset this computer from being disqualified.