Well, this one was gob-smacking! A colleague of mine (Tristan Watkins) pointed me at this article from Mark Russinovich, the developer of the “NewSID” tool that so many people use for creating a new machine SID for a machine (typically after a re-image or copying a virtual machine).
Well, it seems we don’t need to bother anymore and never really did, at least in the vast majority of cases!
“It’s a little surprising that the SID duplication issue has gone unquestioned for so long, but everyone has assumed that someone else knew exactly why it was a problem. To my chagrin, NewSID has never really done anything useful and there’s no reason to miss it now that it’s retired.“
Update – A good follow up summary has also been written by one of my colleagues, Tristan Watkins
This all came about because I am a guinea pig for the new content and code development environment.
The good news is that I have a spiffy laptop with Dual Core, 4GB DDR2 and (this is the good bit) a 320GB 7200rpm hard drive (not bad for a laptop!).
This all allows me to kick it into gear with Server 2008 x64 and Hyper-V.
Now for the bad news … Hyper-V doesn’t support "Shared Networking (NAT)" even though the technically inferior Virtual PC 2007 DOES!
It’s not too much of a heartache though, you simply have to be creative and setup yourself Internet Connection Sharing. This effectively allows your virtual machine to stay completely hidden from the big wide world, safely behind your an internally facing virtual network and your laptop’s firewall.
This is great for development environments, as we can have stand-alone virtual machines which can be copied, rolled-back and swapped around in minutes without any of that messy sys-prep nonsense.
However .. things went awry when I switched on our VPN … I was at home and didn’t have the creature comforts of a dedicated piece of copper between myself and the server.
I turned on my VPN and it did exactly what it was supposed to .. it created a secure tunnel and promptly shut-down all my other network adapters … including my virtual network…
so … a few hours of troublshooting and chomping of the table edge and I nailed it.
You need to:
- Connect to the VPN
- Share the VPN connection
This effectively gives your virtual machine it’s own private access to the corporate network .. great for those TFS check-ins and server builds 🙂
*sigh* another one for midnight oil.
One to punt over from the Microsoft SharePoint Team Blog.
Basically, if you are using this then it’s going to expire … TODAY! (bummer eh?)
But fear not … another one has been published … so download that and be merry instead 🙂