Question

I previously enabled remote desktop in my Azure project to allow me to debug in our staging environment. This added a 3rd endpoint on port 3389 in addition to 80 and 443.

I’ve finished debugging and disabled remote desktop in the publishing wizard then did another deployment to staging. I then tried to do a VIP swap with our production instance, but Azure admin console is throwing an error due to staging have 3 endpoints and production have 2 (you can’t do a VIP swap between instances that have different # of endpoints).

Here’s what I’ve done to verify remote desktop is disabled:

1. I’ve triple checked that in the publish wizard that I specific to have remote desktop disabled.

2. The .azurePubxml has:

   <AzureEnableRemoteDesktop>False</AzureEnableRemoteDesktop>

3. The cscfg has:

   <Setting name="Microsoft.WindowsAzure.Plugins.RemoteAccess.Enabled" value="false" />

4.My csdef has:

<?xml version="1.0" encoding="utf-8"?>
<ServiceDefinition name="mysite.App" xmlns="http://schemas.microsoft.com/ServiceHosting/2008/10/ServiceDefinition">
<WebRole name="www" vmsize="Small">
<Sites>
<Site name="Web">
    <VirtualApplication name="r" physicalDirectory="../ReviewPost/ReviewPost" />
    <Bindings>
        <Binding name="Endpoint1" endpointName="Endpoint1" />
        <Binding name="Endpoint2" endpointName="Endpoint2" />
    </Bindings>
</Site>
</Sites>
<Endpoints>
  <InputEndpoint name="Endpoint1" protocol="http" port="80" />
  <InputEndpoint name="Endpoint2" protocol="https" port="443" certificate="STAR.mysite.com" />
</Endpoints>
<Imports>
  <Import moduleName="Diagnostics" />
  <Import moduleName="RemoteAccess" />
  <Import moduleName="RemoteForwarder" />
</Imports>
<Certificates>
  <Certificate name="STAR.mysite.com" storeLocation="LocalMachine" storeName="My" />
</Certificates>
</WebRole>
</ServiceDefinition>

Despite the above configuration, the azure console is showing 3 endpoints (port 80, 443 and 3389) for the staging environment.

What am I missing?

Answer 1

Based on information from @smarx in the MSDN forums mirror of my question here’s the solution:

Remove these lines from your .csdef:

<Import moduleName="RemoteAccess" />
<Import moduleName="RemoteForwarder" />

These 2 lines control the creation of the extra endpoint even though remote access may be disabled.