Migration, open standards & exit — found from sitemap — grommunio

Cited by

Facts read from this source

• Pff export sources Report an error

  “.pst files can be generated with Outlook interactively .ost files can be taken from C:Users... .pst files can be also generated from an Exchange Server's PowerShell in a mostly unattended fashion”

• Pff2mt import Report an error

  “On the grommunio system, PFF files can be imported on the command-line with gromox-pff2mt and gromox-mt2exm. These are two commands meant to be chained together by way of a pipe”

• Exchange2grommunio script Report an error

  “For migrating many mailboxes, grommunio ships a PowerShell script — exchange2grommunio.ps1 — that automates the whole flow end to end.”

• Script workflow Report an error

  “For every selected mailbox the script: Exports the mailbox to a .pst with New-MailboxExportRequest onto a shared folder that the Exchange subsystem can write to. Reaches the grommunio server over SSH (using plink.exe), where the same folder is mounted (mount.cifs), and imports the .pst. Optionally deletes the .pst afterwards to save space, and records the result.”

• Script resume tracking Report an error

  “Successful imports are written to exchange2grommunio.done and failures to exchange2grommunio.failed, so a run can be resumed or retried.”

• Prerequisites ldap Report an error

  “grommunio is attached to the same LDAP/AD as Exchange, so users resolve on both sides (test LDAP before importing).”

• Prerequisites windows Report an error

  “The script is run from an elevated Exchange Management Shell (Windows Server 2012 R2 or newer, PowerShell 2.0+; 3.0+ is recommended so Linux command output is captured in the logs).”

• Prerequisites shared folder Report an error

  “A shared folder (UNC path) that the Exchange subsystem can write to and that the grommunio server can mount (cifs-utils installed), with enough space for the .pst files.”

• Mailbox selection Report an error

  “Allow-list: set $ImportMboxes (an array of addresses) or, if it is empty, the script reads addresses from the exchange2grommunio.import file on the share. Leaving both empty migrates all mailboxes. Deny-list: $IgnoreMboxes / the exchange2grommunio.ignore file exclude mailboxes (always honored).”

• Mailbox creation modes Report an error

  “$false $false Migrate into existing mailboxes, one by one $true $false Create then migrate each mailbox in turn $true $true Two-pass: create all mailboxes first, then run again with both set to $false to migrate the data”

• Two pass recommendation Report an error

  “The two-pass mode is recommended for large migrations: users can start working in grommunio immediately with empty mailboxes (new mail arrives normally) while the historical data is imported in the background.”

• Stop marker Report an error

  “To stop gracefully, create the stop-marker file (exchange2grommunio.STOP) on the share — the script finishes the current mailbox and then exits.”

• Import list generation Report an error

  “gromox-mbop foreach.mb echo-username > /mnt/pst/exchange2grommunio.import”

Scores citing this record

• The Data Protection Officer Migration, open standards & exit
• The IT Administrator Migration, open standards & exit
• The IT Service Provider Migration, open standards & exit
• The Public Sector IT Lead Migration, open standards & exit
• The Skeptic Migration, open standards & exit
• The Small Firm Owner Migration, open standards & exit