Tom sent me some interesting links just in case you toast e2k7 users by mistake :-| Not tested this yet, but might just for the fun of it in my lab
Undelete the OU/Users/Groups via ADRestore.net (http://blogs.microsoft.co.il/files/folders/guyt/entry12573.aspx)
– or –
ADRestore v1.1 (http://technet.microsoft.com/en-us/sysinternals/bb963906.aspx & http://support.microsoft.com/?kbid=840001)
Then reset password, enable account and re-attach the mailbox.
Just a couple from today
Test the service health for ALL of your E2k7 servers: Get-ExchangeServer | foreach{$_.name;Test-ServiceHealth}
Start non running E2k7 services: Test-ServiceHealth | foreach{$x=$_;$x.ServicesNotRunning | start-service}
I posted first to my twitter account: http://twitter.com/flaphead
This is really good. I have used it before and it looks really sweet now
Check it out: Announcing the release of Exchange Server Remote Connectivity Analyzer and https://www.testexchangeconnectivity.com/
Have you ever installed an Exchange server and wanted to verify your Internet facing services were setup and configured properly? Things like Exchange ActiveSync, AutoDiscover, Outlook Anywhere (RPC/HTTP), and inbound email. Sure there are cmdlets included in Exchange 2007 like test-ActivesyncConnectivity and test-OWAConnectivity, but these tests can only be run inside your network and effectively only test your internal network connectivity. Or what if you get a call or an escalation regarding one of these services not working? How do you verify if just this user or everyone has a problem? And if there is a problem, where do you start troubleshooting? Is it a DNS problem? Is it a certificate problem? Is a port not open on the firewall?
flaphead.com 