Hello @sathya66,   forgetting about the hostname update in the SAS metadata, your host is the first one that has to resolve the new alias, and telnet has to be able to telnet {newalias} 8561. Can the server resolve the new alias to the right IP? Can the server telnet with the new alias on the port number?   Once you do this, you should be able to execute the command properly.   I would carefully review anyways the documented steps for updating hostnames: https://documentation.sas.com/?docsetId=bisag&docsetTarget=n0zdcqxsmd21wtn17vt0w2prek90.htm&docsetVersion=9.4&locale=en https://documentation.sas.com/?docsetId=bisag&docsetTarget=n1ov3paky6afj8n1bj7l55o8jvw5.htm&docsetVersion=9.4&locale=en   Check the troubleshooting guide: https://documentation.sas.com/?docsetId=bisag&docsetTarget=p0vjf8irdhbbndn1ck1ur7j0djlh.htm&docsetVersion=9.4&locale=en   To avoid hostname issues while running SAS Deployment manager you can run   sasdm.sh -confighostname [your_fqdn_hostname_or_alias]   This might get the license place in place, but you still might need to resolve the hostname/alias issue with infra.   ... View more