Carpe Diem: Flaphead@Home

This is just for me ;-) to remind me AGAIN about these errors:  Event Type: ErrorEvent Source: MSExchange ADAccessEvent Category: Topology Event ID: 2114Description:Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=2908). Topology discovery failed, error 0x80040a02 (DSC_E_NO_SUITABLE_CDC). Look up the Lightweight ...

So this was kinda enlightening ... the AD boys have setup for forest for me and schema / domain prepped too. But when I went to Install Exchange I kept getting: setup /mode:install /role:mt,mb,ca,ht Welcome to Microsoft Exchange Server 2007 Unattended Setup Preparing Exchange Setup The following server roles will be ...

Another silent movie ;-) of something I done a while back and wanted to share!

This is something I done a while back and wanted to share!

This is something I done a while back and wanted to share!

If you try and access OWA 2007 you may see this error   440 Login Timeout   It would appear that this error happens if the IUSR_<Servername> and / or IWAM_<Servername> accounts are disabled on the server.   Using Computer Mangement on the server, navigate to Local Users and Groups and select the disabled acount and ...

Okay so just for everyone (and for me to blow the dust off a few brain cells .. and what I understand the issue to be) .. This is a problem introduced with Exchange 2007, and affects any BES or Outlook 2003 user that is on Exchange 2007. Essentially, a users Exchange 2007 OoO is actually stored at the top of the information for a users mailbox, ...

So at last RIM confirm they have a problem! .. Rumour control has the fix scheduled for BES 5.0 ... god knows when that will hit the streets!. So esentially you when you migrate a Blackberry user to Exchange 2007 they shouldn't set an OoO from the BES device!? Source: http://www.blackberry.com/btsc/article/458/KB15155_f.SAL_Public.html ...

Thanks to Ari for this nugget ;-) The following events are visible:Event Source: Service Control ManagerEvent Category: NoneEvent ID: 7000Description:The Microsoft Exchange Monitoring service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.  Event ...