Archive for category Exchange 2007 and older

Exchange Schema Versions

http://social.technet.microsoft.com/wiki/contents/articles/2772.exchange-schema-versions-common-questions-answers.aspx

Exchange Version Forest rangeUpper   attribute of ms-Exch-Schema-Version-Pt Forest objectVersion attribute of   Organization container Domain objectVersion attribute on   Microsoft Exchange System Objects
Exchange 2000 RTM 4397 4406
Exchange 2000 SP3 4406 4406
Exchange 2003 RTM 6870 6903 6936
Exchange 2003 SP1 6870 6903 6936
Exchange 2003 SP2 6870 6903 6936
Exchange 2007 RTM 10637 10666 10628
Exchange 2007 SP1 11116 11221 11221
Exchange 2007 SP2 14622 11222 11221
Exchange 2007 SP3 14625 11222 11221
Exchange 2010 RTM 14622 12640 12639
Exchange 2010 SP1 14726 13214 13040
Exchange 2010 SP2 14732 14247 13040

Tags:

Nmcap – Automatizzare la cattura del traffico di rete con NMCap

Con network Monitor 3.3 è possibile utilizzare la riga di comando per catturare il traffico su determinate interfacce.

E’ possibile scegliere il tipo di protocollo da catturare, quando iniziare a catturare etc.

Alcuni esempi:

nmcap /network * /capture “(tcp.port == 25)” /file t.chn:100M /stopwhen /timeafter 120min /terminatewhen /keypress x

Nell’esempio di cui sopra NMcap catturerà il traffico relativo a tutte le interfacce (parametro “/network *”) indirizzato alla porta TCP 25  e si fermerà dopo 120 min oppure premendo il tasto “X”. Il comando concatena inoltre i dati catturati in N file t(1).chn e t(2).chn, ognuno di 100MB fino al termine previsto per la cattura (su questo punto vi consiglio di prestare particolare attenzione al esaurimento dello spazio disco a disposizione). Ricordo che per default, per fermare la cattura, è semplicemente necessario utilizzare Ctrl+C o Ctrl+Break. Procediamo con un passo indietro e un esempio più semplice:

nmcap /network * /capture /file test.cap

Il comando di cui sopra cattura il traffico su tutte le interfacce salvando i dati nel file test.cap (cattura circolare per un file con dimensione massima pari ai 20MB di default). Un altro esempio interessante può essere il seguente dove effluiamo la cattura di tutto il traffico escludendo la parte relativa al protocollo RDP (Terminal Services):

nmcap /network * /capture “!(tcp.port == 3389)” /file test.cap

Come anticipato nel primo script è possibile impostare la partenza e lo stop della cattura attraverso gli switch /startwhen e /stopwhen dopo un certo numero di minuti (ad esempio 30) col seguente switch: “/TimeAfter 30 mintues” oppure indicando un orario preciso con lo switch “/Time 10:30:00 am 9/10/2006” (attenzione perché il formato della data/ora dipende dai locale settings impostati) oppure, come ho accennato all’inizio del post, col verificarsi di un determinato evento come nell’esempio di cui sotto dove la cattura terminerà non appena NMCap rileverà i passaggio di un frame dal server locale all’ host con IP 10.20.30.41:

nmcap /network * /capture /file t.cap /stopwhen /frame (ipv4.address == ipconfig.localipv4address) AND (Ipv4.DestinationAddress == 10.20.30.41)

Come ho accennato prima è possibile concatenare i file di output della cattura specificando l’estensione “.chn” e la dimensione massima per ogni file (che consiglio di mantenere al di sotto di 100-200MB al fine di non ritrovarsi a gestire file di dimensioni troppo ampie). Per cui, utilizzando ad esempio lo switch “/file t.chn:1M” verranno creati dei file chiamati files t(1).chn, t(2).chn, ecc. ognuno con dimensione pari ad 1MB.

Relativamente alla salvaguardia dello spazio a disposizione sarà possibile indicare anche una condizione alternativa di stop della trace basata sulla percentuale di spazio libero su disco come nell’esempio di cui sotto dove, al raggiungimento del 5% di spazio libero residuo, la cattura terminerà automaticamente:

nmcap /network * /capture /file result.cap /MinDiskQuotaPercentage 5

Tags: ,

Exchange 2007 CAS cannot copy the OAB from the OAB share on Windows Server 2008-based Exchange 2007 CCR clusters

Exchange 2007 CAS cannot copy the OAB from the OAB share on Windows Server 2008-based Exchange 2007 CCR clusters

 

Microsoft Exchange Server 2007 Client Access Servers (CAS) cannot copy the offline address book (OAB) from the OAB share on Windows Server 2008-based Exchange 2007 Cluster Continuous Replication (CCR) clusters. The result of this situation is that OAB data on CAS servers may be stale. Or, you may be unable to download the offline address list because it is unavailable. Additionally, the following event is logged on the CAS server:

Source: MSExchangeFDS
Event ID: 1021
Task Category: General
Level: Warning
Keywords: Classic
Description:
Process MSExchangeFDS.exe (PID=xxxx). Could not find directory <OAB share location> This is normal if the directory has never been generated. Otherwise, make sure this directory and share has read permission for the “Exchange Servers” group.

 

CAUSE:

This problem occurs because Windows Server 2008 clustering introduces the concept of share scoping. In share scoping, a file share is specific to either the node name or to one of the cluster name objects that the share hosts. In this case, if the share is shared by the node name, it cannot be accessed by the Clustered Mailbox Server (CMS) name.

 

RESOLUTION:

Download and install Update Rollup 5 for Exchange 2007 Service Pack 1. For more information about Update Rollup 5 for Exchange Server 2007 Service Pack 1, see the following Exchange Help topic:

Applying Exchange 2007 Update Rollups to Clustered Mailbox Servers

Tags: , , ,

Exchange 2007 Offline Address Book (OAB) keeps asking for authentication

If you are getting a constant authentication box pop up for your users when outlook is trying to connect to the Offline Address book, then read on, I am sure this will help you:

First thing is first make sure you have a vaild OAB

1. open Exchange Management console

2. open organization Configuration > Go to mailbox > choose Offline address book tab.

3. Make sure you have at least one address book here if not create one.

4. Right click on the address book go to properties > distribution Tab . ensure all boxes are ticked. > click on the ADD here you need to locate the appropriate server. > hit Ok.

5. You should be back to the OAB listings, if you have more then one that’s fine leave them for the time being, but choose the one you would like to be the default OAB and right click on it and choose ’set as default’

6. Now we need to update this OAB, right click on the default OAB you have created and then choose ‘update’

7. to ensure that the OAB has updated go to the event viewer and check the application log.

If you get a successful update great move on to step 9

if you get a warning with this event log below:

Log Name:      Application
Source:        MSExchangeSA
Date:          3/03/2009 9:10:24 AM
Event ID:      9320
Task Category: OAL Generator
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      server.domain.com.au
Description:
OALGen could not generate full details for some entries in the offline address list for address list ‘\Global Address List’.  To see which entries are affected, event logging for the offline address list generator must be set to at least medium.
– xxxxxxx Offline Address Book
Event Xml:
<Event xmlns=”
http://schemas.microsoft.com/win/2004/08/events/event”>
  <System>
    <Provider Name=”MSExchangeSA” />
    <EventID Qualifiers=”32768″>9320</EventID>
    <Level>3</Level>
    <Task>13</Task>
    <Keywords>0×80000000000000</Keywords>
    <TimeCreated SystemTime=”2009-03-02T22:10:24.000Z” />
    <EventRecordID>14197</EventRecordID>
    <Channel>Application</Channel>
    <Computer>server.domain.com.au</Computer>
    <Security />
  </System>
  <EventData>
    <Data>\Global Address List</Data>
    <Data>xxxxxx Offline Address Book</Data>
  </EventData>
</Event>

You need to set the event logging a little higher to do this open up the exchange powershell console and run the below command:

Set-EventLogLevel -Identity “MSExchangeSA\OAL Generator” -Level Expert

Now repeat step 7

you should now have some errors

event ID: 9330 MSExchangeSA

OALGen encountered error 80040115 (internal ID 50004ef) accessing Active Directory servername for ”.
– /o=Elcom Technology Pty Ltd/cn=addrlists/cn=oabs/cn=xxxxxx Offline Address Book

and

Event ID 9334 MSExchangeSA

OALGen encountered error 80040115 while initializing the offline address list generation process. No offline address lists have been generated. Please check the event log for more information.
– /o=Elcom Technology Pty Ltd/cn=addrlists/cn=oabs/cn=xxxxx Offline Address Book

8. If these are the same kind of errors you must open ADSIedit (only included in the support package supplied by micorosft)

once you have installed the support tools

start > run > adsiedit.msc

go to

Using ADSIEdit:
1. Navigate to the ‘Default Global Address List’ object
CN=Default Global Address List,CN=All Global Address Lists,CN=Address Lists Container,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Domain,DC=local
2. Go to the properties of the ‘Default Global Address List’ object
3. Copy the distinguishedName attribute of the ‘Default Global Address List’.
It should look similar to the one below.
CN=Default Global Address List,CN=All Global Address Lists,CN=Address Lists Container,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Domain,DC=local
4. Navigate to the ‘Microsoft Exchange’ container.
CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Domain,DC=local
5. Go to properties of the ‘Microsoft Exchange’ container
6. Select the GlobalAddressList attribute and click Edit.
7. Paste in the distinguishedName attribute of the ‘Default Global Address List’ and click Add
8. Click OK twice to close out of the properties.
9. Replicate domain controllers
10. Rebuild the OAB again

above taken from http://forums.msexchange.org/m_1800488370/tm.htm

9. Check your permissions on your OAB go to c:\Program Files\Microsoft\Exchange Server\Client Access\OAB\ find the correct GUID that related to your OAB, right click on the GUID and then go to the security tab. Ensure that administrators and system have full control and authenticated users have only read access. (leave the other permissions)

—- you can use this command to find out

get-offlineaddressbook | fl > c:\OAB_Version.txt

10. Ensure that the OAB has populated with an XML file you can find this in :\Program Files\Microsoft\Exchange Server\Client Access\OAB\GUID_here\oab.XML.

If you have not got an XML file the OAB has not populated revist your event viewer.

11. Now in IIS you should have an OAB virtual directory if you do not you must create this use the below

New-OABVirtualDirectory -DomainController <Fqdn> -ExternalUrl <Url> -InternalUrl <Url> -Path <String> -PollInterval <Int32> -RequireSSL <$true | $false> -Server <ServerIdParameter> -WebSiteName <String>

more info here: http://technet.microsoft.com/en-us/library/aa996917.aspx

If you do already have the virtual directory Change that virtual directory to an application.

Exchange 2007 – “Update Address Lists” (Update Legacy Email Address Policies and Address Lists)

After you removed the last Exchange 2003 Server and you only have Exchange 2007 Exchange 2003 Servers, it’s time to upgrade the following from legacy to “native” Exchange 2007 :

  • Recipient Policy (email address policy)
  • Address Lists
  • Global Address Lists

When you open the Exchange Management Console and try to edit an email address policy, you get an error saying :

“Unable to edit the specified E-mail address policy. E-mail address policies
created with legacy versions of Exchange must be upgraded using the
‘Set-EmailAddressPolicy’ task, with the Exchange 2007 Recipient Filter
specified.”

To update the default email address policy use the following command :

Set-EmailAddressPolicy “Default Policy” -IncludedRecipients AllRecipients

After you’ve updated the default policy, update all non-default policies. Here an example of an email address policy where users with mailboxes AND where the company name is filled with Microsoft need to be applied :

Set-EmailAddressPolicy “Sample Policy” -RecipientFilter { ((RecipientType –eq ‘MailboxUser’) –and (Company –eq ‘Microsoft’)) }

Now update all the address lists and the global address list(s). The following address lists are present by default :

  • All Users
  • All Groups
  • All Contacts
  • Public Folders
  • All Rooms

The Address list “All Rooms” is the only one created by Exchange 2007, so this one doesn’t have to be upgraded. For all the others type in the powershell :

Set-AddressList “All Users” -IncludedRecipients MailboxUsers
Set-AddressList “All Groups” -IncludedRecipients MailGroups
Set-AddressList “All Contacts” -IncludedRecipients MailContacts
Set-AddressList “Public Folders” -RecipientFilter { RecipientType -eq ‘PublicFolder’ }

 

The last step is to update the Default Global Address List. This can be done by typing the following in the powershell :

Set-GlobalAddressList “Default Global Address List” -RecipientFilter {(Alias -ne $null -and (ObjectClass -eq ‘user’ -or ObjectClass -eq ‘contact’ -or ObjectClass -eq ‘msExchSystemMailbox’ -or ObjectClass -eq ‘msExchDynamicDistributionList’ -or ObjectClass -eq ‘group’ -or ObjectClass -eq ‘publicFolder’))}

 

After you have upgraded all your policies and address lists check if everything can be opened by the Exchange Management Console. Another way of checking if everything is upgraded, can be done by :

-Get-AddressList | Format-List Name,*RecipientFilter*,ExchangeVersion

    -Get-GlobalAddressList | Format-List Name,*RecipientFilter*,ExchangeVersion

    -Get-EmailAddressPolicy | where {$_.RecipientFilterType -eq “Legacy”}

    The Exchange version will be “0.1 (8.0.535.0)”. The old ExchangeVersion was “0.0 (6.5.6500.0)”

    Outlook “Offline Address Book” ERROR 0x80190197 or 0x8019194

    When you try to download the OAB from Outlook you may receive the following errors:

    0x80190197

    or

    0x80190194

    There are several reasons for this, see the following articles:

    http://technet.microsoft.com/en-us/library/dd285503(EXCHG.80).aspx

    http://blogs.msdn.com/dgoldman/archive/2006/11/27/Error-0x80190194-when-using-an-outlook-2007-client-to-download-a-web-distribution-enabled-oab.aspx

    http://blogs.msdn.com/dgoldman/archive/2006/08/26/725860.aspx

    Tags: ,

    Exchange 2007 – \NON_IPM_SUBTREE replication – Outlook Client ERROR 0x8004010F

    Task ‘Microsoft Exchange Server’ reported error (0x8004010F): ‘The operation failed. An object could not be found.’

    This could be caused by PF Replication NOT OCCURRING.

    Type the following command in Exchange Shell (it’s one command all on one line):

    [PS]>set-publicfolder -Identity “\NON_IPM_SUBT
    REE\OFFLINE ADDRESS BOOK\/o=YOUR EXCHANGE ORG NAME/cn=addrlists/cn=oabs/cn=Default Offlin
    e Address List” -replicas “Exch2003 Server Name\First Storage Group\Public Folder Store (Server Name)”

    if you don’t know the proper name just run the following command:

    [PS]>Get-PublicFolderDatabase -IncludePreExchange2007
    or
    [PS]>Get-PublicFolderDatabase -identity Exch2003ServerName
     
     
    To view that you have enabled Replicas run the following:
    [PS]>set-publicfolder -Identity “\NON_IPM_SUBT
    REE\OFFLINE ADDRESS BOOK\/o=YOUR EXCHANGE ORG NAME/cn=addrlists/cn=oabs/cn=Default Offline Address List”
    Result:
    AgeLimit
    EntryIdHasSubFolders
    HiddenFromAddressListsEnabled
    LocalReplicaAgeLimit
    MailEnabled
    MaxItemSize
    NameParentPath
    PerUserReadStateEnabled
    PostStorageQuota
    Replicas              : {Public Folder Store (Exch2003SrvName)}
    ReplicationSchedule
    RetainDeletedItemsFor
    StorageQuota
    UseDatabaseAgeDefaults
    UseDatabaseQuotaDefaults
    UseDatabaseReplicationSchedule
    UseDatabaseRetentionDefaults
    Identity
    IsValid
    OriginatingServer

    Tags:

    Exchange 2007 – Move-Mailbox from file (bulk)

    1. Create a text file under C: named userlist.txt.
    2. From ADUC get the list of users you want to migrate.
    3. Select an OU, from View menu/add-column select EXCHANGE ALIAS and E-MAIL ADDRESS; sort the list by E-mail address so to be sure they have a mailbox.
    4. Click on button EXPORT LIST so you will have a TXT file.
    5. Copy the column ALIAS into userlist.txt file perviously created. They must be in a list each one on its own line separated by RETURN

    Now create a file named Move-mailbox.ps1 and copy the following code into it:

    $TargetDatabase = “Basic1DB”
    $SourceFile = “c:\userlist.txt”
    $a = remove-item c:\Movelog.txt -ea SilentlyContinue
    $error.Clear()
    $UserList = Get-Content $SourceFile
    foreach($user in $UserList)
    {
    $message = “Moving User -> ” + $user
    write-output $message | out-file -filePath “c:\MoveLog.txt” -append -noClobber
    move-mailbox -Identity $user -TargetDatabase $TargetDatabase -BadItemLimit 5 -PreserveMailboxSizeLimit:$true -Confirm: $false
    if($error.Count -ne 0)
    {
    $message = “User ” + $user + ” failed to move ???????????”
    write-output $message | out-file -filePath “c:\MoveLog.txt” -append -noClobber
    $message = “Error:::: ” + $error[0].ToString()
    write-output $message | out-file -filePath “c:\MoveLog.txt” -append -noClobber
    $error.Clear()
    }
    }

    ————————————————————————————-

    $TARGETDATABASE –> this is the database where you want to move the mailbox (destination database)

    $SOURCEFILE –> The file with the list of ALIASES

    C:\Movelog.txt –> Log file

    ————————————————————————————-

    Copy this file under c:\program Files\Microsoft\Exchange Server\Scripts.

    Open Exchange Shell and launch the file. This will move the users mailbox listed in userlist.txt file, and you’ll get a log file under C:\Movelog.txt

    Tags:

    Exchange 2007-2010 get version

    The only way is to get the correct version is to check the version on file EXSETUP.EXE under the Bin Folder

      This is Exchange 2010 RollUp1

     This is Exchange 2010

    or via shell:  
    GCM exsetup |%{$_.Fileversioninfo}
    —————————————————————–
    Get-Exchangeserver -Identity MyExchangeServer –> doesn’t show updates or rollups
    —————————————————————–
    HKLM\SOFTWARE\Microsoft\v8.0\<Role>\ConfiguredVersion
    —————————————————————–
    CHECK VERSIONS:
    here
    http://technet.microsoft.com/en-us/library/bb232170(EXCHG.80).aspx
    and here
    http://support.microsoft.com/default.aspx/kb/158530?p=1 

    Tags:

    ESE Database Cache Size in Exchange 2007

    In Microsoft Exchange Server 2007, the maximum size of the Extensible Storage Engine (ESE) database cache is not set by default. As a result, the amount of physical memory that is used by the Exchange store can be much greater than in previous versions of Exchange. The increased size of the database cache, which significantly improves performance, is made possible by the 64-bit architecture in Exchange 2007.

    This topic explains the differences between database caches in Exchange Server 2003 and Exchange 2007. Also, although it is not recommended, you can use the procedure later in this topic to set the maximum size of the ESE database cache.

     Database Cache Size in Exchange 2003

    Exchange 2003 runs on a 32-bit operating system, which limits the maximum size of the virtual address space to 4 gigabytes (GB). The operating system leaves only 2 GB of addressable RAM for a single application such as Exchange (or 3 GB when the /3GB switch is set in the Exchange boot.ini file). With such a limited amount of addressable RAM available, the size of the database cache must be carefully managed to allow Exchange to perform at its highest level. 

     Database Cache Size in Exchange 2007

    A large database cache greatly increases performance because disk input/output (I/O) is reduced and the ability to read information from memory is much faster than having to read information from a disk.

    With the 64-bit architecture in Exchange 2007, the maximum size of the database cache is no longer constrained by limits on the virtual address space. Instead, it is determined by the amount of available memory and by database I/O. For example, on a server that has 16 GB of physical RAM, ESE may increase the database cache to 8 GB if this amount is sufficient to meet its memory needs, and leave the remaining memory for system cache and other applications that are running on the server. 

    Because the maximum size of the database cache is not set by default, ESE can increase the size of the database cache to consume almost all available RAM on the server if there is enough database I/O pressure to justify the increase. If other applications or the Windows Server system cache request or require memory, ESE decreases the size of the database cache as required. ESE does not increase the size of the cache unless there is enough database I/O pressure to justify the growth. The default minimum database cache size for Exchange 2007 is 512 megabytes (MB) on servers that have at least 2 GB of RAM.

     Setting the Maximum Size of the Database Cache

    You can use Active Directory Service Interfaces (ADSI) Edit to set the maximum size of the database cache

    IMPORTANT:

    We do not recommend setting a maximum size for the database cache. The maximum database cache size should not be lower than the minimum recommended amount of physical RAM. If you must reduce the maximum database cache to below the recommended levels, you should simultaneously reduce the number of storage groups on the server. For more information, see “Recommended Maximum Memory Configuration for Mailbox Servers” in Planning Memory Configurations.

    The msExchESEParamCacheSizeMax parameter specifies the size of the database cache in 8-kilobyte pages.

    To set the maximum size of the database cache in Exchange 2007

    1. Start ADSI Edit. (Click Start, click Run, and then type adsiedit.msc.)
    2. In ADSI Edit, from the Action menu, click Connect to.
    3. In Connection Settings, under Connection Point, click Select a well known Naming Context, and then select Configuration from the corresponding list.
    4. Under Computer, click Select or type a domain or server, and then in the corresponding box, select or type the name of your domain controller.
    5. Click Advanced.
    6. In Advanced, select Specify Credentials, and then type your user name and password in the corresponding boxes.
    7. In the Port Number box, type 389.
    8. Under Protocol, click LDAP.
    9. Click OK to close the Advanced dialog box.
    10. Click OK to close the Connection Settings dialog box.
    11. In ADSI Edit, you are connected to the Configuration container of your domain controller.
    12. Navigate to the following object: Configuration/Services/Microsoft Exchange/<Your Organization>/Administrative Groups/<Your Administrative Group>/Servers/<Server Name>/Information Store.
    13. Right-click Information Store, and then click Properties.
    14. On the Attribute Editor tab, click msExchESEParamCacheSizeMax, and then click Edit.
    15. In Integer Attribute Editor, type the maximum size of the database cache, specified as the number of 8-kilobyte pages, and then click OK.For example, to set the database cache size to 14 GB, divide 14 GB (14,680,064 KB) by 8 to get a value of 1,835,008 8-KB pages. In the Integer Attribute Editor dialog box, type this value without using commas or periods.
    16. Click OK to close Information Store Properties.
    17. Close ADSI Edit, and then restart the Microsoft Exchange Information Store service.

    Exchange 2007 console – NEW MAILBOX with NEW USER…..ADUC Permissions “inetOrgPerson”

    In Exchange 2007, when creating a New Mailbox from the “Exchange 2007 console” because there’s no integration with ADUC like it was in previous versions, a Recipient Admin or Helpdesk operator isn’t able to create a New Mailbox for a New User because she/he have no permissions to create objects in Active Directory .
    For example, if you have helpdesk operators that need to create NEW MAILBOXES associated with NEW USERS, they will need additional permissions on Active Directory objects.
    These permissions are “inetOrgPerson“.
    You can delegate control on Domain or specific OUs and grant the user “Create, Delete and manage inetOrgPerson accounts“,
    or
    You can add them directly from the Security TAB and in Advanced you can select the user or group and give “Create inetOrgPerson objects” and “Delete inetOrgPerson objects
    In this way you have the correct and least permissions to create a New Mailbox with a New User directly from Exchange mmc console.

    Tags: ,

    Exchange 2007 Message Classification

    http://www.exchange-genie.com/2007/12/exchange-2007-message-classification/

    How to add a disclaimer to outgoing SMTP messages in Visual Basic script

    http://support.microsoft.com/kb/317680/en-us

    In Exchange Server 2003 or in Exchange 2000 Server, the Exchange Server queues are filled with many non-delivery reports from the postmaster account because of a reverse non-delivery report attack

    http://support.microsoft.com/kb/909005/en-us

    Tags: ,

    How to reset the default virtual directories that are required to provide Outlook Web Access, Exchange ActiveSync, and Outlook Mobile Access services in Exchange Server 2003

    http://support.microsoft.com/kb/883380/en-us

    Tags:

    Fine-tuning and known issues when you use the Urlscan utility in an Exchange 2003 environment

    http://support.microsoft.com/kb/823175/en-us

    Sender ID Framework SPF Record Wizard

    http://www.microsoft.com/mscorp/safety/content/technologies/senderid/wizard/default.aspx

    “Unable to Load Free/Busy Information” Error Message When You Try to Use Meeting Planner in Outlook 2003

    Outlook 2003

    To resolve this behavior, run Outlook on the computer that is experiencing problems publishing Free/Busy information with the /CleanFreeBusy command-line switch. This will refresh the Free/Busy information. To do so, follow these steps:

    1. Click Start, and then click Run.
    2. In the Open box, type “outlook.exe /cleanfreebusy”, and then click OK.
    3. View the published information from another computer.

    Tags:

    How to Change the IP Address of an Exchange Virtual Server

    http://technet.microsoft.com/en-us/library/aa997813(EXCHG.65).aspx

    Tags:

    How to delay mail processing to allow mail to be scanned by anti-virus or anti-spam before being delivered to the BlackBerry smartphone

    Environment
    • BlackBerry® Enterprise Server for Microsoft® Exchange® version 2.1 to 4.1
    Warning: The following procedure involves modifying the computer registry.  This can cause substantial damage to the Windows® operating system.  Document and back up the registry entries prior to implementing any changes.

    Overview
    Administrators can configure the BlackBerry Enterprise Server to delay mail processing in order to allow time for anti-virus or anti-spam software to scan messages.
    To delay mail processing, complete the following steps:
    1. In the Registry Editor, go to one of the following locations: 

      For BlackBerry Enterprise Server version 2.1 and earlier:

      HKEY_LOCAL_MACHINE\Software\Research In Motion\BlackBerry\Server

      For BlackBerry Enterprise Server version 3.5 to 3.6:

      HKEY_LOCAL_MACHINE\Software\Research In Motion\BlackBerry\Servers\<BlackBerry_Enterprise_Server_name>

      For BlackBerry Enterprise Server version 4.0 to 4.1:

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

    2. If the ProcessMailDelay registry entry already exists, change the Value data field to the number of seconds you would like mail processing to be delayed. If the ProcessMailDelay registry entry does not exist, create a registry entry with the following values:  

      Name
      Type
      Value
      ProcessMailDelay
      DWORD
      This value specifies the number of seconds to delay mail processing. For example, a value of 5 delays mail processing for 5 seconds.
       
    3. Restart the BlackBerry Dispatcher and BlackBerry Controller.
    Important: Restarting certain BlackBerry Enterprise Server services will delay message delivery to BlackBerry devices. See article KB04789 for more information.