Collect your drivers and export them to a share

Last week I saw a really interesting Tweet from Adam Eaddy mentioning his blog where he had published a automated way to build Configuration Manager Driver Packages automatically by collecting drivers from a remote PC. The script worked great, but I missed the nice folder structure to keep the drivers nice and ordered. I tweaked his script a bit, so it would fit my needs.

This PowerShell script collects the drivers (in a nice manufacturer\model\version\arch structure) and copies them to a network share. This makes it possible to use your own Configuration Manager driver import script (or import them manually) or even use them in your MDT configuration.

image

Note : you have to run the script as an Administrator.

Please let me know what you think!

Upgrading SCCM 2012 R2 to ConfigMgr 1602

image

A customer wanted to upgrade his current Windows 7 Enterprise devices to Windows 10. Right now he was running SCCM 2012 R2, so before I can start creating a Windows 10 task sequence first there some ConfigMgr upgrading has to be done. I started by downloading the SCCM 1511 bits, Windows ADK 10.0 (not the 1511 version!) and the HP WinPE 10.0 driver pack (since the customer is running HP devices only).

When all the bits were downloaded, the upgrade process can start!

Continue reading “Upgrading SCCM 2012 R2 to ConfigMgr 1602” »

Microsoft Deployment Toolkit 2013 Update 1 Has Arrived!

 

We had to wait a couple of week (since the launch of Windows 10), but it’s finally there : MDT 2013 Update 1!

At the moment (August 19th) it’s not yet available at http://microsoft.com/deployment

image

 

……… but Aaron has put a nice blogpost together over at the /MSDeployment Blog.

 

“The Microsoft Deployment Toolkit (MDT) 2013 Update 1 is now available on the Microsoft Download Center. This update requires the Windows Assessment and Deployment Kit (ADK) for Windows 10, available on the Microsoft Hardware Dev Center. (Scroll to the bottom of the page to the section, “Customize, assess, and deploy Windows on your hardware.” The page also includes other Windows kits; remember for deployment you only need the Windows ADK for Windows 10.)

Significant changes in MDT 2013 Update 1:

  • Support for the Windows Assessment and Deployment Kit (ADK) for Windows 10
  • Support for deployment and upgrade of Windows 10
  • Support for integration with System Center 2012 R2 Configuration Manager SP1 with the Windows 10 ADK (see this post on the Configuration Manager Team blog for more information on using the Windows 10 ADK with Configuration Manager)

Here is a more detailed list of some specific changes in this release:

  • Support for new Enterprise LTSB and Education editions of Windows 10
  • Support for modern app (.appx) dependencies and bundles
  • Improved support for split image files (.swm)
  • Switched to using DISM for imaging processes (instead of deprecated ImageX)
  • Deployment Workbench revisions for deprecated content
  • Enhanced accessibility within the Deployment Workbench
  • Revised lists of time zones, regions and languages in the Deployment Wizard
  • Removed Start menu shortcut for “Remove PXE Filter”
  • Several MVP recommended fixes for Windows Updates, password handling, and PowerShell cmdlets
  • Added missing OOBE settings to Unattend.xml
  • Unattend.xml default screen resolution changed to allow for automatic scaling
  • Updated task sequence binaries from System Center 2012 R2 Configuration Manager SP1
  • New GetMajorMinorVersion function for integer comparison of Windows version numbers

We are still working to update the MDT documentation on TechNet, so in the short-term will use this blog to share any additional necessary information regarding this release.”

 

 

 

https://www.microsoft.com/en-us/download/details.aspx?id=48595

Download System Center 2012 R2 Evaluation VHDs

Microsoft has released a set of pre-configured VHD’s for all of the System Center 2012 R2 components. The download consists of files that you extract into a single pre-configured VHD file for every System Center component. The VHD enables you to create a virtual machine to evaluate the different System Center components.

Click one of the links below to visit the download page of the System Center 2012 R2 Evaluation VHD:

Just click the Download button on the site and select all the files to download the VHD and the installation document.

Upgrading SCCM 2012 R2 Preview to SCCM 2012 R2 RTM

I’ve been running System Center 2012 R2 Configuration Manager for some time now, but since SCCM 2012 R2 was released today I really wanted to upgrade my server to the RTM bits! For now I’m upgrading my machine, since it is still running Windows Server 2012 I will probably do a clean install (on top of Windows Server 2012 R2) somewhere in the near future.

Prepare for the upgrade

Before you can start the upgrade, there ar e some things you should know:

Continue reading “Upgrading SCCM 2012 R2 Preview to SCCM 2012 R2 RTM” »

Upgrade your SCCM 2012 SP1 to R2 Preview

Interesting read: Upgrade SCCM 2012 R2 Preview to SCCM 2012 R2 RTM

At TechEd Europe the availability of System Center R2 Configuration Manager Preview was announced. Since I’m running SCCM 2012 SP1 in my home lab, I found some free time (during TechEd) to upgrade my lab to the Preview release of SCCM 2012 R2.

Prepare for the upgrade
Before you can start the upgrade, there are some things you should know :

  • Since this is a Preview release, you should not run it on your production machines
  • Remove the current Windows ADK 8.0
  • Download and install the new Windows ADK (preview) 8.1
  • In the example below I’m only using one Site Server.

Continue reading “Upgrade your SCCM 2012 SP1 to R2 Preview” »

Deploying Windows Server 2008 R2 (non-VL) with MDT 2012 & Windows ADK

Just a few weeks ago Microsoft has released MDT 2012 Update 1, with full support for Windows Server 2012 and Windows 8. Microsoft did also release the Windows Assessment and Deployment Kit (ADK) for Windows 8, the replacement for the good old WAIK. With the RTM of Window Server 2012 I decided to upgrade my Deployment environment to the latest version. When I did some initial deployments of Windows 8 and Windows Server 2012 everything worked just fine, but when I tried to deploy Windows Server 2008 R2 (non-VL version) or Windows 7, I ran into a small problem.

The Issue
Just after the deployment I had to enter the Product Key.

image

At first I thought I made a mistake during the built proces, but after I asked a question at the Microsoft Deployment Toolkit Forum. Because the first responses suggested that there was something wrong with my Deployment Share. After some suggestions and a start from scratch (the first time I imported and upgraded the ‘old’ deployment shares), also not importing the ‘old’ deployment shares, the answer came from Michael Niehaus:

“MDT 2012 Update 1 switched from using SETUP.EXE to instead use ImageX to apply the image.  As a result, if you use retail or OEM media, you’ll get a prompt because the product.ini file isn’t being read any more (SETUP.EXE did that, ImageX doesn’t).

Fortunately the fix is pretty simple:  Look up the correct setup (generic) key in the product.ini file on your media and specify it in the unattend.xml (second location).  After you do that, it won’t prompt any more.

This won’t happen with volume license media.”

So that’s probably why the people who responded earlier didn’t have the same issue, they were (probably) using volume license media!

 

The Solution
So, to fix the issue had to specify the (generic) product key (from the product.ini in the Sources folder)

image

image

Open the unattend.xml (in the correct Control  Task Sequence folder) and enter the product key at the second   start-tag.

image

Now you can just restart the Task Sequence and you won’t be asked for a product key during the deployment!

Just a few weeks ago Microsoft has released MDT 2012 Update 1, with full support for Windows Server 2012 and Windows 8. Microsoft did also release the Windows Assessment and Deployment Kit (ADK) for Windows 8, the replacement for the good old WAIK. With the RTM of Window Server 2012 I decided to upgrade my Deployment environment to the latest version. When I did some initial deployments of Windows 8 and Windows Server 2012 everything worked just fine, but when I tried to deploy Windows Server 2008 R2 (non-VL version) or Windows 7, I ran into a small problem.

The Issue
Just after the deployment I had to enter the Product Key.

image

At first I thought I made a mistake during the built proces, but after I asked a question at the Microsoft Deployment Toolkit Forum. Because the first responses suggested that there was something wrong with my Deployment Share. After some suggestions and a start from scratch (the first time I imported and upgraded the ‘old’ deployment shares), also not importing the ‘old’ deployment shares, the answer came from Michael Niehaus:

“MDT 2012 Update 1 switched from using SETUP.EXE to instead use ImageX to apply the image.  As a result, if you use retail or OEM media, you’ll get a prompt because the product.ini file isn’t being read any more (SETUP.EXE did that, ImageX doesn’t).

Fortunately the fix is pretty simple:  Look up the correct setup (generic) key in the product.ini file on your media and specify it in the unattend.xml (second location).  After you do that, it won’t prompt any more.

This won’t happen with volume license media.”

So that’s probably also the people who responded earlier didn’t have the same issue, they were using volume license media!

 

The Solution
So, to fix the issue had to specify the (generic) product key (from the product.ini in the Sources folder)

image

image

Open the unattend.xml (in the correct Control  Task Sequence folder) and enter the product key at the second   start-tag.

image

Now you can just restart the Task Sequence and you won’t be asked for a product key during the deployment!

Deploying Windows 8 Release Preview with MDT 2012 Update 1 (Beta)

Today Microsoft has released the beta version of MDT 2012 Update 1. You can upgrade the following versions of MDT with the MDT 2012 Update 1 Beta :

  • MDT 2008 Update 1
  • MDT 2010
  • MDT 2010 Update 1
  • MDT 2012

After you installed MDT 2012 Update 1, you should upgrade your deployment share. You should also read the Release Notes where you can find some more tips about this new version.

Some of the new features :

  • Support for using the DaRT 8 Beta with the Windows 8 Release Preview version of the Assessment and Deployment Kit (ADK).
  • New “Build Your Own Pages” support for User-Driven Installation (UDI), enabling IT pros to create new wizard panes using simple drag-and-drop operations – no coding required.
  • Integration with System Center Orchestrator, enabling task sequences to invoke Orchestrator runbooks at any point in the deployment process.
  • Completely reworked “Roles and Features” logic, supporting both installation and removal, as well as providing a new Lite Touch wizard pane for selecting roles and features to install at deploy time.
  • Support for PowerShell 3.0 to make it easier to run PowerShell scripts inside task sequences on Windows 8, Windows Server 2012, and Windows PE 4.0.
  • Simple monitoring functionality for Configuration Manager task sequences, leveraging the monitoring capabilities provided initially in MDT 2012 for Lite Touch deployments.
  • Improved “boot from VHD” deployment capabilities, supporting both bare metal and refresh deployment

Instead of the Windows AIK (for Windows 7), you can now use the Windows ADK to deploy Windows 8 Release Preview and Windows 7. When installing Windows 7 using Setup.exe with Windows PE 4.0 from the Windows ADK, two error dialog boxes are displayed while still in Windows PE. The dialog boxes do not affect the deployment, but you must click OK in each of them before the deployment process will continue.

I created a small (7 minute) video of a default Windows 8 Release Preview deployment with the new version of MDT. Please leave a comment if you like it.
http://youtu.be/kMAuXzuztY0

Upgrade Microsoft Deployment Toolkit 2012 RC to MDT 2012 RTM

image

It’s quite simple to upgrade your Release Candidate version of MDT 2012 to the RTM version…. just follow the following steps.

  1. Shutdown the (current version of the) Deployment Workbench
  2. Start MicrosoftDeploymentToolkit2012_x64.msi (or the x86 version)
  3. Click Next
  4. Accept the License Agreement and click Next
  5. Keep the default installation path and click Next
  6. Click Install
  7. Wait for the installation to finish succesfully and click Finish.
  8. Open the Deployment Workbench
  9. Right click your Deployment share and select Upgrade Deployment Share
    image
  10. Click Next
  11. MDT will now update the Deployment Share
    image
  12. Click Finish to complete the upgrade!

That’s all…have fun deploying!

P2V Windows XP and Deploy Windows 7

In my previous post I showed how you can configure the P2V Migration Add-on. In this post I would like to show you how the created task sequence can be started to P2V the Windows XP installation, followed by the installation of Windows 7. When that is finished the Windows XP VHD is configured to run as a virtual machine inside the just installed Windows 7 client.

08

Continue reading “P2V Windows XP and Deploy Windows 7” »