Use WIM to store your classes.

As I continue in this line of work, I’m constantly faced with the same issue. How do I preserve all the data that I have accumulated? I’m beginning to think that I have the MCT download site sitting in these little USB powered boxes in front of me. I like to add a little value to the classes that I teach. Don’t get me wrong. The people at Microsoft do good work in developing these classes. As the instructor on the front lines though, I know that my students expect more. As a result I have extra labs, handouts, downloads and then some. Well how do you keep all this organized? Imaging.

I know, what are you talking about? Am I supposed to image my computer for each class? Of course not. You can image your files and restore them later. Let me just tell you a big advantage. My 5115A class with all the VMs, books, and my notes comes in at over 8 gigs. After I ran the imagex command with the /compress maximum switch the total file size is 1.8 GB. At that size, I was able to easily fit 5115 and 5116 on a single DVD as a backup. Sealing them up takes time, but deploying them is a breeze.

Rapid deployment can be a life saver when you show up on site and nobody has deployed the VMs for the class. It has happened to me before. I brought several DVDs and passed around my USB hard drive to the students while I started class. It was still 2 hours before everyone had the VMs running. Utilizing the new WIM image format, you can significantly reduce your rollout time in these situations by utilizing the WIM format.

You do not need to zap any hard drives for this. You are merely adding files to the hard drive. Why not zip them? Well, the WIM format takes advantage of single-instance storage. That means if the same file appears 8 times in what you are imaging, it will only be stored once. That saves significant storage space and increases deployment speed. Give it a try.

Comments

Sticky Key problem between Windows Server 2012 and LogMeIn

This week I instructed my first class using Windows Server 2012 accessed via LogMeIn and discovered a Sticky Key problem every time you press the Shift key. Here is my solution to resolve this. First off, in the Preferences of LogMeIn for the connection to the Windows Server, click General . Change the Keyboard and mouse priority to Host side user and click Apply at the bottom. On the Windows 2012 server, open the Control Panel – Ease of Access – Change how your keyboard works . Uncheck Turn on Sticky Keys . Click Set up Sticky Keys . Uncheck Turn on Sticky Keys when SHIFT is pressed five times . Click OK twice. If you are using Windows Server 2012 as a Hyper-V host, you will need to redo the Easy of Use settings on each guest operating system in order to avoid the Sticky Key Problem. Updated Information: March 20, 2013 If you continue to have problems, Uncheck Turn on Filter Keys .

With the AD Recycle Bin Turned on, What Happens when you Create a User Account with a Password that does not meet the Password Policy?

This was an interesting observation from one of my Windows Server 2012 classes. While working with the AD Recycle bin in a lab, one of my students discovered some interesting accounts that were created. When he created user accounts that did not meet password complexity requirements, an account is temporarily made and then deleted. When a new password is provided that meets the password requirements, then a new account is made. We discovered this in two places. First off in the Active Directory Administrative Center. This is what caused the initial confusion. Take a look. This is in the Deleted Objects OU. You can see multiple deleted accounts for Test2 and one for Test3. Test3 is a valid, functioning user account. Using the PowerShell command Get-ADObject –IncludeDeletedObjects –Filter * –Properties ObjectSID we can see that indeed, two accounts were created, with one of them deleted. Notice the RID portion of the SID is different. ...

Where did a User’s Account Get Locked Out?

Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction. The code below is correct. My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...

Jason Yoder, MCT

Search This Blog