Anyone who’s deployed Hyper-V as part of either Windows Server 2008 R2 Core Install, or, through Hyper-V Server 2008 R2, will know that changing certain settings requires a bit of work in the command line environment. For some people, easy peasy, but for others, it was a step too far, and back to the GUI they went. Then came Core Configurator, which bridged the gap between command line and GUI, without sacrificing reduced footprint, patching, services overhead etc.
Even with Core Configurator, there were still some bits that couldn’t be performed. Take Network Adaptor Protocols. How can you turn them off, turn them on, make changes, change orders etc? If you’re not sure what I’m referring to, I effectively mean:
How do you get these tick boxes from a command line?
John Howard, Senior Program Manager in the Hyper-V team, has blogged about a tool, developed by our very own Keith Mange, called NVSPbind, which gives users easier, granular control over network items they want enabled for their physical NICs and helps fills a gap in troubleshooting, optimising and hardening networking configurations on Server Core or Hyper-V Server. You can get all the info here.
As John says, with all utilities which change network configurations, you have to be extremely careful as you may disrupt or even lose network connectivity if you are managing a machine remotely. It may be handy to have Keith's other utility around just in case. http://code.msdn.microsoft.com/nvspscrub. NVSPscrub is a tool for removing Hyper-V Virtual Networking Configuration from the parent partition. It is especially useful in Server Core environments when the Hyper-V UI may not be available, and if you’ve fiddled with NVSPbind, and things have taken a turn for the worse!
Hi Matt - just saw this on Johns blog - very handy little utility to add to the other bits and bobs
As an aside - do you have a set of tools you like to "enhance" server core hyper-v deployments with?
for me its
Vendor specific support packs (e.g. Prolant Support Pack)
Hope all is well.
I would have a USB-stick laden with the tools. Core Configurator would be top of the list, and now the NVSP tools (although I've never needed them in my small demo environments!), and yes, the vendor-specific bits are important too!
Apart from those, I can't think of any others I'd run from my utility-USB stick!
I'm sure this will change over time!