What Should Server Managament Tools in Vista Look Like?

After we launched Windows Vista, a number of you commented to me that there was no way to install the Windows Server 2003 AdminPak (adminpak.msi) on Windows Vista to manage your existing infrastructure.   Though we did publish a KB document on how to get these tools working in Vista, it is not as clean as it was in Windows XP.

As we get further into the release cycle for Windows Server codename Longhorn, and as Rick and Rod head on on the Future of the Server Room Tour, I wanted to get your input on what administration tools that would run on Longhorn look like.  Should it be similar to what we had before, or should we leverage the new Server Manager functionality and make it work on Vista?  Should the tools in Vista manage Longhorn servers only or previous versions?  Which versions should be managed and which features/functionality?

Let us know what you think server management tools should look like in Windows Vista by leaving a comment.


Comments (5)

  1. Simon Collier says:

    Server Manager is nice and all, but that would be a secondary concern to me: Just getting the MMCs to work at all should be priority 1. There are MMCs that were released in 2003 R2 that are still not supported in XP or Vista properly (to my knowledge) so anything fluffy like remote Server Manager is not high on my list of must-haves.

    I think Server Manager is excellent for setup and removal of components on the local machine, but in remote administration you’re probably looking to do something specific, and in that case the MMC probably holds more value.

  2. DamirB says:

    Thanks for the comments Simon.  My question regarding Server Manager really was to find out if a remote-enabled version of it makes sense for IT Pros to administer server resources.  Really, it comes down to what should remote server management tools in Vista look like in order for them to provide value and benefits to IT Pros?

  3. ye110wbeard says:

    Is there anywhere actually to get a REALLY nicely documented version of the command line goodies that are there (Always have been but I’ve not found a really detailed explaination of the goodies buried in SYSTEM32).

    Items like "NETSH" and "DISKPART", we all know "FTP" is sitting in there as well as TELNET.  (Cough… almost like Unix is sitting there!)  (which in the case of DISKPART was a lifesaver to partition an internal disk while DISKMGMT.MSC was untouchable due to a corrupted O/S from a virus)

    Hmmm.   Is there a chance we get those direct electrical implants so I can just "Think" it straight to the server?

    Uhhh better not.   Can you imagine what would happen if we DID have a direct interface from the Brain to the server?  

    Systems Admin has a "really bad day" and user Passwords are automatically reset to 63 character AlphaNumeric special character and mix in a little Japanese characters with cyrillics!

    Just think what would happen if the "BOFH" had this.   (Don’t know this guy?  Search it online;  Just about every computer guy knows the texts of the "BOFH" and of course the "PFY")

    Cheers and good day all…

    Sean the ‘puter guy

  4. Benoit Lemyre says:

    I think server manager tool that woul;d permit to manage either a longhorn or win2k3 environnement would be ideal because we will have to deal with both environnement and the idea of having 2 sets of tools to manage them would be for me a big mistake.

  5. bklym says:

    I agree that the tools need to work on both Server 2008 and Server 2003 – one tool that can handle both is way better than 2 separate sets of tools.

    Though I would like to have ‘improved’ tools (read easier to use) on Vista, I also expect to be using Windows XP for awhile – so I would like tools that would work on both.

    So having a remote server manager type remote tool that works on Vista and XP, that can manage all the features of Server 2008 and Server 2003, that would be my goal. If there is a real reason to have the tools work on Vista only, I probably could build a case for a new admin. workstation, but it is not my first priority.

Skip to main content