Windows Server 2012 R2 (70-412) Configure Active Directory – Study Guide

Posted on June 16, 2015 by admin

These notes are my personal notes from the FREE training on Pluralsight. You can get your FREE signup through technet/MSDN or Dreamspark. The title of this course is exactly the title of this post. These notes are from this specific course only. I use these as a refresher Study Guide. POWERSHELL topics andcmdlets are in purple. I have a few notes with the “DEMO” each time the training included a DEMO just so you can see how many demos there were which were really helpful. Thanks to Greg Shields @ConcentratdGreg, the trainer, contact info at the end.

Introduction
1. Not about the basics, this is 412 training so the basics should be in place
2. Multiple Forests, multiple domains
3. Configure a Forest or Domain
4. Configure Trusts
5. Configure Sites (remember from an era when WAN connectivity and site replication was expensive)
6. Manage Active Directory and SYSVOL Replication
  1. RODC

Configure a Forest or Domain
1. implement multi domain and multi forest AD, with interoperability with previous versions of AD.
2. Upgrading existing domains and forests, including preparation and functional levels
3. Configure multiple UPN suffixes
4. Used to require contiguous namespace; contoso.com, denver.contoso.com, paris.contoso.com.
  1. now we can use DISJOINTED namespaces. can have a forest with the following domains;
    1. contoso.com
    2. denver.contoso.com
    3. widget.com
    4. This is called a TREE DOMAIN (as in “forest”, “trees” I suppose….) vs. the old
      TREE (disjointed) domain
      
      CHILD DOMAIN
5. When would you want to use a multi domain structure (desired state now is to minimize)?
  1. habit essentially
  2. political or organizational
  3. Autonomy (separation)
  4. Data isolation
  5. Segregation for replication /authentication /authorization
  6. SECURITY is not one of the reasons as part of the same forest.
6. Multi Forest structure
  1. when two forests merge (purchase a company, etc.)
  2. two forests connected by a TRUST of some sort.
  3. Trusts require MANUAL creation
  4. Different requirements for AD Schema can dictate multiple Forests
  5. Exchange Organizations (In Exchange, only allowed one, so if your Exchange needs require more, then you are multi forest)
7. Permissions required for creation
  1. To build a new forest, Local Admin on first DC (there is no AD yet)
  2. To build a new domain tree or child domain, you must be Enterprise Admin
  3. To add additional DCs, you must be a Domain Admin
8. Upgrade Process for Domain or Forest (know this process)
  1. get healthy (make sure everything is working right)
  2. extend the schema (essentially adding columns to AD database, or new characteristics or fields) (ADPREP)
  3. upgrade DCs to new OS (all DCs need to be upgraded prior to raising functional level). Hopefully you don’t have hundreds of DCs.
  4. relocate FMSO roles if needed
  5. raise domain/forest functional level
9. DEMO – extend schema
  1. adprep (link above)
  2. uses the stack of .ldf files where adprep resides
  3. remember you can view these attributes in the ad database using ADSI Edit.
  4. adprep
    1. first use /forestprep
    2. then /domain prep
    3. optionally /gpprep, and /rodcprep
  5. now raise the functional level
    1. ad domains and trusts
    2. cannot go backwords, this is a one way road.
  6. What’s new in the functional levels
  7. Creating new UPN suffix
    1. AD Domains and Trusts, UPN suffixes
    2. add what you want in AD D and T
    3. then in ADUC you can use them in the user account tab
Configure Trusts
1. Configure External, Forest, Shortcut, Realm
2. Configure trust authentication
  1. Forest wide, or “selective”
3. Configure SID filtering
  1. Get-ADUser -filter * | select SAMAccountName,sid (returns SIDS for users)
  2. SID filtering is on my default in external trusts.
  3. used in domain object migrations (from domain to another)
  4. has to be turned OFF to migrate (only time you would do this)
  5. SID history has to be ENABLED to migrate objects, which requires turning off SID filtering. Example; move a user to different domain, if you don’t do this properly a new SID is created and they lose access to printers they used prior. With SID history ENABLED, user object retains a history of both SIDs
  6. Detailed explanation and example of disabling SID filtering, enabling SID history here.
4. Configure Name Suffix Routing
  1. determine what name suffixes get passed / routed to other side of trust
5. Fundamentals
  1. trusts have direction – trusting, vs. trusted
  2. the direction is opposite of the direction of access
  3. remember by “wing it” is ‘eng -> ‘ed. From trustING to trustED.
  4. most are bi-directional
  5. can be transitive (if A trusts B, and B trusts C, then A trusts C)
  6. different types
    1. External from one domain in one forest to domain in a different forest
    2. Shortcut – literally a shortcut to another domain in same complex forest. Not common as AD simplifies
    3. Forest – between two forest roots; everything in forest is trusted. Transitive. Most common type of trust. Acquisitions. Always transitive. Can configure rules of authentication.
      1. Need name resolution to set up. Can be done by consolidating nameservices. In larger environment, conditional forwarders.
      2. create from AD Domains and Trusts
      3. can create both halves of trust from one side (one server)
    4. Realm trust – to non-AD Kerberos realm / Linux
Configure Sites
1. Created for AD replication across geographical locations
2. Associated with subnets (VYOS router for lab)
3. KCC (knowledge consistency checker)
4. Configure Sites and Subnets
  1. rename “Default-First-Site-Name”, use it and create additional as needed
  2. create subnets and associate to sites
5. Create and Configure Site Links
  1. Inter-Site transports
  2. most of the time is IP, NOT SMTP
  3. all sites are added to IP default site link
  4. absolute value of the cost is meaningless, only the RELATIVE value (compared to other links) has meaning
  5. A lot of this had more meaning when network connectivity was expensive and low capacity
6. Manage Site Coverage
  1. you need a DC in each site
  2. are the DCs Global Catalogs (old times was limited due to processing power, bandwidth)
  3. now best practices are simply make every DC a GC
  4. if multiple DCs in a site, define a preferred BridgeHead server. Or leave this alone and leave it to KCC.
  5. best practice is leave it to KCC
7. Manage Registration of SRV Records
  1. determines what DC site computers use
  2. ipconfig -registerdns make the DC set srv records
8. Move DCs Between Sites
Manage AD Replication and SYSVOL replication
1. Upgrade SYSVOL replication to DFS-R (Distributed File System Replication)
  1. If you have an old, upgraded, AD, you might not be on DFS-R and still on the old FRS (File Replication Service)
  2. upgrading to DFSR
    1. three steps after get healthy, migrate to prepared state, migrate to redirected state, migrate to eliminated state
    2. dfsrmig /? (powershell for DFSR migration)
    3. dfsrmig /getglobalstate
    4. results will be “prepared”, “redirected”, or “eliminated”
    5. only do one step at a time then WAIT
    6. Some health check commands
      1. gwmi – class win32_logicaldisk – ComputerName yourcomputername (shows drive space)
      2. repadmin /syncall /force /aped (forces domain sync and ignore all schedules)
      3. update-DfsrConfigurationFromAD
2. Configure replication to RODCs
  1. single use case; unsecure branch location. only contains passwords and content for that branch
  2. never log onto RODC with privileged account
  3. delegated RODC administrator (the selected group can administer the RODC (“managed by” tab)
3. Configure password policy replication for RODCs
  1. set policy for which PWs you want to cache on RODC (password replication TAB)
  2. you can see what users/computers are replicated to RODC on “advanced” tab.
4. Monitor and manage replication
  1. sites and services – right click and “replicate now” from AD Sites and Services
  2. repadmin /replicate server1 server2
  3. repadmin /showrepl
  4. repadmin /kcc
  5. repadmin /prp view servername reveal (shows RODC replication)
  6. in GPMC, look at a domain, you can see replication status
  7. dfsdiag
  8. nltest (tests if you can locate a DC)
  9. AD Change Notification (replicates to all sites instantly)
    1. ADSI edit
    2. sites
    3. “options”, from blank to “1”, now replicates across sites at same replication as intrasite replication.

Jun 14

Windows Server 2012 R2 (70-412) MCSA and the 70-412 Exam – Study Guide

Posted on June 14, 2015 by admin

These notes are my personal notes from the FREE training on Pluralsight. You can get your FREE signup through technet/MSDN or Dreamspark. The title of this course is exactly the title of this post. These notes are from this specific course only. I use these as a refresher Study Guide. POWERSHELL topics and cmdlets are in purple. I have a few notes with the “DEMO” each time the training included a DEMO just so you can see how many demos there were which were really helpful. Thanks to Greg Shields @ConcentratdGreg, the trainer, contact info at the end.

After doing the Advanced Features training, I’m expanding into the rest on Pluralsight and will go through as many as I can before my test date. This content should also apply to the 70-417. The 417 is the one I’m taking is a combination of 410, 411, and 412 all in one. It breaks down the score for each section. You have to pass all three sections. I have passed two of them (410 and 411) but not the 412, so if you fail one of them, you fail the entire test.

An Introduction to the MCSA’s Final Exam
1. bunch of stuff about exam, objectives, strategy
2. 417 is a combination of 410, 411 and 412
3. Intended audience; ok.
4. Without taking a bunch of notes, let’s just say review the exam objectives, just scroll down on the appropriate page for the specific exam you’re looking at;
5. R2 specific information has been included since January 2014. So, while I don’t think you’ll have a lot of questions about the differences from 2012 and Server 2012 R2, I WOULD expect to know the new Server 2012 R2 features.
6. Link on what is NEW in Server 2012 R2
The next section is titled Building Your 70-412 R2 Environment
1. I’m going to put the next section in a new post focused on how to build a lab.

Jun 14

Windows Server 2012 R2 New Features Study Guide

Posted on June 14, 2015 by admin

Windows Server 2012 R2 New Features (test 70-412 or 70-417)

These notes are my personal notes from the FREE training on Pluralsight. You can get your FREE signup through technet/MSDN or Dreamspark. The title of this course is exactly the title of this post. These notes are from this specific course only. I use these as a refresher Study Guide. POWERSHELL topics and cmdlets are in purple. I have a few notes with the “DEMO” each time the training included a DEMO just so you can see how many demos there were which were really helpful. Thanks to Orin Thomas, the trainer, contact info at the end.

Web Application Proxy
1. Replaces AD FS Proxy role
  1. AD FS offers CLAIMS BASED Authentication (based on other atributes from user or computer accounts). For example based on employee type, location, title, etc.
  2. AD FS can work between organizations with different OS (Windows / Linux)
  3. Allows SSO for premise and cloud (like Office 365)
  4. Reverse proxy for web apps (prior might have used TMG / Threat Management Gateway)
2. Web Application Proxy prerequisites
  1. supports pass through authentication
  2. AD FS preauthentication
  3. requries certs;
    1. cert that includes federation service name
    2. specifics for Workplace Join
    3. Certs for each web app, or wildcard cert
Guest Clustering with Shared Virtual Hard Disks
1. I think is the same as using VMware RDMs to sup MSCS clusters on Windows Server VMs. I’ve done a bunch of these at work with vShere 6.0 and Server 2012 R2
2. Nodes can be on different hosts; AKA “Cluster Across Boxes” as opposed to “Cluster in a Box” which is both nodes on one physical host.
3. Shared Virtual Hard Disks allow shared storage WITHOUT SAN. What?
4. More simple than iSCSI
5. Needs to be highly available via
  1. scale out file server
  2. cluster shared volume
6. shared storage needs to be .vhdx
7. Gen1 or Gen2
8. Only with 2012 and 2012R2 for OS
9. DEMO
  1. build out clustered SOFS
  2. configure cluster file server
  3. add csv
  4. set up new share on SOFS using SMB-Applications
  5. Hyper-V hosts need to be able to access this location
10. Then use Hyper-V console to attach the VHD to a SCSI controller
  1. has to be .vhdx
  2. fixed or dynamic
  3. ENABLE VHD sharing
  4. attach to SCSI controller
  5. bring disk online, iitialize, format volume
  6. can create multiple drives on same volume
11. DEMO
  1. create VHD and create VM cluster
  2. enalble vhd sharing
    enable VHD sharing
  3. after each VM (node) can see the storage then you can add the failover clustering FEATURE.
  4. then build the cluster
Improving VHD Performance
1. resizing VHDs
  1. used to have to be shut down, now can be running
  2. must be using .vhdx format
  3. must be connected to a SCSI controller (Gen1, or Gen2)
    1. Gen1 machines boot from IDE, so…
  4. resizing allows to set smaller size upfront, knowing expansion is simple.
  5. use Hyper-V console or Resize-VHD Powershell command
  6. DEMO of above steps
2. Storage QoS
  1. set max/min IOPS
    set IOPS limits
3. Storage Tiering
  1. via storage pools
  2. automatic; turn in and it moves based on activity
  3. CAN manual settings
Windows Server 2012 Clustering Improvements
1. VM Drain on shutdown
  1. If you put a VM in maintenace mode, then VMs are moved to another host.
  2. HOWEVER, in 2012, if you shut down host WITHOUT maintenance mode, there is a disruption of service as VMs go into a saved state, are moved, then started. While they are in a saved state, they are non-functional.
  3. In R2, even if you shut down (without maintenance mode) they move to another host AUTOMATICALLY. This is new in R2
2. Dynamic Quorum / Dynamic Witness
  1. DQ – 2012 and 2012 R2 automatically recalculate quorum if a node is shut down gracefully.
  2. if multiple nodes fail, 1) checks if it has a quorum then 2) recalculates quorum
  3. you can also configure certain nodes to be NON voting node.
  4. Dynamic Witness
    1. configure a witness that will or will not be used based on quorum
    2. if there is an odd number, then dynamic witness doesn’t vote
    3. if there is an even number, then dynamic witness will be active
    4. PURPOSE is to reduce the chance of cluster failure if a witness goes down.
    5. basically insures an odd number of votes
  5. Force Quorum Resiliency
    1. to avoid “split brain” or “partitioned cluster”; nodes are not aware of each other, most often due to network issue. Generally resolved by restarting cluster. Essentially, each set of nodes think they have quorum. Think nodes in two separate datacenters (Sydney and Melbourne)
    2. Force Quorum Resiliency is that when network is restored, the cluster quorum is restored automatically.
  6. Tiebreaker 50-50 Node Split
    1. clusters dynamically adjust a nodes vote (deprecated vote) to ensure odd number.
    2. you have to configure it.
    3. works WITH dynamic witness
    4. works if dynamic witness fails
    5. in multi site clusters, admin can set which site retains quorum
Enhanced Session Mode and Improved VM Export
1. Virtual Machine Connection via Hyper V Console
  1. doesn’t allow cut/paste, scripting, redirect sound, basically only KB and mouse
  2. if you want those features, you usually have to use RDP
  3. Requirements
    1. host on 2012 R2
    2. VMs running R2 or Windows 8.1
    3. Enabled in Hyper V settings on host
    4. account is a member of RDP users or Admins on VM
    5. (do not have to log into VM and enable RDP
2. DEMO of Enhanced Session Mode
  1. allows to set resolution
  2. allows redirect audio
  3. allows record remote audio
  4. redirect printers
  5. redirect clipboard (like RDP)
  6. click “More” to get to map drives, PnP, etc.
  7. Essentially this is like the same thing in RDP but appears pretty robust and solid.
3. Virtual Machine Export IMPROVEMENTS
  1. 2012 or prior, had to shut down machine.
  2. R2 lets you export RUNNING machine.
  3. the exported machine, when you import it, it will be running as well (with certain requirements)
  4. Example; testing; you want to copy a bunch of machines to test a software install.
4. DEMO of Virtual Machine Live Export
  1. create checkpoint (snapshot)
  2. can export checkpoint or live machine
  3. if you do the live machine, it creates temporary checkpoint, then a live update at the last instant to finalize
  4. WILL create a new vm id upon import, if you want. there are three choices; 1) Register in place (use existing unique ID), 2) restore the virtual machine (use existing unique ID), and 3) copy the virtual machine (create a new unique ID). Explanations of these three options here.
  5. Also note the VM unique ID, is a unique Hyper-V GUID, but this is NOT the same as a SID. A SID is used for Active Directory, this is simply for Hyper-V see explanation here.
  6. CAN do multiple imports, like a template. That would usually be option # 3 above.
Generation 2 Virtual Machines – NEW in R2
1. Gen 1 machines WILL run in 2012 R2 no problem.
2. Gen 1 machines emulate older hardware, which creates performance impact
  1. lots of P2V, but now we do a lot of straight to VM
3. Gen 2
  1. supports secure VM boot
  2. don’t need to run on particular older hypervisor
  3. don’t need to support Remote FX
  4. boot volumes bigger than 2.2 Tb (developers will love this; we want all the storage you have….)
  5. there is a new step in VM creation wizard; 1 or 2. Default is still Gen1 (see screenshot)
  6. Can’t really change this later. There is an unsupported script on MSDN and perhaps other places example here.
4. DEMO of Generation 2 VM on Server 2012 R2
  1. It states in the wizard that this cannot be changed, see the warning at the bottom.
  2. next few steps are the same as you’re familiar with.
  3. Gen2 only support new .vhdx format.
  4. Another new feature; no default virtual DVD! This is ONLY created if you specify install by .iso. (see screenshot)
    If you don’t select the .iso, there will be NO default DVD drive created.
5. Generation 2 Boot Order
  1. for booting to .ISO etc.Just like changing boot order in BIOS more less.
  2. Enable secure boot (default is ENABLED)
  3. only supported by Windows OS
  4. VM has to be turned off to change setting.
  5. currently (as of this training)
6. DEMO of Gen2 Boot Order
  1. contained in VM “settings/firmware”
7. NO IDE controller. (older versions HAD to boot off IDE
  1. Gen2 ONLY boot from SCSI
  2. allows hot add storage, or expand storage while running (R2)
8. DEMO of hot add storage and expand
  1. we went over this in the prior post VNEXT First Look
9. Drawbacks to Gen2
  1. no remote FX (so be aware if you are a VDI shop)
  2. no .vhd support for OS drive.
  3. no linux support
  4. no iSCSI reboot
  5. cannot replicate to Azure
SMB and DFS Improvements
1. manage bandwidth based on traffic type; default/Live Migration/Virtual Machine Traffic
2. by default, no limits
3. Bandwidth Limit is a FEATURE, only enabled/configured by POWERSHELL (no GUI install). Installed from Server Manager, enabled by PS
4. SMB manage bandwidth Managed by Powershell, see here.
5. Clone of the DFS database; Use Case; setting it up in a branch office without WAN replication to get initial replication set up.
6. Preserved File Restoration
  1. ConflictAndDeleted and PreExisting can be managed by Powershell;
    1. Get-DfsrPreservedFiles and Restore-DfsrPeservedFiles
    2. can choose to overwrite, or copy to new location
  2. This is a Server 2012 R2 capability.
7. DEMO DFS Export
  1. Get-DfsrCloneState
Remote Desktop Services Improvements
1. Session shadowing, Dynamic Display, RestrictedAdmin Mode, Online Data Deduplication
2. Session shadowing allows admin to connect to Server 2012 R2 session and view mode, or “control mode” so you can interact and control just like the user.
  1. Can be configured to “require permission”
3. DEMO of session shadowing.
  1. similar to what a lot of third party tools have been able to do; Citrix, Webex, LogMeIn123, VNC, etc.
4. Dynamic Display – supports “device rotation” for landscape mode for tablets etc. Multiple monitors, projectors, etc. Supports touch devices.
5. RemoteFX virtualized GPU support DX 11.1
6. compression bandwidth compression – claims of 50% less bandwidth when playing video across Server 2012 R2 RDS WAN link.
7. RestrictedAdmin mode
  1. allows interactive logon without sending credentials
  2. only Windows 8.1
  3. requires /restrictedadmin mode in MSTSC command
  4. more info on RestrictedAdmin mode here.
8. Online Data Deduplication
  1. deduplicates VHD while running
  2. requires Server 2012 R2 with Feature enabled
  3. when deployed on tiered storage, deduped data moved to higher tier
Windows Server 2012 R2 WDS Improvements
1. WDS with Powershell and VHDX deployment
2. lots of new powershell to automate. System Center Orchestrator can call these cmdlets.
  1. New Powershell cmdlets;
    1. New-WdsInstallImageGroup
    2. Import-WdsBootImage
    3. Import-WdsInstallImage
    4. Import-WdsDriverPackage
3. DEMO of Powershell cmdlets via ISE
4. VHDX files Import and Deployment
  1. now can use a GUI to manage.
  2. create in Hyper V, sysprep, then shut down.
  3. no need to capture
  4. import the .vhdx into WDS
  5. make reference machine smaller than 120 Gb or WDS will error thinking it’s larger than the default 120 Gb drive
5. DEMO
  1. demo of sysprep, shut down, etc.
  2. Import to WDS
DHCP and DNS Improvements
1. Implementing DNSSEC, Zone Level Statistics, and DHCP Registration Options
2. DNSSEC allows records to be digitally signed so clients can verify authenticity
3. most Server 2012 R2 improvements related to replication
4. When DNSSEC is enabled, each record gets a matching RRSIG (Record Resource SIGnature) record, and a DNSKEY record and a NSEC/NSEC3. More on DNSSEC here.
5. DNSSEC keys
  1. trust anchor
  2. KSK Key Signing Key
    1. first server with DNSSEC has the KSK
  3. Zone Signing Key
  4. NRPT can be configured after DNSSEC is confitured.
    1. configured with Group Policy
    2. allows you to configure IPSEC
6. DEMO of DNSSEC
7. Zone Level Statistics (improved)
  1. query, transfer, updates
8. Demo of Zone Level Statistics
  1. Get-DnsServerStatistics
9. DHCP registration and Name Protection
  1. DEMO of DHCP registration and Name Protection
  2. site or server level
  3. “enable name protection” checkbox. Does not allow duplicate named hosts.
Upgrading to Windows Server 2012
1. upgrading domain controllers, migrating DHCP servers, migrating file servers
  1. DC not a true upgrade, can’t do x86 to x64 version
  2. only some OS can do an OS upgrade
  3. Recommendation is to introduce a Server 2012 R2 DC to your 2003 functional level domain
  4. promote Server 2012 R2 to DC
  5. transfer FISMO roles to Server 2012 R2 DC
  6. then demote the old DCs (dcpromo)
2. DEMO of upgrading the DCs
  1. netdom query FISMO (shows FISMO roles)
3. Migrating DHCP
  1. back it up using DHCP concsole
  2. install ROLE on Server 2012 R2
  3. then restore the backup
    1. netsh to back up DHCP
    2. 2003 netsh DHCP server export c:\somefilename.txt all (exports the file)
    3. 2003 netsh DHCP server import c:\somefilename.txt all (imports to Server 2012 R2 server)
    4. 2008 use the Server Manager
4. DEMO of transferring DHCP
5. Migrating File Server
  1. biggest issues are permissions, share permissions, and quotas
  2. install migration tools Feature on Server 2012 R2
  3. creates a package to install on source machine
  4. basic steps are;
    1. INSTALL migration tools on Server 2012 R2 target machine
    2. CREATE package for donor/source machine
    3. INSTALL migration tools from package to donor/source machine
    4. START Receive-SmigServerData on target/destination
    5. START Send-SmigServerData on donor/source
    6. More on SmigServerData here.
6. DEMO of moving file server role
  1. install Feature from server manager or PS
    1. DO NEED .net framework 4
    2. create package (just a folder of a bunch of files)
    3. run smigdeploy to start it on the donor/source