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

Ethereum Wallet Stuck on 99% or XX Blocks remaining!

Believe me when I say, this is one of the most frustrating things to happen!

Imagine this, I first get into Crypto - I buy 5 Ether through coinbase - download the Ethereum Wallet so I can have an offline Wallet store and without thinking about it - I got the wallet address and sent it all.

I then left my i7, 12GB, 1TB SSD Linux machine running with QoS enabled for bandwidth benefits for three days.. gradually getting more and more nervous.

I couldn't seem to get past the last few blocks, it would stall or just never really get anywhere!

Firstly, as an observation - I found that if you launch the application - you lose any form of syncing entirely, so leave it at the splash screen.

Secondly however if you really don't think its going to connect, then try these steps:

Go to the Develop Menu item, and change your Sync mode to "Light" it may say Beta on it but its ok.

Go to File > Backup > Accounts data

Rename ChainData to ChainData1 (or whatever you want).  Close down your Wallet and re-launch it.

This didn't work first time for me, (maybe I was too keen) but if thats the case - have faith, close the app again and re-open it.  Leave it on Splash, give it 15 minutes (or so depending on your circumstance) and horrar it should work!!!

Hope this helps somebody else who may have stupidly jumped without looking too...

If this post helped you, please consider donating eth (every little helps!) to my addresses on the right of this page! 


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