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

How to clear the print queue manually when prints won't delete

So your working away on your PC and you send a print but it fails, your out of ink, out of paper or just plain unlucky. You restock your printer but the failed print wont clear in the Queue, the solution is simple:

1.Click "start" and go to "Run"


2.Type "services.msc" at the prompt which will open the Services
window.


3.Scroll down the alphabetical list in the right window pane until you come
to the entry with the name "Print Spooler"


4.Right-click this entry, then select "stop". This will stop the computer
running the process that holds your print queues.


5.Leaving that window open for now, click again on "Start", and then click
"My Computer" to open a Windows Explorer window.

The usual path to the spool folder is
C:\WINDOWS\system32\spool\PRINTERS, but yours may be slightly
different. Your windows drive may have another name for instance, but this would
be uncommon. So click on your Windows drive (usually C), then double-click on
the Windows folder, and then find the System32 folder and double-click on
that. Windows may warn you that you are about to view system files, but click
"View files anyway" message and search out the "spool folder". Within the
Spool folder is your Printers folder, and you should open
that.


7.Delete every file within this folder to empty the jammed print queue
(pressing the "ctrl" and "a" keys will select all files and then you can just
hit "delete").


8.Close the explorer window now that we have emptied the cleared spool files,
and return to your Services window. we must re-start the Print spool
service, and do so by right-clicking the Print Spool entry and selecting
"Start" from the list. Close the services window and try printing again

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