We are proceeding to upgrade to 2022.1 FME Server and would like to take advantage of
the Azure Marketplace install option.
Our cloud provider noticed that domain joining is not supported in the current Marketplace install. There are some workarounds available but this negates some of the benefit of using Marketplace.
Has anyone used this configuration and what is their experience? We need to decide early next week whether to go down this route or whether to go for a tried and test traditional deployment on an Azure VM.
At the moment we have a single stack and should stay this way for the next year.
Any tips or experiences would be appreciated.
Annette
Best answer by jlutherthomas
It's my understanding that you would do this the exact same way like with any other VM to join a domain:
The distributed marketplace template creates it's own networking and doesn't use an existing vnet, and you create user accounts for the VMs (it doesn't use domain accounts).
To RDP into the machines created by the marketplace distributed deployment you will have to use a Bastion or just use a VM as jumpbox which is in the same VNet as the VMSS. Also the domain server needs to be reachable within this VNet. This could possibly be achieved with VNet peering.
As a warning, the default marketplace deployment is not production ready and it is highly recommended to add security rules to the vnet limiting traffic to the minimum possible. We recommend that you download and modify the marketplace template as needed to fit into your cloud environment, or create your own using ours as an example.
The distributed marketplace template creates it's own networking and doesn't use an existing vnet, and you create user accounts for the VMs (it doesn't use domain accounts).
To RDP into the machines created by the marketplace distributed deployment you will have to use a Bastion or just use a VM as jumpbox which is in the same VNet as the VMSS. Also the domain server needs to be reachable within this VNet. This could possibly be achieved with VNet peering.
As a warning, the default marketplace deployment is not production ready and it is highly recommended to add security rules to the vnet limiting traffic to the minimum possible. We recommend that you download and modify the marketplace template as needed to fit into your cloud environment, or create your own using ours as an example.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.
