Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1334
  • Last Modified:

Public Folder Migration Error - from 2007 to Office 365

Good afternoon all –

We are attempting to migrate Public Folders from an Exchange 2007 sever running on 2008 small business server to Office 365 Online (Exchange 2013) using PowerShell. We have followed the “Migrate Legacy Public Folders to Exchange Online” from the following link http://technet.microsoft.com/en-us/library/jj983799(v=exchg.150).aspx When we run the PowerShell script from part 5 of Step 5, (please see below script) we get an error on “RemoteMailboxServerLegacyDN” (please see below error). In Part 3b of Step 5, the document asks for the following -

$source_remoteMailboxLegacyDN = "/o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=Administrator"

Which we got from running the:  Get-Mailbox <PublicFolder_Administrator_Account> | Select-Object LegacyExchangeDN from part 2a of Step 5.

Has anyone tried this before? If so have you seen and resolved this error?
Thank you for any help you can provide.

Dave…

Start of Script –
New-PublicFolderMigrationRequest -OutlookAnywhereHostName: $source_OutlookAnywhereExternalHostName -CSVData (Get-Content Folder2MapPath52013 -Encoding Byte) -RemoteCredential: $source_credential -RemoteMailboxLegacyDN: $source_remoteMailboxLegacyDN -RemoteMailboxServerLegacyDN: $source_remotePublicFolderServerLegacyDN -AuthenticationMethod Basic
End of Script –

Start of error -
Cannot validate argument on parameter 'RemoteMailboxServerLegacyDN'. The argument is null or empty. Supply an argument that is not null or empty and then try the command again.
    + CategoryInfo : InvalidData: (:) [New-PublicFolderMigrationRequest], ParameterBindingValidationException
    + FullyQualifiedErrorId : ParameterArgumentValidationError,New-PublicFolderMigrationRequest
End of error -
0
CMITStamford
Asked:
CMITStamford
  • 3
1 Solution
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
$source_remoteMailboxLegacyDN -RemoteMailboxServerLegacyDN:

Where is the DN of the Server mentioned ?

- Rancy
0
 
CMITStamfordAuthor Commented:
Hi Rancy,

Thank you for your post here. We have come up with an alternative solutions to this problem. We are simply going to export all public folders as PST and then import them.

We have tested this solution and it works for our needs.

Again, thank you,

Dave...
0
 
CMITStamfordAuthor Commented:
Used another solution.
0
 
LANWorxCommented:
This is a mistake in the MS documentation.

Replace " -RemoteMailboxServerLegacyDN: $source_remotePublicFolderServerLegacyDN " with "-RemoteMailboxServerLegacyDN: $source_remotePublicFolderServerLegacyFQDN"
0
 
CMITStamfordAuthor Commented:
Thank you for this update. I will try this solution during our next migration.
0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now