Category: !Things2Remember

Exchange 2007 Messaging Tracking

by ucinfo, posted in !Things2Remember, Flaphead, MsExchange, Powershell

This is an interesting one I found.  We set Message Tracking on out Hub Role servers so it would purge the logs after 30 days .. nice and simple. 

MessageTrackingLogEnabled               : True
MessageTrackingLogMaxAge                : 30.00:00:00
MessageTrackingLogMaxDirectorySize      : 250MB
MessageTrackingLogMaxFileSize           : 10MB
MessageTrackingLogPath                  : F:Program FilesMicrosoftExchange ServerTransportRolesLogsMessageTracking
MessageTrackingLogSubjectLoggingEnabled : True

So, I need to look for some logs over Easter and they where no there!?!  As you can see Message Tracking has another setting MessageTrackingLogMaxDirectorySize and my logs amounted to 240mb which is why I couldn’t find them.

So, make sure you have set MessageTrackingLogMaxDirectorySize to a decent size, like 2gb?  You can do this by running:

Set-TransportServer   -MessageTrackingLogMaxDirectorySize 2gb

Also  make sure these setting are the same on any Mailbox role, as they have Message Tracking logs too!

MessageTrackingLogEnabled               : True
MessageTrackingLogMaxAge                : 30.00:00:00
MessageTrackingLogMaxDirectorySize      : 250MB
MessageTrackingLogMaxFileSize           : 10MB
MessageTrackingLogPath                  : C:Program FilesMicrosoftExchange ServerTransportRolesLogsMessageTracking
MessageTrackingLogSubjectLoggingEnabled : True

But to set it on a Mailbox Role you need to run:

Set-MailboxServer   -MessageTrackingLogMaxDirectorySize 2gb

Gadgets

by ucinfo, posted in !Things2Remember, Flaphead, Gadgets

Okay, just wanted to share some of this with you, and also to “file” it away for my future reference.

So, I want to get away from having a fixed landline at home, and use the mobile phone network.  So phase one would be to use a one of these 

Dock-N-Talk™
The world’s first truly universal cell phone docking station and charger.
The patent-pending Dock-N-Talk™ allows you to dock your cell phone and use your normal corded or cordless phones to make and receive your cell phone calls. Effectively turns your wireless service into “wired” service while docked. The Dock-N-Talk can be used in your home, office, dorm room, weekend home, boat, RV or any other location where cell service is available

So next it is to use wireless broadband.  Now not as good as fixed line broadband in relation to downloading movies and music, but for suring it should be okay.

Originally I looked at the Linksys WRT54G3G Router
 

But Ian pointed  me to this baby Top Global MB6000 3G Phoebus 3G/Wi-Fi Wireless Router

Both so the same thing, and require a PCMCIA celluar adapter, but they could be thing to let me “cut the cord”

 

 

Windows 2003 SP2 & Exchange 2003

by ucinfo, posted in !Things2Remember, Flaphead, MsExchange

Here we go again.  So nice new DL585 G2.  Slapped Exchange 2003 on SP2 and few other fixes and then started noticing there:

Event Type:    Error
Event Source:    Application Popup
Event Category:    None
Event ID:    333
Description:
An I/O operation initiated by the Registry failed unrecoverably. The Registry could not read in, or write out, or flush, one of the files that contain the system’s image of the Registry.

Event Type:    Error
Event Source:    Srv
Event Category:    None
Event ID:    2019
Computer:    GBRPSMMSWM06NA
Description:
The server was unable to allocate from the system nonpaged pool because the pool was empty.

I have /3g /userva:3030.

When you open task manager, Nonpaged is 96512!

This is Windows 2003 Ent with SP2  .. any ideas?

Microsoft Exchange Server by From Wikipedia

by ucinfo, posted in !Things2Remember, .General, MsExchange

Just googling for an issue I heard about (aparently Exchange 2007 RTM might have some performance issues when you go over 500 users .. can’t be true but have the check it out)

Anyway found this on Wikipedia

http://en.wikipedia.org/wiki/Microsoft_Exchange_Server

Microsoft Exchange Server is a messaging and collaborative software product developed by Microsoft. It is part of the Microsoft Servers line of server products and is widely used by enterprises using Microsoft infrastructure solutions. Exchange’s major features consist of electronic mail, calendaring, contacts and tasks, and support for the mobile and web-based access to information, as well as supporting data storage.

Cool! they should pad it out with this http://msexchangeteam.com/archive/2008/01/02/447806.aspx by Paul Bowden

Hey .. the buggers, they have taken my link of the website .. Come on guys add me back, I am doing the world a service here!

My content is still there ;-) http://msexchangeteam.com/search/SearchResults.aspx?q=flaherty

MSExchangeTransport | Routing | 5003

by ucinfo, posted in !Things2Remember, Flaphead, MsExchange

This stumped me for a while.  Attempted an upgrade of VMWare Exchange 2007 Hub Transport Role.  It failed (See http://blogs.flaphead.dns2go.com/archive/2007/12/19/update-exchange-2007-service-pack-1.aspx)

Basically setup fails with: Process execution failed with exit code 3

.. and the setup log says:

[22/01/2008 15:44:08] [2] Beginning processing.
[22/01/2008 15:44:08] [2] Starting: C:WINDOWSsystem32regsvr32.exe arguments: /s “C:Program FilesMicrosoftExchange ServerbinExSMIME.dll”
[22/01/2008 15:44:09] [2] Process standard output:
[22/01/2008 15:44:09] [2] Process standard error:
[22/01/2008 15:44:09] [2] [ERROR] Unexpected Error
[22/01/2008 15:44:09] [2] [ERROR] Process execution failed with exit code 3.
[22/01/2008 15:44:09] [2] Ending processing.

I will come back to this one later.  Anyway, when I tried to start the MsExchangeTransport Service spat this out in the Application Event Log:

Event Type:     Error
Event Source:   MSExchangeTransport
Event Category: Routing
Event ID:       5023
Description:
A transient configuration error was detected while the routing configuration was loading. Exception details: The local server isn’t a member of any routing group. : Microsoft.Exchange.Transport.Categorizer.TransientRoutingException: The local server isn’t a member of any routing group.
   at Microsoft.Exchange.Transport.Categorizer.RoutingGroupRelayMap.ValidateConfig(ExchangeTopology topology, RawRoutingConfigData rawConfigData, DateTime timestamp)
   at Microsoft.Exchange.Transport.Categorizer.RoutingTables.ValidateConfig(RawRoutingConfigData rawConfigData)
   at Microsoft.Exchange.Transport.Categorizer.RoutingTables.PopulateTables(RawRoutingConfigData rawConfigData)

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type:     Error
Event Source:   MSExchangeTransport
Event Category: Routing
Event ID:       5003
Description:
Microsoft Exchange couldn’t load configuration information for routing. The process will block and retry the operation in 10 seconds.

Checked out the server using adsiedit and found for msExchHomeRoutingGroup.  Strange, I don’t touch it .. honest. 

Looked at another working server and copied the value and the MsExchangeTransport Service started … another weird one!

MSExchangeTransport | Routing | 5003

by , posted in !Things2Remember, Flaphead, MsExchange

This stumped me for a while.  Attempted an upgrade of VMWare Exchange 2007 Hub Transport Role.  It failed (See http://blogs.flaphead.dns2go.com/archive/2007/12/19/update-exchange-2007-service-pack-1.aspx)

Basically setup fails with: Process execution failed with exit code 3

.. and the setup log says:

[22/01/2008 15:44:08] [2] Beginning processing.
[22/01/2008 15:44:08] [2] Starting: C:WINDOWSsystem32regsvr32.exe arguments: /s “C:Program FilesMicrosoftExchange ServerbinExSMIME.dll”
[22/01/2008 15:44:09] [2] Process standard output:
[22/01/2008 15:44:09] [2] Process standard error:
[22/01/2008 15:44:09] [2] [ERROR] Unexpected Error
[22/01/2008 15:44:09] [2] [ERROR] Process execution failed with exit code 3.
[22/01/2008 15:44:09] [2] Ending processing.

I will come back to this one later.  Anyway, when I tried to start the MsExchangeTransport Service spat this out in the Application Event Log:

Event Type:     Error
Event Source:   MSExchangeTransport
Event Category: Routing
Event ID:       5023
Description:
A transient configuration error was detected while the routing configuration was loading. Exception details: The local server isn’t a member of any routing group. : Microsoft.Exchange.Transport.Categorizer.TransientRoutingException: The local server isn’t a member of any routing group.
   at Microsoft.Exchange.Transport.Categorizer.RoutingGroupRelayMap.ValidateConfig(ExchangeTopology topology, RawRoutingConfigData rawConfigData, DateTime timestamp)
   at Microsoft.Exchange.Transport.Categorizer.RoutingTables.ValidateConfig(RawRoutingConfigData rawConfigData)
   at Microsoft.Exchange.Transport.Categorizer.RoutingTables.PopulateTables(RawRoutingConfigData rawConfigData)

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type:     Error
Event Source:   MSExchangeTransport
Event Category: Routing
Event ID:       5003
Description:
Microsoft Exchange couldn’t load configuration information for routing. The process will block and retry the operation in 10 seconds.

Checked out the server using adsiedit and found for msExchHomeRoutingGroup.  Strange, I don’t touch it .. honest. 

Looked at another working server and copied the value and the MsExchangeTransport Service started … another weird one!

Exchange 2007 Service Pack 1: New cmdlets

by ucinfo, posted in !Things2Remember, Flaphead, MsExchange

Just run a get-help on an Exchange 2007 RTM vs Service Pack 1.  Here are the new cmdlets

New Cmdlet

Description

Disable-ContinuousReplicationHostName

Use the Disable-ContinuousReplicationHostName cmdlet to disable a Network Name and IP Address resource that was created using the Enable-ContinuousReplicationHostName cmdlet. These resources will be removed from their dedicated cluster group, and the cluster group will be deleted.

Disable-ServiceEmailChannel

The .NET service channel is introduced in Microsoft Exchange Server 2007 Service Pack 1 (SP1). This channel enables Exchange 2007 to store information that it will later forward to applications or devices that are not permanently connected to the Exchange server computer. The Disable-ServiceEmailChannel cmdlet disables the .NET service channel for a specific user. This cmdlet deletes the receive folder in the user’s mailbox under the root folder.

Enable-ContinuousReplicationHostName

Use the Enable-ContinuousReplicationHostName cmdlet to create a Network Name and IP Address resource in a dedicated cluster group that can be used for log shipping and seeding in a cluster continuous replication (CCR) environment.

Enable-ServiceEmailChannel

The .NET service channel is introduced in Microsoft Exchange Server 2007 Service Pack 1 (SP1). This channel enables Exchange Server 2007 to store information that it will later forward to applications or devices that are notpermanently connected to the Exchange server computer. The Enable-ServiceEmailChannel cmdlet enables the .NET service channel for a specific user. This cmdlet creates a receive folder in the user’s mailbox under the root folder named Service E-mail.

Get-X400AuthoritativeDomain

Use the Get-X400AuthoritativeDomain cmdlet to view the configuration information for the X.400 authoritative domains that are configured in your organization

Import-Mailbox

Use the Import-Mailbox cmdlet to import mailbox data from a .pst file to amailbox.

New-X400AuthoritativeDomain

Use the New-X400AuthoritativeDomain cmdlet to create and specify the X.400 authoritative domain for the Microsoft Exchange Server 2007 organization. The X.400 authoritative domain defines the standard fields for the namespace that is appended to the recipient identity for all mailboxes that are assigned an X.400 address.

Remove-X400AuthoritativeDomain

Use the Remove-X400AuthoritativeDomain cmdlet to remove an X.400 authoritative domain. When you remove an X.400 authoritative domain, the X.400 authoritative domain object is deleted from the Active Directory directory service.

Set-X400AuthoritativeDomain

Use the Set-X400AuthoritativeDomain cmdlet to edit an existing X.400 authoritative domain for the Microsoft Exchange Server 2007 organization. The X.400 authoritative domain defines the standard fields for the namespace thatis appended to the recipient identity for all mailboxes that are assigned an X.400 address.

Test-ImapConnectivity

Use the Test-ImapConnectivity cmdlet to verify that the IMAP4 service is running as expected. The Test-ImapConnectivity cmdlet can be used to test the   IMAP4 functionality for a specified Client Access server for all mailboxes on Exchange 2007 servers in the same Active Directory site.

Test-PopConnectivity

Use the Test-ImapConnectivity cmdlet to verify that the IMAP4 service is ru nning as expected. The Test-ImapConnectivity cmdlet can be used to test the  IMAP4 functionality for a specified Client Access server for all mailboxes on Exchange 2007 servers in the same Active Directory site.

Test-ReplicationHealth

Use the Test-ReplicationHealth cmdlet to check all aspects of replication, cluster services, and storage group replication and replay status to provid e a complete overview of the replication system.

Update-Recipient

Use the Update-Recipient cmdlet to add Microsoft Exchange Server 2007 attributes to recipient objects that are created by the global address list (GAL) synchronization management agent in Identity Lifecycle Manager (ILM) 2007. The recipient objects you modify using this cmdlet must reside on an Exchange 2007 server.

Exchange 2007 Service Pack 1: Schema Changes

by ucinfo, posted in !Things2Remember, Flaphead, MsExchange

Bl00dy hell .. why oh why .. I need to get AD sign off now before I can even install Service Pack1!

Ran a CSVDE to dump the Schema and then filtered in Excel.  I came up with these:

CN=ms-Exch-Storage-Group,CN=Schema,CN=Configuration,DC=go,DC=,DC=net
CN=ms-Exch-Schema-Version-Pt,CN=Schema,CN=Configuration,DC=go,DC=,DC=net
CN=ms-Exch-Resource-Property-Schema-Obsolete,CN=Schema,CN=Configuration,DC=go,DC=,DC=net
CN=ms-Exch-Extension-Attribute-13,CN=Schema,CN=Configuration,DC=go,DC=,DC=net
CN=ms-Exch-Resource-Property-Schema,CN=Schema,CN=Configuration,DC=go,DC=,DC=net
CN=ms-Exch-Foreign-Forest-Public-Folder-Admin-USG-Sid,CN=Schema,CN=Configuration,DC=go,DC=,DC=net
CN=ms-Exch-Internal-NLB-Bypass-Host-Name,CN=Schema,CN=Configuration,DC=go,DC=,DC=net
CN=ms-Exch-Mobile-Additional-Flags,CN=Schema,CN=Configuration,DC=go,DC=,DC=net
CN=ms-Exch-Mobile-Allow-Bluetooth,CN=Schema,CN=Configuration,DC=go,DC=,DC=net
CN=ms-Exch-Mobile-Allow-SMIME-Encryption-Algorithm-Negotiation,CN=Schema,CN=Configuration,DC=go,DC=,DC=net
CN=ms-Exch-Mobile-Approved-Application-List,CN=Schema,CN=Configuration,DC=go,DC=,DC=net
CN=ms-Exch-Mobile-Max-Calendar-Age-Filter,CN=Schema,CN=Configuration,DC=go,DC=,DC=net
CN=ms-Exch-Mobile-Max-Email-Age-Filter,CN=Schema,CN=Configuration,DC=go,DC=,DC=net
CN=ms-Exch-Mobile-Max-Email-Body-Truncation-Size,CN=Schema,CN=Configuration,DC=go,DC=,DC=net
CN=ms-Exch-Mobile-Max-Email-HTML-Body-Truncation-Size,CN=Schema,CN=Configuration,DC=go,DC=,DC=net
CN=ms-Exch-Mobile-Min-Device-Password-Complex-Characters,CN=Schema,CN=Configuration,DC=go,DC=,DC=net
CN=ms-Exch-Mobile-Require-Encryption-SMIME-Algorithm,CN=Schema,CN=Configuration,DC=go,DC=,DC=net
CN=ms-Exch-Mobile-Require-Signed-SMIME-Algorithm,CN=Schema,CN=Configuration,DC=go,DC=,DC=net
CN=ms-Exch-Mobile-Unapproved-In-ROM-Application-List,CN=Schema,CN=Configuration,DC=go,DC=,DC=net
CN=ms-Exch-Standby-Copy-Machines,CN=Schema,CN=Configuration,DC=go,DC=,DC=net
CN=ms-Exch-Resource-Schema,CN=Schema,CN=Configuration,DC=go,DC=,DC=net
CN=ms-Exch-Virtual-Directory,CN=Schema,CN=Configuration,DC=go,DC=,DC=net
CN=ms-Exch-Mobile-Mailbox-Policy,CN=Schema,CN=Configuration,DC=go,DC=,DC=net
CN=ms-Exch-Organization-Container,CN=Schema,CN=Configuration,DC=go,DC=,DC=net
CN=Site-Link,CN=Schema,CN=Configuration,DC=go,DC=,DC=net

At the same time Paul found this: http://technet.microsoft.com/en-us/library/bb738144.aspx

Microsoft Exchange Server 2007 Service Pack 1 (SP1) adds new attributes to the Active Directory directory service schema and makes other modifications to existing classes and attributes. This topic provides information about the Active Directory schema changes that occur when you install Exchange 2007 SP1. These changes are incremental and do not include changes that are made by the initial release of Exchange 2007.

#550 5.1.4 RESOLVER.ADR.Ambiguous; ambiguous address ##

by ucinfo, posted in !Things2Remember, Flaphead, MsExchange

So someone has been messing with out GAL and a few users are this error:

Delivery has failed to these recipients or distribution lists:

There is a problem with the recipient’s e-mail system. More than one user has this e-mail address. The recipient’s system administrator will have to fix this. Microsoft Exchange will not try to redeliver this message for you. Please provide the following diagnostic text to your system administrator and then try resending the message after the problem has been resolved.

#550 5.1.4 RESOLVER.ADR.Ambiguous; ambiguous address ## 

Clever Trevor came up with this really cool way to find the duplicate users. Open up AD Users and Computers.  Up by your domain name, right click and select find. In the Find dialog, click on the Find drop down and select Custom Search and click on Advanced

This will search for the specified email address on all object types:

(&(objectCategory=*)( proxyaddresses=smtp:something@somewhere.com))

You can always change the object category (to users, publicfolders, etc) if you want to narrow down/speed up the search.

 How cool is that! Thanks Trevor