WVD and Nokia VitalQIP

%3CLINGO-SUB%20id%3D%22lingo-sub-2353849%22%20slang%3D%22en-US%22%3EWVD%20and%20Nokia%20VitalQIP%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2353849%22%20slang%3D%22en-US%22%3E%3CP%3EA%20question%20for%20the%20hive%20mind.%20Does%20WVD%20work%20with%203rd%20party%20DNS%20solutions%20as%20well%20as%20Windows%20AD-integrated%20DNS%3F%20Specifically%2C%20a%20customer%20uses%20Nokia%20(Alcatel-Lucent)%20VitalQIP%20as%20their%20IP%20management%20solution.%20Is%20this%20a%20show%20stopper%3F%20I've%20asked%20Dean%20at%20The%20Azure%20Academy%20who%20has%20indicated%20that%20this%20is%20unlikely.%20Just%20need%20clarification.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2357794%22%20slang%3D%22en-US%22%3ERe%3A%20WVD%20and%20Nokia%20VitalQIP%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2357794%22%20slang%3D%22en-US%22%3EWVD%20need%20that%20these%20VM%20are%20joined%20in%20a%20ADDS%20hybrid%20environnment%20or%20joinded%20to%20a%20AzureAD%20Directory%20servies%20instance%20(Which%20is%20basicly%202DC%20that%20are%20managed%20by%20Microsoft%20with%20user%20syncs)%20to%20be%20in%20a%20supported%20scenario.%20The%20DNS%20mechnisms%20isthe%20same%20as%20expected%2C%20you%20just%20need%20to%20provide%20the%20correct%20DNS%20servers%20in%20the%20VNET%20or%20per%20Nic%20in%20Azure%20ARM.%20DHCP%20(Address%20spaces%2Fsubnet)%20in%20VNET%20and%20IP%20addresses%20are%20managed%20with%20Azure%20ARM%2C%20you%20can't%20change%20an%20IP%20config%20at%20the%20guest%20level%20configuration%20unless%20it%20reflect%20the%20provided%20IP%20in%20Azure%20sARM%20since%20all%20addresses%20are%20virtual%20in%20Azure%20(same%20as%20SDN%20stuff).%3C%2FLINGO-BODY%3E
New Contributor

A question for the hive mind. Does WVD work with 3rd party DNS solutions as well as Windows AD-integrated DNS? Specifically, a customer uses Nokia (Alcatel-Lucent) VitalQIP as their IP management solution. Is this a show stopper? I've asked Dean at The Azure Academy who has indicated that this is unlikely. Just need clarification.

2 Replies

WVD need that these VM are joined in a ADDS hybrid environnment or joinded to a AzureAD Directory servies instance (Which is basicly 2DC that are managed by Microsoft with user syncs) to be in a supported scenario. The DNS mechanisms is the same as expected, you just need to provide the correct DNS servers in the VNET or per Nic in Azure ARM. DHCP (Address spaces/subnet) in VNET and IP addresses are managed with Azure ARM, you can't change an IP config at the guest level configuration unless it reflect the provided IP in Azure sARM since all addresses are virtual in Azure (same as SDN stuff).

so basicly if you want to add IP addresses policies via a third party software, this software must be Azure aware and must change the config in the Azure portal not at the guest level. (Note that a IP configuration change trigger a VM restart to get their new IP config).