RSAT for... | Fully supported server OS | Download |
---|---|---|
Windows 10 | 2012 R2 and below | Download |
Windows 8.1 | 2012 R2 and below | Download |
Windows 8 | 2012 and below | Download |
Windows 7 SP1 | 2008 R2 | Download |
A newer RSAT version is always backwards compatible with older server OS versions. For example, all Windows versions from 2012 R2 and below are fully supported by RSAT for Windows 10.
Older RSAT versions can manage newer server OS versions, but only features that are also present in older OS versions can be managed properly. For example, RSAT for Windows 7 partially supports 2012 R2: features that are present on 2008 R2 can be managed, but features unique to 2012 or 2012 R2 cannot).
The Microsoft File Checksum Integrity Verifier (fciv.exe) is a command line tool you can use to calculate MD5 and SHA1 hashes for files.
→ http://www.microsoft.com/download/details.aspx?id=11533
It is a suitable alternative to linux's md5sum, and eliminates the need for third party tools or Cygwin.
Based on recommendations and best practices from Microsoft, and information I found here, I compiled a FSMO placement scenario for 2 domain controllers:
DC1 | DC2 |
PDC Emulator RID Master Infrastructure Master | Schema Master Domain Naming Master Global Catalog |
Also, if your domain is top-level in the AD forest, configure DC1 to sync with external time sources.
To safely remove a node from a Windows 2003 Fail-Over Cluster, follow these steps:
Active Directory (AD) integrated DNS zones are not replicated by the DNS server, but replicates through the Active Directory replication mechanism, and uses the same settings for AD replication.
You can trigger replication through Active Directory Sites and Services, or with repadmin.exe on command prompt:
repadmin.exe /replicate target_dc source_dc DC=DomainDnsZones,DC=domain,DC=com
Replace parameters accordingly:
During start up or log on, once in a while, you'll see a message just saying Please wait. To turn this message into a more useful message, you can enable verbose messages through a policy setting (local or GP):
Either through gpedit.msc, or, if you're in a domain, through a GPO, navigate to Computer Configuration → Administrative Templates → System. Look for the setting Display highly detailed status messages and set it to Enabled. Reboot to apply the change.
« ‹ | December 2024 | › » | ||||
Sun | Mon | Tue | Wed | Thu | Fri | Sat |
1 | 2 | 3 | 4 | 5 | 6 | 7 |
8 | 9 | 10 | 11 | 12 | 13 | 14 |
15 | 16 | 17 | 18 | 19 | 20 | 21 |
22 | 23 | 24 | 25 | 26 | 27 | 28 |
29 | 30 | 31 |