I've always found that following the test objectives/road map(or as MS says, "skills measured"), using several resources, is the best way to study for any cert test. So here I'm going to list what resources I'm currently using, and soonish I will start with the first objectives and move on from there.
Books:
Installing and Configuring Windows Server 2012 Exam Ref 70-410
http://www.amazon.com/Exam-Ref-70-410-Installing-Configuring/dp/0735673160/
Similar to what the commentators are saying, this book is fairly light on content. But it does present information in the same roadmap as the test objectives.
Training Guide: Installing and Configuring Windows Server® 2012
http://www.amazon.com/Training-Guide-Installing-Configuring-Windows/dp/0735673101/
http://www.amazon.com/Training-Guide-Installing-Configuring-Windows/dp/0735673101/
This has a little more meat to it, but it's not laid out in order of the test objectives.
Windows Server 2012 Inside Out
This is a beast of a book. Looks like it would make a good reference go-to book. I haven't done much with it yet, but I plan on going through it and matching up objectives eventually.
Learn Windows Powershell 3 in a Month of Lunches.
So far I really like this book. It deals more with the base shell, and not as much with scripting. But is still a great reference for anyone. It's a great help when doing labs with powershell only, and supposedly that's pretty heavy on this test.
Web Sites:
This wiki lists the test objectives, and a lot of technet links for your reference. Useful.
That's right, MS offers free virtual hyper-v sessions with 2012. Especially if you don't have your own in-house lab, you can use these to try out the objectives. Or you can do one of the labs offered. Only drawback: you have 120 minutes to get done.
You may get an error when you click on a lab for the first time regarding CredSSP issues. It looks similar to this:
You can click OK and it will enter the correct registry entries, but why not use some Powershell to do it instead? Turns out, this error is documented in this KB article: http://support.microsoft.com/kb/954357
We now have the registry settings needed to fix it, so click Cancel on this dialog box, and fire up your Powershell.
First, set location to the base key using the hklm: psdrive from the Registry provider:
set-location hklm:\system\currentcontrolset\control\lsa\credssp\policydefaults\
Now you just need to add the Hyper-V property and associated value, as outlined in the KB article, to the listed subkeys:
new-itemproperty -path Allowdefaultcredentials, AllowDefaultCredentialsDomain, AllowFreshCredentials, AllowFreshCredentialsDomain, AllowFreshCredentialsWhenNTLMOnly, AllowFreshCredentialsWhenNTLMOnlyDomain, AllowSavedCredentials, AllowSavedCredentialsDomain, AllowSavedCredentialsWhenNTLMOnly -name 'Hyper-V' -value "Microsoft Virtual Console Service/*"
The labs should now come up without a hitch.
You can click OK and it will enter the correct registry entries, but why not use some Powershell to do it instead? Turns out, this error is documented in this KB article: http://support.microsoft.com/kb/954357
We now have the registry settings needed to fix it, so click Cancel on this dialog box, and fire up your Powershell.
First, set location to the base key using the hklm: psdrive from the Registry provider:
set-location hklm:\system\currentcontrolset\control\lsa\credssp\policydefaults\
Now you just need to add the Hyper-V property and associated value, as outlined in the KB article, to the listed subkeys:
new-itemproperty -path Allowdefaultcredentials, AllowDefaultCredentialsDomain, AllowFreshCredentials, AllowFreshCredentialsDomain, AllowFreshCredentialsWhenNTLMOnly, AllowFreshCredentialsWhenNTLMOnlyDomain, AllowSavedCredentials, AllowSavedCredentialsDomain, AllowSavedCredentialsWhenNTLMOnly -name 'Hyper-V' -value "Microsoft Virtual Console Service/*"
The labs should now come up without a hitch.
That's all for now. If i find any other websites that are useful, I will either post them here or within future blogs.
No comments:
Post a Comment