Posts

Showing posts from October, 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

Microsoft CRM Version 4 Service Calendar Doesnt Show

I'm not too sure how many other people might have seen this error but it was a nuisance for me! Some users will find that the service calendar is not available or simply doesnt appear when viewing the CRM Service element. You need to make registry settings changes to overwrite the servername that is used for the Outlook client - using either a variation of the host name or the IP address of ther server that hosts CRM. See the following knowledge base article for more info. http://support.microsoft.com/kb/910050/en-us

Creating a new User Profile in Vista

Of all the daily issues we face in IT Support a new user profile we expect to be both an easy and quick task...until now. With the introduction of Windows Vista's new profile system although designed to be more stable they still do have tendancies to become as XP did..corrupt. From looking around the Operating system there most certainly isnt any quick or obvious solution to this. After a while of digging on the net and testing in house I have found the solution to be a registry change: regedit: HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList\ and delete the SID key for the corrupt profile. Easiest way to find the correct SID is to search from the 'ProfileList' key for the directory.