Windows

The “No-Install” Hack: Enable Disk Cleanup on Server 2008 R2

Posted on Updated on

Need to free up space right now but can’t afford a reboot or a feature installation? Windows Server 2008 and 2008 R2 actually have the Disk Cleanup files hidden inside the System Component Store (WinSxS). You just have to move them to the right place.

The Manual “Copy-Paste” Method

By manually placing these two files into your System32 directory, you enable the cleanmgr command immediately.

1. Locate the Files

Search your C:\Windows\WinSxS directory for the following two files. Note: The long folder names may vary slightly based on your service pack level, so use the search bar if needed.

For Windows Server 2008 R2 (64-bit):

  • The Executable: amd64_microsoft-windows-cleanmgr_..._cleanmgr.exe
  • The Language Resource: amd64_microsoft-windows-cleanmgr.resources_..._en-us_...\cleanmgr.exe.mui

2. Move to System32

Copy (don’t move, just in case) the files to these specific destinations:

  1. cleanmgr.exe → %systemroot%\System32
  2. cleanmgr.exe.mui → %systemroot%\System32\en-US

3. Run the Tool

You don’t need to register anything. Simply open a Command Prompt or the Run dialog (Win+R) and type: cleanmgr.exe

Why do it this way?

  • Zero Downtime: No reboots, no “Configuring Windows” screens.
  • Lightweight: You don’t pull in the rest of the “Desktop Experience” (like Media Player or desktop themes) that just adds more bloat to a server.
  • Reliable: You are using the exact binaries Microsoft built for that specific OS version.

#WindowsServer #SysAdmin #ITPro #TechHacks #ServerMaintenance #DiskCleanup #LazyAdmin #Troubleshooting #WindowsAdmin #ZeroDowntime

This entry was posted in Windows and tagged , , , , , , , .

Dcdiag Overview: The Essential Domain Controller Diagnostic Tool

Posted on Updated on

If you suspect issues with Active Directory—whether it’s slow logins, replication failures, or DNS errors—the first command you should run is Dcdiag. This command-line tool analyzes the state of your Domain Controllers (DCs) across a forest or enterprise and provides a detailed report of abnormal behavior.

Why use Dcdiag?

In a Windows environment, all DCs are peers. Any DC can update the directory, and those changes must replicate to all other peers. If the replication topology is broken or the DC Locator service has inaccurate DNS information, your environment will quickly fall out of sync.

Dcdiag identifies these “silent” failures before they become major outages.

Key Functional Areas Tested

Dcdiag doesn’t just run one check; it executes a series of specialized tests:

  • Connectivity: Verifies if DCs are reachable and have the necessary services running.
  • Replication: Checks for latent or failed replication links between peers.
  • Topology: Ensures the Knowledge Consistency Checker (KCC) has built a valid path for data to travel.
  • Advertising: Confirms the DC is properly announcing its roles (Global Catalog, KDC, etc.) so clients can find it.
  • DNS: Validates that the necessary resource records are present in DNS.

How to Run Dcdiag

To get the most out of the tool, you should run it with administrative credentials.

To test a single server:

DOS

dcdiag /s:DC_Name

To identify and automatically fix minor DNS/Service record issues:

DOS

dcdiag /fix

Understanding the Scope

Dcdiag is flexible. You can target:

  1. A Single Server: For local troubleshooting.
  2. A Site: To check health within a specific physical location.
  3. The Entire Enterprise: To ensure forest-wide health.

The LazyAdmin Lesson: Make dcdiag a part of your weekly routine. Catching a replication error on Monday is much easier than fixing a fragmented database on Friday afternoon!

#ActiveDirectory #Dcdiag #SysAdmin #WindowsServer #ITPro #TechSupport #ServerHealth #LazyAdmin #ADTroubleshooting #DataCenter

This entry was posted in Windows and tagged , , , , , , , , .

How to Boot a Windows Server 2003 DC into Directory Services Restore Mode (DSRM)

Posted on Updated on

There are times when Active Directory becomes unstable, or you need to perform a “System State” restore. To do this, you must take the Domain Controller offline by booting into Directory Services Restore Mode (DSRM).

In this mode, the server stops functioning as a DC and instead functions as a standalone member server, allowing you to manipulate the AD database files (ntds.dit) while they aren’t in use.

⚠️ The Golden Rule of DSRM: The Password

When you boot into DSRM, Active Directory is not running. This means you cannot log in with your Domain Admin credentials.

You must use the Local Administrator account, and the password is the unique DSRM Password that was set years ago when the server was first promoted to a Domain Controller (via dcpromo).

Tip: If you’ve forgotten this password but the server is still currently running as a DC, you can reset it before rebooting using the setdsrmpassword command in ntdsutil.

Step-by-Step: Booting into DSRM Locally

If you have physical access (or console access via iDRAC/iLO/vCenter) to the machine, follow these steps:

  1. Initiate a Restart: Restart the Domain Controller as you normally would.
  2. The F8 Menu: As soon as the BIOS screen disappears and the Operating System selection menu appears, start tapping the F8 key.
  3. Advanced Options: You will be presented with the Windows Advanced Options Menu. Use the arrow keys to select Directory Services Restore Mode (Windows domain controllers only) and press Enter.
  4. Login: Once the Windows login screen appears, log on as the Local Administrator using that specific DSRM password.

What happens in this mode?

  • The NTDS service is stopped.
  • The server does not respond to authentication requests from users.
  • The local SAM (Security Accounts Manager) database handles authentication.
  • You can now run ntdsutil or backup software to perform database maintenance or restores.

#ActiveDirectory #DSRM #SysAdmin #WindowsServer #ITPro #TechSupport #ServerAdmin #LazyAdmin #Troubleshooting #LegacyIT

This entry was posted in Active Directory, Windows and tagged , , , , , , , .

How to Change the Static IP Address of a Windows Domain Controller

Posted on Updated on

Whether you are re-IPing a subnet or moving a server to a new VLAN, changing a Domain Controller’s IP address requires more than just updating the NIC settings. If DNS records don’t update correctly, users won’t be able to log in, and replication will fail.

Prerequisites

  • Credentials: You must be a member of the Domain Admins group.
  • Access: Log on locally to the system console. If you lose network connectivity during the change, you may need to boot into DSRM to recover.

Step-by-Step: Changing the IP Address

  1. Open Network Connections: Right-click My Network Places (or Network in newer versions) and click Properties.
  2. Edit Adapter: Right-click your Local Area Connection and select Properties.
  3. TCP/IP Settings: Double-click Internet Protocol (TCP/IP).
  4. Update Addresses:
    • Enter the new IP address, Subnet mask, and Default gateway.
    • Update the Preferred and Alternate DNS servers.
    • Note: Usually, a DC points to itself (127.0.0.1) or a partner DC for DNS.
  5. WINS (Optional): If your environment still uses WINS, click Advanced > WINS tab and update any static WINS server entries.
  6. Apply: Click OK until all dialog boxes are closed.

Critical Step: Post-Change Registration

Once the IP is changed, Windows needs to tell the rest of the domain where the DC is now located. Do not skip these commands.

Open a Command Prompt and run:

  1. Register DNS Records:DOSipconfig /registerdns This forces the DC to update its ‘A’ (Host) record in DNS.
  2. Fix Service Records:DOSdcdiag /fix This ensures that vital SRV records (which clients use to find the DC) are updated to point to the new IP.

Potential Pitfalls: Mapped Drives and Hardcoded IPs

Changing the IP settings won’t affect shared permissions, but it will break any connection made via IP address rather than hostname.

  • Avoid This: net use g: \\192.168.0.199\data (This breaks after the change).
  • Do This: net use g: \\DC1\data (This continues to work regardless of the IP).

The LazyAdmin Lesson: Always use DNS names (Hostnames) for your resources. It saves you from manual updates every time a server moves!

ActiveDirectory #SysAdmin #WindowsServer #Networking #IPAddress #ITPro #DNS #Troubleshooting #LazyAdmin #ServerAdmin

This entry was posted in Active Directory, Windows and tagged , , , , , , , , .