You are browsing the archive for 2011 June.

Configuration Manager P2V Migration Toolkit – Part 2

1:16 pm in Uncategorized by nsienaert

Hi There!

In my last blog post I have started exploring the P2V Migration Toolkit for Configuration Manager. I talked you through the wizard and explained the context and the purpose of the tool.

In this post we complete the P2V migration process by booting up the ISO that we have created in Part 1.

Before we do that, let’s first check high-level the most important steps of the Task Sequence that has been auto-created for us. The engine behind the Task Sequence is the Virtualization package that we have created before.

  1. When booting the media a Rehost Wizard will start to declare our variables that will be used later in the Task Seuquence.
  2. The specified disk will be captured into a VHD which we will save to a network path.
  3. Install Windows 2008 R2 and enable the Hyper-V role
  4. Domain Join, Install Updates,…
  5. Create the virtual machine into Hyper-V (VMCreator Tool)
  6. Install additional applications

Some screenshots (taken with my WP7 Glimlach)

Boot the DVD and start the Task Sequence

clip_image001

The UDI Wizard will start

clip_image002

Prerequisites checking

clip_image003

Specify Domain info.

clip_image004

Local Admin PW and Local Administrators

clip_image005

Pretty Straight forward…

clip_image006

Pretty Straight forward…

clip_image007

Location to Save the VHD. (I know, challenging PC name Knipogende emoticon)

clip_image008

Specify some Hyper-v Settings

clip_image009

Summary

clip_image010

The process will start now…

The total elapsed time is of course depending on the size of the disk, disk I/O and network connectivity but to give you an idea it took 3 hours to virtualize 50GB of data on a local Gigabit LAN and on laptop hardware with 2.0Ghz CPU and disks of 7200 RPM.

Once the process is done I can login on my machine and see that indeed Server 2008 R2 is installed with the Hyper-v role enabled and my Primary server is added.

clip_image011

Everything looks fine in the console.

clip_image012

The MP is up and running so the clients can talk to the server and on my central server despool.log, replmgr.log and sender.log look normal so also the site-to-site connection is up and running again.

clip_image013

So good stuff if you ask me!

Now it’s time to do a side-by-side migration to SCCM 2012 (you would forget that this was to original goal Knipogende emoticon) which I will discuss in one of the next blogs.

Stay tuned!

Nico Sienaert

clip_image014

Configuration Manager P2V Migration Toolkit – Part 1

8:04 pm in Uncategorized by nsienaert

Hi There!

The ConfigMgr Product Team is developing a tool to migrate your ConfigMgr07 Site server on remote sites with limited on-site support. The P2V Migration Toolkit is currently in CTP release since the end of March.

As ConfigMgr07 only can migrated side-by-side to ConfigMgr12 a second server needs to be available or a virtualization solution can help you out. And that ‘s what this toolkit is all about.
Virtualizing the ConfigMgr07 Site Server so you can install the new ConfigMgr12 Site Server on that same server next to the virtualized ConfigMgr07 Site.

Sounds maybe complicated, but in fact it isn’t, so lets have a look.

Install the Toolkit on your Central Server. You probably haven’t installed the Desktop Experience feature on your machine. If not, the Toolkit will ask you to do so.

clip_image001

Once you have installed this feature, a reboot (!) is required.

Install the Toolkit…

Once installed, open the application with “Run as Administrator”.

clip_image002

On the left you will notice that you can select 3 wizards.

– Create a task sequence: This will create the VHD, copy the VHD to a network drive,     Reinstall the machine, enable the Hyper-v Role and mount the VHD. –> Make sure that the hardware is x64 compatible!

– Create Standalone Task Sequence media: This will create the media that will install the task sequence

– Create a Windows PE boot Image

On the right you can see the 4 necessary steps you have to accomplish with the help files attached.

– Create the Task Sequence

– Create Standalone media

– Boot off the Standalone media

– Run the Task Sequence (an LTI wizard will kick off the process. Fill in the domain, path to save the VHD, specifiy computername,… will be required steps)

If you select one of the wizards the toolkit will connect to the Site Server.

clip_image003

When creating the task sequence a simple wizard needs to be executed. Specify the ConfigMgr Client Package, specify the Image Package (Server 2008 R2 capture WIM file), a virtualization package (the wizard will create this for you) and you can also specify additional packages\applications that you like to have installed during the Task Sequence process. 

clip_image004

Once the wizard is finished, the task sequence gets created together with the Virtualization package. The content of this package are all the necessary files to cover the virtualizaton part.

Note that no program is created for this virtualizaton package. Make sure you distribute this new package to the appropriate DP.

clip_image005

If we open the Task Sequence we see a bunch of steps that are added automatically. Also a lot of variables are used which we will declare during the wizard when starting the Task Sequence. So actually, despite of maybe so minimal customizations this is ready to use!

clip_image006

Now it’s time to create the bootable media (CD, DVD or USB Flash Drive) that we will send to the remote branch.

Again a simple wizard needs to be accomplished. Select the x64 boot image with the correct NIC and storage drivers included and select the new Task Sequence.

For the sake of demo I have created an ISO that I will burn on a DVD. I’ll send it now with a courrier to the other side of my lab… Knipogende emoticon

clip_image007

In the next part we will boot from the media and see how this ConfigMgr07 server gets virtualized.

Till next time!

Nico Sienaert (twitter: nsienaert)

MDT 2012 Beta1: Sneak Peak

2:47 pm in Uncategorized by nsienaert

 

Hi there!

At MMS we could hear that the MDT team will try to release MDT 2012 RTM 30 days after the RTM release of SCCM 2012.

Last week the Beta1 was released. Let’s have a sneak peak.

With this version there is support of:

  • The SCCM App Model & UDA
  • Integration with the SCCM 2012 Console
  • New UDI components (new wizard & Designer) and more customization will be possible
  • Support UEFI
  • Support of new OSes: Windows POSReady7 & Windows ThinPC
  • Cross-platfrom deployment (Install x64 OS from x86 windows PE) The other combination, booting from an x64 boot image and deploying an x86 OS, isn’t supported by Windows Setup.
  • Deploy to VHD – creating a VHD file during the task sequence that can then be used for booting the OS (“boot from VHD”).

Maybe you are wondering if there are changes on USMT, Windows PE and WAIK. Well no, only bug fixes. WAIK (USMT is part of WAIK) is depending on Windows releases not MDT releases, that’s why.

The MDT Team wants to remove support of Windows XP & Server 2003 but SCCM 2012 does still support XP SP3, so probably MDT will 2012 still support XP SP3 as Source OS, not as Target OS.

Features that will be added in next releases:

  • Integration of Windows RE (Set Recovery partition during OS Process)
  • Integration with MDOP tools like App-V and DaRT
  • Powershell support in Task Sequence
  • LTI Facelift

At first glance, visually not much has been changed in the SCCM console. One button has been added to the Tab Bar to start the MDT Task Sequence wizard.

clip_image001

Once we have created an MDT Task Sequence via the wizard, we don’t notice much changes in the Task Sequence.

Probably the 2 most biggest changes are:

  1. USMT has more GUI options

clip_image002

    2.   The New App Model

clip_image003

Note that the MDT Team added an extra script before the Install Application step to “workaround” something. Application variables end up with 2 digit suffixes (ex. Applications01), MDT expects 3 digit suffixes (ex. Packages001). The script is making a 3 digit list and convert it to a 2 digit list so SCCM can install the applications.

Also in the MDT LTI Workbench no much changes can be observed.

  1. Integration of the new App Model (note: also ConfigMgr Packages can still be used)

clip_image004

     2.   The Deploy to VHD Templates. (only supported in LTI scenarios)

clip_image005

So, now we have looked into the changes, let’s deploy a Bare Metal image via the MDT Wizard in the SCCM Console.

Once I finished the MDT wizard, it failed immediately with following error:

Started processing.

Creating boot image.

Generating boot image.

Error while importing Microsoft Deployment Toolkit Task Sequence.

System.Exception: Unable to mount image C:\Users\ADM-NS~1\AppData\Local\Temp\2\winpe.wim to C:\Users\ADM-NS~1\AppData\Local\Temp\2\PE20_mount.x86 —> System.ComponentModel.Win32Exception: A required privilege is not held by the client

— End of inner exception stack trace —

at Microsoft.BDD.ConfigManager.PEManager.Generate()

at Microsoft.BDD.Wizards.SCCM_ImportTaskSequenceTask.DoWork(SmsPageData smspageData, Dictionary`2 data)

From my experience I remember that the deployment tools of WAIK like to be executed with “Run as Administrator”.

So I have restarted my SCCM Console with “Run as Administrator”, as from now the image could be mounted correctly and the wizard finished successfully.

Stay tuned for more blogs that go deeper into the MDT Topic.

Till next time!

Nico Sienaert (twitter: nsienaert)