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?
Thanks

There 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."

Similar Messages

Public folders in hosted Exchange 2013

Hi,
Is it possible to setup public folders for a tenant i Exchange 2013, eg. with custom id 0 set or something like that?
Thanks!

Hi,
If you want to deploy public folders in an Exchange 2013 multi-tenant environment, you can create a public folder mailbox per tenant.
Here is a related thread for your reference.
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?forum=exchangesvradmin
More information about public folder in Exchange 2013 here:
http://technet.microsoft.com/en-us/library/jj552408.aspx
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Problem with Exchange 2010 Public Folders after installing Exchange 2013 in my environment.

I currently have an Exchange 2010 server with all the roles installed. Before installing Exchange 2013, I was able to launch the Public Folder Management Console but now I get an error. When I installed Exchange 2013, I got an error saying I
had a instance of Exchange 2000 or Exchange 2003, but I didn't have any of these servers left. There was still something in AD referencing my old server. I went into ADSIedit and deleted an old administrative group. This deletion caused my access
to my public folders to get messed up. I followed this article, http://blog.bruteforcetech.com/archives/766, and I was able to gain access back in my outlook client but I still can't see the public folders in OWA. I also get this error when
trying to access either Default or System Public Folders. "Cannot complete the operation because there isn't an available public folder database on server 'ExchangeServer'. It was running the command 'get-publicfolder - getchildren -identity '\'
-server 'ExchangeServer' "
My Public Folder Database exists and is mounted. Any help is appreciated.

Hi Belinda,
Thank you for responding. Yes you do understand my problem correctly. One correction is that after deleting this entry in ADSIEdit, we couldn't access public folders at all either in Outlook or OWA. I followed these steps in the below article:
http://blog.bruteforcetech.com/archives/766
After following these steps and recreating the entry on FolderHieachies in ADSI edit, I was able to gain access to the public folders again through Outlook, but still can't see them in OWA and can't access them in Public Folder Management Console.
Here are the results to your requests:
et-PublicFolder -Recurse | Format-List Name
Name : IPM_SUBTREE
Can't get the public folder database using legacy distinguished name '/O=HEROIX CORPORATION/OU=EXCHANGE ADMINISTRAT
GROUP (FYDIBOHF23SPDLT)/CN=CONFIGURATION/CN=SERVERS/CN=EXCHANGE2010/CN=MICROSOFT PUBLIC MDB'.
+ CategoryInfo : NotSpecified: (:) [Get-PublicFolder], TaskInvalidOperationException
+ FullyQualifiedErrorId : B546E0B0,Microsoft.Exchange.Management.MapiTasks.GetPublicFolder
[PS] C:\Windows\system32>Get-PublicFolder -Identity \NON_IPM_SUBTREE -Recurse | Format-List Name
Name : NON_IPM_SUBTREE
Name : EFORMS REGISTRY
Can't get the public folder database using legacy distinguished name '/O=HEROIX CORPORATION/OU=EXCHANGE ADMINISTRATIVE
GROUP (FYDIBOHF23SPDLT)/CN=CONFIGURATION/CN=SERVERS/CN=EXCHANGE2010/CN=MICROSOFT PUBLIC MDB'.
+ CategoryInfo : NotSpecified: (:) [Get-PublicFolder], TaskInvalidOperationException
+ FullyQualifiedErrorId : B546E0B0,Microsoft.Exchange.Management.MapiTasks.GetPublicFolder
Also the msExchOwningPFTree attribute should be correct because this was edited with the correct value when I followed the instructions in the above article:
CN=Public Folders,CN=Folder Hierarchies,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=Heroix Corporation,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=hero,DC=net

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

Multiple Exchange 2013 SSL Certificates & Web Services URLs

I have two Exchange 2013 CU5 Standard servers in a DAG. Both servers have both the CAS and Mailboxes roles installed.
The servers are running Server 2012 Standard. The DAG uses a file share witness server.
The witness server and one Exchange server, which is usually the active server, are on the same subnet in our primary data centre.
The second Exchange server is on a different subnet in our backup data centre across town.
The domain that these servers are in is part of a forest with another domain.
That domain is, physically, in another jurisdiction. The domains share a namespace.
All users in both domains have username at name.com as their e-mail address.
The other domain has two Exchange 2013 servers in a DAG. It also has one Exchange 2007 server, that is being phased out.
All messages that my domain users send to external recipients pass though the Exchange servers in my domain, a firewall for my domain, an Internet connection, a firewall in the other domain, the Exchange servers in the other domain, the firewall for
the other domain, and then out to the external recipients. The reverse path is followed for inbound mail from external senders.
All ActiveSync traffic for my users passes through the Exchange servers and a proxy server in the other domain.
I have a self-signed SAN certificate on the Exchange servers in my domain.
That certificate is also deployed on all of the mobile devices that my users have.
I have been asked to see if I can set things up so that a test user can send and receive e-mail with their mobile device, and have that traffic go from my Exchange servers, through the firewall for my domain, and out to external recipients.
Due to a lack of test systems, I have been asked to develop this on my production servers, without disrupting the existing mail flow.
Is that possible? What would need to be done to accomplish this?
If the test is possible, and successful, my Exchange servers, and all other relevant systems, would be changed so that all mail traffic from my domain no longer goes through the other domain.

You could set a test send connector for @outsidedomain.com to use your Exchange servers as source servers, and make sure you have at least one reverse DNS entry (PTR) in place for whatever IP your external firewall presents to the world for the Exchange
servers. This is critical in order not to have the rest of the world discard your emails (spammers usually fail the reverse DNS name).
For incoming traffic, you could use a DNS domain that you own and that's not in use currently (eg oldcompany.com belonging to someone your current employer purchased) and have an MX record for this pointing to the public IP address(es) of the published Exchange
servers.
However mail routing cannot be done to work one way with mobile devices and another way with Outlook. In this case both ActiveSync and Outlook are simply interfaces to send/receive emails using your common SMTP infrastructure. So once configured for the
test as above, both ActiveSync, Outlook, OWA, EWS clients will send/receive emails in the same way. In the example above - anyone sending to @outsidedomain.com, regardless it's the users hosted on your Exchange servers or the ones in the other domain, will
be sent using the new route.

Public Folders on Microsoft Exchange

Is there a way to access public folders on Microsoft Exchange. This can be any version of ColdFusion and any version of Exchange. Right now I have CF9 and Exchange 2007, but we are looking to upgrade to CF10 and Exchange 2013.

UPDATE: (WORKING)
I tried Mihir's suggestion to change the ownership to the SERVERNAME$ for the objects within the CN=Microsoft Exchange System Objects container. I could not check the actual owner on any new folders as they will not appear in this container until they are
mail enabled. (Of which I cannot mail enable them)
On trying to change the owner from SYSTEM which is what it is on seemingly all objects, whilst I could select the Exchange server from the list, the setting would not take. (The SERVERNAME$ never appears in the list of possible owners after selecting it)
Instead I tested giving the Exchange Server (SERVERNAME$) full control permission on one of the objects/Public Folders. (Via ADSIEdit) This immediately allowed me to change as properties for the folder to include Send-As. (At last!!)
To fully resolve all permission issues, noting the Exchange server is a member of the Exchange Trusted Subsystem Group, I gave this group full control permissions on the CN=Microsoft Exchange System Objects folder and this resolved ALL permission issues
to include being able to create new folders, mail enable them etc.
No reboots/logoff etc were required, the settings are taken immediately. (Mileage may vary with replication)
Many thanks for getting me on the right track.

How to migrate public folders from legacy (exchange 2003 ) to exchange 2010

How to migrate public folders from legacy (exchange 2003 ) to exchange 2010 . Please suggest ?
Aditya Mediratta

Hi Aditya,
please find the answer in
http://blogs.technet.com/b/agobbi/archive/2010/08/04/how-to-move-public-folder-from-exchange-2003-to-exchagne-2010.aspx
Please ensure you have a working mailflow from Exchange 2003 to 2010, vice versa, before you begin.
Basically it's the same procedure as adding some PF Database in E2K3; just
run .\AddReplicaToPFRecursive.ps1 -server "Exchange 2010 Server" -TopPublicFolder "\" -ServerToAdd "Exchange 2010 Server"
Wait until some initial data started to replicate; after that run
Update-PublicFolderHierarchy -Server "Exchange 2010 Server"
After replication has finished you can do a
.\MoveAllReplicas.ps1 -Server "Exchange 2003 Server" -NewServer "Exchange 2010 Server"
Please let me know if it worked.
Kind regards,
Martin

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 regards

Hi,
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

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?
Thanks

Hello,
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

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!

Probling with Throttling of Emails by Exchange 2013 servers

We are experiecing delay of emails for users because of the Throttlig on Exchange 2013 servers.
This is causing company wide Delay and users are complaining as it takes a lot of time for the queue to get cleared.
We called in Microsoft and they suggested some values changes to msexchangedelivery.exe.config file
We added the following values, but still we face issues when there is Email flood.
Any one faced this or any suggestions that you have.
mdimthyas

Hi mdimthyas,
Thank you for your question.
Could you tell more details which throttling was configured on Exchange 2013 in organization?
Could you tell me how long was emails in the queue?
Are there any other issue which could help us troubleshoot.
We could remove the customized throttling and re-configure it to check if the issue persist.
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim
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]
Jim Xu
TechNet Community Support

Accounts made in o365 can't access legacy public folders - Migrated through 2010/2013 Hybrid can access

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

Migrate only a selection of public folders from 2007 to 2013

Like the subject says- I've been asked to move a small selection only from 2007 to 2013. Essentially out of 4700 public folders they only want to migrate 170. I've always just moved them all and can't think of a way to do this. I can't just delete
the rest of the public folders on 2007- they want to keep them for a short while just in case they've screwed their logic. (They are relying on LastModifiedTime- no access in the last 6 months).
Any Suggestions?
regards
Tony

I agree with Gary that with the MS default process this is true, however if you are open to 3rd party products Lucid8's DigiScope would allow you to open an Offline Copy of the 2007 PF, Filter out what you don't want to copy and then restore the balance
of folders from the offline EDB directly into the 2013 PF.
And of course you could also export the 170 folders to PST and then import to 2013 however that could get a bit ugly...
Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline Exchange Mailbox and Public Folder EDB's and Live Exchange Servers or Import/Migrate direct from Offline EDB to Any Production Exchange Server, even cross version i.e. 2003
--> 2007 --> 2010 --> 2013 with Lucid8's
DigiScope

Method to use Set-EventLogLevel against all the Exchange 2013 servers.

Recently Ran into an issue where we needed to troubleshoot an issue that required us to turn up the logging level across multiple exchange servers using the Set-EventLogLevel command.
I was trying to figure out a way to run this command without having to go to each of the exchange servers.
PSSession doesn't work because then your not running the exchange commandlets on that remote system.
Invoke-Command doesn't work either.
Unfortunately because of some security settings using Connect-ExchangeServer doesn't proxy in the command either.
So any ideas on how we can execute an exchange cmdlet against multiple exchange servers from powershell.
Jeff C

I can set it via this method on Exchange 2010, I don't have Exchange 2013 in front of me but it should be same I believe.
This will set MSExchangeIS\9000 Private\Logons level from Lowest to Low of all the Exchange server in my environment
$test = Get-ExchangeServer
$test | %{Set-eventloglevel "$_\MSExchangeIS\9000 Private\Logons" -Level Low}
To see if those are set or not run this...
$test | %{get-eventloglevel "$_\MSExchangeIS\9000 Private\Logons"}
Blog
|
Get your Exchange Powershell Tip of the Day from here

Public folders in Mixed Exchange environment

We are running
- Exchange 2007 - a LOT of users and a LOT of PF
- Exchange 2010 ( currently very limited )
- Exchange 2013 - about 2000 users
The Exch 2010 environment was pretty much stood up and had 30 pilot accounts on it before we decided to go to Exch 2013 instead/ These account have since been migrated to Exch 2013, so it is currently VERY LIMITED use.
We have a large number of Public Folders in Exch 2007. We do not plan on using the Exch 2013 model of shared mailboxes, but are looking to create the Public Folders in the Exch 2010 environment so we can close down Exch 2007.
The bulk of my users are still on 2007, but I have a couple thousand already moved to 2013. All users can access the Public Folders on Exch 2007.
We have not created any Public Folders in Exch 2010 yet. Practically all the posts I read state to enable replication for the 2007 folders to get them to 2010, but what about NEW folders. If I create a new folder on Exch 2010, without configuring replication
to 2007, will the Exch 2007 and Exch 2013 users be able to access it?
Tom

For Exchange 2010 or Ex2007 you will need to setup the replication but for Exchange 2013 it is different.
what is your plan,, do you want to keep them on 2013 or 2010 or you want keep the mix environment?
If I create a new folder on Exch 2010, without configuring replication to 2007, will the Exch 2007 and Exch 2013 users be able to access it? Yes you can still access them. You will need to setup the database for the default public folders.
Where Technology Meets Talent

Public Folders on multiple Exchange 2013 servers

Similar Messages

Maybe you are looking for