Hi,

I think that the only way to achieve this is to create DNS records for each customer of admin.[DOMAIN] with the IP of your SCP Portal, which can be set in the server config under DNS in the SCP for new customers (but would need manually creating for existing DNS zones)

Then you would need to manually add those admin.[DOMAIN] into the bindings of the SCP Portal - Could script this or do it manually but I don't think there is a way within SCP to do this.

Hi again,

In my Case, I have 4 Servers for Web, SQL, DNS and Exchange separately, that SolidCo enterprise and portal Are Installed on Web Server, I think I can Remove Portal from Web Server And Install It on Another Server, Is That right?? Is This Case problem?

Hi,

Yes, you can install the portal on to another server and remove the existing one however this would not resolve your initial query as the bindings in IIS would still have to be altered.

Hi,

I have had a think about your situation regarding the redirect for admin.customerdomain.com to the SolidCP portal and I think I have a way that will work, but only via HTTP, not HTTPS:

• In IIS where your portal is select the "Default Web Site" -> HTTP Redirect
• Set the redirect to your existing portal address (i.e. http://admin.yourdomain.com)

At this point if you now navigate to the IP of the server hosting the portal in a web browser it should redirect to the portal.

• In your customers DNS add an A record for 'admin' pointing to the IP address of the server where your portal is

Now when the customer browses to admin.yourcustomerdomain.com they will hit the Default Web Site HTTP redirect rule which will send them to http://admin.yourdomain.com

Just remember that the redirect for the IP of the server with the portal will send all requests that are unknown to that server (not matching bindings) to the portal.