The Deployment Bunny

OS Deployment, Virtualization, Microsoft based Infrastructure…

  • Archives

  • Meta

Archive for the ‘Lite Touch’ Category

Deployment Roadshow 2013 in Sweden!

Posted by Mikael Nystrom on March 29, 2013

Inte första gången

och inte heller sista gången som vi gör detta, det är nämligen en av de få sakerna vi gör bara för att det är så grymt kul. Vi kommer att visa massor med olika saker kring OS Deployment och management. Du kan ta med dej kunskaperna hem och I praktiken använde det du har lärt dej direkt!. Mitt förslag är att du snabbt som attan anmäler dig här innan det är fullt. För du vill väl inte missa tillfället att ställa frågor och få svar, eller se praktiska runbooks, VDI demos, ConfigMgr 2012 SP1 prylar, nya snygga saker I AD:t, en portion PowerShell och annat smått och gott!

http://www.deploymentevents.se/

Var? När?
Göteborg 2013-04-22
Malmö 2013-04-23
Stockholm 2013-04-24
Umeå 2013-04-25

 

/mike

Posted in Deployment, Lite Touch, MDT, RoadShow, SCCM, System Center 2012, Windows 7, Windows 8, Windows Server 2012 | Tagged: , , , , , | Leave a Comment »

Modelalias User Exit for Microsoft Deployment Toolkit 2010/2012

Posted by Mikael Nystrom on May 1, 2012

No, I did not create this script, I think this has been around for a long time, somewhere around 2007 and correct me if I’m wrong but I believe it was Ben Hunter that started this back in the days. I have then seen this at the Deployment Guys and various other TechNet sites I did some updates to it since I do a lot of OS deployment in virtual environments, VirtualBox, VMware, Xen and of course Hyper-V. In MDT 2012 they spot most of this with the following information but in some cases you need a bit ore, and you need to be able to modify it to

So Credit goes to Microsoft, Ben Hunter and “The Deployment Guys” (and I’m sure Michael Niehaus has been involved too, so credits for him as well)

Using the Modelalias User Exit script in the Virtual World

In MDT 2012 they have bumped up the information you get from the ZTIGather script, below is the most important information we get from it. But sometimes we need more, but before we get into that, check out the list below. Notice the two last Hyper-V examples, we have the same info returned but that is not the same version of the Hypervisor.

What do you get directly from MDT 2012 s virtualization information?

Here is the result you get during the inventory when running on a VMWare ESXI or VMware Workstation

  • Property IsHypervisorRunning is now = True
  • Property IsVM is now = True
  • Property VMPlatform is now = VMware

Here is the result you get during the inventory when running on a VirtualBox

  • Property IsHypervisorRunning is now = False
  • Property IsVM is now = True
  • Property VMPlatform is now = VirtualBox

Here is the result you get during the inventory when running on a Xen

  • Property IsHypervisorRunning is now = True
  • Property IsVM is now = True
  • Property VMPlatform is now = Xen

Here is the result you get during the inventory when running on Hyper-V (2008 R2)

  • Property IsHypervisorRunning is now = True
  • Property IsVM is now = True
  • Property VMPlatform is now = Hyper-V

Here is the result you get during the inventory when running on Hyper-V (2012 BETA)

  • Property IsHypervisorRunning is now = True
  • Property IsVM is now = True
  • Property VMPlatform is now = Hyper-V

There are more info that we will get in MDT around virtualization, here is the complete information around virtualization for a Hyper-V guest OS

  • Property IsHypervisorRunning is now = True
  • Property SupportsVT is now = False
  • Property SupportsNX is now = True
  • Property Supports64Bit is now = True
  • Property SupportsHyperVRole is now = False
  • Property VMHost is now = IBL04.tslab.net
  • Property VMName is now = TESTHV20
  • Property IsVM is now = True
  • Property VMPlatform is now = Hyper-V

As you can see we also get the hostname and VMname, but only if the IC’s are loaded and they are not loaded by default in WinPE, but a friend of mine banged his head against the keyboard for a while and here is the answer…

Is this ok?

This is mostly ok and fine, but sometimes I really need to know what version of Hyper-V (or other platform) it is and at the same time I would like to support and handle the different naming standards that all vendors has and translate it all to one new property called ModelAlias. Then I can use ModelAlias instead of Model, since I can tweak, twist and bend whatever the OEM’s try to do I can translate it to something that is easy to handle. ModealAlias has been one of the easy ways to deal with Lenovo’s interesting model naming. They use 4+3 digits as model, the first 4 is the real model and the rest is the “unique” build, like unique keyboards and such (things that matters outside the OS deployment world), but for me the same driver is going to be installed even if the keyboard is in Swedish…

If you look at the last example, you will see that we get the same result for Hyper-V in all releases, well that’s “ok”, but the issue is that If I need to install the Integration Components I need to know what version to install to be supported and optimized. So by using the ModelAlias userexit script in MDT (Works in both LiteTouch and in ZeroTouch) the script will examine the bios version (and other information if you need to) and determine the version. So if we take a peek into the script it looks like this for the Hyper-V part.

As you can see BIOS version VRTUAL – 3000919 will give me ModelAlias=Hyperv2008R2 and BIOS version VRTUAL – 9001114 will give me ModelAlias Hyper-V2012BETA

Using the Modelalias User Exit script in the Physical World

Here is another example on how to use this, I was deploying servers not long ago and I was using MDT 2010 LiteTouch. I handle drivers using %make%\%model% in most cases but in this case that was kind of tricky. The reason, well IBM has some fancy characters in the model string (like -[]-), not really easy to use as a path. J

As you can see they have —[HS22]— as model name and after using the userexit script it will be converted into IBMHS22 and that is a bit easier to handle as part of a file path.

Here is one other example for a HP Compaq 8240. HP has a bunch of “different” 8240′s, but from my perspective it is just the same when it comes to drivers and apps, so we convert them into something more useful, like this

Here you can see the real model name being “HP Compaq nw8240 (PY442EA#AK8)” and after a translation it will be just “HP Compaq nw8240″ instead, easier to handle, easier to have as a path in MDT

How do you use the UserExit script?

This is the easy part, just download it, unpack it and save it in the scripts folder in MDT. Then you modify the customsettings.ini to use the script like this:

[Settings]
Priority=SetModelAlias, ModelAlias, Default
Properties= ModelAlias

[SetModelAlias]
UserExit=ModelAliasExit.vbs
ModelAlias=#SetModelAlias()#

[Hyper-V2008R2]
MandatoryApplications001=<GUIDNumberOFApplicationInLTI>

[Hyper-V2012BETA]
MandatoryApplications001=<GUIDNumberOFApplicationInLTI>

(If you are using SCCM you will the use Packages or Application name, but it works the same)

When you run ZTIGather.wsf you can see the result like this on a Windows Server 2012 BETA

You can download the ModelAlias.vbs script here

Here is some links to older versions of the script:

The Deployment Guys

Ben Hunters Blog

/mike

Posted in Deployment, Hyper-V, Lite Touch, MDT, SCCM | Tagged: , , | Leave a Comment »

OS Deployment PreCon(s)–Spring and Summer 2012

Posted by Mikael Nystrom on March 3, 2012

This spring I will deliver 3 PreCons on the topic of OSD or Operating System Deployment. All these three will bi similar, we will cover both the basics and the really advanced topics. The focus will be on Windows 7 deployment, but we will also cover Windows 8 and Server Deployment. The tools that we will cover are MAP/ACT, WAIK/ADK, WDS, MDT and SCCM (and then some). The hardware vendors that we will cover are HP, Dell and Lenovo. We had some questions regarding the level of these sessions, so I did an interview with Michael Niehaus

Microsoft TechDays 2012

  • Date: 24th of April 2012
  • Speakers: Mikael Nystrom and Johan Arwidmark
  • Language: Swedish
  • Location: Örebro, Sweden

Microsoft TechEd North America 2012

  • Date: 10th of June 2012
  • Speakers: Mikael Nystrom, Michael Niehaus and Ben Hunter
  • Language: English
  • Location: Orlando, US

Microsoft TechEd Europe 2012

  • Date: 25th of June 2012
  • Speakers: Mikael Nystrom, Michael Niehaus and Ben Hunter
  • Language: English
  • Location: Amsterdam, NL

Posted in ACT, Deployment, Drivers, Lite Touch, MAP, MDT, SCCM, SCVMM, TechEd, Windows 7, Windows 8, WinPE | Tagged: | 3 Comments »

Nice to know: A simple branding kit for your Windows 7 deployment

Posted by Mikael Nystrom on January 24, 2012

Even if this is anything else but important, branding your OS could sometimes be needed for fun or for profit. The basic concept is to replace some of the images in Windows with your own corporate ones. This simple kit will change the logon UI, the background picture and it will add the OEM logo for the famous company ViaMonstra (The company that Johan Arwidmark and I use as a sample company when we write our books). Since everyone on this planet are using MDT to create your reference image you just import this as an application, modify the pictures and then add the application to the task sequence and create the reference image. Done!

The reason that I never posted this is that all the pictures are my customers, not mine. But then Johan Arwidmark started writing “Deployment Fundamentals Vol III”. That is about Deploying Windows 7 using SCCM (extended with MDT) we thought that branding would be fun to have in the book, and suddenly I was in the position to create graphics that we can use in the book. So now I have something to share, and here it is. The ViaMonstra Branding Kit!

This “Application” has three folders (and one VBScript) , LogonUI, OEMLogo and Wallpaper. In each of these folder you then have the pictures.

In the LogonUI folder you will find “BackgroundDefault.jpg” with a size of 800 x 600 pixels.

image

In the OEMLogo folder you will find “OEMLOGO.bmp” with a size of 305 x 301 pixels.

image

In the Wallpaper folder you will find “CorporateWallpaper.JPG” with a size of 960 x 720 pixels.

image

You will also see a vbscript that will put all the files in the correct location and also update the registry correctly

image

The VBScript is kind of simple,

image

it will create folders on the local machine, copy all the files to the correct location and update the registry for the local admin account. So if it updates the local admin account, how will that apply to all the users that logs on to the machine then?. Easy, we use the “CopyProfile” in the unattend.xml file when we deploy the image. Note, we do not use copyprofile while creating the image, only when we deploy the image.

image

You can download the kit from

http://deploymentresearch.com/mnfiles/Install%20-%20ViaMonstra%20Branding%20Pack%20for%20Windows%207.zip

/mike

Posted in Deployment, Lite Touch, MDT, SCCM, Windows 7 | Tagged: | 7 Comments »

Deployment Geek Week in Redmond – December 12-16, 2011

Posted by Mikael Nystrom on November 22, 2011

It’s time for Johan Arwidmark and me to deliver the “Geek Week”, this is by far the most exiting training I have ever done, it is fun, it is very technical and I have never ever had so many “-Aha, I did not know you could do that?”

The reason why it is so fun for us and in many cases “exiting” for our attendees is that it is “complete”, that means that we cover everything more or less, we start out with general Windows 7 Deployment, ref images, Windows Deployment Services, Microsoft Deployment Toolkit, Lite Touch, Zero touch, Applications, MAP and ACT and that is only the first 2 days and you build most of this. So what will happen next then? Since the world is not perfect and deployment people normally know less of the “Dark Side” (That is Server Side) we start putting up different solutions for app-compat issues, so we will setup System Center Virtual Machine manager, learn Hyper-V, Scripting Hyper-V, Deploy Terminal Servers, Learn GPP/GPO, learn things around File, Print, Cluster, Active Directory and everything that you really need know about. Not only will you learn, you will learn by doing, since you are building the entire infrastructure around this. We also spend time on troubleshooting of course

We normally stay at the same hotel, that means all of us, so is just happens to be a bar there. So after class there will be a bunch of doing down in the hotel to continue the “class” over a drink.

It is hard to describe this event, but at least I tried. We don’t run those events very often so you might want to join in, I’ll guess we will run the next event in the summer of 2012 or even later than that.

Anyway, you can read what other are saying about this here Microsoft Pinpoint

and you can read more and sign up here – http://www.truesec.com/infrastructure/labs/deployment/migration/deployment_geek_week

Really hope to see you there.

/mike

Posted in Deployment, Geek Week, Hyper-V, iSCSI, Lite Touch, MDT, SCCM, SCVMM, Windows 7, Windows Server 2008 R2 | Tagged: , , , , , , | Leave a Comment »

How to split a Media based OS Deployment into multiple DVD’s?

Posted by Mikael Nystrom on September 4, 2011

The Deployment Guys has done it again, that is, they wrote a very nice blog post about the fact that if you do need to use media based deployment and you have to much data to store on the media, well suddenly life is no fun any more. It can be solved in a couple of different ways, one is to switch over to USB keys, but maybe that solution is not for you and in that case they have a nice solution to it. The solution contains of scripts and a HTA.

Read their solution for “Getting more into DVD Media Based Deployment”

(direct download to the ZIP)

Here is how it looks when running it:

DVDExchange1

Posted in Deployment, Lite Touch, MDT | Tagged: , , | Leave a Comment »

 
Follow

Get every new post delivered to your Inbox.

Join 2,346 other followers