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 USER@m365xxxxx.onmicrosoft.com to domain join, even if it links back to the domain - this is where the conflict arrises.    Instead, use your full internal domain UPN.  USER@prefix.domain.co.uk  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
Post a Comment

Remote Desktop Connection - Fatal Error 5

-
When connecting to another machine using Remote Desktop (RDP) you may experience the error "Fatal Error 5" as per general google search instructions: although you can continue working by opening another RDP connection window, most people would agree this is more of a workaround than a fix!

After some troubleshooting it looks like this issue is caused by corruption in the default.rdp file usually located in My Documents, simply renaming this file to default.old will do the trick...

Comments

  1. Unknown21 November 2009 at 07:25

    Working in remote support, such problems can cost us a lot in terms of customer support. We switched to RHUB http://www.rhubcom.com on-premise appliance for Remote Support, and we haven’t had any problems with it till now.

    ReplyDelete

Post a Comment

Popular posts from this blog

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

-
I got this message installing a HP CM1312 on an SBS server, how on earth it is justifiable that an SBS server doesnt meet requirements is beyond me, obviously this being a network shared printer this was no solution so I had to install it. Even going to the HP website you get the same installer package so you can't use the add printer wizard... a few hours with HP later and finally we cracked it. So to get past this error simply hold down CTRL + SHIFT when pressing Cancel on the installer, this will then keep the installer running passed the error and works a treat. Enjoy! Did I solve your problem? Buy me a virtual beer by clicking on a Google ad :). Thanks!
Read more

SBS 2008 hangs on Applying Computer Settings

-
I have to admit, out of all server installs I have ever done, I have probably had one of the worst experiences ever recently with 2008 SBS. I thought I would blog about this problem simply because I was in a mess and I'm sure anyone else in this scenario would want to get out of it just as quickly as I did! My Scenario At first the clients were complaining that the Exchange was down, I noticed that the store service wasnt running so quite rightly I tried to start it but it wasnt having any of it. I went to Event Viewer and it had items like "Cannot connect to Active Directory" and "Exchange topology not starting" amongst many others. My most stupid mistake at this point was to reboot the server which is where I ended up watching a spinning wheel at "Applying Computer Settings". I couldnt think what it was until I found that it could be affected by IPv6 at which point it became clear that this definately was the problem, I had turned it off the d
Read more

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

-
LSASS.EXE - System Error, security accounts manager initialization failed because of the following error: Directory Services cannot start. Error status 0xc00002e1. I know everyone's scenario's when seeing this message are pretty varied but I found a nice way to fix this within an hour providing you have a similar setup. In my particular case I had two servers an SBS 2000 (oh dear I hear you cry) and a Standard Server 2003 running SP1. The 2K3 machine was rebooted and upon reboot we were presented with the above error. So to fix try the following: 1. Reboot the 2K3 server into "Directory Services Restore Mode" then logon to the machine locally, in my case I didnt know the restore password (results of taking on machines from other support companies.) -If this is the case go onto the second server, right click "my computer" and select manage, within the new window, right click the "Computer Management" header and then click connect to anothe
Read more