Posts

Showing posts from October, 2010

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

I’ve been nominated for the Computer Weekly IT Blog Awards 2010!

Image
It's a great feeling to have been nominated for the Computer Weekly IT Blog Awards 2010 in the Male IT Professional Blogger category , sponsored by IBM . The voting structure is very simple, number of votes cast, with one vote cast per visitor. So if you’re a reader of this blog, and want to vote for me, visit the Computer Weekly Voting Page for the Male IT Professional 2010 category , hit the big Vote Now button, and pick my name from the list for the Male IT Professional drop-down. I’m really grateful to those people who took the time and effort to nominate me, and for anyone else who votes for me – I really appreciate it :). Don't forget to vote for some of the other fantastic nominee's in the other categories as you only get one chance to vote. Thanks Kris

Duplicate Name Exists On The Network

Wowzers, this is an annoying message! I spent the better part of Three days trying to crack this for a customer! Ok so in my scenario, I had 30 PC's coming up with this error at bootup. I think at that point its a fair assumption that there aren't actually 30 PC's all running with duplicate names sitting downstairs in a store cupboard right..? So first port of call, check the event log. I had something like this: The name "MYDOMAINNAME/MYPCNAME :0" could not be registered on the Interface with IP address 192.168.1.100. The machine with the IP address 192.168.1.1 did not allow the name to be claimed by this machine. The SBS in this case was 192.168.1.10 so why is 192.168.1.1 even talking to my machine when it boots up!? I checked the source of the problem 192.168.1.1 and at first glance couldnt find any problems but then a little more digging and we found out the issue. 192.168.1.1 was a Linux server, named exactly (yes I said exactly) the same as the Inte

Num Lock not enabled by Default on some new PC's

Strangely enough to mine and I'm sure many other peoples surprise, the commands are no longer in BIOS. See below. HKEY_USERS\.DEFAULT\Control Panel\Keyboard and HKEY_CURRENT_USER\Control Panel\Keyboard 0 - Turn all indicators Off (NumLock, CapsLock, ScrollLock) 1 - Turn CapsLock On 2 - Turn NumLock On 3 - Turn CapsLock and NumLock On 4 - Turn ScrollLock On 5 - Turn CapsLock and ScrollLock On 6 - Turn NumLock and ScrollLock On 7 - Turn all indicators On (NumLock, CapsLock, ScrollLock) In my case, the string value was some 7 or 8 digit number such as 21765430. These entries are the cause of the reboot change in the num lock status. If you want it on when you boot, set the string value to 2 in all the keys with numeric values. Problem solved! Compliments of @RWheeldon