Weekly Post #7

There’s some debate going on at the moment about whether System Admins prefer their administration tools with a User Interface (UI), or Commandline.

My issue has been that traditionally, Microsoft Tools were great at performing whatever the task was against a single machine, but didn’t usually scale to performing the same task against, say 1,000 machines. That has been were commandline usually picks up the slack.

My passion for PowerShell isn’t exactly secret, but I’m also lazy. If I need to do one task on one machine I’m happy to click around and use the UI. If I’m trying to build out an environment, then I’ll move to commandline.

What do you prefer? Cast your vote in the Poll on the Polls page or on the right of the front page.

How do you prefer to administer your Windows environment?

View Results

Loading ... Loading ...

RTM – MAP 4.0 Released!

Microsoft Assessment and Panning  Toolkit 4.0

Microsoft Assessment and Panning Toolkit 4.0

According to the MAP Team Blog, MAP 4.0 moved out of Beta yesterday :)

Download MAP 4.0

What’s New with v4.0?
Version 4.0 of this toolkit has the following new features:
• Windows 7 Hardware and Device Compatibility Assessment
• Windows Server 2008 R2 Hardware and Device Compatibility Assessment
• Virtualization Candidates Assessment for Hyper-V R2 Server Consolidation
• Integration with the Microsoft Integrated Virtualization ROI Calculator
• Inventory of VMware Server Hosts and Guests
• User Interface and Proposal Customization for Partner co-branding
• Enhanced Usability and Improved Inventory Performance

Additional Features
• Virtualization Candidates Assessment for Hyper-V Server Consolidation
• Windows Vista Hardware and Device Compatibility Assessment
• Windows Server 2008 Hardware and Device Compatibility Assessment
• 2007 Microsoft Office Readiness Assessment
• SQL Server Instance Discovery
• Desktop Security Assessment for Anti-virus and Anti-malware Programs Installation
• Forefront Client Security/NAP Readiness Assessment
• App-V Infrastructure Readiness Assessment
• Power Savings “Green IT” Calculator

More infromation on this excellent tool is available on TechNet.

WAIK Beta Oddities

In the last post I talked about a first look at Microsoft’s MDT 2010 Beta 2.

My inplace upgrade from Beta 1 “apeared” to be successful. However when I went to update the deployment share, I received the following error:

Update Deployment Share - Failed

Update Deployment Share - Failed

This appears to be caused by a directory structure change in the WAIK between Beta and RC. Uninstalling WAIK, and resinstalling with the RC version will resolve this, but which version is the RC version? The WAIK RC is available from here as per Michael’s recent post

I have two ISO’s that I’ve downloaded recently from Microsoft:

en_windows_automated_installation_kit_x86_x64_ia64_dvd_349519.iso
KB3AIK_EN.iso

So according to the filename on the link on Michael’s blog I should be using KB3AIK_EN.iso. Except that this is the one that I did install when I built the server for MDT Beta 1.

Looking at the readme.htm in both ISO’s provides no clue either as neither are clearly marked as Beta or RC. Using Orca from the MSI SDK 4.5 I took a look at the ProductVersion and ProductName from the Property Table in the wAIKAMD64.msi. The values were the same for both:

ProductVersion = 2.0.0.0
ProductName = Windows Automated Installation Kit

In the end the only way I able to differenciate them was by the PackageCode in the Summary Information Stream:

Beta = {7FB35EC9-03A9-49AF-B0A1-81BDBA3949F5}
RC = {3BD5A1BF-F520-4BAA-9C7E-FAA12EF37AAF}

Restarting the MDT 2010 Beta 2 Workbench after the correct version of WAIK is installed, caused the following prompt:

Follow the steps as described to resolve the issue.

Follow the steps as described to resolve the issue.

I don’t know how the filenames got reversed because I’m pretty sure I didn’t rename either of the WAIK ISO’s, but it provided for an entertaining half hour!