J
John_Curtiss
I have a domain where all of the member servers live on a DMZ, and the domain controllers live internally, with a (palo alto) firewall between them.
I want to put 2016 servers in the DMZ, and I want to use VAMT to activate them. currently the (internal) domain controllers are 2012 r2 activated via KMS, but obviously those will get upgraded to 2016 sooner or later, and will need to be activated via VAMT.
everything I can find on the internet about "vamt firewall" is about putting rules in the windows firewall. not about which ports to open in a physical firewall.
I understand that the vamt server will need to talk via WMI to the clients being activated.
would it make more sense to put my VAMT server inside the network with the domain controllers, and allow the necessary traffic outbound through the firewall to the clients? what ports would I need to allow outbound through the firewall to the clients?
Continue reading...
I want to put 2016 servers in the DMZ, and I want to use VAMT to activate them. currently the (internal) domain controllers are 2012 r2 activated via KMS, but obviously those will get upgraded to 2016 sooner or later, and will need to be activated via VAMT.
everything I can find on the internet about "vamt firewall" is about putting rules in the windows firewall. not about which ports to open in a physical firewall.
I understand that the vamt server will need to talk via WMI to the clients being activated.
would it make more sense to put my VAMT server inside the network with the domain controllers, and allow the necessary traffic outbound through the firewall to the clients? what ports would I need to allow outbound through the firewall to the clients?
Continue reading...