JoinDomain VMExtensionProvisioningError when deploying WVD (aka Conflict Error)

Deploying WVD Fails with a conflict error and when clicking for more information it presents a conflict and not much else that is useful by way of toubleshooting. Hopefully this helps someone else as it had me head scratching for a little while.. When creating the Host Pool, make sure that you haven't made the fatal error of using the Azure Active Directory Credential INSTEAD of the Local AD Domain Credential.  i.e do not use to domain join, even if it links back to the domain - this is where the conflict arrises.    Instead, use your full internal domain UPN.  Re-deploy your same configuration and you should find it goes through now without any problems. Additional findings.... Albeit my mistake above was an easy one, it does appear the error is directly linked to the domain join process. If you go into your resource groups, locate the session host and MSTSC directly to it.  Try the domain join pr

Citrix VDI-in-a-Box and whats next?!

VDI-in-a-Box is on its way out, but killing the product wasn't always Citrix's intention. Technical problems, development time and a poor sales strategy appear to be the cause of the product's death.
VDI-in-a-Box has been rumoured to be on the chopping block since Citrix acquired Kaviza (the original company behind the product) back in May 2011.  While many people lauded Citrix for gaining a VDI product that was easy to install and operate, others thought that the acquisition might have been nothing more than an attempt to alleviate the competition.  
Many of us held out hope that there would ultimately be some blending of XenDesktop and VDI-in-a-Box, with the best elements of each creating a new VDI platform, but that never proved true.
Citrix earlier this year were quoted as saying “We’re going to ‘end-of-sale’ that product and it will be replaced by a simpler and more price competitive version for VDI that we have coming”.   The news comes as no real surprise, given that in 5 years since the products acquisition, there’s been virtually nothing done with the software at all.  But the future (for the moment) seems unclear. 
There were/are two very distinct groups of customers when it comes to Citrix, those who want VDI in a Box - for its simplicity, its price point and its low maintenance requirements.  And then those who want XenDesktop, which can offer the same features (along with a whole host of others) but very clearly requires a different skill set.  On the news of the products soon to be death, customers are worrying – what should they be doing next? And what could possibly help in this situation where moving to a more complex product is not the answer.

For me, I think this is genuinely a fantastic reason to start thinking about outsourcing your Citrix infrastructure to a specialist provider.  Ask yourself these questions, would it be more cost effective if you could pay only for what you use? Would it be less stressful if you let somebody else maintain the complexities of a more advanced system? And would it better enable your business if you could reap the features and benefits of a more powerful system at a third of the cost, with little complexity?  If you answered yes to any of the above questions, then you’re in the right place to talk to a  managed services provider - and you should be! 

Alas, as we soon say Goodbye in 2016 to Citrix VDI-in-a-Box, a promising product that had its own niche market appeal.  We open the doors to a new era of outsourced cloud delivered solutions.  One that delivers all the business benefits of a low maintenance, feature rich, cost effective solution – but delivered in a different way.  
Talk to me today, to see how I can help! 

Did you find this an interesting read? Or did I solve your problem? Buy me a virtual beer by clicking on a Google ad :). Thanks!


Popular posts from this blog

This product type does not match the list of supported product types

SBS 2008 hangs on Applying Computer Settings

LSASS.EXE - System Error / Rebuilding Active Directory Indices. When booting windows server 2003