@Chris_Atkinson
Thanks for the suggestion.
As far I know that, If I build a Management Server with Private IP address and then enable the Endpoint security blade and export the client package (Not Initial client) then when I installed the client on any machine then after installation Client try to communicate with IP address (Management Server Private IP address) So basically if I follow sk112099 did the same also then How the Client will try to communicate with the Public IP ?
Endpoint Server is hosted behind the Firewall.
Workaround😉
Not Sure the below suggestion is recommended or not but work for me.
Step1: Create a static NAT for Endpoint Management Server (Give a Static public IP) on the Internet-facing firewall.
Step2: Configure external NAT on Endpoint Management Server (sk112099).
Step3: Change the Management Server IP using Smartconsole and publish and don't install the database because its not possible because we change the IP address from private to public IP.
Step4: Close the SmartConsole and reopen the Smartconsole by using the Private IP address and you able to see the public IP address on the Smartconsole.
Step5: Open the Endpoint Management Console and create a new package and export the msi package.
Step6: Now installed that package on windows Machine and connect using public internet and able to communicate with the Endpoint Management Server.
Step7: Change the IP address of MGMT Server on Smart Console and able to install the Database.
Its work for me 😉😉
Regards
@Chinmaya_Naik