Netbios is turned off for security reasons. Will MMAD still work correctly on our network? What are my options?

Our security team had us disable Netbios on our network devices/servers/PC's.  Does implementing the registry hacks in the 3rd KB article below get around having to have Netbios enabled on your network for MMAD to work?


Is NETBIOS resolution required for MMAD and MMEX? (145657)
Absolutely, Migration Manager for AD & Exchange require Netbios connectivity throughout the product.
Product(s): Migration Manager for Exchange, Migration Manager for AD
Last Updated On: 1/13/2015

What methods of name resolution does Migration Manager rely on for proper functionality? (15574)
- The Resource Updating Manager console uses Netbios resolution to obtain and communicate with workstations during processing and enumeration of the computer list.
Product(s): Migration Manager for AD
Last Updated On: 2/19/2018

Is there a way for Quest Resource Updating Manager (RUM) Agents to communicate to the RUM Control (86174)
By default RUM Agents communicate with the RUM Controller Service server via NETBIOS name during the discovery process. Is there a way to configure RUM Agents to communicate to the RUM Controller Service server via FQDN name or IP Address?
•    Cause
In some environment, the source workstations may not possible to use NETBIOS to communicate between the system due to the some hardening or security in-place.
•    Resolution
 On the RUM console (by default it's QMM console server) please perform the following workaround steps:
Registry entries go here...
•    Additional Information
In QMM versions 8.6 & 8.6.1, this setting is only configurable for agents being deployed from the RUM console; the Create Agent Setup does not have this option.
Product(s): Migration Manager for AD
Last Updated On: 9/12/2016