Posts

Showing posts from June, 2008

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

Robocopy GUI

Fed up of writing all of those custom scripts... Missing the all important quotation marks... Parse errors... No more is this a problem, the clever little people at Microsoft have now helped us out with a GUI for use with Robocopy, simply open up the .exe fill in the blanks and out pops your script. A fantastic time saver tool for an already very useful dos based application. Download Link: Click Here for Download

A required installation file sku011.cab could not be found. Outlook 2003

It happens to most Office users; one day, completely randomly and without warning . Your PC decides it doesn't want to let you run any of the Microsoft Office applications. You also most likley see the error "Installation Error: File not Found" Well before you go scrambling in the closets to go find those 5 - 10 year old discs that you obviously put in a safe place, never to be seen again you will be happy to know that the error isnt the error at all. If that makes sense... Basically the file the office package needs is still on your PC it just needs to be told where. The fix is actually pretty straight forward: Simply go to: 1. Start 2. Run and type "Regedit" 3. Naviagate to the following Key: HKLM > Software > Microsoft > Office > 11.0 > Delivery. 4. Then click the GUID sub key (Usually a string of numbers) 5. Now on the right you will see, CDCACHE with an entry of "2". 6. Right click and select Modify, change the "