The fix is to stop using Metro, and block users from even using it. That is how you fix this problem the easy way. It does help to know what you are using for your Domain Server with Windows 8.
Why would i want my end users to stop using Metro? I think its an awsome way to interact with windows in order to start an application.
If people actually spent the time to learn the NEW operating system then i am sure they too would stop being stuck in the old days, i mean come on whats microsoft meant to do? if they made it the same as Windows 7 people would complain they did nothing and it looks the same LOL. Its a 20/20.
I hated Windows 8 at first, absolutley hated it and then i got a tablet givin to me to test before we deployed a few and i did some reading, found out some tips and learnt trhe new explorer and tested soem GPO compadability's and secpol.msc testing as well..
This all ties to the key (Computer) being the default name on this particular machine. Even if i change the key value by ownership i noticed it still has to be cached some where else because a new user still gets the old name when pinning a shortcut to Metro. So any other suggestios Greg or is this a little over your head mate?
The servers are Windows 2008 R2, the only servers i will be having on my network as Windows 2012 is just pathetic and doesnt bring much to the table.
I will agree on not having any metro theme on a server, its for administering and not facebook and social netwoking. They made a very big mistake there.
(I soley manage over 100 nodes and end users, all use different technologies/applicatiosn and mobile devices. I am the only SysAmin on the entire network managing 15 + servers + Unix machines)