Create a Custom View in Event Viewer to show Reboot Events

Scenario

A server reboot can explain related events and alarms triggered by monitoring systems, so it’s always handy to check for reboots first when troubleshooting.

With this in mind, you want a quick and easy way of finding out when the server last rebooted.

Solution

You need to create a Custom View in Event Viewer, that will only show shutdown and startup events, including reasons why the server rebooted.

Here’s the steps to create the Custom View:

[Read more…]

The trust relationship between this workstation and the primary domain failed

Scenario

You’ve just reverted to a previous snapshot using VMware vSphere 5.1, and the next time you try to login, you get the following error:

The trust relationship between this workstation and the primary domain failed

Solution

Unjoin then rejoin the computer to the domain.

You can also change some settings in GPO for computer passwords.

Configuring the Password Expiry

Contrary to user account password policy, the machine account password is managed by two options:

  • The change interval specified the time between forced changes of the machine account password.
  • The expiry defines whether machine account password expires at all.

Both options are configured through group policies under the following node:

Computer Configuration > Policies > Windows Settings > Security Settings > Local Policies > Security Options

  • Domain member: Disable machine account password changes
  • Domain member: Maximum machine account password age

Both options are not configured by default.

Best Practices in Virtual Environments

In virtualised environments, machine account password changes should be disabled. By preventing machines from changing this password automatically, domain synchronization issues are effectively remedied.

By default, a machine account password is changed every 30 days. When a virtual machine has been in use for more than 30 days and is then reset to an earlier state, the snapshot contains an outdated password causing the machine to loose its connection to the domain.

Source

Task Scheduler failed to start task for user. Additional Data: Error Value: 2147943645

Problem

You scheduled a task, but it failed to run with Error Value: 2147943645
Task-Scheduler-Failed-2147943645_001

Log Name: Microsoft-Windows-TaskScheduler/Operational
Source: Microsoft-Windows-TaskScheduler
Date: 17/01/2013 04:00:00
Event ID: 101
Task Category: Task Start Failed
Level: Error
Keywords:
User: SYSTEM
Computer: [removed]
Description:
Task Scheduler failed to start “\ServerReboot” task for user “DOMAIN\user”. Additional Data: Error Value: 2147943645.

Solution

This error occurs when the user which the task is run under only has permission to run it when logged in.

To allow the task to run when the user is logged on or not, select Run whether user is logged on or not, on the General Tab in the Task Properties:
Task-Scheduler-Failed-2147943645_002

Enable Disk Cleanup on Server 2008 R2 Without Using Add Features

Scenario

You’re running out of space on a computer running Server 2008 R2, but cannot find the Disk Cleanup tool. You know you can add it using Add Features > Desktop Experience, but you just want Disk Cleanup; not the other stuff.

Solution

You need to copy a few files from C:\Windows\winsxs.
Here is a batch script to copy the files to the correct locations, and also pin Disk Cleanup to the Start Menu (using VBScript called PinItem.vbs, shown below): [Read more…]

Ultimate Active Directory resource page

I recently suffered an Active Directory meltdown than made me look to the sky and curse the Gods of Redmond!

I had many good resources to refer to, but I’m sure this page full of linky goodness would’ve helped further: http://blogs.technet.com/b/askds/archive/2010/07/27/post-graduate-ad-studies.aspx

Well worth reading if you want a thorough understanding of the underlying components in Active directory.

Installing SQL Server 2008 R2 on a Failover Cluster using Server 2008 R2

Scenario

You’ve configured a Failover Cluster using Server 2008 R2, and now you want to install SQL Server 2008 R2.

Solution

Changes

A few changes were made to the simple Failover Cluster that was previously configured:

  • Several LUNs were added to the FreeNAS VM so separate disks could be used for each function:
  • 3 x Network Interface Cards (NICs) were configured on each node, each on a different subnet:
    • LAN: 10.10.10.0/24
    • SAN: 10.10.20.0/24
    • Heartbeat: 10.10.30.0/24
  • The FreeNAS interface was configured on the SAN subnet (10.10.20.220).

This time round, the Failover Cluster Validation Report didn’t have a single warning; all green ticks 😉

[Read more…]

Using the DHCP Split-Scope Wizard on Server 2008 R2

Problem

You want to provide some fault tolerance for DHCP, so you plan to add another DHCP server to your network.

You used to have to set up the scopes and exclusions manually, but now you can use the Split-Scope wizard using Server 2008 R2.

[Read more…]

Predefined DHCP Options for VOIP on Server 2008 R2

Problem

You need to set some Predefined Options on your DHCP server to allow your VOIP handsets to connect to the phone system etc.

[Read more…]

When good Domain Controllers go bad!

Scenario

It’s a pleasant day and all is well with the world. Colleagues are skipping around the office with smiles on faces…until…duh duh daaa! One by one, services start failing:

  • Printers go offline:
    • First, for Win7 users
    • Then for all clients
    • Can still print from server though
  • File shares go offline
  • Active Directory replication fails
  • DNS console will not open

Basically, your main Domain Controller (DC) has just taken a dump…and so have you!

These are the steps I took to troubleshoot the issues and get everything back online.

[Read more…]

Configure a Failover Cluster using Server 2008 R2

Scenario

You have already installed and configured an iSCSI SAN for your shared storage, and now you want to configure a Failover Cluster to provide increased availability to services like Exchange, SQL Server and virtualisation.

Two servers called node01 and node02 have already been joined to the domain, each with multiple Network Interface Cards (NICs).

Microsoft’s iSCSI Initiator was used to connect the volumes (LUNs) on the iSCSI SAN. One disk for Data, the other for the Witness disk.

[Read more…]