Showing posts with label Exchange 2007. Show all posts

Microsoft has released Service Pack 3 for Exchange Server 2010 and Update RollUp 10 for Exchange Server 2007 SP3 today.

These updates will make your existing Exchange 2010 and 2007 environment to coexist with Exchange Server 2013.
Exchange Server 2010:
Microsoft Exchange Server 2010 Service Pack 3
http://www.microsoft.com/en-us/download/details.aspx?id=36768

Issues that the service pack resolves
http://support.microsoft.com/kb/2808208

Exchange Server 2007:
Update Rollup 10 for Exchange Server 2007 Service Pack 3
http://www.microsoft.com/en-us/download/details.aspx?id=36708

Issue that the update rollup resolves
http://support.microsoft.com/kb/2788321

Note: Microsoft also released Update Rollup 6 for Exchange Server 2010 SP2.
Update Rollup 6 for Exchange Server 2010 Service Pack 2
http://www.microsoft.com/en-us/download/details.aspx?id=36716

Issue that the update rollup resolves
http://support.microsoft.com/?kbid=2746164

I would strongly suggest not to install SP3 for Exchange 2010 right now, instead play around with RU6 in the LAB first and then install it in the production. Do the same for SP3 as well.
Install the SP3 after enough testing in the LAB.

We all have been waiting for these release since few months and finally Microsoft has delivered it. Now, this is were the FUN begins.

Update: 15-02-2013
We still can't coexist exchange server 2010 SP3 with Exchange Server 2013 entirely. Cumulative update (CU) is required for Exchange 2013 for coexistence between Exchange 2010 SP3 and Exchange 2013. The change to the cumulative update model, from the past rollup update model, was just announced last Friday.

We should expect the CU for Exchange Server 2013 in the month of April or late March. Let's keep the finger cross.

When you run the command Get-Mailbox, it throws the warning on DiscoverySearchMailbox.




















WARNING: Object exchangeranger.in/Users/DiscoverySearchMailbox {D919BA05-46A6-415f-80AD-7E09334BB852} has been corrupted and it is in an inconsistent state. The followng validation error has occurred:WARNING: The value of property 'RecipientTypeDetails', 536870912, is not defined in the Enum type 'RecipientTypeDetails'.

Check the Adsiedit.msc --->Domain Context (Domain Partition)--->Users--->DiscoverySearchMailbox, go to the properties and locate the attribute msExchRecipientTypeDetails.


























As we know, DiscoverySearchMailbox is User Mailbox, hence for Object Type for User Mailbox, the decimal value should be 1. In this issue the decimal value is 536870912.

I checked the same attribute on my mailbox and found that, the decimal value is set to 1, which is correct.


























Change the decimal value 536870912 to 1 on DiscoverySearchMailbox by going at the location Adsiedit.msc --->Domain Context (Domain Partition)--->Users--->DiscoverySearchMailbox, go to the properties and locate the attribute msExchRecipientTypeDetails
















































Once you set the decimal value to 1, run the command Get-Mailbox and you should get the below result.




















Here is the list of Object Type with there decimal values in exchange server.

































Note: If you don't fix this warning and ignore it, DiscoverySearchMailbox feature won't work.

Cheers,

	BinaryTree
	Quest Migration Tool
	Other

There are many articles available on running BETest, I thought of writing my own article with experience I had running BETest.

The version of BETest that is used here is located in the VSS SDK, which can be
Downloaded from the following location
http://www.microsoft.com/downloads/details.aspx?FamilyID=0B4F56E4-0CCC-4626-826A-ED2C4C95C871&displaylang=en
The current version of the VSS SDK is 7.2

After installing the VSS SDK, you will then find BETest in the following directory.
%Program Files%\Microsoft\VSSSDK72\TestApps\betest\obj\x64 (or i386). There are separate versions of Betest for x64, and i386.
Make sure to run the version that corresponds to the OS build that you have (x64 or x86).

The next step to using Betest is to build your input file. Most documentation refers to it as components.txt, but it can be called whatever you want. The contents are what is important. The information required in the components.txt file is as follows:

"<writer-id>": "<component-logical-path>";

The first step in building your components.txt file is to determine the writer ID. Fortunately, the Exchange Writer ID does not change.
That ID will be as follows.

"{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}":

This information can be confirmed by running the following command from a command prompt.

vssadmin list writers
Writer name: 'Microsoft Exchange Writer'
Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
Writer Instance Id: {9ba5818d-b602-4486-b014-9c667a9a8916}
State: [1] Stable
Last error: No error

You now have the Exchange Writer ID, which makes up the first half of the input file. The second part of the file is the logical path. This is the path to the GUID of the Storage Group that you want to back up. This requires you to find out what the GUID of the storage groups are. Fortunately, with Exchange 2007, this is easily done using PowerShell. Simply run the below command.

Get-StorageGroup -server <servername> | fl name, guid

Name: First Storage Group
Guid: aaecdeb8-7891-4fca-ade8-a1a3c0bf97f8

Name: Second Storage Group
Guid: 32fca98d-e58c-42dd-b2d2-a0982a3ff480

Name: Third Storage Group
Guid: e28a4919-79fa-4741-b76d-b780d5578460

Standalone
"{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}": "Microsoft Exchange Server\Microsoft Information Store\<SERVERNAME>\aaecdeb8-7891-4fca-ade8-a1a3c0bf97f8";

CCR system input file
"{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}": "Microsoft Exchange Server\Microsoft Information Store\<SERVERNAME>\<GUID of SG>"

You are now ready to run the BEtest command. Note that the switches included with the command are case sensitive

BETEST.exe /B /E /T 1 /S output.xml /C components.txt /D c:\backup

The backup should now start, and you will see output on the screen similar to the following.
Asked to do backup only
Asked to exclude BETEST test writer
Backup-type to use is 1
File name to save/load Backup Document is "output.xml"
File name for Components Selection is "sg1active.txt"
Directory to save/restore backup files is "c:\backup\"

Conclusion:
BETest is a utility to test Exchange Writer. If BETest is successful, and leaves the Exchange Writer in a STABLE state (observed from the output), then the you needs to be referred to your backup vendor for further troubleshooting of their application. Prior to testing with BETest, ensure that you have the most recent Windows VSS hotfixes/updates applied.

Note: This article applies to Exchange Server 2007 running on Windows Server 2003 only. Refer to my previous blog for running BETest on Windows Server 2008.

Cheers,

Download Update Rollup 6

I was working on Exchange 2007 SP1 to upgrade it to SP3. I upgraded the server with SP3 without any issue and restarted the server. After the restart i found that MS Exchange Information Store service is not started. I tried to start it manually but it failed with event id 5000.
As per the support article http://support.microsoft.com/kb/944752 but in my case it wasn't the issue.

Mailbox Server Role:

Here you will find all commands what would help you to recreate all Virtual Directories for Exchange 2007. You can also use just a few of them. But never delete or create it in IIS. This has to be done under Exchange Management Shell

First you shall write down the information what you will get (for example: if it "Default Web Site" or "SBS Web Applications" and if they have the information, what InternalURL or External URL is configured):

- Open Exchange Management Shell with elevated permission
- Run the following commands:

Get-AutodiscoverVirtualDirectory
Get-OABVirtualDirectory
Get-OWAVirtualDirectory
Get-WebServicesVirtualDirectory
Get-ActiveSyncVirtualDirectory
Get-UMVirtualDirectory

Then you can remove the Virtual Directories but change the ####### to the information you got earlier

Remove-OWAVirtualDirectory -Identity "Owa (#######)" -Confirm:$false
Remove-OWAVirtualDirectory -Identity "Exadmin (#######)" -Confirm:$false
Remove-OWAVirtualDirectory -Identity "Exchange (#######)" -Confirm:$false
Remove-OWAVirtualDirectory -Identity "Exchweb (#######)" -Confirm:$false
Remove-OWAVirtualDirectory -Identity "Public (#######)" -Confirm:$false
Remove-WebServicesVirtualDirectory -Identity "EWS (#######)" -Confirm:$false
Remove-ActiveSyncVirtualDirectory -Identity "Microsoft-Server-ActiveSync (#######)" -Confirm:$false
Remove-OabVirtualDirectory -Identity "OAB (#######)" -Force:$true -Confirm:$false
Remove-UMVirtualDirectory -Identity "UnifiedMessaging (#######)" -Confirm:$false
Remove-AutodiscoverVirtualDirectory -Identity "Autodiscover (#######)" -Confirm:$false

To verify that the directories have been removed, run the following commands. You should receive no output:

Get-AutodiscoverVirtualDirectory
Get-OABVirtualDirectory
Get-OWAVirtualDirectory
Get-WebServicesVirtualDirectory
Get-ActiveSyncVirtualDirectory
Get-UMVirtualDirectory

To properly create these virtual directories, run the following commands (Please keep the information what you got earlier for ####### and change it here to):

- Open Exchange Management Shell with elevated permission
- Run the following commands:

New-OWAVirtualDirectory -WebsiteName "#######" -OwaVersion "Exchange2007"
-ExternalAuthenticationMethods Fba

Set-OWAVirtualDirectory -InternalUrl "https://INTERNAL_FQDN_OF_EXCHANGE/owa/"
-ClientAuthCleanupLevel "Low" -LogonFormat "UserName" -DefaultDomain “NetBiosDomainName”
-Identity "Owa (#######)"

New-OWAVirtualDirectory -WebsiteName "#######" -OwaVersion "Exchange2003or2000"
-VirtualDirectoryType "Exadmin" -ExternalAuthenticationMethods Fba

New-OWAVirtualDirectory -WebsiteName "#######" -OwaVersion "Exchange2003or2000"
-VirtualDirectoryType "Mailboxes" -ExternalAuthenticationMethods Fba

New-OWAVirtualDirectory -WebsiteName "#######" -OwaVersion "Exchange2003or2000"
-VirtualDirectoryType "Exchweb" -ExternalAuthenticationMethods Fba

New-OWAVirtualDirectory -WebsiteName "#######" -OwaVersion "Exchange2003or2000"
-VirtualDirectoryType "PublicFolders" -ExternalAuthenticationMethods Fba

New-WebServicesVirtualDirectory -WebsiteName "#######"
-InternalUrl "https://Internal_FQDN_OF_EXCHANGE/EWS/Exchange.asmx" -basicauthentication 1
-windowsauthentication 1

New-ActiveSyncVirtualDirectory -WebsiteName "#######"
-InternalUrl "https://Internal_FQDN_OF_EXCHANGE/Microsoft-Server-ActiveSync"
-ExternalAuthenticationMethods Basic -InternalAuthenticationMethods Basic

New-OabVirtualDirectory -WebsiteName "#######" -InternalUrl "https://INTERNAL_FQDN_OF_EXCHANGE/OAB"

Set-OabVirtualDirectory -PollInterval "30" -Identity "oab (#######)"

New-UMVirtualDirectory -WebsiteName "#######" -InternalUrl "https://Internal_FQDN_OF_EXCHANGE/UnifiedMessaging/Service.asmx"

New-AutodiscoverVirtualDirectory -WebsiteName "#######"
-InternalUrl "https://Internal_FQDN_OF_EXCHANGE/Autodiscover/Autodiscover.xml"
-BasicAuthentication 1 -WindowsAuthentication 1

Set-ClientAccessServer -Identity “Servername” -AutoDiscoverServiceInternalUri "https://Internal_FQDN_OF_EXCHANGE2007/Autodiscover/Autodiscover.xml"

Set-OfflineAddressBook "Default Offline Address Book" -VirtualDirectories "Servername\OAB (#######)" -Versions Version2,Version3,Version4)"

- To check if we were successful in creating the virtual directories correctly type in the commands:

Get-AutodiscoverVirtualDirectory
Get-OABVirtualDirectory
Get-OWAVirtualDirectory
Get-WebServicesVirtualDirectory
Get-ActiveSyncVirtualDirectory
Get-UMVirtualDirectory

* Keep in mind if you run -
New-ActiveSyncVirtualDirectory
New-OabVirtualDirectory
New-OWAVirtualDirectory
It will create the Virtual Directories if you are running single server in the environment.

Hi All,

I worked with one of the client last week, they had one strange issue with all of there Mac 2011 outlook clients.

As per the client Outlook 2011 started getting the prompt since last few days and prior to this they were working fine.

Exchange Server 2007 SP2 with latest Rollup Updates.

We recreated the profile and it worked for around 30 minutes and failed again with the error above error message.
As Outlook and OWA was working fine correctly i didn't thought of that it could be anything else. Moved the mailbox into another Mailbox Database and checked the issue, and guess what it worked fine for another 30 minute and got the same popup again.
If i click on No and reopen the client than it works fine for sometime and give the same error message.
We had total three outlook 2011 clients on Mac and rest of them were using Outlook 2007.

Removed the EWS VirtualDirectory and recreated the EWS VirtualDirectory New-WebServicesVirtualDirectory and the issue got resolved.

Cheers,
-Gulab