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

Please make sure that you run this command as Administrator and the Administrator in the Organization Management and Server Management .

Please also try to run this command with one publicfoldermailbox, like ProxyMailbox1 only.

Thanks

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

• Edited by NipTuck170 15 hours 38 minutes ago

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

• Edited by NipTuck170 Thursday, March 05, 2015 4:40 PM

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

• Edited by NipTuck170 Thursday, March 05, 2015 4:40 PM

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

• Edited by NipTuck170 Thursday, March 05, 2015 4:40 PM

I too am getting the same error. I can see the mailbox if I run get-mailbox, so I know it exists. If you find an answer I hope you post it here.

I only have one and it's named PFMailbox1. It resides in a new mailbox database inside the same storage group and on the same server as our exchange 2007 public folders database.

When I run Get-Mailbox PFMailbox1 from either the exchange 2007 or 2013, it returns the mailbox. When I run 'Set-OrganizationConfig -PublicFoldersEnabled Remote -RemotePublicFolderMailboxes PFMailbox1' from exchange 2013, I get the message 'Couldn't find object "PFMailbox1". Please make sure that is was spelled correctly or specify a different object.'

Is PFMailbox1 the alias name? Can you confirm it has been sycned to Office 365 with get-mailuser PFMailbox1?

I only have one and it's named PFMailbox1. It resides in a new mailbox database inside the same storage group and on the same server as our exchange 2007 public folders database.

When I run Get-Mailbox PFMailbox1 from either the exchange 2007 or 2013, it returns the mailbox. When I run 'Set-OrganizationConfig -PublicFoldersEnabled Remote -RemotePublicFolderMailboxes PFMailbox1' from exchange 2013, I get the message 'Couldn't find object "PFMailbox1". Please make sure that is was spelled correctly or specify a different object.'

Is PFMailbox1 the alias name? Can you confirm it has been sycned to Office 365 with get-mailuser PFMailbox1?

It's a single domain forest. Same error with quotes.

Couldn't find object "PFMailbox1". Please make sure that it was spelled correctly or specify a different object.

To be on the safe side I also tried with ViewEntireForest set to true and still got the same error.

and PFMailbox1 is a "user Mailbox", not another type? 

get-mailbox PFMailbox1 |FL *type*

I havent had a need to do this, but if you 

Set-OrganizationConfig -RemotePublicFolderMailboxes PFMailbox1@domain.com 

does that work?

It's a single domain forest. Same error with quotes.

Couldn't find object "PFMailbox1". Please make sure that it was spelled correctly or specify a different object.

To be on the safe side I also tried with ViewEntireForest set to true and still got the same error.

and PFMailbox1 is a "user Mailbox", not another type? 

get-mailbox PFMailbox1 |FL *type*

I havent had a need to do this, but if you 

Set-OrganizationConfig -RemotePublicFolderMailboxes PFMailbox1@domain.com 

does that work?

PFMailbox1 is the Name and the Alias. We're doing an on-premises install (not hybrid) and used the instructions listed on https://technet.microsoft.com/en-us/library/dn690134(v=exchg.150).aspx. When I try to run "Get-MailUser PFMailbox1" on either server (2007 or 2013) I get an error. For 2013, the error is "The operation couldn't be performed because object  'PFMailbox1' couldn't be found on '<DOMAIN_CONTROLLER_HERE>'". For 2007, the error is "Get-MailUser : PFMailbox1 is not a mail-enabled user". The instructions I mentioned above had me create a mailbox not a mailuser, which explains Get-MailUser erroring out; should I have created a mailuser instead?

Ah, ok. I assumed you were doing this for hybrid.

So, yes, get-mailbox is the correct command.

So if this is multi-domain forest ensure you are scoped to the entire forest

Set-ADServerSettings -ViewEntireForest $true

For the actual command:

Can you try it with quotes around the mailbox name?

Set-OrganizationConfig -RemotePublicFolderMailboxes "ProxyMailbox1"

It's a single domain forest. Same error with quotes.

Couldn't find object "PFMailbox1". Please make sure that it was spelled correctly or specify a different object.

To be on the safe side I also tried with ViewEntireForest set to true and still got the same error.

It's a single domain forest. Same error with quotes.

Couldn't find object "PFMailbox1". Please make sure that it was spelled correctly or specify a different object.

To be on the safe side I also tried with ViewEntireForest set to true and still got the same error.

[PS] C:\Windows\system32>get-mailbox PFMailbox1 | fl *type*

ResourceType         :
RemoteRecipientType  : None
RecipientType        : UserMailbox
RecipientTypeDetails : UserMailbox

Same error when using Principal name (@domain.local) and SMTP address (@domain.com). Tested with and without quotes.

[PS] C:\Windows\system32>get-mailbox PFMailbox1 | fl *type*

ResourceType         :
RemoteRecipientType  : None
RecipientType        : UserMailbox
RecipientTypeDetails : UserMailbox

Same error when using Principal name (@domain.local) and SMTP address (@domain.com). Tested with and without quotes.

I only have one and it's named PFMailbox1. It resides in a new mailbox database inside the same storage group and on the same server as our exchange 2007 public folders database.

When I run Get-Mailbox PFMailbox1 from either the exchange 2007 or 2013, it returns the mailbox. When I run 'Set-OrganizationConfig -PublicFoldersEnabled Remote -RemotePublicFolderMailboxes PFMailbox1' from exchange 2013, I get the message 'Couldn't find object "PFMailbox1". Please make sure that is was spelled correctly or specify a different object.'

I only have one and it's named PFMailbox1. It resides in a new mailbox database inside the same storage group and on the same server as our exchange 2007 public folders database.

When I run Get-Mailbox PFMailbox1 from either the exchange 2007 or 2013, it returns the mailbox. When I run 'Set-OrganizationConfig -PublicFoldersEnabled Remote -RemotePublicFolderMailboxes PFMailbox1' from exchange 2013, I get the message 'Couldn't find object "PFMailbox1". Please make sure that is was spelled correctly or specify a different object.'

[PS] C:\Windows\system32>get-mailbox PFMailbox1 | fl *type*

ResourceType         :
RemoteRecipientType  : None
RecipientType        : UserMailbox
RecipientTypeDetails : UserMailbox

Same error when using Principal name (@domain.local) and SMTP address (@domain.com). Tested with and without quotes.

• Edited by RazörEdge 12 hours 47 minutes ago Fixed some typos

• Edited by Trece Henrie 12 hours 27 minutes ago misspelling

I ended up leaving the config as default and testing PF access after a move. 2013 users were able to see 2007 PFs just fine without this command. I'm working with a SLD so I suspect its causing the command to fail but I'm not clear what this procedure is for is it works without it.

• Edited by RazörEdge Thursday, June 18, 2015 6:40 PM Fixed some typos

• Edited by RazörEdge Thursday, June 18, 2015 6:40 PM Fixed some typos

• Edited by Trece Henrie Thursday, June 18, 2015 7:00 PM misspelling

• Edited by Trece Henrie Thursday, June 18, 2015 7:00 PM misspelling

No its $null

Ok, so in that case, it sounds as if the 2013 servers are still using the legacy code to find the PFs. You can verify in the Outlook autodiscovery response and see if the PublicFolderInformation section contains the SMTP address of the PF Proxy Mailbox, which it shouldn't in this case.

If you are on 2013 CU7 and above, then its important to make the change to the new config, otherwise, PF access from Outlook may not work in the future.

I would consider opening a ticket with Microsoft if you cant get those commands to work.

No its $null

Ok, so in that case, it sounds as if the 2013 servers are still using the legacy code to find the PFs. You can verify in the Outlook autodiscovery response and see if the PublicFolderInformation section contains the SMTP address of the PF Proxy Mailbox, which it shouldn't in this case.

If you are on 2013 CU7 and above, then its important to make the change to the new config, otherwise, PF access from Outlook may not work in the future.

I would consider opening a ticket with Microsoft if you cant get those commands to

No its $null

Ok, so in that case, it sounds as if the 2013 servers are still using the legacy code to find the PFs. You can verify in the Outlook autodiscovery response and see if the PublicFolderInformation section contains the SMTP address of the PF Proxy Mailbox, which it shouldn't in this case.

If you are on 2013 CU7 and above, then its important to make the change to the new config, otherwise, PF access from Outlook may not work in the future.

I would consider opening a ticket with Microsoft if you cant get those commands to

No its $null

Ok, so in that case, it sounds as if the 2013 servers are still using the legacy code to find the PFs. You can verify in the Outlook autodiscovery response and see if the PublicFolderInformation section contains the SMTP address of the PF Proxy Mailbox, which it shouldn't in this case.

If you are on 2013 CU7 and above, then its important to make the change to the new config, otherwise, PF access from Outlook may not work in the future.

I would consider opening a ticket with Microsoft if you cant get those commands to

No its $null

Ok, so in that case, it sounds as if the 2013 servers are still using the legacy code to find the PFs. You can verify in the Outlook autodiscovery response and see if the PublicFolderInformation section contains the SMTP address of the PF Proxy Mailbox, which it shouldn't in this case.

If you are on 2013 CU7 and above, then its important to make the change to the new config, otherwise, PF access from Outlook may not work in the future.

I would consider opening a ticket with Microsoft if you cant get those commands to