Configure legacy public folders where user mailboxes are on Exchange 2013 servers
Hello all,
I have mailboxes on an exchange 2013 server than need access to public folders on a 2010 server before I migrate them over. I followed the commands in the TechNet article with the subject "Configure legacy public folders where user mailboxes
are on Exchange 2013 servers" (sorry, I wasn't allowed to insert a link because I wasn't verified?). The problem is when I run the last command of "Set-OrganizationConfig -PublicFoldersEnabled Remote -RemotePublicFolderMailboxes ProxyMailbox1,ProxyMailbox2,ProxyMailbox3"
on the 2013 server, using the mailbox name I had created, it says it cannot be found. Of course I checked and the mailbox exists, is configured properly, and so is the new database. The 2013 EAC also sees the mailbox with no issues.
Can someone tell me why I am getting this error?
Thanks,
Shaibal
Hi Mavis,
Thank you for your response. I am the full domain admin, and check and was part of both groups mentioned above. Also, I have only one 2010 server with public folder, and so the command I am running on the 2013 looks like this: Set-OrganizationConfig
-PublicFoldersEnabled Remote -RemotePublicFolderMailboxes PFMailbox1. I even just created a second user and mailbox using the console instead of the shell, and still no luck.
Below is the error I get:
[PS] C:\Windows\system32>Set-OrganizationConfig -PublicFoldersEnabled Remote -RemotePublicFolderMailboxes PFMailbox2
Couldn't find object "PFMailbox2". Please make sure that it was spelled correctly or specify a different object.
+ CategoryInfo : NotSpecified: (:) [Set-OrganizationConfig], ManagementObjectNotFoundException
+ FullyQualifiedErrorId : [Server=ZOR-EXCHANGE01,RequestId=cc567b2f-34d8-41ba-9261-143223566e06,TimeStamp=3/5/2015
4:36:10 PM] [FailureCategory=Cmdlet-ManagementObjectNotFoundException] 2EF24201,Microsoft.Exchange.Management.Sys
temConfigurationTasks.SetOrganizationConfig
+ PSComputerName : zor-exchange01.zubatkin.lan
Similar Messages
-
Unable to access public folders on Exchange 2007 when user mailbox is on Exchange 2013
Hi
I have coexistence with Exchange 2007 and Exchange 2013. I've moved a mailbox to Exchange 2013 and now cannot view the public folders on Exchange 2007. The error message I get is "could not connect to the public folder server. microsoft exchange is
not available. either there are network problems or the exchange server is down for maintenance."
Mailboxes on Exchange 2007 do not have any problems viewing public folders. I can't migrate users to Exchange 2013 until this issue is resolved.
The IIS permissions to the Public virtual directory on Exchange 2007 is set to Intergrated Windows and Basic authentication.Hi northerly,
I recommend you follow the steps below for troubleshooting:
1. Please run the Get-OutlookAnywhere cmdlet to verify the Outlook Anywhere settings on Exchange Server 2013 Client Access servers.
2. If "ExternalHostName" is set, and "ExternalClientAuthenticationMethod" is Negotiate, change "ExternalClientAuthenticationMethod" to something other than Negotiate.
3. If "InternaClientlAuthenticationMethod" is set to Negotiate, and "InternalRequireSSL" is True, change "InternalClientAuthenticationMethod" to something other than Negotiate, or change "InternalRequireSSL" to False.
What's more, here is a helpful KB for your reference.
Users of Exchange Server 2013 or Exchange Online can't open public folders or shared mailboxes on an Exchange 2010 or Exchange 2007 server
http://support.microsoft.com/kb/2834139/en-us
Hope my clarification is helpful.
If there are any problems, please feel free to let me know.
Best regards,
Amy
Amy Wang
TechNet Community Support -
Enable legacy public folders for Exchange 2013 prior to migration?
We're about ready to migrate to Exchange 2013 from 2010. We have a public folder database on 2010 that users can't see once migrated to 2013. If I run through the commands according to the technet article "Configure legacy public folders where user
mailboxes are on Exchange 2013 servers" (https://technet.microsoft.com/en-us/library/dn690134(v=exchg.150).aspx), will users who's mailboxes are still on Exchange 2010 be able to see these public folders?I know they've made alot of changes recently in how legacy public folders are handled in Exchange 2013 (mostly CU7), but I haven't had to do anything more than just setting the proper public folder database on the Exchange 2013 databases.
That being said, looking over the article you are not doing any moves, and it looks eerily similar to this blog post:
http://blogs.technet.com/b/exchange/archive/2014/11/07/on-premises-legacy-public-folder-coexistence-for-exchange-2013-cumulative-update-7-and-beyond.aspx
So I don't think this would hurt Public Folder access for your users in your legacy environment.
Did you deploy CU7? If so, then do what both articles say. If not try using Set-MailboxDatabase -Identity <2013 db name> -PublicFolderDatabase <PF DB NAME>
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread -
Mailbox migration between two Exchange 2013 servers is horribly slow
Hi,
when migrating mailbox between 2 exchange 2013 servers,it s horribly slow. I have found some articles which describing problems about content indexing and missing AD group. This is not my problem, I have tried solutions but it didn't work. Both exchange
are next to each one, same VLAN, same switch. Just migrating between databases.
When I start batch jobs it is migrating only 1 mailbox at once and speed is really slow (2000 - 3000 mail items per 5 minutes). So mailboxes which have 10GB it's migrating 3 hours. My server is on 1gbps LAN.
I have also checked MsExchangeMailboxReplication.exe.config on both servers:
MaxActiveMovesPerSourceMDB="20"
MaxActiveMovesPerTargetMDB="20"
MaxActiveMovesPerSourceServer="100"
MaxActiveMovesPerTargetServer="100"
MaxTotalRequestsPerMRS="100"
Do you have any idea where to look why only 1 mailbox is migrating at once?
ThanksHello,
For the reason why only 1 mailbox is migrating at once when you start batch jobs, there is no official articles or blog to explain it.
I recommend you check if the speed is slower when you move a smaller mailbox. If the issue doesn't occur, I recommend you set
the AllowLargeItems parameter.
Here are some articles for your reference.
New-MigrationBatch
http://technet.microsoft.com/en-us/library/jj219166(v=exchg.150).aspx
Exchange 2013 Local Mailbox Moves
http://www.msexchange.org/articles-tutorials/exchange-server-2013/mobility-client-access/exchange-2013-local-mailbox-moves-part1.html
If you have any feedback on our support, please click
here
Cara Chen
TechNet Community Support -
Error 1006 - Changing Ad Site for subnet where exchange 2013 servers was setup
We wanted to change Ad site for subnet where exchange 2013 servers was setup.
When we do that error id 1006 appear on 2 MBX Servers :
The Microsoft Exchange Mailbox Replication service was unable to process jobs in a mailbox database.
Database: Database02
Error: An attempt to logon cross-site for Mdb 'xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx' was prevented to Server 'yyyyyyyy-yyyy-yyyy-yyyy-yyyyyyyyyyyy' in Site 'DomainAAA/Configuration/Sites/SiteB'. Local site is 'DomainAAA/Configuration/Sites/SiteA'.
DomainAAA - Our Domain
SiteA - AD site which temporarily cover subnet A and Subnet B
In subnet A are installed 2 DCs (Global Catalog) and other aplication servers.
In subnet B are installed all EX2013 servers (2 MBX and 2x CAS) ,1 DC (Global Catalog) and other app servers.
SiteB - new created AD site intended for subnet B
These subnets are on diferent physical location.
When we change Ad site for subnetB from the AD siteA to AD SiteB, above error appear.
There is a object ExchEdgeSyncService under the AD site : SiteA , where the installation EX2013 was done.
So do We need to create the new edgesyncservice under the siteB ?
What steps do we have to make ?
Our intention is to eventually remove all servers from the siteA and move to to SiteB.
So that siteA will no longer exist.
Thanks in advance , and sorry for bad english.
Best regardsHi,
Why don't you just extend the VLAN so you don't have to create another site and do changes so much
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Krisna Ismayanto | My blogs: Krisna Ismayanto | Twitter:
@ikrisna -
RPC error when configuring Exchange 2013 servers in 2nd site
Hello. I'm running into an error when trying to configure any of my Exchange 2013 servers in my 2nd AD site. To get into the loop of what my server structure looks like, please check below:
Site 1 servers:
DC1 - Domain Controller
DC2 - Domain Controller
CAS1 - CAS server
CAS2 - CAS server
MBX1 - Mailbox server
MBX2 - Mailbox server
MATHAFTMG - TMG server
Site 2 servers:
CCCDC1 - Domain Controller
CCCDC2 - Domain Controller
CCCCAS1 - CAS server
CCCCAS2 - CAS server
CCCMBX1 - MBX server
CCCMBX2 - MBX server
CCCTMG - TMG server
Currently I have a site-to-site vpn connection between site 1 and site 2 TMG servers via Internet connection; I can access the servers of the other site perfectly (whether I am in Site 1 or Site 2).
All user mailboxes are currently in Site 1 MBX servers; when users are in Site 2, they connect to the CAS servers in Site 1 to access their mailboxes.
Many users will stay permanently in Site 2, so it makes sense to have Exchange servers in Site 2 to provide faster access to mailboxes. I created the Site 2 domain controllers, and made sure AD replication is working; and it is. I then added the MBX servers
and CAS servers in Site 2 in this order: CCCMBX1, then CCCCAS1, then CCCMBX2, then CCCCAS2.
All Exchange servers in Site 2 installed beautifully. But then I tried to access the servers via ECP to proceed with the configuration. In ECP, I click on the server link, and all Exchange servers in both sites appear. If I try to configure the virtual directories
of Site 1 CAS servers, no problem. But when I try to configure virtual directories of Site 2 CAS servers, I get this error message:
The task wasn't able to connect to IIS on the server 'CCCCAS1.domain.com'. Make sure that the server exists and can be reached from this computer: The RPC server is unavailable.
The virtual directories issue is just an example. Same thing happens if I try to configure Outlook Anywhere for Site 2 CAS servers.
Users connect to Site 1 CAS servers via mail.domain.com. I have the A record mail.domain.com pointing to the IP address of CAS1 server, and another A record mail.domain.com pointing to the IP address of CAS2 server. Not the best load balancing going on here,
but it works great with Exchange 2013.
From mail.domain.com I can access OWA and ECP internally and externally; no problems there. From ECP I can access and configure any Site 1 Exchange 2013 servers.
The only problem is when I access ECP to configure the Site 2 Exchange 2013 servers, I get the same error message:
The task wasn't able to connect to IIS on the server '<server name>.domain.com'. Make sure that the server exists and can be reached from this computer: The RPC server is unavailable.
Even if I try to access a Site 2 Exchange 2013 server via https://localhost/ecp to configure it, it get the same error message.
I updated all Exchange 2013 servers in both sites to CU2 v2 and rebooted the servers in the proper order; problem still there.
Any clue what might the problem be?
Thank you!Hello. I'm running into an error when trying to configure any of my Exchange 2013 servers in my 2nd AD site. To get into the loop of what my server structure looks like, please check below:
Site 1 servers:
DC1 - Domain Controller
DC2 - Domain Controller
CAS1 - CAS server
CAS2 - CAS server
MBX1 - Mailbox server
MBX2 - Mailbox server
MATHAFTMG - TMG server
Site 2 servers:
CCCDC1 - Domain Controller
CCCDC2 - Domain Controller
CCCCAS1 - CAS server
CCCCAS2 - CAS server
CCCMBX1 - MBX server
CCCMBX2 - MBX server
CCCTMG - TMG server
Currently I have a site-to-site vpn connection between site 1 and site 2 TMG servers via Internet connection; I can access the servers of the other site perfectly (whether I am in Site 1 or Site 2).
All user mailboxes are currently in Site 1 MBX servers; when users are in Site 2, they connect to the CAS servers in Site 1 to access their mailboxes.
Many users will stay permanently in Site 2, so it makes sense to have Exchange servers in Site 2 to provide faster access to mailboxes. I created the Site 2 domain controllers, and made sure AD replication is working; and it is. I then added the MBX servers
and CAS servers in Site 2 in this order: CCCMBX1, then CCCCAS1, then CCCMBX2, then CCCCAS2.
All Exchange servers in Site 2 installed beautifully. But then I tried to access the servers via ECP to proceed with the configuration. In ECP, I click on the server link, and all Exchange servers in both sites appear. If I try to configure the virtual directories
of Site 1 CAS servers, no problem. But when I try to configure virtual directories of Site 2 CAS servers, I get this error message:
The task wasn't able to connect to IIS on the server 'CCCCAS1.domain.com'. Make sure that the server exists and can be reached from this computer: The RPC server is unavailable.
The virtual directories issue is just an example. Same thing happens if I try to configure Outlook Anywhere for Site 2 CAS servers.
Users connect to Site 1 CAS servers via mail.domain.com. I have the A record mail.domain.com pointing to the IP address of CAS1 server, and another A record mail.domain.com pointing to the IP address of CAS2 server. Not the best load balancing going on here,
but it works great with Exchange 2013.
From mail.domain.com I can access OWA and ECP internally and externally; no problems there. From ECP I can access and configure any Site 1 Exchange 2013 servers.
The only problem is when I access ECP to configure the Site 2 Exchange 2013 servers, I get the same error message:
The task wasn't able to connect to IIS on the server '<server name>.domain.com'. Make sure that the server exists and can be reached from this computer: The RPC server is unavailable.
Even if I try to access a Site 2 Exchange 2013 server via https://localhost/ecp to configure it, it get the same error message.
I updated all Exchange 2013 servers in both sites to CU2 v2 and rebooted the servers in the proper order; problem still there.
Any clue what might the problem be?
Thank you! -
Public folders for users to identify spam
It looks like it should work, but ...
I have SL server providing IMAP mailboxes for users, and that all works fine. As it is now, for a user to notify SpamAssassin that it didn't classify a message properly, they have to actively redirect the message to the junkmail or notjunkmail account. This is a PITA and a) they can't be bothered and b) the email address to which they're to redirect or forward the improperly classified message is subject to errors.
What I'd like is a pair of public mailboxes that they can just drag misclassified messages to, so I set up a public namespace containing two mailboxes, JunkMail and NotJunkMail. They're visible to all the users I want them to be and the permissions seem right. The plan is to whip up a launchd job to digest the contents of these mailboxes in the middle of the night, much like the stock sa-learn job.
The problem is that when I try to drag a sample email message from my inbox to the JunkMail foler, I get an error that says <bold>Blah blah blah</bold> The IMAP command "UID COPY" (to Public.JunkMail) failed for the mailbox "wherever I drag from" with server error: Character not allowed in mailbox name '.'.
I've tried changing the 'separator' in the namespaces to bot '/' and '.', with no discernible difference in behavior or message. I've set all of the mail logging levels to DEBUG to no avail. I've made the public mail boxes world-writable. Nothing seems to help, or even change the client-side behavior.
If someone more knowledgeable about dovecot and its IMAP configuration can point me in the right direction, I'd appreciate it greatly.
Thanks,
- TedThis is a followup to let people know how I got it to work.
My supposition is that when dovecot evaluates whether a user can write into a folder it does not do a full group membership expansion to determine the user's rights, so making the folders in question writable by the shared 'mailusers' group (that all human mail users are members of) was not adequate.
Instead, I had to add ACLs to the target folders granting explicit rights to each individual user. My nightly spam-training script uses the approach of stopping the mail server, moving any folders that might contain trainable messages aside, replacing those folders with empty versions of themselves, then restarting the mail server.
I had been using a more elaborate approach that evaluated whether there was anything to process before stopping the mail server, but with the ACL approach that also meant comparing the current group membership with what users had been set on the folders' ACLs. After I had written the script to do that, I decided the slight increase in efficiency wasn't worth the added complexity - bouncing my mail server in the middle of the night isn't even marginally problematic for my users, but YMMV. Instead, by just replacing the folders each night with their ACLs generated from the current group membership, membership changes are incorporated within 24 hours, which is good enough for me.
Anyway, this Bash snippet shows the crux of what I'm doing now:
readonly SP='[:space:]'
readonly UserList="$(dscl '/LDAPv3/127.0.0.1' \
'-read' "/Groups/$UserGroup" 'Member' | sed -En \
"s!^[$SP]*Member[$SP]*:[$SP]*(.+)[$SP]*\$!\\1!p")"
readonly ServerStatus="$(serveradmin status mail \
| sed -En 's!^[^"]*"([^"]+)".*$!\1!p' \
| tr '[:upper:]' '[:lower:]')"
[[ "$ServerStatus" != 'running' ]] \
|| serveradmin stop mail > /dev/null
for d in "$PublicSpamPath" "$PublicHamPath"
do
[[ ! -d "$d" ]] || mv "$d" "$d.$ScanSuffix"
mkdir -m 2755 "$d"
chgrp "$UserGroup" "$d"
for n in $UserList
do
chmod +ai "$n allow $UserAcls" "$d"
done
mkdir -m 2755 "$d/cur" "$d/new" "$d/tmp"
chgrp "$UserGroup" "$d/cur" "$d/new" "$d/tmp"
done
[[ "$ServerStatus" != 'running' ]] \
|| serveradmin start mail > /dev/null
If this helps, you're welcome. -
We've added two 2013 hybrid servers to our existing 2010 environment. Added the CAS role to all 2010 mailbox servers per ( https://technet.microsoft.com/en-us/library/dn249373%28v=exchg.150%29.aspx ) and currently have public folders (located on our
2010 mailbox servers) working in Outlook client for users whose mailboxes have been migrated from on-prem 2010 to o365. The problem is when we create a new user in o365, that user CAN see that we have public folders via Outlook client, but when we expand
the public folder list a credential window pops up and will not accept any set of credentials (even those of working hybrid migrated accounts).
We are following this method when creating new o365 accounts:
1) Make a user in AD
2) Dirsync the user
3) License the user for exchange
4) Run on on-prem mailbox server via Exchange Management Shell: Enable-RemoteMailbox "[email protected]" -RemoteRoutingAddress "[email protected]"
5) In o365 Remote Exchange Powershell run: Get-Mailbox -identity "[email protected]" |fl Identity,ExchangeGUID
6) Copy ExchangeGUID
7) Back on on-prem mailbox server via Exchange Management Shell: Set-RemoteMailbox "[email protected]" -ExchangeGUID <paste GUID here>
8) Dirsync the user again
I've compared two Remote User Mailboxes, ones that were migrated via Hybrid, and ones that were created in o365 and the settings look identical outside of the attribute "RemoteRecipientType" is set to Migrated vs ProvisionMailbox. I'm not
sure what else the difference in these accounts could possibly be that would be causing this credential failure.
Any thoughts would be appreciated.Hi,
Please do the following steps to create an Exchange Online mailbox in your Hybrid environment:
Method 1: Create a remote mailbox for an existing user.
If you already have created a user in Active Directory, and the user has already been synced to online with license, we can give that user a mailbox in Exchange Online by using the Exchange Management Shell cmdlet Enable-RemoteMailbox on
your on-premise Exchange server:
Get-User “User1” | Enable-RemoteMailbox
Then the mailbox is enabled with an Exchange Online mailbox. We can check the mailbox by running the following command in On-premise Exchange server:
Get-RemoteMailbox “Test1” | FL *address*
Method 2: Directly create a new remote mailbox.
1. Create the remote mailbox in On-premise Exchange server by running:
$Credentials = Get-Credential
New-RemoteMailbox -Name "Test2" -Password $Credentials.Password -UserPrincipalName
[email protected]
2. Launch dirsync and assign a license to the newly created user with Office 365 account.
Then Test2 can sign in, using his on premises credentials, and open his online mailbox.
For more information about the remote mailbox, please refer to:
http://blogs.technet.com/b/ilvancri/archive/2011/08/24/exchange-online-exchange-on-premises-shared-namespace-how-about-mail-routing.aspx
Regards,
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Winnie Liang
TechNet Community Support -
Access refused in public folders when user is in a Group
Hi,
We have a Exchange 2003 server and an Exchange 2010 server
The Public folders are on the 2003.
Since 2 or 3 days, there is a access issue in juste ONE public folder: SOME users cannot access to the folder anymore if there are in a group (it asks for a login and a password -> if the user enters them, it doesn't work)
BUT the issue is just for some users not all and there are in the SAME group.
The issue is the same with both distribution or security group (and universal).
Please HelpHi,
From your description, I recommend you follow the steps below for troubleshooting:
1. Please run the Get-PublicFolderAdministrativePermission -Identity "xxx" -User "xxx" cmdlet to check these users' permissions for the public folder.
2. If they don't have the related permissions, please use the Add-PublicFolderClientPermission -Identity "xxx" -AccessRights xxx -User xxx cmdlet to add the permissions for them.
For more information, here are some articles for your reference.
View Public Folder Administrative Permission Settings
http://technet.microsoft.com/en-us/library/aa998587(v=exchg.141).aspx
Add Permissions for Client Users to Access Public Folder Content
http://technet.microsoft.com/en-us/library/aa998834(v=exchg.141).aspx
Hope it helps.
If you need further assistance, please feel free to let me know.
Best regards,
Amy
Amy Wang
TechNet Community Support -
My folders in my mailboxes are not will not sync
My folders in my mailboxes will not sync to my iphone
See:
* http://kb.mozillazine.org/Images_or_animations_do_not_load
* You can see the permissions for the domain in the current tab in Tools > Page Info > Permissions
* You can see all exceptions in [http://kb.mozillazine.org/Menu_differences Firefox > Preferences] > Content: Load Images > Exceptions
* You can check the Tools > Page Info > Media tab for blocked images (scroll through all the images) -
Public Folders on multiple Exchange 2013 servers
Two companies (lets call them WestCoast Company and EastCoast Company) have merged. Each one has Ex2010 with PFs of local scope (the companies don't need access to each other's PFs). I want to move them to a single Exchange Organization with one Exchange
server in each office and possibly a 3rd Exchange in a data center. I am looking for the best/simplest solution for those legacy PFs. Questions:
- With Exchange 2010 I can only have one PF database so I will have to merge the PF structures. If the "master" PF DB sits in the data center I can choose which folders to replicate to each regional Exchange server (ie I can have only WestCoast
folders on the WestCoast Exchange and similar for East Coast). Are these statements correct?
With Exchange 2013:
- Can I have more than one PF trees (one per PF mailbox) or am I limited to a single PF hierarchy?
- If only one PF hierarchy, am I forced to have one location that holds all the content or can the content remain distributed in different locations?
- Can I have content (or PF mboxes) that only show up on some of the Exchange servers? (ie WestCost PFs will show up only on WestCoast Exchange)
- Do the PF limits (10,000 folders, 1 million items, etc) apply per PF mbox or for the whole thing?
ThanksThere is just one public folder hierarchy. You can assign sub-trees under the root to different mailbox databases, though, and through permissions you could restrict who can see each of them.
You can have public folder mailboxes mounted in different mailbox databases, with different databases mounted in different locations. So you could have the Europe folders in a mailbox in a mailbox database mounted on a European server, and the Americas
folders in a mailbox in a mailbox database mounted on an Americas server.
You can do that but only by grouping public folder mailboxes in mailbox databases that are mounted where you want them to be mounted. As stated before, you might be able to hide folders through permissions, not by where they are mounted.
Yes, the 10,000-folder limit applies to the organization. If you have more than that, wait until the limit is increased.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems." -
OWA still redirects to Exchange 2007 (legacy) after mailbox-move to Exchange 2013
Hi,
I am in the process of implementing Exchange 2013 in coex with 2007. I am testing now in a copy of the production environment and have installed the Exchange 2007 SP3 RU11 prior to installing Exchange 2013 using the SP1 media.
We use a wildcard certificate and I prepared the Exchange 2007 internal/external URLs for OWA/OAB/etc to use the legacy.domain.com names and in Exchange 2013 I set them all to email.domain.com. Exchange 2013 has Outlook Anywhere configured.
All tests like autodiscover (internally via SCP) run fine and for a new Exchange 2013 mailbox the Outlook and OWA functionality is as expected. A mailbox still on 2007 also connects fine via Outlook and while connecting to OWA (using the htps://email.domain.com/owa
url) also redirects me to https://legacy.domain.com/owa just fine.
HOWEVER: after a successfull mailbox-move from 2007 to 2013 my OWA logon-request STILL get's redirected to the 2007 legacy URL. When I then logon again on the 2007 OWA I get the message that I should connect to the 2013 URL and end-up in a loop.
Anyone any tips where to search?
Many thanks in advance.
Best regards and many thanks in advance, Eric VegterThis seems to be an outstanding issue.
We just performed a fresh install of Exchange 2013 on a Windows Server 2012 R2 operating system. We're migrating from our existing Exchange 2007 server. At the moment we have everything properly setup in a co-existence state. All we lack is to complete the
migration of our mailboxes from the 2007 DB to the 2013 DB.
In performing the first mailbox move, to test the migration process and make certain mail flows as expected, we noticed this same problem. Before reading through this thread, I was able to assign Full Access to a delegate user and then perform the "Open
Mailbox" feature from a 2013 user's account. This was successful in opening the mailbox within OWA 2013. However, I still could not access the account by simply logging into the Outlook Web App. It would login, then proxy back to OWA 2007 with the message,
"Use the following link to open this mailbox with optimal performance:
http://mail.domainname.com/"
After reading about cycling the OWA app pool, I immediately tried it as a workaround and it worked. It is a little frustrating going about it in this way. Hoping to see more activity on this thread.
-Lorne -
Exchange 2010 System Public Folders trying to replicate to decommissioned Exchange 2003
I was checking the mail queue on Exchange 2010 and noticed several hundred messages in retry. Looking at the messages I found that they were all destined for an old 2003 exchange that has been decommissioned. I looked at the System Public Folders and found
replication is set up on "events root, OWAScatchpad, SchemaRoot, and Store Events. They are set to replicate to the old mail server. When I try to remove the old server from replication it gives me an error;
Microsoft Exchange Error
The following error(s) occurred while saving changes:
Set-PublicFolder
Failed
Error:
You must specify a value with the Replicas parameter.
OK
Not sure where to go with this error. Could someone point me in the right direction?
Thank you,
Wade HarrisHi,
For this issue, I recommend you add an Exchange 2010 public folder database to the replica list and then remove Exchange 2003 server from this list to check result.
I tested in my lab, and I got the same error with yours, we need to keep at least one public folder database in the replica list.
Best regards,
Belinda
Belinda Ma
TechNet Community Support -
Exchange 2013 user cann't access exchange 2013 public folder
Hi, during the coexistence exchange 2007 and exchange 2013, outlook is unable to access public folder of exchange 2007 from exchange 2013, I've install CU2 for exchange 2013 and also set authentication to Ntlm, but also failed. please help to look into this
problem, thanks.
belows are information about outlook anywhere in our exchange.
exchange 2007：(primary site)shmail04,shmail05,shmail06; (DR site)drpmail05,drpmail06
exchange 2013：(primary site)shcas01,shcas02; (DR site)wxcas01
Identity : SHCAS01\Rpc (Default Web Site)
InternalHostname : infor.tdw.com
InternalClientAuthenticationMethod : Ntlm
InternalClientsRequireSsl : True
ExternalHostname : infor.tdw.com
ExternalClientAuthenticationMethod : Ntlm
ExternalClientsRequireSsl : True
IISAuthenticationMethods : {Ntlm}
Identity : SHCAS02\Rpc (Default Web Site)
InternalHostname : infor.tdw.com
InternalClientAuthenticationMethod : Ntlm
InternalClientsRequireSsl : True
ExternalHostname : infor.tdw.com
ExternalClientAuthenticationMethod : Ntlm
ExternalClientsRequireSsl : True
IISAuthenticationMethods : {Ntlm}
Identity : WXCAS01\Rpc (Default Web Site)
InternalHostname : infor.tdw.com
InternalClientAuthenticationMethod : Ntlm
InternalClientsRequireSsl : True
ExternalHostname : infor.tdw.com
ExternalClientAuthenticationMethod : Ntlm
ExternalClientsRequireSsl : True
IISAuthenticationMethods : {Ntlm}
Identity : SHMAIL04\Rpc (Default Web Site)
InternalHostname :
InternalClientAuthenticationMethod : Ntlm
InternalClientsRequireSsl : False
ExternalHostname : legacy.tdw.com
ExternalClientAuthenticationMethod : Ntlm
ExternalClientsRequireSsl : True
IISAuthenticationMethods : {Ntlm}
Identity : SHMAIL05\Rpc (Default Web Site)
InternalHostname :
InternalClientAuthenticationMethod : Ntlm
InternalClientsRequireSsl : False
ExternalHostname : legacy.tdw.com
ExternalClientAuthenticationMethod : Ntlm
ExternalClientsRequireSsl : True
IISAuthenticationMethods : {Ntlm}
Identity : SHMAIL06\Rpc (Default Web Site)
InternalHostname :
InternalClientAuthenticationMethod : Ntlm
InternalClientsRequireSsl : False
ExternalHostname : legacy.tdw.com
ExternalClientAuthenticationMethod : Ntlm
ExternalClientsRequireSsl : True
IISAuthenticationMethods : {Ntlm}
Identity : DRPMAIL05\Rpc (Default Web Site)
InternalHostname :
InternalClientAuthenticationMethod : Ntlm
InternalClientsRequireSsl : False
ExternalHostname : legacy.tdw.com
ExternalClientAuthenticationMethod : Ntlm
ExternalClientsRequireSsl : True
IISAuthenticationMethods : {Ntlm}
Identity : DRPMAIL06\Rpc (Default Web Site)
InternalHostname :
InternalClientAuthenticationMethod : Ntlm
InternalClientsRequireSsl : False
ExternalHostname : legacy.tdw.com
ExternalClientAuthenticationMethod : Ntlm
ExternalClientsRequireSsl : True
IISAuthenticationMethods : {Ntlm}Hi,
I have found an article said that we need to set the external host name the same. See more details in the following link:
http://blogs.technet.com/b/mspfe/archive/2013/10/21/upgrading-to-on-premises-exchange-server-2013.aspx
To allow your Exchange 2013 Client Access server to redirect connections to your Exchange 2007 servers, you must enable and configure
Outlook Anywhere on all of the Exchange 2007 servers in your organization. If some Exchange 2007 servers in your organization are already configured to use Outlook Anywhere, their configuration must also be updated to support Exchange 2013.
The following configuration is set on each Exchange 2007 server:
The Outlook Anywhere external URL is set to the external hostname of the Exchange 2013 server.
Sent By
Silver -
Can You Open a User Mailbox with Your Exchange Account on the iPhone?
I can add user mailboxes on the same domain to my Outlook on my Mac and/or Windows PC but I don't see an option on my iPhone when I add my Exchange Account to the Mail App.
Is this possible?Select the Exchange account under Accounts.
Select Edit at the top right for the account.
Select New Mailbox at the bottom right to create a new server store mailbox fot the account.
Enter the name for the new mailbox in the space provided.
Select Save at the top right.
Select Done when finished.
Maybe you are looking for
-
Single-sourcing: Deleted content in FM source not reflected in RH update
I discovered today that, when I delete content in my linked FM source, the same content is not deleted or even marked as 'changed' or anything in the RH update! In one situation, I deleted an entire chapter but the topic wasn't deleted. In another, I
-
LR4 "All Photographs" does not show any images.
This week I upgraded from LR3 to LR4 on my Mac. Unfortunately, since doing so, "All Photographs" has stopped showing any images even though it indicates that there are 26,000 images in the library. Also, even though I have activated "Show photos in s
-
Trying to upgrade iPad software to newest version. It downloads but stops while backing up and says not enough space on hard drive to back up if i continue all media on iPad will be lostor deleted. Can I get it back after upgrade by just synching or
-
My hp dv6700 shuts down after 1 second. i recently upgraded the processor to intel t7500.
I recently tried to upgrade the processor of my HP dv6700. I upgraded to an Intel T7500 and after reassembling the laptop and trying to power it up, the laptop shuts down after 1 second. The computer turns on, the fan makes a brief noise, and then th
-
Calendars display, but no .ics files on my hard drive!
ICal started behaving weirdly after I upgraded to Tiger. Calendar groups I created would disappear every time I quit and restarted iCal, and new 'Home' and 'Work' calendars would appear at the same time. I deleted preference files. I even re-installe