Windows 7 Beta and Release Candidate Update

I just wanted to take a moment and post a few quick reminders.

As always, your key source for Discovering, Exploring, Piloting, Deploying and Managing Windows 7 are available on Springboard at www.microsoft.com/springboard.

For the latest tips and trick, follow us on Twitter at @MSspringboard


Managing Windows 7 with DISM

This week I am proud to feature guest blogger Justin Rodino. He is a Microsoft Desktop Experience MVP and a member of our STEP (Springboard Technical Experts Panel) program. His own blog is available here. This weeks guest blogger topic is on the new DISM tool. A great way to make deploying and maintaining Windows 7 images easier.

What is DISM

DISM – the Deployment Imaging Servicing and Management Tool is a new part of Windows 7 that has been created to help you manage (and deploy) images with greater ease. Previous versions of Windows included tools such as:

  • ImageX – a tool which allowed you to mount offline images
  • Pkgmgr – A device driver and package manager
  • PEImg – A WindowsPE Utility to prepare images once edited with pkgmgr
  • Intlcfg – An International Settings Configuration Tool

All of the above tools have very specific feature sets, but using these makes modifying and changing the created images very cumbersome. The first problem naturally was which tool to use when.  Once you figured this out, you had to go through a series of steps in order to get the image mounted – of which you could only do “offline” – and when completed you had to recompile or re-make the new image you wished to deploy.  With DISM, all of these tools become one and even better – you can do certain things to an “online” or live image.  What we’re going to do is take a quick look at DISM, get some information about our current installation as well as service it, whilst using it.

Starting DISM

The first thing we need to do in order to run DISM is have an elevated command prompt open.  Simply going Start –> Run –> cmd –> Enter won’t do the trick as that runs with user privileges.  What we need to do is either do Start –> Run –> Cmd –> Shift+CTRL+Enter or Click on Start type cmd and when it appear in the search box, right click on it and choose “Run as Administrator”:

1 (2)

Once we’ve got the elevated command prompt open – we can check this by looking in the task bar and the title should be prefixed by “Administrator:

2 (2)

Now if we type “dism” we should get help about dism.  If you get the message:

Error: 740

Elevated permissions are required to run DISM.
Use an elevated command prompt to complete these tasks.

Then you didn’t successfully get a command prompt with elevated privileges open.

Finding Basic Information With DISM

Now that we’ve got our command prompt ready for action, we can find some basic information about the OS we’re currently running. At the prompt type:

dism /online /Get-CurrentEdition

This tells dism we want to use the current version (/online) and the command – similar to PowerShell – tells dism we want to get information about the current edition (/Get-CurrentEdition).  Proving successful the results should return something like:

Deployment Image Servicing and Management tool
Version: 6.1.7100.0

Image Version: 6.1.7100.0

Current edition is:

Current Edition : Ultimate

The operation completed successfully.

Now let’s take it one step further.  As there are different versions of Windows 7 available, we have the potential to upgrade.  If we run dism (referencing the online image - /online) with /Get-TargetEditions, it will tell us what versions we can upgrade to (if at all possible).  So, if I run

dism /online /Get-TargetEditions

against a machine that is already running Windows 7 Ultimate, DISM should return:

Deployment Image Servicing and Management tool
Version: 6.1.7100.0

Image Version: 6.1.7100.0

Editions that can be upgraded to:

(The current edition cannot be upgraded to any target editions.)

The operation completed successfully.

So, scripting the above can prove useful if we need to interrogate or find information about our existing machine or its capabilities.

Changing the System with DISM

As well as querying the system for information, one of the most powerful features of DISM is its capability to “service” an “online” or live image.  This allows us the capability to change the OS on the fly.  For example, Windows 7 ships with numerous games and features installed that we might not want as part of our corporate build.  Using the functionality built in to DISM – whilst the OS is running – we can remove these features.

First, let’s look at what is installed and what we can change.  To do this, at the prompt we need to type:

dism /online /Get-Features | more

Again, we reference the current version (/online) and we use the command /Get-Features to show us the currently installed features.  The “| more” simply paginates the output so we can see it without having to scroll.  If we look through the list some of the features we want to remove can be seen:

….

Feature Name : FreeCell
State : Enabled

Feature Name : Minesweeper
State : Enabled

Feature Name : PurblePlace
State : Enabled

….

As the state of these currently shows “Enabled” we want to remove or disable them.  Using DISM, we can easily do this.  At the prompt we can type:

dism /online /Disable-Feature /FeatureName:<NAME GOES HERE>

Where we simply replace <NAME GOES HERE> with the feature from the list of results we got using /Get-Features.  NOTE: The features are CaSe SEnSItivE.  As an example, if we wanted to remove PurblePlace, we could simply enter:

dism /online /Disable-Feature /FeatureName:PurblePlace

at which time DISM will kick in and should return results like the following:

Deployment Image Servicing and Management tool
Version: 6.1.7100.0

Image Version: 6.1.7100.0

Disabling feature(s)
[==========================100.0%==========================]
The operation completed successfully.

Let’s now check to see if it was disabled:

dism /online /Get-FeatureInfo /FeatureName:PurblePlace

Deployment Image Servicing and Management tool
Version: 6.1.7100.0

Image Version: 6.1.7100.0

Feature Information:

Feature Name : PurblePlace
Display Name : Purble Place
Description : Purble Place
Restart Required : Possible
State : Disabled

Custom Properties:

(No custom properties found)

The operation completed successfully.

As we can see “State : Disabled” means we’ve disabled it.  Should we want to re-enable it, we can simply type:

dism /online /Enable-Feature /FeatureName:PurblePlace

At which time DISM will put the feature back on the machine in a similar way it removed it:

Deployment Image Servicing and Management tool
Version: 6.1.7100.0

Image Version: 6.1.7100.0

Enabling feature(s)
[==========================100.0%==========================]
The operation completed successfully.

Conclusion

As you can see DISM is a very powerful tool and the introduction of online/live servicing makes it even more useful to the IT professional.  To get more information about DISM or any of its functions or capabilities, use the /? flag when you get stuck.  Some examples include:

  • “dism /?” – which will tell you about the root level capabilities
  • “dism /online /?” – which will tell you about the online image servicing capabilities
  • “dism /online /Get-Features /?” – which will tell you about the Get-Features function

And from there, the sky’s the limit.  Happy DISM’ing.


Talking About Windows Talks UX, Security, and Reliability

Check out our latest addition to TalkingAboutWindows. Ever wonder how decisions were made about the user experience (UX) in Windows 7? Linda Averett is a key program manager on the Windows Team. From Aero Peek and Aero Snap to the design of the new Windows Taskbar. Linda discusses the key decisions we made to make Windows 7 a great end user experience. Find out why “it’s all about you, and what you do.”

Linda

Also this week meet Blessing Sibanyoni and Mikael Nystrom. Blessing discusses how he is working to deploy features like BranchCache and DirectAccess to reduce complexity and simplify his bank’s IT environment and listen in as Mikael with TrueSec talks about his customers' needs for a more secure, reliable OS.

Mikela      Blessing

Hear what they have to say and get heard. Join the conversation.


Get ready to deploy Windows 7 and Windows Server 2008 R2 with Microsoft Deployment Toolkit 2010 Beta 2

The Windows 7 and Windows Server 2008 R2 launches are just around the corner. As you prepare to deploy these operating systems, get a jump start with Microsoft Deployment Toolkit (MDT) 2010 Beta 2. Leverage this Solution Accelerator to achieve efficient, cost-effective deployment of Windows 7 and Windows Server 2008 R2.

MDT 2010 is the next version of Microsoft Deployment Toolkit, a Solution Accelerator for operating system and application deployment. New features such as flexible driver management, optimized user interface workflow, and Windows PowerShell can simplify deployment and make your job easier. MDT 2010 will support deployment of Windows 7 and Windows Server 2008 R2 in addition to deployment of Windows Vista, Windows Server 2008, Windows Server 2003, and Windows XP. Join the beta now! 

Microsoft Deployment Toolkit is the recommended process and toolset for automating desktop and server deployment. MDT provides you with the following benefits:

  • Unified tools and processes required for desktop and server deployment in a common deployment console and collection of guidance.
  • Reduced deployment time and standardized desktop and server images, along with improved security and ongoing configuration management.
  • Fully automated zero touch installation deployments by leveraging System Center Configuration Manager 2007 Service Pack 2 beta and Windows deployment tools. For those without a System Center Configuration Manager 2007 infrastructure, MDT leverages Windows deployment tools for lite touch installation deployments. 

Screenshot1

New Functionality

Microsoft Deployment Toolkit 2010 Beta 2 is a significant upgrade over MDT 2010 Beta 1.  MDT 2010 Beta 2 adds the following new features and functionality:

Deployment Workbench Enhancements

  • Manage multiple Deployment Shares from a single Deployment Workbench including local Deployment Shares or from a network location including standalone DFS shares
  • Replicate content between Deployment Shares through "Linked Deployment Shares" and use selection profiles to manage what content gets replicated
  • Multiple users can now interact with the same Deployment Share
  • Create folders to manage Drivers, Task Sequences, Operating Systems, and OS Packages
  • Drag-and-drop, copy-and-paste, and cut-and-paste between folders or between Deployment Shares

Powershell Capabilities

  • Anything done from within the Deployment Workbench can be scripted through Powershell
  • A drive provider has been added for enumerating folders, items, and properties
  • Cmdlets can be used for importing content such as Drivers, Operating Systems, Task Sequences, etc.

screenshot2

Task Sequence and Script Enhancements

  • Improved Diagnostics and Logging with more specific error messages
  • Real time logging directly to a network share
  • Enhanced log collection
  • Two new task sequence templates (Capture Only, Post OS Installation)
  • Pause and Resume a task sequence
  • Automatically detect and fix domain join problems
  • Improved user interface for client wizards
  • Deploy to a specified disk or partition (Vista or later)
  • Refresh Bitlocker encrypted systems to Windows 7 without decrypting the contents of the disk

Configuration Manager Enhancements

  • Improved wizard for creating task sequences
  • USMT 4.0 hard-link support

Next Steps


What’s new at Talking About Windows.com

If you haven visited Talking About Windows.com in a while, you are missing a lot!

You missed Microsoft Engineers like Ian Burgess talking about the engineering design of DirectAccess and BitLocker and Mario Garzia discussing application compatibility and how Windows 7 works with legacy applications.

You can interact with IT pros like Darren Baker, the National Director of Infrastructure Solutions for Sogeti USA talk about how virtualization and imaging has made implementing Windows 7 in his organization easier.

Talking About Windows.com is your chance to hear what Microsoft Engineers and IT pros like you have to say and gives you a chance to interact with them.

Hear what they have to say and get heard. Join the conversation.

IAN   Darren  

Mario


System Center Configuration Manager 2007 Service Pack 2 Beta released

Today I am featuring guest Blogger Jeremy Chapman from the Windows Product Team. To see more of Jeremy, view our latest VRT on Application Compatibility. To learn more, click here. Below is his interview with Jeff Wettlaufer from the System Center Team.

I recently interviewed fellow product manager, long-time friend and fellow “automator” of operating system deployment tasks, Jeff Wettlaufer, from the System Center team. He explained the new features in the recently released System Center Configuration Manager 2007 Service Pack 2 Beta (let’s just call it “ConfigMgr07 SP2” for short), and how that will help with Windows 7 deployment and management.   

Jeremy: What is ConfigMgr07 SP2 and where do people get it?
Jeff: Thanks for having me and thanks for saying configmgr and not sccm for once… SP2 adds support for new operating systems – Windows 7 and Server 2008 R2 and Windows Vista SP2 – along with exciting enhancements around Intel AMT integration. If you have the  Intel vPro hardware, there are many things we can do. Out of Box Wired/Wireless Management: Wireless Profile Management, End Point Access Control: 802.1x support, Access Monitor: Audit Log, Remote Power Management: Power State Configuration. You were at Microsoft Management Summit in May and already saw this, but we demoed waking Windows XP PCs up wirelessly and kicking off the deployment to Windows 7 using USMT and hard-link migration. Those machines were mid range Dell latitude laptops, and we migrated to Windows 7 with 4GB user data and apps in 18 minutes.

Win7 ACT

Jeremy: I saw that, it was amazing. There is a video of that on Microsoft PressPass. And I thought I was fast with 23-minute migrations from Windows XP on my computers. Let’s take a step back for a second. From the 10,000 ft level, how does ConfigMgr07 help with client management?

Jeff: A lot of people probably know about how ConfigMgr can help with their inventory, software update (patch) management, and application distribution - but you may not be aware of things like the ability to manage PCs over the Internet, in the ‘serverless’ branch, at home, on the road and wherever people work these days.  In addition, ConfigMgr can now deploy virtual applications in the same way as SMS and ConfigMgr have always delivered traditional physical formats.  We can stream apps to desktops, or deliver the apps locally in what’s called download and execute, so even mobile laptop users can use virtual apps.  There is a lot there and I’d encourage everyone to check out http://technet.microsoft.com/en-us/configmgr/default.aspx

Jeremy: Explain Internet-based client management.

Jeff: A lot of people say that mobile workforce management is a key challenge they face today on the client. Laptops are outselling desktops and people are taking these on the road, home or otherwise not connecting to the corporate network very often. So with ConfigMgr, we can manage ConfigMgr clients when they are not connected to your company network but have a standard Internet connections. This feature has a number of advantages, including the reduced costs of not having to run virtual private networks (VPNs) and being able to deploy software updates to remote users while they are traveling or at home. 

win7 AppV

Jeremy: Explain the new client hardware compatibility reports in HW inventory.

Jeff: We’ve updated the hardware compatibility reports in ConfigMgr to include the minimum bars for Windows 7 hardware compatibility, so you can see which machines in your environment are capable of running Windows 7 in a single view.  We did this for Vista, and we found it really helped organizations understand where they were at the hardware level.  We are taking that work forward to also help customers understand from their existing inventory of managed systems, which ones meet the minimum requirements before they start for Windows 7.  As well as helping understand the hardware side of readiness, we also are providing support for applications. In the past we have provided support for the Application Compatibility Toolkit through a connector, that brings the app knowledge right into the Admin console.  As ACT moves to version 6 for Windows 7, we will update the connector to support that effort.  The ACT data is a real hidden gem, in 1 view you can see your apps – and organize your testing to compare it in that 1 view to the vendor, the community, and even Microsoft.  This information can really help make the right decisions moving forward, and ConfigMgr can help migrate apps by supporting Application virtualization where needed.

Jeremy: How about the operating system deployment support.

Jeff: With any operating system deployment, you have to migrate user files off the old system, lay down a new OS, configure it with updates, packages and apps, then restore the user files and settings you migrated off in the first step. ConfigMgr can automate the whole process and do it without you having to visit the targeted PCs. I know you’ve got a lot of videos walking through the Lite Touch Installation process on the web, but ConfigMgr can even target the PCs for installation and kick off the process for you. Along the way we encrypt your user state, passwords and product keys, so it is more automated and enterprise-class.  ConfigMgr has built on the great work in deployment technology from the Windows gang, by embracing and integrating the tools usage like WinPE, USMT, BitLocker and more.  Our Task Sequencer helps to truly separate the hardware from the OS and application layers, by using the boot.wim and install.wim formats from Windows, and then providing a console UI experience to chain user data migration, applications and other settings. 

win7 Task Seq

Jeremy: Are all the Windows 7 deployment enhancements like the image servicing in DISM (Deployment Image Servicing and Management), hard-link migration, and Multicast included in the ConfigMgr SP2’s OS deployment?

Jeff: Like you saw at MMS, we do support USMT in ConfigMgr07, including hard-link migration. The Microsoft Deployment Toolkit 2010 Beta 2 extensions for SP2 enable hard-link migration without additional customization, or you can call the User State Migration Tool in a custom task to use the hard-link commands.  Multicast is also supported and since we use the Windows 7 deployment tools, dism.exe is leveraged as well.

Jeremy: When can we expect RTM release of SP2?

Jeff: We recently made the Beta available and the final version should be ready within 90 days of Windows 7 RTM. Everything depends on the customer feedback we get from the Beta though – quality is the priority.

Jeremy: Thanks Jeff. If you have ConfigMgr and want try to SP2 Beta, visit connect.microsoft.com, join the System Center Configuration Manager 2007 Service Pack 2 Connection and download SP2.