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

Microsoft My Phone 'Beta'

With the ever growing Windows Mobility market showing no signs of slowing down, Microsoft have begun developing a new service to be announced at the World Mobile Congress in Barcelona next week called MyPhone (Currently codenamed "SkyBox")

According to the My Phone Web site, "If your phone is lost or stolen, or if you upgrade to a new phone, you can easily restore the contacts, calendar appointments, photos and other information that you stored on My Phone to a compatible new or replacement phone."

Users will be limited to 200MB of storage space for the service, which will initially be available in a limited, invite-only beta for Windows Mobile

http://www.microsoft.com/windowsmobile/myphone/

Comments

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