Please note: If you register your VM Cloud resource provider in WAP with all the settings at once, you will not run into this issue. It's only if you decide to add the RDGateway afterwards, or are making changes to the existing one.
Monday, August 18, 2014
VM Cloud is missing in Windows Azure Pack
Recently, I’ve encountered a bug when working with WAP and VM Cloud as the resource provider.
You have connected the service management API to your SPF endpoint and added a VMM management stamp together with a Remote Desktop Gateway.
If you decide to change the FQDN of the Remote Desktop Gateway registered with your VMM management stamp, you will end with a blank VM Cloud in the admin portal.
The connection to the SPF endpoint is still present, but the VMM management stamp with its cloud is missing.
This causes also the VMs and the virtual network for the tenants to appear as missing in the tenant portal.
On the SPF server you will find the following event logged for ManagementODataServices:
On the server where the admin API is installed, you will find the following in the event viewer:
When you make changes to the FQDN of the Remote Desktop Gateway in WAP, you will have another SCSPFServer record present in SPF together with a SCSPFSetting that has the same ID as the previous records.
As you can see from the screenshot below, we have now two records of the ServerType “RDGateway”.
If we dig deeper, the following screenshot shows that we have two entries with the same ID, both registered to the VMM management stamp.
In short, the VMM management stamp is registered again, which generates a duplicate ID that results in this behavior.
In order to clean up, we have to work directly on the SPF server using the SPFAdmin module with PowerShell.
Note: when doing this correctly, you will not delete, loose or cause any harm to your production environment so pay attention.
1. Log on to your SPF server and import the SPFAdmin module
2. Run the following cmdlets to identify and remove your RDGateway servers! In our case, we have two records and have to remove both of them before we later add the RDGateway we want.
The reason for that is that because when you try to add the RDGateway in WAP afterwards, you will see that this column is empty although it exist in SPF. If you try to add the RDGateway again, you will end up in the exact same situation. Therefore we must remove both servers in SPF.
3. Remove the duplicate SCSpfSetting with the following cmdlets. The SCSpfSetting on the top is the setting you want to remove with the duplicate ID.
4. Next, we want to register the RDGateway directly to our stamp with SPF to avoid creating duplicate ID's.
Once this is done, you can perform a refresh in both the admin portal and the tenant portal, and your VMM management stamp should again be present.
Also edit the connection to verify that the RDGW is registered with the correct values.