Digging further...
If I move the laptop back to the adapter/IP used to activate the client, manually restarted Avast Business Console Client and I can send task to the client, "cloud" server will allow it to communicate with it again, receive any changes I made to the policy, etc.
The moment I move to a different adapter/IP than used to activate, manually restarted Avast Business Console Client and I loose all "cloud" server communication and thus the client is no longer being monitored / updated / can't send task to the client, etc.
Client at this point is technically DOA, but yet the "cloud" server still indicates it's "SAFE".
Okay, the million dollar question is -- how do I protect this machine when it roams from network to network?
Second, how do I inform the "cloud" server the IP has been changed on a workstation without having to completely un-install and restart the client, because that is the only way I have been able to affectively inform the "cloud" server the IP has changed.