Time: Wed Dec 21 07:55:38 ALMT 2011
Springboard Series Insider – December 2011 Edition
https://profile.microsoft.com/RegSysProfileCenter/subscriptionwizard.aspx?wizid=0a38cd1e-d6dd-4236-aae0-41a581c8524a&lcid=1033
Sign up for this newsletter |
https://profile.microsoft.com/RegSysSubscriptionCnt/SubCntDefault.aspx#NewsLetterSub
Unsubscribe |
https://profile.microsoft.com/RegSysProfileCenter/Infodefault.aspx
Update your profile
NOTE FROM THE EDITOR
Season's greetings, and welcome to a special edition of the Springboard Series Insider!
Between our recent tour to South America (make sure you check out the great videos from
http://go.microsoft.com/?linkid=9794932
Chile ,
http://go.microsoft.com/?linkid=9794933
Argentina ,
http://go.microsoft.com/?linkid=9794934
Peru , and
http://go.microsoft.com/?linkid=9794935
Brazil ), the releases of Microsoft Assessment and Planning (MAP) Toolkit 6.5 and Security Compliance Manager 2, and preparations for
beta, we have been quite busy!
With many people being out of the office this time of year, we know that many of you are also quite busy taking advantage of this time to deploy applications, updates, and packages, and upgrade your environments to Windows 7. As a result, we would like to take this opportunity to give you a special edition of the Springboard Series Insider dedicated to deployment. We have a great piece from Microsoft Deployment Toolkit (MDT) guru Michael Niehaus, deployment advice from community experts like Johan Arwidmark and Rhonda Layfield, and guidance from the Internet Explorer and Office teams.
With the year winding down, I want to give a huge "thanks" to the Springboard Series Insider Team—Heather, Trudy, Anurag, Andy, Brian, and Brad—and all of our Springboard Series Technical Expert Panel (STEP) members who help to provide and assemble great content for you each month.
So, take a break and dive into this month's Insider. I hope you enjoy reading it as much as we enjoyed putting it together for you. We look forward to continuing to bring you resources that help you to be the best IT professional you can be, and I want wish you a healthy and happy new year.Stephen Rose
Sr. Community Manager, Microsoft Windows Client IT Pro
mailto:stephen.rose@microsoft.com
stephen.rose@microsoft.com
FIVE TIPS FROM THE DEPLOYMENT DOCTORBy Rhonda Layfield, Microsoft Setup and Deployment MVP and STEP Member
#5 – Application Testing
Quite often, application testing doesn't get the respect it deserves. I can't tell you how many times I've met with deployment teams around the world to discuss planning their deployment projects only to find that they have not even considered application compatibility testing. They just assumed testing would be done during deployment, but by whom they don't know. Proper application testing can make or break an entire deployment solution because, ultimately, when you migrate a machine from Windows XP to Windows 7, if the applications users need to perform their job don't work, then the deployment was not successful. Sure you got a new operating system on the machine, but the machine is pretty much useless without working applications. Windows XP has been out for a long, long time now, and, as you know, over time new versions of applications are created.
Another common challenge for organizations today is multiple versions of the same product. Many users get newer versions of applications due to attrition. A computer purchased today will likely get Microsoft Office 2010 installed while the rest of the organization might still be running Microsoft Office 2007. And when you get into websites and all the add-on software needed to view and interact with different sites, there can be a seemingly infinite number of applications (and different versions of them) installed.
When you deploy a new operating system, it's the perfect time to get all users running the same software—right down to the version. Believe me, your help desk personnel will thank you. The
http://go.microsoft.com/?linkid=9794936
Microsoft Application Compatibility Toolkit (ACT) 5.6 is a free download from Microsoft that will assist you in testing your applications. ACT can evaluate which applications are currently running in your environment; then, based on that information, you can choose which applications, and which versions of them, become the corporate standard. Not all applications that were built to run on Windows XP workstations are going to run on Windows 7 (big surprise right?), so before you begin deployment, find out which applications will work, which ones will not, and which ones can be mitigated to run on Windows 7 (even if they are not running at 100 percent). ACT also tests versions of Windows Internet Explorer to ensure you can still access websites properly.
One of my favorite features of ACT is that the tool is community-based. What that means is that organizations around the world have fed information into the ACT database, reporting which applications work, which ones don't, and how to resolve some of the issues. And you have access to all this information. It is very likely if you are having an issue with an application, ACT probably already knows about it and can supply you with a quick fix.
Microsoft Architect and Technical Lead Chris Jackson, a.k.a. The App Compat Guy, has provided a wealth of information—complete with his
http://go.microsoft.com/?linkid=9794937
blog , videos, and more—on how to get started using ACT. You'll find Chris's contributions and additional fantastic resources for ACT and Windows 7 deployment, including a Windows 7 Application Compatibility List and Windows XP to Windows 7 Migration Guide, on the
http://go.microsoft.com/?linkid=9794938
Springboard Series Application Compatibility zone .
#4 – Educate End Users
Migrating your operating system doesn't necessarily mean that your deployment was successful or that your users view the deployment as successful. This is prime time for your IT team to really shine. Think about how you feel when you change the operating system or an application on your own computer and can't figure out how to perform the simplest tasks such as opening documents or printing. I remember the first time I saw the Ribbon feature that is part of the Microsoft Fluent user interface. I was presenting at a conference and about 40 minutes before I was supposed to start, I remembered I needed to print my demo cheat sheet (okay, that's supposed to be a secret, but sometimes if someone asks a question in the middle of a demo I forget what I was going to do next so I rely on my cheat sheet). No problem (or so I thought) I got out my USB stick and copied my doc to it. Then I took the USB out to one of the computers hooked up to a printer, opened the doc and got my first look at the Ribbon. I just sat there for a second thinking "How hard can this be?" Then I started freaking out a bit because I really needed to be at the presentation, but I couldn't find the Print option. Thank goodness I remembered Ctrl + P, which worked just fine. But my first experience with the Ribbon was not a happy one. We've all been there. So think back to how you felt, and help your end users with a little education.
If you don't already have one, create an IT newsletter and document the top 10 ways to perform the simplest and/or most common tasks. Include screenshots and step-by-step directions. For example, you can show users a comparison between the same task in Windows XP versus Windows 7. In Windows XP you opened a document by opening the application first (Word for example); then chose Open from the File menu, and browsed to the document or double-clicked on the document in Windows Explorer. Now, in Windows 7, you can open documents from the Windows Taskbar using the new Jump List. Use screenshots to show how to use Jump Lists. Truly educating your users would involve a full one (two or maybe three) day class taught by experienced trainers. If your organization is not planning education for your users, don't leave them hanging; help them embrace Windows 7.
#3 – Update All Routers and Switches
Network components get outdated just like any other software. Of course, network deployments rely on your network routers and switches. So, ensuring your routers and switches have the most up-to-date software (BIOS and patches) can help in many ways. Now before you shoot this tip down… I am not suggesting that you update your network infrastructure at the same time you deploy a new operating system image. That would be ridiculous. What I am suggesting is that you speak with your networking team to find out if the latest updates have been applied to your network infrastructure. If not, this would be a great opportunity to get the network in its optimal condition; this way, your 5, 10 or 15 GB operating system images will be deployed quickly, efficiently, and with the least amount of re-transmits possible. One of the biggest benefits is Windows 7 will be thought the hero for better network performance.
#2 – Use the Right Tool for Your Environment
I present at conferences all over the world, and the question I easily get asked most often is "Which tool should I use—Microsoft System Center Configuration Manager, Microsoft Deployment Toolkit (MDT) or Windows Deployment Services (WDS)?" The answer is simple, though it primarily depends on the type of customer you are. If you are an Enterprise customer, you probably already own and use System Center Configuration Manager. If you already own it, and it is being used in your environment, you should use it. Configuration Manager gives you the option to perform Zero-Touch or Lite-Touch Installation for operating system deployments. Plus, the reporting capabilities are fantastic.
If you don't own Configuration Manager, MDT is the tool I would choose. MDT is easy to set up and manage, and it doesn't require installation on a server or any network infrastructure components. My favorite feature of MDT is how easy it is to make changes later. Whether those changes are big or small doesn't matter. For example, you could change the version of an application being deployed in less than five minutes, or swap out the operating system you are deploying in less than two minutes.
http://go.microsoft.com/?linkid=9794939
MDT is a free download from Microsoft, and the only software it requires is the Windows Automated Installation Kit (also a free download).
Windows Deployment Services requires DHCP, DNS, and Active Directory and must be installed on a server. You can only deploy bare metal, fat operating system images. Fat images include the operating system plus all your applications. The biggest drawback to using WDS is making changes to your images, including simple changes such as the version of an application. To change the application, you must deploy the image to a machine, make your changes, create a new image, and add it to WDS. Of course WDS does have positive features; integrating with Configuration Manager or MDT provides extended functionality for both products. When integrated with the other products you get PXE boot and multicasting of your image, which is not possible with either MDT or Configuration Manager alone.
#1 – Build Your Deployment Solution to Last
In almost every deployment I have participated in, I've seen a situation in which some piece of the deployment (an application, a driver, or any one of the other 200 things you are attempting to do) doesn't work, and someone says "Let's not worry about that now; we can always come back to it later—let's just get this working." And what happens? Nobody ever goes back to address those temporary fixes. Over time, these fixes don't work anymore, and you're left with all those issues being exposed and causing headaches for years.
Deploying an image to a computer one time probably isn't the last time that computer will receive an image. What a lot of people don't think about is re-imaging machines today as a valid troubleshooting step. We do it all the time. When is the last time you spent four hours troubleshooting an issue on a desktop machine? Today, most of our user's data is stored on network shares, so we don't need to worry so much about data anymore. When a machine starts acting up the easiest and quickest way to fix it is to re-image the machine. So while you're building your deployment solution, think about living with it for the next five years. Is it set up to last? Did you take the time to really do the job right or did you just do it fast?
If you truly want to be a deployment hero, the last idea I'd like to leave you with is this: Contact your help desk personnel and ask what the top 10 issues are that initiate phone calls to the help desk. Resolve those issues in your new image. It will be noticeable to all.
Happy deploying!
http://go.microsoft.com/?linkid=9794940
Rhonda Layfield has been in the IT industry since 1982. She is a Microsoft Setup and Deployment MVP and Desktop Deployment Product Specialist who also offers lecture-based (demo-driven) and hands-on deployment courses. For more information, visit
http://go.microsoft.com/?linkid=9737939
www.DeploymentDr.com .
WINDOWS DEPLOYMENT "SNACKS" FROM THE SWEDISH CHEFBy Johan Arwidmark, Microsoft Setup and Deployment MVP and STEP Member
For the last 21 years, I have been a die-hard deployment fan. It all started with automating my Commodore Amiga Workbench environment, which led to DOS 3.30 installations and building various menu systems to get my gaming going. DOS led to Windows, and many Windows versions followed. When I was in high school, I started to work, after school hours, for a local original equipment manufacturer (OEM), building and deploying machines for corporate customers. I quickly learned that automation led to more machines deployed by the hour, and a bigger paycheck from my manager, something quite important when you are 17 years old.In this article, I'll share my thoughts on deploying the current versions of Windows, using state-of-the-art deployment solutions.
For the last 21 years, I have been a die-hard deployment fan. It all started with automating my Commodore Amiga Workbench environment, which led to DOS 3.30 installations and building various menu systems to get my gaming going. DOS led to Windows, and many Windows versions followed. When I was in high school, I started to work, after school hours, for a local original equipment manufacturer (OEM), building and deploying machines for corporate customers. I quickly learned that automation led to more machines deployed by the hour, and a bigger paycheck from my manager, something quite important when you are 17 years old.In this article, I'll share my thoughts on deploying the current versions of Windows, using state-of-the-art deployment solutions.
Why Should You Be Using Microsoft Deployment Solutions?
Back in the 1990s, there was no such thing as a standard deployment solution; just about every company had its own tools and tricks. Microsoft did not do much either—at least not until 2003, when Microsoft released the Business Desktop Deployment 1.0 solution as its own solution for desktop deployments. The most recently released version of a deployment tool is Microsoft Deployment Toolkit (MDT) 2010 Update 1. As of this writing, it has been downloaded well more than 600,000 times from the Microsoft Download Center.
The benefit of using a standard solution, such as MDT 2010, with or without Microsoft System Center Configuration Manager, is that you are not alone if you run into problems. There is plenty of guidance and training available, and MDT is fully supported by Microsoft.
Deployment Scenarios Explained
Microsoft deployment solutions support five primary scenarios for Windows deployment:
- New computer. The most common scenario. Also known as the bare metal scenario, this scenario occurs when you have a blank machine you need to deploy, or an existing machine you want to wipe and redeploy without caring about any existing data. The setup starts from a boot media, using CD, USB, ISO, or PXE.
- Refresh. A reinstall of the same machine, with or without using the User State Migration Tool (USMT) that is part of the Windows Automated Installation Kit. Sometimes called wipe-and-load migration, this is the new "upgrade." The process is initiated on the running machine, either local or remote.
- Replace. Replacing the old machine with a new machine. A computer replace is similar to the Refresh scenario. But since we are replacing the machine, we divide this scenario into two main tasks: Backup of the old machine, and bare metal deployment of the new machine. As with the Refresh scenario, we can use USMT to back up and restore settings.
- Offline Media. You can also generate a full offline media, including all the files needed for a deployment, and use that media (CD, DVD, or USB devices) to drive the deployment.
- OEM. MDT also supports a special OEM scenario that you can use if you want to prepare an image in house and then send it to an OEM for cloning.
The Art of Automation, Quality is King
A central part of modern, efficient deployment is automating as much as we possibly can. We can still provide some input when starting a deployment—for example, by using a deployment wizard—but after those initial (optional) selections, everything deploys automatically. In MDT, most of the settings are done by configuring the MDT rules (Customsettings.ini) and by designing task sequences that will control which actions are executed during deployment. In general, the more you automate, the higher quality you get.
Figure 1. The MDT Windows Deployment Wizard, with a selection of Windows Server task sequences, ready for deployment.
Enabling Dynamic Deployments
MDT enables something I call dynamic deployments, which allow for deployment task sequences to behave differently depending on what settings we have on the deployment server. For example, I can have the deployment solution generate settings based on hardware model, location, whether it's a laptop or desktop, and whether the machine is assigned to a role.
Figure 2. The power of dynamic deployment: A MDT task sequence deploys a full-blown Configuration Manager 2012 Release Candidate 1 site server because I assigned the Configuration Manager Site Role to the machine being deployed.
http://go.microsoft.com/?linkid=9794941
Johan Arwidmark , Microsoft Certified Systems Engineer (MCSE) and Microsoft MVP in Setup & Deployment, is a consultant and all-around geek specializing in enterprise Windows deployment solutions. He speaks at several worldwide conferences each year, including MMS and TechEd, and is actively involved in deployment communities like
http://go.microsoft.com/?linkid=9794942
deployvista.com ,
http://go.microsoft.com/?linkid=9794943
deploymentcd.com and
http://go.microsoft.com/?linkid=9794944
myITforum.com . He also recently helped launch a new deployment community called
http://go.microsoft.com/?linkid=9794945
Deployment Research .
WHY YOU NEED A REFERENCE IMAGE, AND HOW TO A CREATE ONEBy Mikael Nystrom, Microsoft Setup and Deployment MVP and STEP Member
What is a Reference Image?
Basically, it is a customized operating system image that you will use when you install Windows. A reference image can have many different names, and if you haven't heard of a reference image, you may have heard of a golden image, master image, corporate standard image, or custom image.
So, Why Would You Need a Reference Image?
It's all about time. Let's say that you need to update (refresh) a Windows XP machine to Windows 7. How much time do you have to reinstall the PC before it must be finished?
Let us do some calculations. The PC is running Windows XP, with Microsoft Office, and we use User State Migration Tool (USMT) 4.0 to save the user state locally on the drive, install Windows 7, run Windows Update, install Office 2010, install all drivers, run Windows Update again to get the Office updates, and then you are done.
- USMT = 2-3 minutes
- Windows 7 = 20 minutes
- Windows Update = 10-20 minutes
- Office 2010 = 10-15 minutes
- Windows Update = 10-20 minutes
That is somewhere between 57 and 88 minutes and the question is: Is that ok or not? This timeframe will increase as you address more patches and updates, Windows Internet Explorer, the Microsoft.NET Framework, and so on. It could take as long as three to four hours to install a PC before it is ready and maybe, just maybe, that is time you or your users don't have.
One of the issues is that when the operating is new and fresh there aren't many updates; the difference in time between using the standard image that Microsoft provides you with and using your own custom image isn't that big, so customers use the default image. But that also can mean that after you have been deploying Windows 7 for six months, you suddenly need to learn something new and change the process. That's just a bad idea.
There are other reasons for needing a reference image:
- Copy Profile – This feature will copy Profile settings from the local Administrator account to the new user that logs on. These profile settings won't be always needed, but the need does arise from time to time. This situation could also be addressed using scripts, but generally the only supported way is to use "Copy Profile."
- The Look and Feel of Windows – While it's not really necessary to change the look and feel of Windows, it can make a difference in the end user experience. Let's say that a user logs on and everything is perfect. You will most likely get not only a happy user but also an efficient user, since he or she can start working immediately instead of spending an hour adjusting various settings. It's fun to calculate this: Let's say you have 1,000 users and it takes each of them one hour to address basic settings. That, my friend, is 1,000 billable hours down the drain…
I prefer the thin image, since that gives me more flexibility, but that also means that applications will need to be installed during deployment of the image, and that takes time. In reality, most reference images I create are hybrids.
Which Applications Should Go Into the Reference Image?
There are some criteria to keep in mind and here is my list.
- The application must survive a Sysprep.
- The application should be a "big" application so that we save time.
- The application should not be one that needs updates every day.
So here are some good applications to include in your reference image:
- Microsoft Office
- Microsoft Visual Studio
- Internet Explorer (a newer version than we have in Windows)
- .NET Framework
These applications take considerable time to install, they are updated automatically by Windows Update, and they survive a Sysprep. If you need them on your computer, they are perfect candidates for including in the reference image.
So, if these are the good applications, it follows that there must be some not-so-good applications, and there are.
- Antivirus – Antivirus software should never be in the reference image, because it can interfere with Sysprep. It also needs to be updated frequently. Additionally, some antivirus software can have "identify" issues and may not really understand what happens when Sysprep runs.
- Readers – Some readers are updated frequently, which means that if you put one of them in the reference image and then deploy the image, you will need to install the new version. This will trigger an uninstall of the old version and then an install of the new version, and that will not really help you, because it takes a longer time.
- Drivers – Even if it's possible to do so, drivers should not normally be included in the reference image. If you use a normal deployment solution, it will detect which drivers are needed and install them into the operating system during deployment.
How Do I Create a Reference Image?
Now the fun begins. Essentially, you can create a reference image two ways: through a manual or automated process.
Manual process
This is easy: Just install Windows, run Windows Update, install all the applications, and tweak all settings. When you are done, run sysprep.exe /generalize /OOBE, wait for it to shut down, and then boot on WinPE, run ImageX to capture the image, and turn it into a .WIM file. Most importantly, you need to remember every step you took, since you will need to regenerate or update the reference image approximately 20 to 40 times over the next five years. So, I have to be honest: Even if a manual process is possible, I will not use it, nor will I recommend it.
Automated process
With Microsoft Deployment Toolkit, you can automate the process so that the only thing you need to do is to start a virtual machine on an ISO Image and it will boot up, install Windows, install your applications, run Windows Update, tweak your settings, run Sysprep, and capture itself and finally turn itself off. This is the way to go!
The basic steps are:
1. Download the
http://go.microsoft.com/?linkid=9794946
Windows Automated Installation Kit (Windows AIK) for Windows 7 and install.
2. Download the
http://go.microsoft.com/?linkid=9794947
Microsoft Deployment Toolkit (MDT) and install.
3. Download
http://go.microsoft.com/?linkid=9794948
Internet Explorer Administration Kit 9 (IEAK 9) and install.
4. Open Deployment Workbench in MDT.
5. Import Windows.
6. Import Office.
7. Import Internet Explorer 9.
8. Create a task sequence in MDT.
9. Enable the Windows Update steps in the task sequence
10. Update the deployment share
11. Boot a virtual machine on the ISO image that was created during the update of the deployment share
12. Follow the wizard
13. Wait until the installation is done
Congratulations! You have a reference image!
I Need More Information!
The number one site for more information is the
http://go.microsoft.com/?linkid=9794949
Springboard Series for Windows 7 . There you will find almost everything there is to know around Windows 7 deployment, and more. The Springboard Series also offers sites for
http://go.microsoft.com/?linkid=9794950
Office 2010 and
http://go.microsoft.com/?linkid=9794951
Internet Explorer 9 to name a few.
Of course, there are other resources as well. Here are some sites and blogs where you can find more information about deployment:
-
http://go.microsoft.com/?linkid=9794952
Deployment Bunny blog
-
http://go.microsoft.com/?linkid=9794945
Deployment Research website
-
http://go.microsoft.com/?linkid=9794944
myITforum.com
Happy deployment!
http://go.microsoft.com/?linkid=9764561
Mikael Nystrom is a Microsoft MVP and Microsoft Certified Trainer (MCT) specializing in deployment, virtualization, and management. He has been involved in Technology Adoption Programs (TAPs) for several Microsoft products and technologies including Windows Server, Hyper-V, and Windows 7. In addition to his work as a speaker, trainer, and consultant, Mikael frequently shares technical news and insights through his
http://go.microsoft.com/?linkid=9764562
blog and on
http://go.microsoft.com/?linkid=9764563
Twitter .
FIVE THINGS YOU MIGHT NOT KNOW ABOUT MDT 2012By Michael Niehaus, Senior Program Manager, Microsoft Deployment Toolkit
Most of you have probably seen the announcements about the latest version of the Microsoft Deployment Toolkit (MDT) 2012, MDT 2012 Beta 2, which is currently available for beta testing through
http://go.microsoft.com/?linkid=9794953
Microsoft Connect . (If you haven't downloaded it yet, there's still time to try it out and provide your feedback.) And you've probably already heard about the biggest new features, including:
- Support for Microsoft System Center Configuration Manager 2012. User Driven Installation (UDI) and Zero Touch Installation (ZTI) both now work with Configuration Manager 2012 (while still supporting Configuration Manager 2007, too).
- New User Driven Installation Wizard and Designer, which provides extensibility and more scenarios for greater Configuration Manager deployment flexibility.
- Integration with the Microsoft Diagnostics and Recovery Toolset (DaRT), which makes all DaRT tools (including remote control) an integrated part of the MDT Lite Touch boot images.
- Monitoring capabilities for Lite Touch deployment, so that you can easily see which computers are currently being deployed.
But MDT 2012 is more than just these noticeable new features. There are many other enhancements in the background, out of sight, which ensure that your deployment process is smooth and trouble-free. Those enhancements are what I would like to focus on today:
#1 – Improved Partitioning Support
One of the primary goals with MDT has always been "deployment that just works." That means figuring out the right thing to do, regardless of what's thrown at it, without requiring any fancy task sequence customization. With various ways of partitioning disks, this has been somewhat challenging. Take Windows 7 for example: You might have a system with a single partition (a typical result of a standard Configuration Manager task sequence). You might have one with a small boot partition at the beginning of the disk and then an operating system partition (typical if you install from Windows 7 media directly). You might have a system with the operating system partition and then a small boot partition (typical if you used MDT Lite Touch to deploy the system). Regardless, you want the process to work.
With MDT 2012, we have implemented two simple rules (for Lite Touch and Configuration Manager):
- When refreshing a computer, we want to deploy the new operating system to the same partition as the existing operation, regardless of what partition that might be. The task sequences will automatically adjust.
- When deploying an operating system to a new computer, we want to create the recommended partition structure for that operating system [Windows XP, Windows Vista, Windows 7; Unified Extensible Firmware Interface (UEFI) or not].
If we have done our jobs correctly, we won't need to think about partitioning any more.
#2 – Ability to Detect "Dirty" Deployments
So what exactly is a "dirty" deployment? Probably not what you think, so let me describe the basic scenario: You've performed an operating system deployment, but it failed (due to configuration issues, missing drivers, pressing the power button, or whatever other reason). Now when you try to do a new Lite Touch deployment to that same computer, there are still remnants of the previous deployment on the disk, and these interfere with the new deployment. In effect, the computer is "dirty" and that "dirt" gets in the way of subsequent deployments.
In MDT 2012, we have added logic to detect "dirty" computers and automatically prompt to clean up the mess (even if you power the computer off in the middle of a deployment). So, if you see a prompt like this:An existing in-progress deployment was found but is not in an expected state. Would you like to ignore this in-progress deployment and start a new one?
You can just say "yes" and MDT 2012 will remove all signs of the previous deployment task sequence so that the new one can proceed without any interference.
#3 – Support for Windows PowerShell Inside the Task Sequence
For those of you who are familiar with the inner workings of MDT, you know that we have used Visual Basic Script (VBScript) for almost everything during the deployment process. That has a lot of benefits for us: There is no need for any runtime components on existing or new computers, lots of visibility into what it being done during every step, ability to tweak the scripts for your specific needs, and more.
But the time will come when we need to move forward from VBScript and begin using Windows PowerShell. While MDT 2012 itself doesn't yet do this (and don't worry, it's not something that will happen overnight —it will be a gradual migration over a period of years), we wanted to make sure that we started laying the groundwork for this today. The new "Run PowerShell Script" task sequence action is the first step. It has some nice features, including:
- Automatic, integrated logging support. MDT will capture the output of every Windows PowerShell script into the BDD.LOG, just like any other MDT script.
- Progress display. MDT will show the progress of the Windows PowerShell script in the task sequence progress dialog, so you know what the script is doing.
- Task sequence variable integration. Windows PowerShell providers will expose all task sequence variables and variable lists to the Windows PowerShell script, making the scripting task easier.
#4 – Deployment Using Native UEFI
First, a simple observation: UEFI is the way of the future; BIOS is on its way out. Over the coming months, you will see more and more emphasis on UEFI, so it's important that your deployment tools are able to support it. You probably don't even realize how many computers today ship with full UEFI support (the majority of enterprise laptops), but typically these are operated in "compatibility mode" so they look like they are using a legacy BIOS.
With MDT 2012, we want to enable enterprises to start moving away from the legacy BIOS and fully embrace UEFI. MDT fully supports Lite Touch deployments to computers using UEFI (and not using the "compatibility module"). Be sure to read up on UEFI and background information on why it's important through my
http://go.microsoft.com/?linkid=9794953
TechNet blog post on this topic.
#5 – Eases Migration from Windows XP to Windows 7 and Works with the Windows 8 Developer Preview
Many of you are running Windows XP. And you're quickly running out of time to migrate to Windows 7 before Windows XP support ends in April 2014. Think about it: Windows deployment projects can take years to complete, and if you haven't started yet, it's probably time to start worrying. So that's obviously the biggest focus in MDT 2012—making sure that Windows XP to Windows 7 migration goes smoothly.
But there's another new operating system, Windows 8, coming down the line, so we have added in some basic support for performing lab deployments of the Windows 8 Developer Preview, using either the Windows Automated Installation Kit (Windows AIK) from Windows 7 or the new Automated Deployment Kit (ADK) for Windows 8, so that you can learn what's changing in this new release.
Fortunately, there won't be many changes in the deployment process for Windows 8, so don't expect to see anything drastic.Rest assured your current investments in MDT and Configuration Manager will be preserved, and we'll continue to work on MDT to ensure that you're always ready to deploy versions of Windows operating systems as soon as they come out, and with little fuss.
More to Come
We're not done yet. MDT 2012 Release Candidate 1 is due out during the first quarter of 2012. The main focus for that release is addressing customer feedback from those who have already reviewed the functionality in MDT 2012 Beta 2. There's still time to do some lab testing and provide your feedback through
http://go.microsoft.com/?linkid=9794953
Microsoft Connect , so please send us your thoughts and help us ensure that this MDT release is the highest quality possible.
http://go.microsoft.com/?linkid=9794955
Michael Niehaus is a senior program manager in Microsoft's Solution Accelerator Team responsible for the Microsoft Deployment Toolkit, a free collection of tools and guidance for deploying Windows and Office faster and more efficiently. Prior to joining Microsoft in 2004, Michael spent his entire career in enterprise IT, focused on deploying and managing Microsoft software.
ANNOUNCING INTERNET EXPLORER 9 VIRTUAL LABSBy Anurag Pandit, Product Manager, Windows Internet Explorer
If you're an IT professional looking to deploy Windows Internet Explorer 9, there are many resources that can help you get started. TechNet hosts some great content that is organized by the deployment lifecycle. You can quickly get up to speed on
http://go.microsoft.com/?linkid=9794956
Internet Explorer Administration Kit (IEAK) and
http://go.microsoft.com/?linkid=9794957
what it can do for you , and how to
http://go.microsoft.com/?linkid=9794958
enable automatic detection and configuration of browser settings . Although the information in articles like these helpget you up and running quickly, the best way to learn is to try something yourself.
The Internet Explorer team has three virtual labs that give you the hands-on application compatibility, deployment, and management compatibility experience you need. All you have to do is to browse to a site and launch the virtual lab.
-
http://go.microsoft.com/?linkid=9794959
TechNet Virtual Lab: Internet Explorer 9 Application Compatibility
This lab is designed to introduce you to tools such as Internet Explorer Compatibility Test Tool, Microsoft Application Compatibility Toolkit, Internet Explorer developer tools, and more.These tools can help you identify compatibility issues quickly and teach you how to apply Group Policy to address compatibility artifacts.
-
http://go.microsoft.com/?linkid=9794960
TechNet Virtual Lab: Internet Explorer 9 Deployment
This virtual lab gives you hands-on experience with various technologies that can be used to easily deploy the browser throughout your enterprise environment.
-
http://go.microsoft.com/?linkid=9794961
TechNet Virtual Lab: Using Security Compliance Manager for Internet Explorer 9
It is vital to help ensure that your company has the best security policies in place. This virtual lab shows you how you can use Microsoft Security Compliance Manager to secure your browser deployment. The tool enables you to create a baseline for security settings that can be applied to browsers throughout your company's environment.
http://go.microsoft.com/?linkid=9794962
Anurag Pandit is Product Manager with Microsoft's Internet Explorer Business Group. Anurag started his career after graduating from UC Berkeley and prior to his current role, he was a Program Manager helping improve various developer and enterprise products such as MSMQ, WCF, and BizTalk Server.
'TIS THE SEASON FOR OFFICE 2010 DEPLOYMENTBy Andy O'Donald, Product Manager, Microsoft Office
For many IT departments, the holiday season is also the deployment season. Desktop upgrades can sometimes be disruptive to the business, so the holidays can be a great time to lessen that impact on business units. This holiday season is an especially important deployment opportunity as we approach the
http://go.microsoft.com/?linkid=9794963
end of support for Microsoft Office 2003 and Windows XP SP3 . April 8, 2012 will mark the two-year countdown for end of support. Since for many companies large scale rollouts can take between 18 and 32 months, it is important that customers start the transition early enough to avoid security, hardware, and software support issues.
Luckily, Microsoft has many resources to help you jumpstart your pilot or full-scale deployment of Microsoft Office 2010. What follows in this article is a quick reference for key articles that will help you get Office 2010 out to your company. I'm going to assume you already know some of the features and benefits of Office 2010, but, if not, be sure to check out our
http://go.microsoft.com/?linkid=9794964
Discover & Explore Office 2010 page.
If you want to jump in and get started deploying, use this
http://go.microsoft.com/?linkid=9794965
new step-by-step article . Once you're ready to dive into more of the complexities, read further.
First, make sure that you've decided on a
http://go.microsoft.com/?linkid=9794966
deployment method for your organization. Second, make sure you are prepared for
http://go.microsoft.com/?linkid=9794967
volume activation for Office 2010 , which supports the same Key Management Service (KMS) standard as Windows 7. For a typical managed desktop, we recommend that you use
http://www.microsoft.com/downloads/details.aspx?FamilyID=3bd8561f-77ac-4400-a0c1-fe871c461a89
Microsoft Deployment Toolkit (MDT) 2010 , which is a free download, to build your image if you are doing a full desktop refresh, or a task sequence if deploying Office 2010 separately.
Now it is time to customize Office 2010 for your organization. You will need to know your business requirements, such as the
http://go.microsoft.com/?linkid=9794968
languages ,
http://go.microsoft.com/?linkid=9794969
accessibility , and
http://go.microsoft.com/?linkid=9794970
security options you support. Once you know your requirements, you are ready to start configuring the
http://go.microsoft.com/?linkid=9794971
Office Customization Tool (OCT) and the
http://go.microsoft.com/?linkid=9794972
config.xml file , both of which can be easily accessed from MDT once you've loaded your Office 2010 source. Also, don't forget to load
http://go.microsoft.com/?linkid=9794973
Office 2010 Service Pack 1 into the updates folder!
Once you've customized Office 2010 for your business needs and set up activation, it is time to push out the bits. As you see in the
http://go.microsoft.com/?linkid=9794966
deployment method poster , Office 2010 supports many options for deployment. Check out a full list of articles that describe deployment scenarios and installation instructions
http://go.microsoft.com/?linkid=9794974
here , and pick the deployment option that makes sense based on your organization's standard approach.
Again, for the fastest way to get started, use the quick and complete guidance for deploying Office 2010 using MDT that is provided in this
http://go.microsoft.com/?linkid=9794965
new step-by-step article . As always, go to
http://go.microsoft.com/?linkid=9794950
Springboard Series for Office 2010 for additional resources about Office 2010.
We hope these tips help you give the gift of Office 2010 to your organization!
From all of the Office IT Pro & Deployment Team here in Redmond, we wish you Happy Holidays and Happy New Year!
http://go.microsoft.com/?linkid=9794975
Andy O'Donald is a product manager in the Microsoft Office team currently focused on Office deployment and Office 365. Check out his
http://go.microsoft.com/?linkid=9768448
TechNet Radio interview for answers to common IT pro questions on topics such as Office 2010 planning, deployment tools such as the Office Migration Planning Manager, end user resources, and the Office Web Apps.
Microsoft respects your privacy.To learn more please read our online
http://go.microsoft.com/fwlink/?LinkId=81184
Privacy Statement .
If you would prefer to no longer receive this newsletter, please click
http://pages.email.microsoftemail.com/page.aspx?QS=38dfbe491fab00ea380afe73db21804e1836ec2291e123ed&emailid=199655&memberid=10022325&jobid=1383693&listid=887189&listname=Subscription_10022325_106841&subscriberkey=xxxxxxruet@gmail.com&emailaddr=xxxxxxruet@gmail.com&subscriberid=328449823
here .
To set your contact preferences for other Microsoft communications click
http://click.email.microsoftemail.com/m_hcp.aspx?qs=a508ac43a4c30fea332825da1e209da64cfb8de8bf4bc1b75ca469e393f59e864a2a2ab4551e5c43d1ffaed7328f0a8906595fa3409551a329cb359c9aeb32260603052646e0325135f10a3a309465c3ca166b0dd553b4c8e937da588255dbfa
here .
Microsoft Corporation
One Microsoft Way
Redmond, WA 98052 USA
DECEMBER 2011
SPECIAL EDITION
>>
Five Tips From the Deployment Doctor
>>
Windows Deployment "Snacks" from the Swedish Chef
>>
Why You Need a Reference Image, and How to a Create One
>>
Five Things You Might Not Know About MDT 2012
>>
Announcing Internet Explorer 9 Virtual Labs
>>
'Tis the Season for Office 2010 Deployment
>>
http://technet.microsoft.com/windows/aa905066.aspx?ITPID=insider
Application Compatibility
>>
http://technet.microsoft.com/windows/gg276319.aspx?ITPID=insider
Desktop Virtualization
>>
http://technet.microsoft.com/windows/aa905062.aspx?ITPID=insider
Security and Control
>>
http://technet.microsoft.com/windows/aa905087.aspx?ITPID=insider
Networking
>>
http://technet.microsoft.com/windows/aa905090.aspx?ITPID=insider
Performance and Hardware Compatibility
>>
http://technet.microsoft.com/windows/dd197314.aspx?ITPID=insider
Volume Activation
>>
http://windowsteamblog.com/blogs/springboard
Springboard Series
http://windowsteamblog.com/blogs/springboard/rss.aspx
>>
http://windowsteamblog.com/blogs
Windows Team
http://windowsteamblog.com/blogs/MainFeed.aspx
>>
http://blogs.msdn.com/e7/default.aspx
Engineering Windows 7
http://blogs.msdn.com/b/e7/rss.aspx
>>
http://go.microsoft.com/?linkid=9764540
Service Pack 1 (SP1) for Windows Server 2008 R2 and Windows 7
>>
http://technet.microsoft.com/evalcenter/cc442495.aspx?ITPID=insider
Windows 7 90-Day Trial
>>
http://technet.microsoft.com/library/ee956903.aspx?ITPID=insider
Deploying Windows 7 from A to Z
>>
http://technet.microsoft.com/library/dd446674.aspx?ITPID=insider
Windows 7 Upgrade and Migration Guide
>>
http://technet.microsoft.com/library/ee523212.aspx?ITPID=insider
Guidance for Small and Midsize Businesses
>>
http://technet.microsoft.com/windows/dd320282.aspx?ITPID=insider
Windows 7 Videos
>>
http://technet.microsoft.com/windows/bb187457.aspx?ITPID=insider
Support and Troubleshooting
>>
http://technet.microsoft.com/windows/dd262148.aspx?ITPID=insider
Service Pack 2 for Windows Vista and
Windows Server 2008
>>
http://technet.microsoft.com/windows/bb738089.aspx?ITPID=insider
Windows Vista SP1
>>
http://www.microsoft.com/downloads/details.aspx?FamilyID=ab377598-a637-432c-a3c8-1607ab629201&displaylang=en
Performance and Tuning
>>
http://technet.microsoft.com/windows/ee940590.aspx?ITPID=insider
Support and Troubleshooting
>>
http://www.microsoft.com/learning/windows-7/default.mspx#BOOKS
Upcoming Microsoft Press Titles on
Windows 7
>>
http://www.microsoft.com/MSPress/books/12069.aspx
Windows Internals, Fifth Edition
>>
http://www.microsoft.com/mspress/books/11297.aspx
Windows Administration Resource Kit:
Productivity Solutions for IT
Professionals
>>
http://www.microsoft.com/learning/en/us/books/9361.aspx
Windows Vista Inside Out
>>
http://www.microsoft.com/mspress/books/9536.aspx
Windows Vista Resource Kit
>>
http://go.microsoft.com/?linkid=9682964
Register for the TechNet Flash
Newsletter
(c) 2011 Microsoft Corporation
http://microsoft.com/info/cpyright.mspx
Terms of Use |
http://www.microsoft.com/library/toolbar/3.0/trademarks/en-us.mspx
Trademarks |
http://go.microsoft.com/fwlink/?LinkId=81184
Privacy Statement
readmore »»
