Exchange Online (O365) and Exchange 2013 On-Premise, Public Folder issues?

Hello,
I have recently migrated from Exchange 2010 to Exchange 2013 on premise (decommissioned the old server) and migrated my public folders to the new mailbox architecture found in Exchange 2013.
We are also hybrid setup with Office 365 and Exchange Online (AD FS and Password Sync). For our on-premise Exchange we use Split DNS.
What I am trying to do now is give my Exchange Online users the ability to see our on-premise public folder infrastructure however I am not having any luck in getting this to work.
On premise I have the "PublicFolderMaster" mailbox which is the Primary Public Folder Mailbox, and PublicFolderMailbox1 which is the secondary mailbox (where all the public folder data is).
How do I configure my Exchange Online to allow the users to see on-premise public folders? I tried..
Set-OrganizationConfig -PublicFoldersEnabled Remote -RemotePublicFolderMailboxes PublicFolderMaster,PublicFolderMailbox1
In my O365 user's Outlook I see Public Folders, but when I try to expand it I get an error saying unavailable...
What am I doing wrong?

Or must I follow all these steps in addition to the last step above?
http://technet.microsoft.com/en-us/library/dn249373(v=exchg.150).aspx

Similar Messages

ADFS SSO and SharePoint 2013 on-premise Hybrid outbound search results from SharePoint Online - does it work?

Hi,
I want to setup an outpund hybrid search for SharePoint 2013 on-premise to SharePoint Online.
But I'm not shure if this works with ADFS SSO.
Has somebody experience with this setup?
Here's my guide which I'm going to use for this installation:
Introduction
In this post I'll show you how to get search results from your SharePoint Online in your SharePoint 2013 on-premise search center.
Requirements
User synchronisation ActiveDirectory to Office 365 with DirSync
DirSync password sync or ADFS SSO
SharePoint Online
SharePoint 2013 on-premise
Enterprise Search service
SharePoint Online Management Shell
Instructions
All configuration will be done either in the Search Administration of the Central Administration or in the PowerShell console of your on-premise SharePoint 2013 server.
Set up Sever to Server Trust
Export certificates
To create a server to server trust we need two certificates.
[certificate name].pfx: In order to replace the STS certificate, the certificate is needed in Personal Information Exchange (PFX) format including the private key.
[certificate name].cer: In order to set up a trust with Office 365 and Windows Azure ACS, the certificate is needed in CER Base64 format.
First launch the Internet Information Services (IIS) Manager
Select your SharePoint web server and double-click Server Certificates
In the Actions pane, click Create Self-Signed Certificate
Enter a name for the certificate and save it with OK
To export the new certificate in the Pfx format select it and click Export in the Actions pane
Fill the fields and click OK Export to: C:\[certificate
name].pfx Password: [password]
Also we need to export the certificate in the CER Base64 format. For that purpose make a right-click on the certificate select it and click on View...
Click the Details tab and then click Copy to File
On the Welcome to the Certificate Export Wizard page, click Next
On the Export Private Key page, click Next
On the Export File Format page, click Base-64 encoded X.509 (.CER), and then click Next.
As file name enter C:\[certificate
name].cer and then click Next
Finish the export
Import the new STS (SharePoint Token Service) certificate
Let's update the certificate on the STS. Configure and run the PowerShell script below on your SharePoint server.
if(-not (Get-PSSnapin "Microsoft.SharePoint.PowerShell" -ErrorAction SilentlyContinue)){Add-PSSnapin "Microsoft.SharePoint.PowerShell"}
# set the cerficates paths and password
$PfxCertPath = "c:\[certificate name].pfx"
$PfxCertPassword = "[password]"
$X64CertPath = "c:\[certificate name].cer"
# get the encrypted pfx certificate object
$PfxCert = New-Object System.Security.Cryptography.X509Certificates.X509Certificate2 $PfxCertPath, $PfxCertPassword, 20
# import it
Set-SPSecurityTokenServiceConfig -ImportSigningCertificate $PfxCert
Type Yes when prompted with the following message.
You are about to change the signing certificate for the Security Token Service. Changing the certificate to an invalid, inaccessible or non-existent certificate will cause your SharePoint installation to stop functioning. Refer
to the following article for instructions on how to change this certificate: http://go.microsoft.com/fwlink/?LinkID=178475. Are you
sure, you want to continue?
Restart IIS so STS picks up the new certificate.
& iisreset
& net stop SPTimerV4
& net start SPTimerV4
Now validate the certificate replacement by running several PowerShell commands and compare their outputs.
# set the cerficates paths and password
$PfxCertPath = "c:\[certificate name].pfx"
$PfxCertPassword = "[password]"
# get the encrypted pfx certificate object
New-Object System.Security.Cryptography.X509Certificates.X509Certificate2 $PfxCertPath, $PfxCertPassword, 20
# compare the output above with this output
(Get-SPSecurityTokenServiceConfig).LocalLoginProvider.SigningCertificate
[/code]
## Establish the server to server trust
[code lang="ps"]
if(-not (Get-PSSnapin "Microsoft.SharePoint.PowerShell" -ErrorAction SilentlyContinue)){Add-PSSnapin "Microsoft.SharePoint.PowerShell"}
Import-Module MSOnline
Import-Module MSOnlineExtended
# set the cerficates paths and password
$PfxCertPath = "c:\[certificate name].pfx"
$PfxCertPassword = "[password]"
$X64CertPath = "c:\[certificate name].cer"
# set the onpremise domain that you added to Office 365
$SPCN = "sharepoint.domain.com"
# your onpremise SharePoint site url
$SPSite="http://sharepoint"
# don't change this value
$SPOAppID="00000003-0000-0ff1-ce00-000000000000"
# get the encrypted pfx certificate object
$PfxCert = New-Object System.Security.Cryptography.X509Certificates.X509Certificate2 $PfxCertPath, $PfxCertPassword, 20
# get the raw data
$PfxCertBin = $PfxCert.GetRawCertData()
# create a new certificate object
$X64Cert = New-Object System.Security.Cryptography.X509Certificates.X509Certificate2
# import the base 64 encoded certificate
$X64Cert.Import($X64CertPath)
# get the raw data
$X64CertBin = $X64Cert.GetRawCertData()
# save base 64 string in variable
$CredValue = [System.Convert]::ToBase64String($X64CertBin)
# connect to office 3656
Connect-MsolService
# register the on-premise STS as service principal in Office 365
# add a new service principal
New-MsolServicePrincipalCredential -AppPrincipalId $SPOAppID -Type asymmetric -Usage Verify -Value $CredValue
$MsolServicePrincipal = Get-MsolServicePrincipal -AppPrincipalId $SPOAppID
$SPServicePrincipalNames = $MsolServicePrincipal.ServicePrincipalNames
$SPServicePrincipalNames.Add("$SPOAppID/$SPCN")
Set-MsolServicePrincipal -AppPrincipalId $SPOAppID -ServicePrincipalNames $SPServicePrincipalNames
# get the online name identifier
$MsolCompanyInformationID = (Get-MsolCompanyInformation).ObjectID
$MsolServicePrincipalID = (Get-MsolServicePrincipal -ServicePrincipalName $SPOAppID).ObjectID
$MsolNameIdentifier = "$MsolServicePrincipalID@$MsolCompanyInformationID"
# establish the trust from on-premise with ACS (Azure Control Service)
# add a new authenticatio realm
$SPSite = Get-SPSite $SPSite
$SPAppPrincipal = Register-SPAppPrincipal -site $SPSite.rootweb -nameIdentifier $MsolNameIdentifier -displayName "SharePoint Online"
Set-SPAuthenticationRealm -realm $MsolServicePrincipalID
# register the ACS application proxy and token issuer
New-SPAzureAccessControlServiceApplicationProxy -Name "ACS" -MetadataServiceEndpointUri "https://accounts.accesscontrol.windows.net/metadata/json/1/" -DefaultProxyGroup
New-SPTrustedSecurityTokenIssuer -MetadataEndpoint "https://accounts.accesscontrol.windows.net/metadata/json/1/" -IsTrustBroker -Name "ACS"
Add a new result source
To get search results from SharePoint Online we have to add a new result source. Run the following script in a PowerShell ISE session on your SharePoint 2013 on-premise server. Don't forget to update the settings region
if(-not (Get-PSSnapin "Microsoft.SharePoint.PowerShell" -ErrorAction SilentlyContinue)){Add-PSSnapin "Microsoft.SharePoint.PowerShell"}
# region settings
$RemoteSharePointUrl = "http://[example].sharepoint.com"
$ResultSourceName = "SharePoint Online"
$QueryTransform = "{searchTerms}"
$Provier = "SharePoint-Remoteanbieter"
# region settings end
$SPEnterpriseSearchServiceApplication = Get-SPEnterpriseSearchServiceApplication
$FederationManager = New-Object Microsoft.Office.Server.Search.Administration.Query.FederationManager($SPEnterpriseSearchServiceApplication)
$SPEnterpriseSearchOwner = Get-SPEnterpriseSearchOwner -Level Ssa
$ResultSource = $FederationManager.GetSourceByName($ResultSourceName, $SPEnterpriseSearchOwner)
if(!$ResultSource){
Write-Host "Result source does not exist. Creating..."
$ResultSource = $FederationManager.CreateSource($SPEnterpriseSearchOwner)
$ResultSource.Name = $ResultSourceName
$ResultSource.ProviderId = $FederationManager.ListProviders()[$Provier].Id
$ResultSource.ConnectionUrlTemplate = $RemoteSharePointUrl
$ResultSource.CreateQueryTransform($QueryTransform)
$ResultSource.Commit()
Add a new query rule
In the Search Administration click on Query Rules
Select Local SharePoint as Result Source
Click New Query Rule
Enter a Rule name f.g. Search results from SharePoint Online
Expand the Context section
Under Query is performed on these sources click on Add Source
Select your SharePoint Online result source
In the Query Conditions section click on Remove Condition
In the Actions section click on Add Result Block
As title enter Results for "{subjectTerms}" from SharePoint Online
In the Search this Source dropdown select your SharePoint Online result source
Select 3 in the Items dropdown
Expand the Settings section and select "More" link goes to the following URL
In the box below enter this Url https://[example].sharepoint.com/search/pages/results.aspx?k={subjectTerms}
Select This block is always shown above core results and click the OK button
Save the new query rule

Hi Janik,
According to your description, my understanding is that you want to display hybrid search results in SharePoint Server 2013.
For achieving your demand, please have a look at the article:
http://technet.microsoft.com/en-us/library/dn197173(v=office.15).aspx
If you are using single sign-on (SSO) authentication, it is important to test hybrid Search functionality by using federated user accounts. Native Office 365 user accounts and Active Directory Domain Services
(AD DS) accounts that are not federated are not recognized by both directory services. Therefore, they cannot authenticate using SSO, and cannot be granted permissions to resources in both deployments. For more information, see Accounts
needed for hybrid configuration and testing.
Best Regards,
Eric
Eric Tao
TechNet Community Support

Exchange Online users logging into OWA On Premises.

Greetings!
We are implementing hybrid Exchange Online with Exchange 2013, and we face the following situation:
When an Exchange Online user tries to access through OWA on-premises, a page appears with a link to the Exchange Online OWA.
Is it supposed to be this way?
Why the redirection is not automatic?
Seems so obvious that the redirect should be automatic that if it is to be this way (the user having to click the link), there must be some technical justification. Can anyone refer me some article about it? For to convince the top brass of the company here
that it has to be like that!
Thanks in advance !!!
Fabio Martins MCDST/MCSA Brasil!!!

Hi
As per the information and details provided by you, to solve the problem of Exchange online users logging into OWA on Premises, please follow these steps: -
The user will be able to use the
OWA URL points to the on-premises Exchange 2013 server. On the redirection page, you can choose to
save the new URL to his browser favorites and click on the URL.
When clicking on the URL, the user will be taken through the authentication process. For OWA, that means that you can try to access his mailbox in Exchange Online &
Exchange online will redirect the user to “login.microsogtonline.com”, where
you can enter UPN.
Once the UPN is entered and you switches to the password field, Office 365 will detect that the UPN domain is federation with an Office 365 tenant. This result in a redirect
to the on-premises federation endpoint (in this case sts.clouduser.dk) and depending on whether the user is domain joined and domain-connected or uses an external client, you will get
single sign-on (SSO) or be required to enter your UPN and password.
Because of the organizational relationship that was set up between Exchange Online and Exchange on-premises during the Exchange hybrid configuration lookups when booking
meetings, mail tips, etc. also work as expected from Exchange Online to Exchange on-premises and vice versa.
I hope this information will be helpful for you.
Thanks and regards
Shweta@G

Exchange 2013 SP1 RU4 Public Folder Permissions

Hi All,
Exchange 2013 SP1 RU4 Public Folder Permissions
We have a weird problem after migrating our PF from Exchange 2010 to 2013.
Users do not have permission to create or delete in PF even thou they have owner permissions.
Example:-
I have created a '\test1' folder in the root which has the following permissions (this works OK):-
Myself - Owner
Default - Author
Anonymous - None
I have created another folder '\admin\test2' folder which has the same permissions as above but i get the "cannot create the folder. you don't have appropriate permissions to perform this operation"
I get this problem across all of the folders that were migrated. clean folders created at the root with the correct permission function as per expected.
Regards
Paul Sheldon

Hi,
I recommend you use the Get-PublicFolderClientPermission -Identity publicfolder command to check the client access permissions to a public folder.
If possible, please remove permission and re-add permission to check the result.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Calendar Sharing between 2 organisation Exchange 2010 SP3 and Exchange online with Federation Trust.

Hi...
Our company is running Exchange Server 2010 SP3 Standart would like to have Shared calendar with organisation running with Exchange online.
We made a Federation trust between organisations and I checked that one certificate was installed and the rule for their domain was created. but when I try to share my calendar I always receive.
"Calendar sharing is not available with the following contacts because of permission settings on your network."
Name I took from GAL or input manually and always same. Forgot to mention that we migrated from Exchange 2003 to 2010 SP3 and all old exchange servers I removed. I tried everything that I know and read and nothing helped.
Hope for your support.
Thank you.

1)I deleted everything and made step by step as indicated in your articles.
2) recreated organisation relationship:
RunspaceId : xxxxxxxxxx
DomainNames : {xxxxxxx.microsoftonline.com, xxxxxxxxx.onmicrosoft.com, xxxxxxx.com}
FreeBusyAccessEnabled : True
FreeBusyAccessLevel : LimitedDetails
FreeBusyAccessScope :
MailboxMoveEnabled : False
DeliveryReportEnabled : False
MailTipsAccessEnabled : False
MailTipsAccessLevel : None
MailTipsAccessScope :
TargetApplicationUri : outlook.com
TargetSharingEpr :
TargetOwaURL :
TargetAutodiscoverEpr : https://pod12312.outlook.com/autodiscover/autodiscover.svc/WSSecurity
OrganizationContact :
Enabled : True
ArchiveAccessEnabled : False
AdminDisplayName :
ExchangeVersion : 0.10 (14.0.100.0)
Name : xxx
DistinguishedName : CN=xxx,CN=Federation,CN=uxx,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=uxxx,DC=com
Identity : Lxx
Guid : a8xxx
ObjectCategory : upxxs.com/Configuration/Schema/ms-Exch-Fed-Sharing-Relationship
ObjectClass : {top, msExchFedSharingRelationship}
WhenChanged : 27/01/2015 3:23:47 PM
WhenCreated : 26/01/2015 9:41:39 AM
WhenChangedUTC : 27/01/2015 8:23:47 PM
WhenCreatedUTC : 26/01/2015 2:41:39 PM
OrganizationId :
OriginatingServer : xxx.upxxxns.com
IsValid : True
3. Configured Sharing Policies:
[PS] C:\Windows\system32>Get-SharingPolicy
Name Domains Enabled Default
Default Sharing Policy {*:CalendarSharingFreeBusySimple} True False
Lxxx {lxxx.com:CalendarSharingFreeBusy... True True
added my mail box to sharing policy but in the end receive same error
Calendar sharing is not available with the following contacts because of permission settings on your network.
In EventViewer everything seems to be fine....
No errors on policy creation... How can be checked this permission
settings on your network they are on exchange on in DC ?

Exchange Online Archive and Single Item recovery

We are currently looking to implement online archiving in Exchange 2010.
From my perspective, we are doing it to relocate the older messages to some cheaper storage, while making primary mailbox sizes are little more manageable.
Management however, want to ensure that once an item is moved to the online archive that it cannot be permanently deleted until after a 7 year retention period (for discovery purposes).
Journaling isn't an option at this point..
We have an Archive RPT which moves the items to the users archive after 90 days.
We have another RPT which will Delete items from the Archive after 7 years (Delete no Recovery).
We then have "Keep deleted Items for", set to 30 Days on the Primary Mailbox Database.
and then have "Keep deleted Items for", set to 7 years (2555 Days) on the Archive Database(this is so that items are not immediately deleted if the user manually deletes from the archive).
Obviously with this setup, users will be able to purge items from the "Deletions" sub folder (Recover Deleted Items) if they want to remove it from the archive.
My understanding is that if I enable Single Item Recovery for everyone, then the items that the user might remove from the "Deletions" sub folder will be transparently moved to the "Purges" sub folder, and are therefore discoverable
if required, up until the retention period of each database (30 days for Primary mailbox, 7 years for archive).
This sounds like exactly what we are after.
Thus my questions;
Apart from the obvious storage implications of doing this (7 years is alot of email), are there any other issues\risks associated with going down this method for email retention?
Is there a better way of achieving what we are after? I dont suppose we could completely restrict deletion access to the users archive completely for example?
If a user was to drag an item back into their primary mailbox.. and then delete it before the Managed Folder Assistant moved it back to the archive.. Would that be a potential hole in the retention requirement?
Thanking you all in advance for your insight..

You may want to use Litigation Hold to have users unable to delete the item permanently.
http://blogs.technet.com/b/exchange/archive/2011/08/16/retention-hold-and-litigation-hold-in-exchange-2010.aspx
I know it works on Active mailbox but not sure if the same attributes available for Archive Database. Just run the cmdlet and see if it can be done.
Where Technology Meets Talent

Exchange Online Protection and Public Folders

Hi,
We have just been migrated to Exchange Online Protection from FOPE and although users can now manage their own quarantines, they cannot do this for Mail Enabled Public Folders. Is this possible?
Many Thanks

Hi Paul,
I replied to a post from you in another thread. It's easy to miss though, so here's what I said:
"You should tell mail2web that there is an option in Exchange to hide public folders from IMAP clients. I'm an IT manager at a large software company with 50% of our users on Macs. We turned on the option to hide public folders from IMAP clients a while ago, long before the iPhone. It's worked very well and continues to work for iPhone people (like me!).
There was no reason for us to make public folders viewable via IMAP, so hopefully the same will be true for mail2web."
I'm actually really glad that Apple made this change. I want to see most of the folders at the inbox level in Exchange and with the Exchange switch turned on to hide public folders, there's no downside.
Regards,
fh

E71 Imap4 Exchange Public Folder Issue

Hi All,
I am trying to find a way to easily access a Public Folder on my E71.
We share Support e-mails via an Exchage Public Folder.
Mail for Exchange only accesses the Inbox which is disappointing for what is supposed to be a Corporate Application.
E-mail access via IMAP4 correctly shows all Folders/SubFolders EXCEPT none under "Public Folders/". I have checked that these are accessible via Windows Mail so I know that it should work.
Does anyone know why I can't see the folders under Public Folders or have a suggestion for accessing Public Folders on the E71 (preferably without recourse to 3rd Party Software). For a "Road Warrior" phone it does seem a glaring omission in functionality.
Thanks in advance,
Adam

Hi,
Please check the replica for "SCHEDULE+ FREE BUSY", right click the folder and then select Properties. In the Replication tab, please confirm there is a replica. If there is no replica, add one public folder database as a replica for the folder.
After that, please restart the Microsoft Exchange Mailbox Assistants service to check the result.
Best regards,
Belinda
Belinda Ma
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!"

How to change the Name and/or Alias of a Public Folder Mailbox in Exchange 2013

So when I migrated our servers from 2010 to 2013. I did not plan well and ended up with this.
Name                      Alias
Mailbox1                  PF1
Mailbox2                  Mailbox2
Mailbox3                  Mailbox3
As you can see the first mailbox is named PF1. I want to be able to change both the name and the alias, but have failed to find mechanism for doing so in ecp or powershell. Any assistance is greatly appreciated. I would also like to change the email address
for these as right now they are [email protected], [email protected], [email protected]
Thank you very much

Set-Mailbox -Identity Mailbox1 -PublicFolder -Name NewName1 -Alias NewName1 -PrimarySMTPAddress [email protected]
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Integration b/w Exchange 2010 SP2 and Exchange 9.1.1.7 connector

Has any succesfully integrated exchange 2010 sp2 with 9.1.1.7 conncetor ..
Sp2 is not in the certifcation list in the connector documentation .. just want to check if any one has done this before ..
Thanks

Hi Sembee,
We did this already.
We got it working now after doing above but with the shell.
First we confirmed if the mailbox is disabled with the following command: Get-MailboxStatistics -Database MBD01 | Where { $_.DisconnectReason -eq "Disabled" } | Format-List LegacyDN, DisplayName, MailboxGUID, DisconnectReason
It did show as disabled but when we try to enable it we got the following: This task does not support recipients of this type.
So we disabled the mailbox in the shell, enable it again and it was fine.
Get-MailboxStatistics -Database MBD01 | Where { $_.DisconnectReason -eq "Disabled" } | Format-List LegacyDN, DisplayName, MailboxGUID, DisconnectReason helped us, cause in the EMC exchange showed the user as enabled.
Thanks

Cascading Dropdown Menu with O365 and InfoPath 2013

Hello
I'm trying to resolve a situation where I have 2 dropdown lists in an InfoPath form on SharePoint for O365.
For example States and Cities, selecting State from DD1 displays the cities in that state in DD2. Should be fairly simple I know but unfortunately a real stumbling block for me.
I have found a good few examples on the web but I cant get them working, I'm wondering if this a snag with the O365 version.
Many thanks
Jon

Hi Jon,
Please refer to the following article.
Cascading Drop Down Lists in SharePoint/ Office 365 using REST
Please don't forget to mark it answered, if your problem resolved or helpful.

Exchange 2013 on-premises doesn't see Exchange Online profile pictures

Hello!
We are on an hybrid deployment with some users on Exchange 2013 on-premises and others on Exchange Online (Office 365 E3 plan). We have enabled photo sync (PhotosEnabled attribute) in the organization relationship, both on-premises and online, but while
Exchange Online users can see all profile pictures, Exchange on-premises can see only on-premises pictures.
It also looks like that online users can see only a low resolution version of on-premises users' pictures.
Do you have any idea how to troubleshoot or fix this, please?
Thanks!

... but Exchange Online doesn't copy his his-res photo to online AD. This would explain why on-premises users cannot see online photos, but vice versa works...
Hi,
Generally, if you upload a hi-res photo in Exchange Online, Exchange will automatically create a 48 pixel by 48 pixel version of that photo and update the user's thumbnailPhoto attribute. Note, however, that the reverse is not true: if
you manually update the thumbnailPhoto attribute in Active Directory, the photo in the user's Exchange 2013 mailbox will not automatically be updated.
Therefore, the user photo would be read by the following method in order:
1. The higher-resolution photo which is cached to 648 pixels by 648 pixels in Exchange Online\2013 used for Lync 2013.
2. The higher-resolution photo which is cached to 96 pixels by 96 pixels in Exchange Online\2013 used for OWA, Outlook and Lync 2013.
3. The low-resolution photo which is stored in the user’s ThumbnailPhoto attribute in Active Directory.
In your scenario, please upload a higher-resolution photo in OWA (Settings > Options > account > Edit information > photo > change) for a test Exchange Online user, wait for the photo updates in Exchange and AD. Then check whether this photo
can be viewed by other Exchange Online users and Exchange 2013 users.
Regards,
Winnie Liang
TechNet Community Support

Exchange online and Exchange 2010 on-premise calendar availability

I am running a hybrid exchange 2010 on-premise and online exchange environment. The online exchange users cannot see calendar availability of anybody on premise. The on-premise users can see the online exchange availability. I can see the
calendar if the calendar is shared, but trying to setup a meeting or calendar appointment still shows the unavailable through all days.
All of the users are using office 365 for outlook on premise and exchange online. If it is only working one way, could it be an autodiscover issue where it is not configured correctly on our on-premise exchange 2010 or online exchange? Which
side would be causing the issue?

I have done a little more research and ran the following in powershell:
[PS] C:\Windows\system32>Get-FederationInformation -domainname weiman.com
RunspaceId            : f4af09c7-134a-4fe7-95c0-acd120c63949
TargetApplicationUri : outlook.com
DomainNames           : {Weiman.onmicrosoft.com, weiman.com, Weiman.mail.onmicrosoft.com}
TargetAutodiscoverEpr : https://autodiscover-s.outlook.com/autodiscover/autodiscover.svc/WSSecurity
TokenIssuerUris       : {urn:federation:MicrosoftOnline}
IsValid               : True
[PS] C:\Windows\system32>Get-OrganizationRelationship | FL
RunspaceId            : f4af09c7-134a-4fe7-95c0-acd120c63949
DomainNames           : {herbertstanley.com, weiman.com, Weiman.mail.onmicrosoft.com}
FreeBusyAccessEnabled : True
FreeBusyAccessLevel   : LimitedDetails
FreeBusyAccessScope   :
MailboxMoveEnabled    : True
DeliveryReportEnabled : True
MailTipsAccessEnabled : True
MailTipsAccessLevel   : All
MailTipsAccessScope   :
TargetApplicationUri : outlook.com
TargetSharingEpr      :
TargetOwaURL          : http://outlook.com/owa/herbertstanley.com
TargetAutodiscoverEpr : https://pod51043.outlook.com/autodiscover/autodiscover.svc/WSSecurity
OrganizationContact   :
Enabled               : True
ArchiveAccessEnabled : True
AdminDisplayName      :
ExchangeVersion       : 0.10 (14.0.100.0)
Name                  : On Premises to Exchange Online Organization Relationship
DistinguishedName     : CN=On Premises to Exchange Online Organization Relationship,CN=Federation,CN=WEIMAN,CN=Microsof
                        t Exchange,CN=Services,CN=Configuration,DC=herbertstanley,DC=com
Identity              : On Premises to Exchange Online Organization Relationship
Guid                  : 26b4ec5d-fe93-473e-b451-1f9aa2e94ebb
ObjectCategory        : herbertstanley.com/Configuration/Schema/ms-Exch-Fed-Sharing-Relationship
ObjectClass           : {top, msExchFedSharingRelationship}
WhenChanged           : 1/13/2014 1:25:54 PM
WhenCreated           : 12/17/2013 1:04:32 PM
WhenChangedUTC        : 1/13/2014 7:25:54 PM
WhenCreatedUTC        : 12/17/2013 7:04:32 PM
OrganizationId        :
OriginatingServer     : gemini.herbertstanley.com
IsValid               : True
I am not sure why we have that value for the OriginatingServer. That server is a backup domain controller, not the server that houses the on-premise exchange.
I then ran the set-OrganizationRelationship and get the below error.
[PS] C:\Windows\system32>Set-OrganizationRelationship -Identity weiman.mail.onmicrosoft.com -targetapplicationUri outloo
k.com -TargetAutodiscoverEpr https://pod51043.outlook.com/autodiscover/autodiscover.svc/WSSecurity
The operation couldn't be performed because object 'weiman.mail.onmicrosoft.com' couldn't be found on 'gemini.herbertst
anley.com'.
    + CategoryInfo          : NotSpecified: (0:Int32) [Set-OrganizationRelationship], ManagementObjectNotFoundExceptio
   n
    + FullyQualifiedErrorId : F2215CB2,Microsoft.Exchange.Management.SystemConfigurationTasks.SetOrganizationRelations
   hip
How do I change the originating server to be my exchange server?

MT Exchange 2013 and Public Folder Limits

So having some real trouble trying to digest this data from a multi-tenant perspective.
Total public folders in hierarchy
10,000
Although you can create more than 10,000 public folders, it isn’t supported. Create
a Public Folder
Sub-folders under the parent folder
10,000
Although you can create more than 10,000 sub-folders under a parent folder, it isn’t supported.FolderHierarchyChildrenCountReceiveQuota parameter on the Set-Mailbox cmdlet.
So if my hierarchy consists of root folders 0-9,A-Z. Then below those top levels I place tenant domain level folders. Then below that I actually have folders for tenant data. Which of the above category applies? Sub-folders under
the parent folder is somewhat misleading? Does that mean in my above scenario I would only have 36 "parent" folders then would be able to have a total of 10k subfolders under those parents?
Or does it effectively mean 10k folders, that is all. One parent folder and 9,999 sub-folders? Or some combination of the two?
I had very high expectations for the redesigned public folders with incorporation into the DAG, but this solution seems MUCH less scalable and flexible then the legacy design. Additionally the recommendation of 2k concurrent users per PF mailbox, with
a max number of PF mailboxes at 100 effectively sets an org limit of 200k total mailboxes.
I can't help but feel this is just another nail in the coffin of non O365 Exchange resellers.

Hi,
Based on my research, the public folder size can be up to 100GB in the hosted Exchange 2013 environment:
http://www.wisnet.com/blog/hosted-exchange-2013-is-available-now/
As long as the total number is beyond the limit, we can at most have 100 public folder mailboxes ,10k public folders, 10k subfolders under one public folder and 200 concurrent users for one public folder mailboxes.
For more information about the public folders in Exchange 2013, you can refer to the following articles:
Public folders
http://technet.microsoft.com/en-us/library/jj150538(v=exchg.150).aspx
FAQ: Public Folders
http://technet.microsoft.com/en-us/library/jj552408.aspx
Public folders in the new Office
http://blogs.technet.com/b/exchange/archive/2012/11/08/public-folders-in-the-new-office.aspx
Exchange 2013 Modern Public Folders
http://windowsitpro.com/blog/exchange-2013-modern-public-folders
Public Folder Hierarchy and PF Mailboxes for Hosted setup
http://social.technet.microsoft.com/Forums/exchange/en-US/e9062abe-f484-462b-bc5e-ebdcb0862760/public-folder-hierarchy-and-pf-mailboxes-for-hosted-setup
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make
sure that you completely understand the risk before retrieving any suggestions from the above link.
If you have any question about Exchange server, please feel free to let me know.
thanks,
Angela Shi
TechNet Community Support

Exchange Online (O365) and Exchange 2013 On-Premise, Public Folder issues?

Similar Messages

Maybe you are looking for