Quantcast
Channel: Exchange Server 2013 - Setup, Deployment, Updates, and Migration forum
Viewing all articles
Browse latest Browse all 7129

Legacy proxy PF vs Migrate PF

$
0
0

Hi guys. Durring cooexistence EX2010 & EX2013 we have followed this instructions for LEGACY PUBLIC FOLDERS enablement:

https://technet.microsoft.com/en-us/library/dn690134%28v=exchg.150%29.aspx?f=255&MSPPError=-2147217396

One of the commands that we needed to run was also:

Set-OrganizationConfig -PublicFoldersEnabled Remote -RemotePublicFolderMailboxes ProxyMailbox1-on-ex2010

Now after we have already migrated all the users (and arbitration mailboxes) from ex2010 -> ex2013 we are in phase of moving public folders and we are following this instructions:

https://technet.microsoft.com/en-us/library/dn912663(v=exchg.150).aspx

Now the thing that concerns me is:

Step 7: Finalize the public folder migration (downtime required)
Set-OrganizationConfig -PublicFoldersEnabled Remote

As you can see we are using the same command as we did on settin' up "Proxy-legacy-public-folder".

Durring the cooexistence we have also ran this command:

Set-OrganizationConfig -PublicFoldersEnabled Local

So current settings are that PublicFoldersEnabled is set on LOCAL.

Now the thing is that if we run Get-

OrganizationConfig | fl on exchange 2013 we see that RemotePublicFolderMailboxes is still pointing to "ProxyMailbox1-on-ex2010" because that configuration was done durring "Proxy-legacy-public-folder".

What changes do you need to do if you have done Proxy legacy public folder and now you are in the PF migration process? We should probably "empty/clear" that -RemotePublicFolderMailboxes parameter which is pointing to "ProxyMailbox1-on-ex2010", right?

with best regards


bostjanc



Viewing all articles
Browse latest Browse all 7129

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>