When you try to remove a Exchange 2007 public folder database after a migration to Exchange 2010 you’ll get a “Object is read only because it was created by a future version of Exchange: 0.10 (14.0.100.0). Current supported version is 0.1 (8.0.535.0).” error.
Solution: Run adsiedit.msc goto configuration container CN=Configuration , CN=Services , CN=Microsoft Exchange , CN=First Organisation , CN=Administrative Groups , CN=Exchange Administrative Group (FYDIBOHF23SPDLT) , CN=Servers , CN=EXCHANGE2007SERVER , CN=Information Store , CN=Second Storage Group delete the CN=Public Folder Database.
After someone (accidentally) deleted a exchange public folder in a exchange 2010 organization, you can easy recover the deleted folder using ExFolders. ExFolders is the exchange 2010 replacement of the PFDAVAdmin tool. ExFolders must be run on a exchange 2010 server and it can connect to Exchange 2007 or 2010.
Download the Exchange 2010 RTM ExFolders tool here and the Exchange 2010 SP1 version here.
To recover a exchange 2007 or 2010 public folder start the ExFolders tool. Choose file – Connect and select a Global Catalog and the public folder database where the deleted public folder was on.
Right click public folders and choose “Show deleted subfolders”
After that you will see the deleted public folders in red.
Select the concerning folder, right click and choose “Recover folder”. Recovery starts now just wait depends on the size of the public folder it can take a while.
We were migrating a SBS 2003 server to a new SBS 2008 server via the swing migration method. After turning on the SBS 2008 server and temporary dc / exchange 2003 server we were not able to access or move the exchange 2003 mailboxes.
The mailbox move gives a: “The move-mailbox task for mailbox ‘mailboxname’ failed. Error: Failed to open mailbox with error: The operation failed.” error on the SBS 2008 (Exchange 2007) server.
On the Exchange 2003 server we get a: Event id 1022: “Logon Failure on database “First Storage Group\Mailbox Store” – Windows account domain\accountname; mailbox /o=domain/ou=first administrative group/cn=Recipients/cn=accountname.Error: 1144″ error.
Solution: It looks like that after forklift and update a exchange 2003 database it could take some time to connect because AD has to replicate the information between the 2 domain controllers. When this is done everything works fine. This can also occur after moving the exchange mailboxes to a the new sbs 2008 / exchange 2007 server.
Posted in
Blog,
Exchange 2007,
SBS 2008 at August 17th, 2010.
No Comments.
After installing a exchange 2010 Hub transport server in a exchange 2007 organisation, no mail is send from the exchange 2010 hub to the exchange 2007 hub. When you take a look in the queue viewer on the exchange hub transport server you see the emails stuck with the following error:
“451 4.4.0 Primary target IP address responded with: “451 5.7.3 Cannot achieve Exchange Server authentication.” Attempted failover to alternate host, but that did not succeed. Either there are no alternate hosts, or delivery failed to all alternate hosts”
This error occurs when on the exchange 2007 hub transport server a additional receive connector is created, for instance a anonymous relay connector. The interal exchange connections use Transport Layer Security (TLS) authentication to communicate, this is not selected in the additional receive connector, so communication fails.
Solution: Create a new Internal receive connector, at remote ip addresse give in alle exchange hub transport servers. This creates a receive connector with TLS and Exchange server authentication enabled. On the permission groups tab the exchange servers and legacy exchange servers must be enabled.
Probably the same error can occur otherwise round or when you have more then 1 exchange 2007 of 2010 hub transport servers.
After migrating a Windows SBS 2003 server to a Windows SBS 2008 server no new external (internet) mail is deliverd to the new server. E-mailing internal works fine.
Solution: When you take a look in the Exchange 2007 Server Manager at server configuration, Hub Transport you see only a “Default Servername” receive connector:
Take a look at the properties and then the network tab, you probably see at receive mail from remote servers that have these IP addresses: only the internal ip addresses.
Option 1: You can change this to 0.0.0.0 – 255.255.255.255
Option 2: You can recreate the “Windows SBS Internet Receive Servername” receive connector. Open a Exchange Management Shell and use the following command:
new-receiveconnector -Name “Windows SBS Internet Receive SERVER-NAME” -RemoteIPRanges 0.0.0.0-192.167.255.255,192.168.0.1-192.168.0.1,192.168.1.0-255.255.255.255 -Bindings “192.168.0.2:25” -AuthMechanism “Tls” -PermissionGroups “AnonymousUsers” -Usage “Internet” -Server “SERVER-NAME”
Change the command to your ip address in this example the server ip is 192.168.0.2.
Option 2 is prefferred I’ve seen some strange problems with option 1 do’nt know for sure if this was relelated to this issue but if you can use option 2
Posted in
Blog,
Exchange 2007,
SBS 2008 at July 23rd, 2010.
No Comments.
After you attach a Exchange 2010 Client Access role server to a Exchange 2007 environment you get an “An IIS directory entry couldn’t be created. The error message is Access is denied. HResult = -2147024891 It was running the command ‘Get-OwaVirtualDirectory’.” when you go to Server Configuration, Client Access in Exchange 2010 management console.
Solution: Because Exchange 2010 tries to read some information from the Exchange 2007 server, you have to add the “Exchange Trusted Subsystem” security group to the “local admin” group on all Exchange 2007 servers.
Posted in
Blog,
Exchange 2010 at July 17th, 2010.
No Comments.
