Outlook 2007 on Terminal Server cannot manage Public Folder Favorites after Migration to Exchange 2013

Hi,
we are running a Server 2008 R2 as a Terminal Server with Outlook 2007 SP3 (incl Nov 2012 Update 12.0.6665.5000) which is known as fully supported with Exchange 2013.
With Exchange Server 2007 we did not have any issues. But after having successfully migrated to Exchange 2013 we cannot manage our public folders favorites from these clients anymore.
As we are running Outlook 2007 on a WTS we can not use Exchange Cache Mode and so we can also not download Public-Folders-Favorites as an option. Whenever we try to delete existing favorites or when we try to delete public folders with content or subfolders
there will be an error msg that says that it cannot be deleted and that there may be no sufficient permissions. But this IS NOT the issue NOR the solution as I have full admin rights and am owner of the public folders.
On single fat clients with Outlook 2007 with Exchange Cache Mode enabled we can manage the favorites and the public folders without problem.
We need to be able to manage the favorites of all users (circa 50-60 users) from the WTS with Outlookm 2007. I have no more ideas right now. Does anyone know how to get this settled?
Thanks, Paula

Hi,
Based on the description, users could access public folders successfully, but when they tried to manage public folder favorites or wanted to remove specified folders, they got error message of no sufficient permissions.
Is it right?
You mentioned on single fat clients with Outlook 2007 with Exchange Cache Mode enabled, user can operate normally. Is this a WTS with Outlook 2007 installed?
If possible, please switch this Outlook client from cached mode to online mode to check result.
Best regards,
Belinda Ma
TechNet Community Support

Similar Messages

Object-Owner missing in Public Folder Calenders after Transition to Exchange 2013 SP1

Hi there,
we transfered all Public Folders from Exchange 2003 to 2010 to 2013 SP1. We have some Calendars with PublicFolderClientPermission Author witch includes EditOwnedItems and DeleteOwnedItems
Unfortunately the Author Rights wont work after migration. it seems like the creator of the object got lost.
since i never notices that in transitions from exchange 2003 to 2010, i think that should be related to the exchange 2013 transition.
Can anybody approve or disprove that behavior?
thanks alot

Noticed now in the Exchange 2013 Event Logs that we're getting quite a few of these warnings:
"Process <Select one exchange releated process>.exe (PID=<whatever>). Object [CN=Public Folder Database,CN=Databases,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=Contoso,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=contoso,DC=local]. Property [PublicFolderDatabase] is set to value [contoso.local/Configuration/Deleted Objects/Public Folder Database
DEL:ca62a715-05b2-4b08-ae0f-7f7c4b7e4cc3], it is pointing to the Deleted Objects container in Active Directory. This property should be fixed as soon as possible."
If i take a look at that mailbox database it's obvious that it's pointing towards the old Public Folder Database, which is quite interesting as Exchange 2013 isn't supposed to used that value at all (according to http://technet.microsoft.com/en-us/library/bb123971(v=exchg.150).aspx):
[PS] C:\Windows\system32>Get-MailboxDatabase -Identity "Mailbox database" | fl
PublicFolderDatabase : contoso.local/Configuration/Deleted Objects/Public Folder Database
DEL:ca62a715-05b2-4b08-ae0f-7f7c4b7e4cc3
I'm assuming this is what happens when messing around with ADSIEdit :) So, further ADSIEdits to set that value to null on the existing Mailboxdatabases, or anyone have any other suggestions?

After migration to Exchange 2013 the old outlook clients do not automatically reconfigure

After migration to Exchange 2013 the old outlook clients do not automatically reconfigure
we use outlook 2013

Hi ,
I hope you would be having exchange 2013 coexistence environment with exchange 2010 or 2007.
Autodiscover is the feature which will make the outlook profiles to configure automatically.So please make sure the following things are in place.
1.Autodiscover record on the internal dns need to be configured and it has to be resolved properly to the cas servers or else to the LB if you have.
2.Please check the autodiscover internal url.
get-clientaccessserver -identity "server name" | fl *internaluri*
3.Make sure the name used for the autodisocver and internal outlook anywhere are available on the SAN certificate installed in exchange.Same time we need to enable the installed SAN certificate for the exchange services like iis,pop,imap,smtp.
4.You need to have the autodicover name and internal outlook anywhere name on the internet explorer proxy exceptions when you have proxy servers available on your network for internet access.
Note : moreover we need an additional information's from your side about your environment.
Thanks & Regards S.Nithyanandham

Users cannot access calenders from outlook after migration to exchange 2013

I have a strange situation after upgrading to exchange 2013 some users are reporting that they cannot open or create calender appointments for calenders they used to be able to manage. we currently are using outlook 2010. also when the users access the calenders
with the webmail they are reporting that they can access the calenders and are able to do all the things they need to do.
i have tried reinstalling office and adding their exchange accounts but this does not help.
another stange thing is that to be sure i had setup the correct access policy i have reset all the security entries on all the calendars with the help of powershell. this seemed to have helped but after a couple of hours some users started reporting that they
could not access calendar items again!

Hi,
Is there any error description when the problematic users cannot open or create calendar items? Since the issue only happens to some users instead of all users and all calendars can work well in OWA, I think the calendar in the mailbox
should be configured properly.
Please configure the problematic user’s Outlook account in a clean computer with new installed Outlook to check whether the issue persists.
Thanks,
Winnie Liang
TechNet Community Support

Public Folder Mailbox causes database failover Exchange 2013

Hi , we are completing a migration from Exchange 2007 to Exchange 2013. All was going swimmingly until we migrated our legacy public folders. Now every now and again ( once a day generally ) the Exchange Database hosting the Public Folder Mailbox
crashes and fails over to another DAG member.
We are using CU5 and our old 2007 server is offline but not removed from the organization yet.
The error message is as follows :
Event ID 1013
The mailbox with mailboxguid "xxxxxxxxxxxx" caused crash or resource outage on database (GUID="xxxxxxxxxxx")
along with :
Event ID 1001
Microsoft Exchange Server Information Store has encountered an internal logic error. Internal error text is (Unable to apply maintenance GetNonKeyColumnValuesForPrimaryKey-norow, index corruption?) with a call stack of ( at Microsoft.Exchange.Server.Storage.Common.ErrorHelper.AssertRetail(Boolean
assertCondition, String message)
and :
Event ID 1002
Unhandled exception (Microsoft.Exchange.Diagnostics.ExAssertException: ASSERT: Unable to apply maintenance GetNonKeyColumnValuesForPrimaryKey-norow, index corruption?
The Mailbox Guild matches the Public Folder Mailbox GUID and the Database GUID matches the Database where the mailbox is mounted.
The error seems to be the same as this question :
https://social.technet.microsoft.com/Forums/office/en-US/7e823810-29f4-48f2-ad60-37e6ac147d3e/exchange-2013-database-dismounts-unexpectedly
However I'm after a bit more concrete information as to what actually causes this and if an upgrade to CU6 is required. This link appears to suggest moving the mailbox will help. Has anyone else come across this with CU5 and will a mailbox move
correct it ?
http://blogs.technet.com/b/exchange/archive/2014/10/03/those-pesky-lazy-indices.aspx

Hello,
Thank you for your post.
This is a quick note to let you know that we are performing research on this issue.
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Mail Enabled Public Folder Issues after migration online

Hi
We have recently migrated our Legacy (Exchange 2010) Public Folder Infrastructure to Exchange Online - we have a hybrid setup, SSO and DirSync.
We initially had an issue where some of our mail enabled public folders had lost their link with the associated MailPublicFolder objects and as such could not receive email.
We resolved this issue ourselves however we are now experiencing a different issue which i believe should be easily resolvable however this isn't the case at the minute.
The issue is that when a user emails a Mail Enabled Public folder Exchange online is attempting to relay the email back to our onPrem servers. This is occuring for the bulk of our Mail Enabled Public Folders - we have ~1200 of these. The only
folders that are working as expected are those that had the initial issue above and for which we had to remove and re mail enable these folders. We also had to recreate any secondary smtp address for these folders. This accounts for 88 of our total
MEPFs.
I have checked the attributes on the MailPublicFolder objects for those that are not working and those that are functioning as expected. The only difference in these that I can see is that the MEPFs with the issue have a value set in the ExternalEmailAddressAttribute.
I have tried to programatically set this value to $Null however i receive the following error:
The external e-mail address $null is not an SMTP e-mail address.
I have also tried the following : set-mailpublicfolder -Identity "MEPF"-ExternalEmailAddress "<not set>"
with the same resultAttempting to use the following syntax -externalemailaddress @{remove=$oldAddress} returns the following error:
Cannot process argument transformation on parameter 'ExternalEmailAddress'.Cannot convert the "System.Collections.Hashtable" value of type"System.Collections.Hashtable" to type "Microsoft.Exchange.Data.ProxyAddress".
At present the only fix that I have for this is to take a copy of the email addresses for an affected public folder, Mail disable it, wait for the object to be cleared, re-enable the public folder as a mail public folder and then re-add the email addresses.
This is ok on an adhoc basis but not for the ~1200 folders that are affected. Especially when from what i can see it should be relatively straightforward to resolve this with a simple PowerShell script.
I do have a case open with MS for this but I am hoping that somebody here can help also.
Thanks
Joe

Ok so i fixed it myself.
The thinking here is that the ExternalEmailAddress was set using the Primary SMTP address while the Public Folders were on premises.
In order to get the required information we ran a script to export all the MailPublicFolder objects which had a value in the ExternalEmailAddress attribute. We exported the Name, ExternalEmailAddress and GUID
We then ran a second script to export the Identity, MailRecipientGuid from Get-PublicFolder -recurse.
The MailRecipientGUID is what ties the Mail Enabled Public folder to the MailPublicFolder object.
Using Excel I then matched the two up and created a csv file with the Identity Attribute from the get-PublicFolder command and the ExternalEmailAddress Attribute from Get-MailPublicFolder.
The following script then used this csv file to first Mail Disable the Public Folder, then Mail Enable the Public Folder.
Once these steps have been completed the final stage is to add the SMTP address back in to the Public folder.
To do this it is necessary to retrieve the new MailRecipientGUID and use it to return the MailPublicFolder for the Set-MailPublicFolder command.
I was happy to use this script after i tested with a small subset of the data. It is provided as is with no guarantee that it will be suitable for you to use and any use of this script is at your own risk.
Script to Automatically fix brokenn Public Folder Objects
Created By: Joe McGrath
Created On: 18/02/2014
$Path = "C:\PublicFolders.csv"
import-csv -Path $Path | ForEach-Object `
Disable-MailPublicFolder -identity $_.Identity -Confirm:$False
Write-Host "Broken Public Folders Now Mail Disabled"
Write-Host "Waiting for commands to be fully processed online - the script will continue in 5 minutes"
Start-Sleep 300
Write-Host "Re MailEnabling Public Folders"
import-csv -Path $Path | ForEach-Object `
Enable-MailPublicFolder -identity $_.Identity
Write-host "Broken Public Folders now enabled"
Write-Host "Now waiting to allow online service to catch up - script will continute in 5 minutes"
Start-Sleep 300
Write-Host "Updating email addresses for broken public folders"
import-csv -Path $Path | ForEach-Object `
$NewPF = get-publicfolder -identity $_.Identity
Write-Host $NewPF.Identity
Write-host $newPF.MailRecipientGuid
$EmailAddresses = $_.AdditionalEMailAddresses
$NewMailPF = get-MailPublicFolder -resultsize unlimited | Where-Object {$_.Guid -eq $NewPF.MailRecipientGuid}
Set-MailPublicFolder -identity $NewMailPF.identity -EmailAddressPolicyEnabled:$FALSE
Set-MailPublicFolder -identity $NewMailPF.identity -EmailAddresses $EmailAddresses -EmailAddressPolicyEnabled:$FALSE
Set-MailPublicFolder -identity $NewMailPF.identity -EmailAddressPolicyEnabled:$TRUE
$EmailAddresses = ""
Write-Host "Completed!"

After Migrating To Exchange 2013 All Outlook 2010 Users Constantly Prompted For Password (BUT OUTLOOK WORKS).

I have two servers. One is Exchange 2010 and the other is Exchange 2013.
Three of our users had mailboxes on Exchange 2013 for the last few weeks with no problems. They used Outlook 2013 and Outlook 2010. After moving the rest of our ~25 users to Exchange 2013 the users with Outlook 2010 began to be prompted for their
password constantly.
They try entering it and it immediately reappears.
The odd thing is it shows connected and they are able to send and receive emails correctly.
I've tested our exchange connectivity using www.testexchangeconnectivity.com and all is well there.
I'm not really sure what's going on.
Any help is appreciated.
Luke
Thanks, Luke Pickard

This can appear if Outlook clients are trying to connect to OAB virtual directory, and don't succeed for some reason. Mailbox and mailflow will work, but password prompt will appear when Outlook tries to contact OAB. Try to investigate in that direction.
Also, perform Outlook Configuration test (right click Outlook icon in task bar while holding CTRL and select Test email autoconfiguration.
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Thank you! Damir

Public Folder Mailbox- Missing Primary Hierarchy Exchange 2013

Hi guys,
I was attempting to create a Public Folder using the Exchange Admin Center but when i tried it came up with the error "Couldn't find the public folder mailbox."
When I went back to check on the Public Folder Mailbox that I had created I noticed that there was no Primary Hierarchy even though Secondary Hierarchy where visible.
Is it Possible to recreate the Primary or change one of the existing Secondaries.
Thanks
A K richardson

Hello,
Is there any update?
Cara Chen
TechNet Community Support

Syncing calendars using Outlook 2007 from iCal Server

Hi,
I would like to know the procedure to sync calendars using Outlook 2007 from iCal Server.
I'm setting up Internet Calendar on Outlook 2007 from == Tools> Account Settings> Internet Calendars>New> Enter the URL and click on add button
Post that, I'm getting an error:
"Error: Cannot verify or add the Internet Calendar in Outlook. Verify the link is a valid calendar link:
webcal://fully qualified domain name:8443/calendars/_uids_/Generated UID/Calendar"
Looking forward some response soon.
Thanks!!

Hi!
That is never going to work if you are looking for 2-way sync with iCal server. You need a 3rd party application to do that, like ical4ol or the open source Outlook sync plugin available here: http://caldav.calconnect.org/implementations/clients.html.
Or alternatively, use another mail client like eMClient for mail and calendaring.
/Hasse

Outlook integration on terminal server

Hi Experts,
I am facing Outlook Integration problems with one of our clients who uses outlook integration on their terminal server for about 10 users. They were on SAP 2007A SP00 PL47 and using outlook integration on terminal server for about 10 users without any problems.
I recently upgraded them to SAP 2007A SP01 PL7 and after that there are add-on initialization errors on the terminal server with outlook integration and payment add-on. The add-ons are installed and working OK on application server and other client machines.
On the terminal server;
1. Initialization of add-ons failed giving "Initialization Failed" error. I tried to reinstall add-on on Terminal server but same result.
2. When trying to logon to SAP within Outlook; system gives ""XYZ" is not a valid company name" error and login fails.
Any help on this will be highly appreciated.
Thanks in advance
Regards
Dave
Edited by: Devinder Sareen on Feb 23, 2010 6:34 AM

Can anyone on the forum shed any light on this subject please?

How to determine actual path/location of Outlook Public Folder favorite?

I have several end users that use the Public Folder favorite system in Outlook. Our Public Folder structure is very large and messy which makes finding these favorites difficult to find. When I go to the properties of the favorited folder, it does not find
the actual path.
Is there a PowerShell command or some tool that will allow me to determine the path?
Thanks in advance,

Hi,
Public Folders can be set as a Favorite Folder at 2 levels in Outlook. one within the Public Folder structure and one within the Navigation Pane:
http://www.msoutlook.info/question/281
Seems you are using the favorite in the Public Folder structure. We can find the folder path by right-clicking and select Properties, and then select
Summary tab. Now you can see the path from the Folder Path field:
Hope this helps.
Best Regards,
Steve Fan
TechNet Community Support

While trying to access my local network I get the message..."The page could not be opened because server cannot be found." This, after updating to Yosemite and paying (again) for the server app.

while trying to access my local network I get the message..."The page could not be opened because server cannot be found." This, after updating to Yosemite and paying (again) for the server app.

It's absolutley scandalous that a company with Apple's resources can let this happen. They should have staggered the release by region rather than opening the flood gates. The upgrade itself took me about 10 attempts to download it, and then I thought I was home free. That was until it rebooted and won't activate. It's over 2 hours now.
Scandalous!

Exchange 2007 migrate to Exchange 2013

Dear MS Support,
I did migrate Exchange 2007 to Exchange 2013
The install complete, the exchange 2007 and 2013 can work together successful
DAG has created and work fine
Below is capture on exchange group after migrate
The exchange 2007 work fine with outlook anywhere, all the users can connected and send and receive mail in 5 year
The cerificate enroll with
Alternative Names: mail.biendongpoc.vn
The autodiscover on exchange 2007:
[PS] C:\Windows\system32>Get-ClientAccessServer | ft Identity,*uri* -AutoSize
Creating a new session for implicit remoting of "Get-ClientAccessServer" command...
Identity AutoDiscoverServiceInternalUri
BDPOC-SERVER1 https://mail.biendongpoc.vn/Autodiscover/Autodiscover.xml
I have created new certificate for Two exchange 2013
The certificate enroll with
Alternative Names: cas.biendongpoc.vn
I have create cname cas point to dag on DNS server
I have create A record autodiscover.biendongpoc.vn point to IP of dag.biendongpoc.vn
I did migrate mailbox from exchange 2007 to exchange 2013, the migrate successful , the outlook can
connected to Exchange 2013 and working perfectly
Our problem, the account exchange 2007 work not stable ,
sometime it connect to mail.abc.com, sometime it connect to cas.abc.com
If the outlook connect to cas.biendongpoc.vn, the request put password and i can't connect to exchange 2007, if outlook connect to mail.biendongpoc.vn i can connect
It is not stable for current exchange 2007
Anyone who can help me ?
Thanks

Hi
huynhtrongnhatminh,
I suggest you please go through this article.
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
Please check this for step by step guide.
http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration.aspx
Please point your autodiscover and commonname to Exchange2013 CAS
Please configure your URLs. There is no CAS array in Exchange2013 but the concept of single name space remains.
You need to have an A record (e.g. legacy.domain.com) in yout external DNS and add that name (legacy.domain.com) in your certificate for exchange 2007 users to have access externally.
Configure your commonname URLs in Exchange2013. Point commonname and autodiscover to exchange2013 in both external and internal DNS servers
Configure URLshttp://www.mustbegeek.com/configure-external-and-internal-url-in-exchange-2013/
No CASARRAY in 2013http://exchangeserverpro.com/exchange-2013-client-access-server-high-availability/
Please configure splitdns or pinpoint DNS in your internal DNS server if not configured
http://exchange.sembee.mobi/network/split-dns.asp
Thanks, MAS
Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

Can only access emails through OWA after migration from exchange 2007 to 2013

can only access emails through OWA after migration from exchange 2007 to 2013, in other words unable to access mails through outlook or from other Applications services.
needed RCA ... plz help..

Hi,
From your description, you can send and receive messages only when you use OWA after migration from Exchange 2007 to Exchange 2013. If I have misunderstood your concern, please let me know.
In your case, I recommend you create a new test mailbox in your Exchange 2013 and check if you can send and receive messages on Outlook. If yes, it is recommended to create a new profile to solve this issue.
Hope this can be helpful to you.
Best regards,
Amy Wang
TechNet Community Support

Instant Search not working on local mailbox in Outlook 2007 on Windows Server 2008 R2 Terminal Server

Sometime last week Instant Search stopped working on a Terminal Server we have deployed. I don't use Outlook on the server so I didn't notice it myself but users started complaining several days ago. When I checked instant search settings everything was
grayed out. I noticed that the feature for Windows Search was disabled so I enabled that feature rebooted the server and now instant search is looking for email in archive folders and sharepoint lists. Local Mailbox mail however is not being indexed by instant
search. When I check data files it says that there is no file for the local mailbox. I checked and Cached Exchange Mode is disabled so no OST is being created and apparently there is no PST for it either.
Do I need an OST/PST to search the local mailbox?
Also I have added the Office GPO Templates and enabled the GPO for allowing Cached Exchange Mode but that doesn't seem to be helping either. Please help.

Have you had any luck with this?
One of our clients has reported that 5 different users, when RDP'd into 3 different RDS Servers, cannot use the Instant Search.
I haven't been able to find anything about this in my online searches.
Like you, the mailboxes aren't even appearing under Instant Search > Search Options. Also, it would appear that there are no locally-hosted .ost/.pst's for any of the users on this server; can the instant search function work on a .pst that's saved
somewhere else on the network?

Outlook 2007 on Terminal Server cannot manage Public Folder Favorites after Migration to Exchange 2013

Similar Messages

Maybe you are looking for