Paul,
I just wanted to chime in and verify this for you. My two go to commands are this:
Reboot immediately:
shutdown /f /r /t 0
Shutdown immediately:
shutdown /f /s /t 0
In both instances I use a "0" timer and the /f modifier works as expected. You can test it out pretty easily by opening a notepad window and typing something. Then, issue one of the above commands without saving the notepad document. You will see the server force close notepad and then shutdown or reboot.
Hope that helps,
Don Pezet
Host, ITProTV

SSDs are actually becoming very common in datacenters. If you shop around for hosted VPS solutions you will find a lot of them offering SSD storage as a premium option. However, that wasn't always the case. When SSDs were becoming popular they had two major flaws:

They could only be written to a certain number of times before failing and, while it varied from drive to drive, the number was fairly low. The drives put out a lot of heat which made them problematic in large arrays.
Those two things kept them out of the server room for a long time. In the last few years we have seen the temperature of the drives come down significantly and the amount of writes before failure increase. That allowed them to creep in to high-end datacenters. They were really popular for OLAP database scenarios which are almost entirely read operations and benefited greatly for the decreased seek time of an SSD. Now, we see them used for everything including general OS drives. All that being said, though, any admin worth their salt builds it in to their budget to replace the SSDs every two years. The increased cost of replacing the drives is more than compensated by the improved performance.
As for the overhead created by storage pools it is actually very small. Every read/write operation passes through the Windows Hardware Abstraction Layer (HAL) on its way from the OS to the physical disk. The redirection occurs within the HAL so it gets great performance with minimal impact. I wouldn't use it on a heavy OLTP database server, but on a home media server you won't even notice it.
Hope that helps,
Don Pezet
Host, ITProTV

The import/export process is documented in this TechNet posting:
http://blogs.technet.com/b/teamdhcp/archive/2012/09/11/migrating-existing-dhcp-server-deployment-to-windows-server-2012-dhcp-failover.aspx
That article covers moving DHCP from Windows Server 2008 to Windows Server 2012. I have not done a migration from Windows Server 2003 straight to 2012, but I would be surprised if it did not work. Even without the power shell commands you will likely be able to move the DHCP database files over as they have barely changed since Windows Server 2003.
Hope that helps,
Don Pezet
Host, ITProTV

Christopher,
You must do both to object auditing.
If you turn on auditing on the folder but do not enable auditing in the GPO, auditing will not take place. You must enable it on the server via group policy--domain or local. You must then configure auditing on the resource's SACL.
Cordially,
Ronnie Wong,
Host, ITProTV

A new copy of that episode is up. Enjoy!
nate

Christopher,
We're checking right now, Episode 16 is not there, but not there on purpose. We used that number for a temporarary episode in marketing. If you continue onto Episode 17, the material was included in there.
Cordially,
Ronnie Wong
Host, ITProTV

Links to FAQ PDF:
http://download.microsoft.com/download/4/D/B/4DB352D1-C610-466A-9AAF-EEF4F4CFFF27/WS2012_Licensing-Pricing_FAQ.pdf

Christopher,
You've got it right! remember, two basic purposes of NIC teaming--bandwidth aggregation and failover.
Cordially,
Ronnie Wong
Host, ITProTV
"You'll learn without knowing I.T."

I just noticed the new site layout messed up my code entries again. I'll have to fix it.

I spoke with Ronnie this morning and he attached his notes to the episode also. He listed the exact steps he followed during the show. Let us know if you have any issues with it.
Thanks,
Don Pezet
Host, ITProTV

Chris,
This may depend the way you install the application. If you do it per computer and for all users the computer or just for this user. If using roaming profiles on all the computers the user may use you should install the client per computer and not per user. If installed this way, the mail settings should roam without the user needing to set up per system when that user logs in...I should say that it should be automatically set up for the when they log in an open the email client the first time.
Cordially,
Ronnie Wong
Host, ITPro.TV
p.s. click the up arrow if this was helpful. I'm trying to catch up to Don! :)

James,
Thanks for posting this. We have used a few different products like this over the years (EAZ-Fix, Baseline Shield, Deep Freeze, etc), but this is the first one I have seen that supports Windows 8.
Thanks again,
Don

Robert,
We don't have a specific episode for it, but I can give you the details here. James' post above pretty much covers it. The only thing I would add is a little bit of history as to how it got started because that will show you how closely the technologies are related. In the mid-90's Microsoft and Citrix worked together to create a product called Winframe. It was Windows NT 3.51 with mainframe-like terminal support, only using a GUI instead of a text based interface. It was a revolutionary product at the time but the relationship between the two companies didn't stick. In the next version of Windows, Microsoft dropped the Winframe product and integrated the technologies that they held the license for in a new product called Windows NT 4.0 Terminal Services Edition. At the same time, Citrix release Citrix Metaframe which could be installed on top of Windows NT 4.0 and added back in all the technologies that Citrix held the license for. From that point on, Microsoft and Citrix moved along two different development paths. Microsoft continued to develop Remote Desktop Protocol (RDP) and Citrix developed Independent Computing Architecture (ICA). The two protocols do basically the same thing, allow multiple users to view a desktop rendered by a remote server. However, each has its own bells and whistles.
Both products have evolved a lot since then. Microsoft's Terminal Server changed names and became Remote Desktop Services or RDS. Citrix Metaframe changed names and became Citrix Metaframe XP, then Citrix Presentation Server and finally Citrix XenApp which is the name it holds today. It is all the same product, just a different name. If it sounds confusing, that's because it is. I can only keep it straight because I have worked with Citrix across all the versions. If you are new to it, it is a naming mess.
Combine that with James' answer above and you should have a pretty exhaustive answer to your question. Let me know if there is anything else I can help with.
Don Pezet
Host, ITProTV

Yes and no. It has definitely gotten a lot better. For the most part, the Retail, TechNet and MSDN copies are now all the same media. However, the VLE copies are still a different media. I'm not sure why Microsoft chose to do that, but it has been an annoyance for a long time.
Thanks for posting,
Don

If you are enrolled into college and have a .edu email you can get entered into the dreamspark program https://www.dreamspark.com/ and they give you licence keys for most of those operating systems listed in the current reply.
Best Regards
Chris