Timothy,
We described the process at the beginning of the show and showed the DHCP Enforcement because we wanted demonstrate what we could do within a limited environment for the DHCP enforcement. If you wanted to put DHCP server on a different server than the NAP. You would configure your DHCP server by going to your scope properties and selecting your Network Access Protection Tab and enable it for the scope. You would reconfigure your scope options for the
003 Router to use the default gateway for your NAP compliant computers; 006 DNS Server would be configured for the routers used by the NAP compliant computers and 015 DNS Domain Name would be configured for the full-access network you want to allow for your NAP compliant clients.
In your User class settings, you choose Default Network Access Protection Class and set the following:
003 Router for the default gateway used by the non compliant NAP clients. 006 DNS Servers for the non compliant NAP computers 015 DNS Domain type in a restricted domain for the non compliant NAP clients
(*user class settings may be identical to the scope options)
Cordially,
Ronnie Wong
Host, ITProTV

James,
We had originally decided that the vlab was to be a sandbox environment, the chance for users to build everything. The configuration was to begin with just the most basic idea of connectivity. This way people could build and try what they wanted to do.
We are talking about building up scenarios. This is on our list of to dos that continues to grow. *sigh -- we're trying*
The isolated server is set up at it's default install which means the firewall is on and may need to be reconfigured for basic connectivity. I normally disable it to prove that it is connected to the network, then go back and turn on the firewall and enable the connectivity through it I need.
Cordially,
Ronnie

Hello,
My advise is .. in my experience is ... build and destroy your Lab. It has helped me out a lot. Also I would read more than one book. If I could suggest the Windows Server 2012 Inside Out by William Stanek or Windows Server 2012 Unleashed by Rand Morimoto, Michael Noel, Guy Yardeni, Omar Droubi, Andrew Abbate. Also go through Microsoft's Technet. Thank you for your time and have a nice day.
Kind Regards,
Paul

Hey Chris,
When refreshing group policy, the list of GPOs on the server is compared against a list of applied GPOs on the local machine. This list includes the GUID, version number and path. By comparing this information, it can be determined which policies have changed and need to be reapplied. It cannot determine what has changed within the policy. Therefor the entire policy will have to be downloaded, cached locally and applied again.
The size of the GPO is not determined by the number of settings configured in the GPO, but the number of administrative templates. This is not as much of an issue with the new ADMX/ADML format and the use of a central store. However the number of settings that need to be applied, and the number of conflicting settings with other policies can affect startup and logon times. I personally prefer multiple smaller GPOs as this tends to make troubleshooting easier. I do not find that having multiple smaller GPOs affects performance.
Mike

Ian,
My apologies about the delay in getting to your question!
Both you and the episode are correct in your descriptions. NIC teaming allows for a single VM to have a single Virtual NIC but be able connect to multiple NICs. This means that even if a single physical NIC fails, this wouldn't cause the VM's virtual NIC to fail! So this is cool!
As long as you're not using the SingleRoot IO Virtualization (SR-IOV). SR-IOV connects directly to the virtualization functions on the physical NIC. So this means that if you're using this, your VMs do not take advantage of the NIC teaming provided from your OS network stack at the Management OS. Put differently, SR-IOVs don't see the NIC teaming.
This setting shows that both you and the episode to be right! It allows the VMs to use all of the SR-IOV adapters, This means that the VMs will see 2 Virtual NICs and use them both for the purposes you've stated.
Cordially,
Ronnie Wong
Host, ITProTV

Hi,
Thank you for your help, I'm happy to hear that is possible and I'll request it in a few weeks when I'm going to have time to prepare for the exam properly. :)
Regards.

Those notes are posted. They are listed in the order used during the episode. Enjoy!

Nathan,
Glad you're watching the episodes. Under the 70-411 course overview, please check ou the vlab link there. You'll see the setup that we have there or you can use that setup there. The basic setup is:
1. 2012 DC (contoso.com)
2. 2012 Member Server (unconfigured) 2 network adapters
3. 2 Windows 8 clients
Cordially,
Ronnie Wong
Host, ITProTV

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