Wake Active Directory from the Dead

So you have this 10-server test setup with multiple domains, multiple domain controllers, member servers and clients. It is running Virtual Server and for some months ago you left it and now it is time to use it again.

You power it back on and everything works - - - Not (If you seen Borat you know what I mean!)
The object changes I made in the child domain did not appear in the GC on the parent domain!?

Looking into the problem, I found this event -

Event Type: Error
Event Source: NTDS Replication
Event Category: Replication
Event ID: 2042
Date: 19-09-2007
Time: 11:37:04
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: SRV02
Description:
It has been too long since this machine last replicated with the named source machine. The time between replications with this source has exceeded the tombstone lifetime. Replication has been stopped with this source.
The reason that replication is not allowed to continue is that the two machine's views of deleted objects may now be different. The source machine may still have copies of objects that have been deleted (and garbage collected) on this machine. If they were allowed to replicate, the source machine might return objects which have already been deleted.
Time of last successful replication:
2007-04-12 15:57:10
Invocation ID of source:
032bf6c8-f6b8-032b-0100-000000000000
Name of source:
d063611f-7ff1-4445-a7bf-45bd0066dcc6._msdcs.dlt-root.as
Tombstone lifetime (days):
60

The replication operation has failed.

User Action:

Determine which of the two machines was disconnected from the forest and is now out of date. You have three options:

1. Demote or reinstall the machine(s) that were disconnected.
2. Use the "repadmin /removelingeringobjects" tool to remove inconsistent deleted objects and then resume replication.
3. Resume replication. Inconsistent deleted objects may be introduced. You can continue replication by using the following registry key. Once the systems replicate once, it is recommended that you remove the key to reinstate the protection.
Registry Key:
HKLM\System\CurrentControlSet\Services\NTDS\Parameters\Allow Replication With Divergent and Corrupt Partner

Oh no - do I have to rebuild it all? Fortunately not. Doing a series (the message says registry key, but it is a value) of -
reg \\server\HKLM\System\CurrentControlSet\Services\NTDS\Parameters /v "Allow Replication With Divergent and Corrupt Partner" /t reg_dword /d 1

(one line, but may be wrapped here)

and restarting the domain controllers solved the problem.

Read more in Event ID 2042: It has been too long since this machine replicated

Windows Server 2008 Kernel Changes

Just saw/heard the Windows Server 2008 Kernel Changes by Mark Russinovich (SEC416) from TechEd in Orlando. As always, valuable information - and hearing Mark stumble as his system unexpectedly crashes for him is kind of funny.

For those of you having 32-bit terminal services systems, you should look forward to the improvements: More virtual memory, parallel sessions initiations (e.g. logons) etc.
But, hear it all for yourself here.

Gartner Magic Quadrant for Unified Communications 2007

Interesting reading, Gartner has published a new MQ for Unified Communications 2007, where Microsoft is the leader in "ability to execute" (With IBM and Cisco lagging behind).

Gartner concludes that 2008 will be the year where UC will be mainstream and even refers to Microsofts VoIP As You Are versus "rip and replace" strategy for implemting UC ;-)

Btw if you haven't seen the two PBX's discussing VoIP As You Are before then it i a must. Also two new PBX Replacement Cam videos has been released (I bet they had some fun making these ;-)

USB telephony updates for Windows XP / Vista

During my UC Bootcamps I've had problems a few times with my USB handsets being set as primary sound device (Therefore sound from demo's and videos would be redirected to my Anacapa device instead of my Logitech USB loudspeakers).

I'm switching quite a bit between the Roundtable device, speakerphone's and the Anacapa, so it's quite an annoyance to always check whether my Logitech is still the default

There is an XP/Vista update for this that I've blogged about before, but it has now been updated so I will try to test it again.

Find the updates here -

A USB telephony device that is installed on a Windows Vista-based computer is unexpectedly set as the default audio device
A USB telephony device that is installed on a Windows XP-based computer is unexpectedly set as the default audio device