Friday, August 31, 2007

Export the IP Relay List on SMTP Virtual server

We will Export the IP Relay List on SMTP Virtual server into a txt file. The Process is getting this work done is very simple.

  • Download and save it to your C drive
  • Open CMD windows and navigate the same directory.
  • From Command line run the following command

regsvr32 exipsec.dll

Now use the following command below (Change the Exchangeserver=Your Exchange server name & DomainControllerName=Your DC name )

cscript ipsec.vbs -s ExchangeserverName -o e -r relay -d DomainControllerName >>IPRelayList.txt

Download, ExIPSecurity


oz ozugurlu

No Free/Busy information could be retrieved

Here is one of the common problems I have seen after not successful migration. The old server still has the Schedule + Free Busy information, and Exchange administrator forget to replicate it over to new server and decommissions the old server. The new exchange server works the most part works just fine except Free Busy information. Lets clear this up first what is free busy and where we find this folder in Exchange org.

Here is the location

  • Public Folders


Exchange Server 2003 stores free/busy information in a dedicated public folder that is named SCHEDULE+ FREE BUSY

This folder contains a separate subfolder for each administrative group in your Exchange organization. When a user publishes free/busy data, Exchange Server 2003 posts the information in a message in the appropriate free/busy subfolder. The free/busy folders are system folders and function in a manner that is similar to offline address book folders.

How a user locates this information

When a user schedules an appointment or meeting and wants to determine the availability of another user, the client must obtain free/busy data for that user. To do this, the client must first locate the appropriate free/busy folder, and then identify the free/busy message for the specified user. Outlook performs this task slightly differently than Outlook Web Access and Outlook Mobile Access

Locating Free/Busy Information with Outlook

When locating a user's free/busy public folder, Outlook uses a process that is similar to its publishing process. Outlook starts by retrieving the user's legacyExchangeDN value from Active Directory, and then uses that value to identify the name of the free/busy folder and the subject line of the appropriate free/busy message. Outlook then searches for the appropriate folder and message, starting with the specified user's default public folder store, and if necessary, requesting a referral to an appropriate server

Location Free/Busy with OWA and OMA

When Outlook Web Access or Outlook Mobile Access requests free/busy information for a selected user, the Exchange server that supports the Outlook Web Access applications (generally a front-end server) processes the request.

The front-end server sends a query to the users default public folder store ( if you don't have the Free/Busy folder there here you will have problems), which responds with a list of available free/busy servers. As is the case with a normal public folder referral, the front-end server sends a query to the first available server in the list, which responds with the free/busy data. The front-end server only queries another free/busy server if the first server in the list does not respond. If Outlook Web Access or Outlook Mobile Access does not use a front-end server, the users default public folder store will only respond with a single free/busy server. If that server is unavailable, the request will fail. No other servers can be queried.

Multiple Sites Consideration

When Outlook Web Access or Outlook Mobile Access requests free/busy information, the mailbox store will use one free/busy server to find the information. This limitation may cause problems if your topology has multiple sites, because in the default configuration, each free/busy server holds only that site's free/busy data. You need to configure the free/busy folders to replicate if you want data from multiple sites to be available to all users.

Removed a users still getting conflicting meeting request, here is the reason

I have seen many times, a secretary leaves the company who and account gets deleted but people still gets conflicting meeting request, and cannot understand why. Sometimes users will retrieve old free/busy information for a user with a moved mailbox because the legacyExchangeDN is not valid or has been manually changed. This situation causes significant problems for the moved user because the user may receive many conflicting meeting requests. The free busy data is the information which is published on the Public folder and shows the user availability or schedule.

Common mistakes and the fix are in the KB article 284200. The summarization of the cause is as below


This behavior occurs because the only instance of the "Schedule+ Free/Busy" system folders has been deleted or contains invalid data. The new Exchange 2000 or Exchange 2003 Server points to an incorrect Exchange Server computer as being the public folder server for the administrative group.

Basically the Administrator forgets to replicate all system folders properly, and causes the Free/Busy to be lost on the new exchange server.


Follow the article 284200

Open adsiedit.msc and locate the following

  • Configuration Container [Computer.Domain.Com]
  • CN=Configuration, DC=(YourDomainController),DC=com
  • CN=Services
  • CN=Microsoft Exchange
  • CN=(YourOrganization)
  • CN=Administrative Groups
  • CN=(YourAdministrativeGroup)


Go to attributes, Properties, and locate "SiteFolderServer"

If you are seeing old server name this has to be changed to new server name. In order to do that, you need to know the distinguishedName.

Drill down in ADSIedit.msc

  • Configuration Container [Computer.Domain.Com]
  • CN=Configuration, DC=(YourDomainController),DC=com
  • CN=Services
  • CN=Microsoft Exchange
  • CN=(YourOrganization)
  • CN=Administrative Groups
  • CN=(YourAdministrativeGroup)
  • CN=(Servers)
  • CN=(YourServer)
  • CN=InformationStore
  • CN=First Storage Group


  • In the right pane, double-click CN=Public Folder Store (YourServerName) to open the properties.
  • Under Select a Property to View, click distinguishedName.
  • Copy the value.

You need to paste this value into SiteFolderServer" on the first step. Close ADSIedit.msc and restart information store service on the Exchange server.If you are still not seeing the Free/Busy folder under public folders (backup all PF information) delete the PF database and recreate the new one.


Do not forget to replicate the Free/Busy information and all other system folders if you do a migration.



Oz Ozugurlu

Saturday, August 25, 2007

Blocked Worker Threads

What causes Blocked Worker Thread error messages is the one of the most asked question among community. Below are some nice notes collected from Web to clear of some of this question? In order to communicate with Microsoft Exchange, the BlackBerry Enterprise Server utilizes Microsoft's Messaging. Application Programming Interface (MAPI). Under certain conditions, it is possible that MAPI can achieve a deadlock state where all of the MAPI worker threads become hung and cannot recover. In the regular operations of the BlackBerry Enterprise Server, a disconnect (i.e. Exchange Server taken offline) between the Microsoft Exchange

Server and the BlackBerry Enterprise Server can result in Microsoft's MAPI threads to enter a deadlock state. Once the MAPI threads enter a hung state condition, there is a possibility that the threads will not be released and all MAPI threads used by the BlackBerry Enterprise Server will eventually reach deadlock. It is this deadlock state that results in the stoppage of the redirection of messages to and from the BlackBerry handheld

There are multiple reasons for blocked MAPI worker threads.

  • The BlackBerry Enterprise Server attempted to contact a BlackBerry device user's mailbox but could not initiate a connection with the Microsoft Exchange Information Store.
  • The BlackBerry Enterprise Server attempted to contact the Microsoft Exchange server and is still waiting for a response.
  • The Microsoft Exchange server might be offline or another unreachable state.
  • The BlackBerry Enterprise Server attempted to contact the Microsoft Exchange server but did not receive a timely response. This could be due to issues such as packet loss on the network or complex calls to the Microsoft Exchange server (e.g. a bulk load on a BlackBerry device user with more than 5000 calendar entries).
  • The Microsoft Exchange server may be taxed too heavily and cannot handle the load.

After the cause has been determined, it will probably be necessary to restart the BlackBerry Enterprise Server. After a pool of threads has crashed restarting the BlackBerry Enterprise Server services will not release them, as they are part of the Messaging Application Programming Interface (MAPI) subsystem.

If only individual threads are hung, restarting the BlackBerry Enterprise Server services will release those threads and reinitialize them without restarting the BlackBerry Enterprise Server. However, since it is difficult to determine whether individual threads have crashed, or an entire pool of threads, it is better to restart the BlackBerry Enterprise Server rather than restarting only the services.

RIM KB00778


Oz Ozugurlu


How to delay the SRP reconnection

This post is the resolution for SRP key Connection, brought to my attention by one of my visitor, so Howie gets the credits.


The BlackBerry Enterprise Server may disconnect the Server Routing Protocol (SRP) connection to the BlackBerry Infrastructure. This disconnection may be due to the following network conditions:

  • Packet loss
  • Latency
  • Other symptoms of poor network conditions

Immediately following the SRP disconnection, the BlackBerry Enterprise Server attempts to reconnect to the BlackBerry Infrastructure. However, if poor network conditions persist during this time, the SRP connection may be repeatedly disconnected and reconnected by the BlackBerry Enterprise Server.

The BlackBerry Infrastructure is configured to disable SRP identification (IDs) that establish and exceed five connections within one minute.

Note: To actively monitor the BlackBerry Enterprise Server's SRP connection, see KB05279.


The following procedure involves modifying the computer registry. This can cause substantial damage to the Microsoft Windows® operating system. Document and back up the registry entries prior to implementing any changes. Logic code has been added to the following versions of the BlackBerry Enterprise Server, whereby the SRP connection, following a disconnection, will be delayed to prevent the SRP IDs from being disabled:

  • BlackBerry® Enterprise Server for Lotus Domino software version 4.1 Service Pack 4

  • BlackBerry® Enterprise Server for Microsoft Exchange software version 4.1 Service Pack 2

  • BlackBerry® Enterprise Server for Novell GroupWise software version 4.1 Service Pack 2


The delay will only function correctly while the BlackBerry Enterprise Server services are running. Restarting the BlackBerry Enterprise Server may prevent the delay from functioning as expected.

Important: Restarting certain BlackBerry Enterprise Server services will delay email message delivery to BlackBerry devices. For more information, see KB04789

For earlier versions of the BlackBerry Enterprise Server, the following registry value can be used to add a delay between the time the BlackBerry Enterprise Server detects the SRP connection has been disconnected and when it attempts to reconnect to the BlackBerry Infrastructure.

The following Registry value can be used to add a delay between the time the BlackBerry Enterprise Server detects the SRP connection has been disconnected and when it attempts to reconnect to the BlackBerry Infrastructure.

  • On the computer hosting the BlackBerry Enterprise Server, select Start > Run, type regedit, and click OK. This process opens the Registry Editor.   
  • Go to one of the following locations, depending on the BlackBerry Enterprise Server software version:

    For BlackBerry Enterprise Server software version 2.2, go to

    HKEY_LOCAL_MACHINE\Software\Research In Motion\BlackBerry\Server\

    For BlackBerry Enterprise Server software version 3.6, go to

    HKEY_LOCAL_MACHINE\Software\Research In Motion\BlackBerry\Servers\<BlackBerry Enterprise Server_name>

    For BlackBerry Enterprise Server software versions 4.0 and 4.1, go to

    HKEY_LOCAL_MACHINE\SOFTWARE\Research In Motion\BlackBerry Enterprise Server\Dispatcher\

  • Determine if the InitialReconnectTimeout registry entry is present.
    • If the InitialReconnectTimeout entry exists, change the Data field to the number of seconds you would like the SRP reconnection to be delayed.
    • If the InitialReconnectTimeout registry entry does not exist, create a registry entry with the following values:







This value specifies the number of seconds the SRP reconnection is to be delayed. For example, a value of 15 delays reconnection for 15 seconds. For the Base, specify Decimal.


Note: To try and prevent the BlackBerry Enterprise Server from disabling its own SRP ID due to network conditions that cause the SRP to disconnect, this value should be set to a minimum of 15 seconds. This ensures that the BlackBerry Enterprise Server will not make five SRP connections within one minute, thereby preventing the SRP from being disabled.



Oz Ozugurlu

Thursday, August 23, 2007

Locating Duplicated SMTP Proxy Address in Active Directory

I am trying to add a user account in AD which is fine but when I try and change the email alias it tells me that the address is already in use. I am having a hard time finding which user has this alias. I have tried to query

AD for the email address but cannot find it. What can I use to find the user in AD that is using the alias?

Solution 1:

  • First go to ADUC (active directory computers users)
  • Click, start, run, type DSA.MSC
  • Click on Icon (find objects in active directory) Top far right corner
  • Click Drop down menu and pick Custom Research, Click Advance, in the LDAP queries
  • Type following (Modify the name oz and the part to your scenario)

Solution 2:

Download Adfind.exe

Run below command to locate the SMTP Proxy address

adfind -b dc=SMTP25,dc=Net -f (proxyAddresses=smtp:oz*) name proxyaddresses

adfind -b dc=SMTP25,dc=Net -f (proxyAddresses=smtp:oz*)


Oz Ozugurlu

Trouble shooting 5.1.1 errors in large Enterprise environment

The user A is belonging to Child Domain A. the user B is belonging to Child Domain B. The Forest infrastructure is as below. User A can sent mail to user B, User B cannot sent mail or reply any of the mails coming from User A. When user B tries to reply, he gets 5.1.1, and mail bounce now, keep it mind these domains are two child domain, and domain controllers on both domains are GC (Global Catalog servers)

Your message did not reach some or all of the intended recipients.

Subject: RE: Test

Sent: 8/21/2007 11:42 AM

The following recipient(s) could not be reached: on 8/21/2007 11:42 AM

The e-mail account does not exist at the organization this message was sent to. Check the e-mail address, or contact the recipient directly to find out the correct address.

< #5.1.1>

Now we have three DC/GC involving into our problem scenario

DC1. (user A resides) Another DC/GC ( (User B Resides)

We will ask first domain controller is the user object reside in the GC (Global Catalog)

adfind -h –b dc=archq,dc=RI,dc=Smtp25,dc=Net -gc -f (samaccountname= oz)

It returned below information, so we know the information is there.Now we will ask second DC/GC same question

adfind -h –b dc=archq,dc=RI,dc=Smtp25,dc=Net -gc -f (samaccountname= oz)

The information is being returned as well.Now we will ask third DC/GC same question

adfind -h –b dc=archq,dc=RI,dc=Smtp25,dc=Net -gc -f (samaccountname= oz)

We get object cannot be found, BINGO here is where the problem lays. The Third DC/GC does not have the information about the requested user

The Adfind is incredible fast and efficient. I am appreciating more every day how useful Adfind toll is.

We are still working on the failed replication issue, we know the replication failed due to orphan object in AD, and trying to empty to deleted item dumpster in the effected DC/GC

If Joe Nagy won't lose his patient on me I am going to write more about Adfind and exchange and share with Exchange community.

Using server:

Directory: Windows Server 2003

dn:CN=Ozugurlu\, Oz (Consultant),OU=Users,OU=CSC,OU=NHQ Region,DC=archq,DC=ri,DC=Smtp25,DC=net

>objectClass: top

>objectClass: person

>objectClass: organizationalPerson

>objectClass: user

>cn: Ozugurlu, Oz (Consultant)

>sn: Ozugurlu

>l: Falls Church

>st: Virginia

>title: Senior Messaging Administrator

>description: NHQJPK1FS1, ETS Ops, 05/26/06

>postalCode: 22042




>givenName: Oz

>distinguishedName: CN=Ozugurlu\, Oz (Consultant),OU=Users,OU=CSC,OU=NHQ Region,DC=archq,DC=ri,DC=Smtp25,DC=net

>instanceType: 0

>whenCreated: 20060525194528.0Z

>whenChanged: 20070728124729.0Z

>displayName: Ozugurlu, Oz [Consultant]

>garbageCollPeriod: 0

>mDBUseDefaults: FALSE











1 Objects returned


Oz ozugurlu

Wednesday, August 22, 2007

Change FQDN name on EHLO/HELO


My email server has been listed at CBL (Composite Blocking List) due to an improper HELO response.  My outbound IP Address resolves to at our authoritative DNS.  When certain servers do an EHLO/HELO check for spamming, my email server returns servername.domainname.local (my internal domain name).  How can I get my Exchange Server 2003 to respond with my DNS listing of


  • Open ESM drill down to
  • Administrative groups
  • Servers
  • Your server
  • Protocols
  • SMTP
  • Virtual Server, Properties

Deliver, and Advance, under Full qualified domain name, ( replace the entry with your public host record of your mail server FQDN (, click Check DNS to make sure it is valid.

Stop and restart your Exchange Virtual server, now if you telnet into your server on port 25 you will get SMTP banner as


Oz Ozugurlu

Tuesday, August 21, 2007


You must not rename or move the Exchange Administrative Group or the Exchange Routing Group after you install Exchange Server 2007 in a mixed-mode environment After you install Microsoft Exchange Server 2007 in a mixed-mode environment, you must not rename the Exchange Administrative Group or the Exchange Routing Group in Exchange Server 2007. This is because Exchange Server 2007 uses the Exchange Administrative Group for configuration data storage and uses the Exchange Routing Group to communicate with earlier versions of Exchange Server. Additionally, the process of moving objects that are contained in the Exchange Administrative Group or in the Exchange Routing Group is not supported in Exchange Server 2007.

Do not move Exchange 2007 servers out of Exchange Administrative Group (FYDIBOHF23SPDLT) and do not rename Exchange Administrative Group (FYDIBOHF23SPDLT) by using a low-level directory editor. Exchange 2007 must use this administrative group for configuration data storage. We do not support moving Exchange 2007 servers out of Exchange Administrative Group (FYDIBOHF23SPDLT) or renaming of Exchange Administrative Group (FYDIBOHF23SPDLT).

If you replace each letter in FYDIBOHF23SPDLT with the previous letter in the alphabet, you get EXCHANGE12ROCKS. Setup also creates a new routing group inside this new administrative group, and it is named "Exchange Routing Group (DWBGZMFD01QNBJR), replace each letter in DWBGZMFD01QNBJR with the next letter in the alphabet, it comes up to EXCHANGE12ROCKS!

Exchange 2007 is ROCK

Here is the real story

As most people know, back in the days of Exchange 5.5, Exchange servers were grouped into sites, representing groups of well-connected servers.  In Exchange 2000 and Exchange 2003 we introduced the idea of routing groups, which represented well-connected servers, and administrative groups, which represented administrative boundaries.

In Exchange 2007 (aka Exchange 12), our management model has evolved such that we no longer need to expose routing groups or administrative groups.  However, because we live in the same Active Directory hierarchy and object model as Exchange 2000/2003, we found that we still needed to create secret admin and routing groups to hold Exchange 2007 servers; groups that would never be exposed to administrators... unless they used legacy management consoles or poked around manually in the Active Directory.

So the question arose, here in the cloistered hallways of the Redmond campus, what should we name these secret groups? They had to be named something, and we had to be sure that we chose a name that nobody with an existing Exchange 2000/2003 deployment had chosen (because we want to be sure that the new groups contain only Exchange 2007 servers); but since they were to be hidden from all but the nosy, they didn't have to be particularly euphonious names.

 In fact, as you know if you've performed haruspicy on the Exchange 2007 AD configuration, the names we chose are these:

Exchange Administrative Group (FYDIBOHF23SPDLT) & Exchange Routing Group (DWBGZMFD01QNBJR)

Not, perhaps, poetic.  In part, at least, rather mundane.  "Exchange Administrative Group". No Pulitzers there.  But whence those odd jumbles of letters and numbers? The original idea had been to append GUIDs to the names to ensure uniqueness.  But it was put to us that this was unimaginative, and that if we had any pride we would think of something "clever".  So the floor was opened to suggestions. Some people favored numbers, transcendental or otherwise interesting pi (3.141592654...), e (2.718281828...), phi (1.618033989...).  The Hardy-Ramanujan number (1729, the smallest number that can be written as the sum of two cubes in two different ways) was mentioned.Pop culture references began to appear; 24601 (Jean Valjean's prisoner number), 2716057 and 3370318 (Bender and Flexo's serial numbers, from Futurama).  THX1138 (Lucas' trademark) was too obvious to need mentioning.

As the person actually making the change, however, I got final say; and I chose to reject the math and pop culture geeking of my peers in favor of my own.  I cast my mind back to 2001 (the novel movie, not the year), and HAL.  It was widely asserted that the name HAL had been derived from IBM, by employing a simple Caesar cipher and shifting each letter one space backwards.  I resolved that if it was good enough for Arthur C. Clarke, it was good enough for me - and, by extension, good enough for you, the valued customer.

 At this point, it should be a trivial exercise to "decode" the hidden message in the admin and routing group names - if a further hint is needed, I'll add that they both decode to the same message.  For the lazy or impatient, I'll reveal the answer on the other side of a handful of ellipses



Exchange 2007 is SPDL


Best Regards,

Oz Ozugurlu

SMTP Server Responses

During the protocol conversation, the SMTP server might reject certain commands. One reason is because of the lack of permissions. The following list explains what combination of configuration and (lack of) permissions are responsible for the certain protocol rejects by the SMTP server.

We have seen this on Exchange 2007 new installation


  • Open EMC (exchange management Console)
  • Go to Server configuration
  • Hub Transport
  • Default (Receive connector)
  • Permissions Group
  • Tick, Anonymous users


530 5.7.1 Client was not authenticated

In response to "MAIL FROM". The session is not authenticated and does not have the ms-Exch-SMTP-Submit permission.


535 5.7.3 Authentication unsuccessful

In response to "AUTH". Either the credentials are incorrect, or the authenticated user does not have the ms-Exch-SMTP-Submit permission. (The reason why the lack of the Submit permission results in an authentication failure, and not an authorization failure is because the server would give away information, making the SMTP server a resource for password guess attacks.)


550 5.7.1 Client does not have permissions to submit to this server

In response to "MAIL FROM". The session is authenticated but does not have the ms-Exch-SMTP-Submit permission.


550 5.7.1 Client does not have permissions to send as this sender

In response to "MAIL FROM:". The "MAIL FROM" command specified an address at an authoritative domain, and the session does not have the ms-Exch-SMTP-Accept-Authoritative-Domain-Sender permission.


550 5.7.1 Client does not have permissions to send on behalf of the from address

In response to End Of Data. The authenticated user does not have permission to submit on behalf of the sender address specified in the header of the message, and

the session does not have the ms-Exch-SMTP-Accept-Any-Sender permission.


550 5.7.1 Unable to relay

In response to the "RCPT TO". The recipient domain does not match any of the accepted domains, and the session does not have the ms-Exch-SMTP-Accept-Any-Recipient permission.




Oz Ozugurlu

How long it takes to move 1.2Gig mailbox to another Exchange server

How long it takes to move 1.2Gig mailbox to another Exchange server (100Meg) within the Pick time. We did the test as follows, and come up with roughly 15Minutes.The mailbox is used for this test is heavily uses mailbox and may items and E-mails belong to user. Moving mailbox (1.2GB) on 100Meg connection from Server 1 to Server 2 on pick time. This mailbox is in used years, and there are a lot of subfolders and content exist

<?xml version="1.0" encoding="unicode" ?>

<taskWizardRun taskName="
Move Mailbox" dcName="NHQDTCDC5" buildNumber="7638" runningAs="">

2007-08-21 13:07:10.563" milliseconds="955422" />

<moveMailbox mixedMode="
false" maxBadItems="0">


/dc=net/dc=SMTP25/dc=ri/cn=Configuration/cn=Services/cn=Microsoft Exchange/cn=SMTP25/cn=Administrative Groups/cn=SMTP25/cn=Servers/cn=EX5VS/cn=InformationStore/cn=EX5-SG2/cn=EX5-SG2-MB3</database>



0" completedCount="1" warningCount="0" errorCode="0x00000000" />


<item adsPath="
LDAP://,OU=Mail Test,OU=Service Accounts,OU=NHQ Region,DC=SMTP25,DC=ri,DC=SMTP25,DC=net" class="user">

-6" milliseconds="955391" />

<summary isWarning="
false" errorCode="0x00000000">

The operation has completed successfully.



/dc=net/dc=SMTP25/dc=ri/cn=Configuration/cn=Services/cn=Microsoft Exchange/cn=SMTP25/cn=Administrative Groups/cn=SMTP25/cn=Servers/cn=EX1VS/cn=InformationStore/cn=EX1-SG2/cn=EX1-SG2-MB1</database>









Oz ozugurlu

Monday, August 20, 2007

Outlook Crashes on Reply E-mail from Specific User

Today I have experienced real weird issue, when client replies to an E-mail came from certain user, outlook crashed to a death. There is no sign on the device manager what might be going wrong. (Outlook 2000, 2003, and 2007). I started troubleshooting this weird issue. One of the first thighs I have done to download Process Explorer for windows. Shortly after I have figured out what was going on.


Outlook Crashes on Opening or replying to certain e-mails came from a specific person.


Second Fix

The message has embedded pictures inside and on the reply it crashed the outlook.

Resent the mail, it will not crash anymore. One other thing is good to remember is that, if you save the E-mail which is crashing the system and view the source you will realize, there are a lot of hidden embedded pictures and code inside the mail. So it is always good idea to double check


Oz Ozugurlu

How to make sure the BlackBerry device has the data service turned on

When performing troubleshooting with a remote user, who has the handheld, it is useful to find out if the data service has been turned on the device. If data service is not turned on, and assumed to be on by client it is almost impossible to move forward, so below is the way to determine if it is on or not.

If the register option won't generate an E-mail back to the Device, this indicates Either Data service is not turned on the device

Or having troubles, either way Service provider need to fix the issue

  • On the device
  • Options
  • Advance option
  • Host Routing table
  • Register now
  • You should  get automatic E-mail registration confirming the registration


This means the data service has been turned on the device, if you are not getting the e-mail, it means data service is NOT turned on; Service provider for the BB (BlackBerry) needs to be contacted



Oz Ozugurlu

Thursday, August 16, 2007

Mail-Box Count Script

Below is a nice script to run against your exchange server and get the count of mailboxes, users and size of the mailboxes. You don't have to know scripting at all to make this work. Follow the steps I am listing below, of course I got it from a coworker.

  • Copy and paste the entire code into notepad
  • Change the server name, into your server name (ServerList = Array("server1", "server2", "server3")
  • Save the file on your Hard drive as mailboxCount.vbs ( c:\ mailboxCount.vbs)
  • Now go to command line
  • Drill down to same directory ( c:\ mailboxCount.vbs)
  • Run the file by typing, c:\ mailboxCount.vbs


Option Explicit

On Error Resume Next

Dim ServerList        ' List of computers to check

Dim server            ' Current computer to check

Dim fso                ' File System Object

Dim strWinMgmts            ' Connection string for WMI

Dim objWMIExchange        ' Exchange Namespace WMI object

Dim listExchange_Mailboxs    ' ExchangeLogons collection

Dim objExchange_Mailbox        ' A single ExchangeLogon WMI object

Dim logfile            ' Output file

Const cWMINameSpace = "root/MicrosoftExchangeV2"

Const cWMIInstance = "Exchange_Mailbox"

Const LOG_FILE = "EMailSize.csv"


' Set up the array of email servers


ServerList = Array("server1", "server2", "server3")


' Set up log file


set fso = CreateObject("Scripting.FileSystemObject")

Set logfile = fso.CreateTextFile(LOG_FILE)

logfile.WriteLine("""Display Name"",""Mailbox Size"",""Mailbox TotalItems"",""Mailbox StoreName"",""Mailbox ServerName""")

' Create the object string, indicating WMI (winmgmts), using the

' current user credentials (impersonationLevel=impersonate),

' on the computer specified in the constant cComputerName, and

' using the CIM namespace for the Exchange provider.

WScript.Echo "Starting now"

'The rest of the script will fetch mailbox sizes for our servers. Mailbox sizes are in Kilobytes.

For Each server in ServerList

    WScript.Echo "Starting " & server & " search."

    strWinMgmts = "winmgmts:{impersonationLevel=impersonate}!//" & server & "/" & cWMINameSpace

    'WScript.Echo strWinMgmts


    Set objWMIExchange = GetObject(strWinMgmts)

    ' Verify we were able to correctly set the object.

    If Err.Number <> 0 Then

        WScript.Echo "ERROR: Unable to connect to the WMI namespace."


        'The Resources that currently exist appear as a list of

        'Exchange_Mailbox instances in the Exchange namespace.

        Set listExchange_Mailboxs = objWMIExchange.InstancesOf(cWMIInstance)

        ' Were any Exchange_Mailbox Instances returned?

        If (listExchange_Mailboxs.count > 0) Then

            ' If yes, do the following:

            ' Iterate through the list of Exchange_Mailbox objects.

            For Each objExchange_Mailbox in listExchange_Mailboxs

                ' Display the value of the Size property.

                logfile.WriteLine("""" & objExchange_Mailbox.MailboxDisplayName & """,""" & objExchange_Mailbox.Size & """,""" & objExchange_Mailbox.TotalItems & """,""" & objExchange_Mailbox.StoreName & """,""" & objExchange_Mailbox.ServerName & """")



            ' If no Exchange_Mailbox instances were returned, display that.

            WScript.Echo "WARNING: No Exchange_Mailbox instances were returned."

        End If

    End If


Wscript.Echo "Completed"


Best Regards

Oz Ozugurlu

Missing Free/Busy information

The solution to this problem is fairly simple, as long as the person is comfortable with ADSIEDIT.MSC. It takes some time to work with this toll to make the changes within the NTDS.DIT database, and needs attention since deleting the whole org would be very easy to achieve, so please be very careful when you get there.



Users are not able to see others Free/Busy information, Group colander is no longer functioning


The Client went through a migration from Exchange 2000 and Exchange 2003. Prior to migration all free/Busy information seems to be working fine, after the migration Client releases the group calendar, is no longer functioning.


The attribute "SiteFolderServer" has the old Server name, and this information need to be updated to a new server follow the article span>284200

You will need ADSIEDIT.MSC installed on the server

The attribute "SiteFolderServer" is located

  • Configuration Container [Computer.Domain.Com]
  • CN=Configuration, DC=(YourDomainController),DC=com
  • CN=Services
  • CN=Microsoft Exchange
  • CN=(YourOrganization)
  • CN=Administrative Groups
  • CN=(YourAdministrativeGroup)

Locate the attribute make sure the name of the server is NOT matching to a current server

Now you need to place the valid Value

Go to

  • Configuration Container [Computer.Domain.Com]
  • CN=Configuration, DC=(YourDomainController),DC=com
  • CN=Services
  • CN=Microsoft Exchange
  • CN=(YourOrganization)
  • CN=Administrative Groups
  • CN=(YourAdministrativeGroup)
  • CN=(Servers)
  • CN=(YourServer)
  • CN=InformationStore
  • CN=First Storage Group

Go to property locate the
distinguishedName, copy it and paste it into , SiteFolderServer properties

Exit out from ADSIEDIT.MSC


Best Regards

Oz ozugurlu