During the migration, PowerShell sessions are opened with Office 365 for backend processes. If these PowerShell sessions are closed without NME's knowledge, then the following error may be seen:
19:01:36 AdFwd::Init() - PowerShell Result: Processing data from remote server pod51044psh.outlook.com failed with the following error message: [ClientAccessServer=BL2PR08CA018,BackEndServer=bl2pr08mb066.namprd08.prod.outlook.com,RequestId=8c7a6451-a243-4e6c-a9de-e782e8ed8423,TimeStamp=1/23/2014 11:02:05 PM] The request for the Windows Remote Shell with ShellId 299A1A91-16E1-4648-8C45-B63D61B7D5C3 failed because the shell was not found on the server. Possible causes are: the specified ShellId is incorrect or the shell no longer exists on the server. Provide the correct ShellId or create a new shell and retry the operation.
WORKAROUND 1:
Ensure that you are right-clicking and running all MFG tools "as Administrator" every time they are launched.
WORKAROUND 2:
This issue can be resolved by adjusting a parameter within the settings for Migrator for GroupWise (MFG):
1.) Open the following location in Windows Explorer:
C:\Program Files\Quest Software\Migrator for GroupWise
or
C:\Program Files\Dell\Migrator for GroupWise
2.) Open the "gwmigapp.ini" file.
3.) Scroll down to the bottom of the file to locate the [PowerShell] heading.
4.) Add the following parameter under the [PowerShell] heading:
IdleConnectionTimeoutSeconds=0
5.) Save and close the text file.
6.) Re-run the migration.
It may be possible to increase the timeout to a number below 30 seconds, such as 10 seconds. If the errors above return, then the timeout should be reduced until the errors subside. Here is more information regarding this parameter from the Parameters Reference Guide:
[PowerShell]
IdleConnectionTimeoutSeconds=<##>
Type: integer. Default: 30 or 60 (see below)
Determines how long (in seconds) NME/MFG will hold open an idle remote PowerShell connection before closing it. This feature applies only to the duration of an idle state during a connection. Each command execution resets this timer to zero, so a series of commands with only short idle periods between commands could keep the connection open indefinitely. The default IdleConnectionTimeoutSeconds=30 will be suitable for most environments.
IdleConnectionTimeoutSeconds=0
would tell NME/GME to not wait (wait 0 seconds) for a second command after a first, so would close any PowerShell connection immediately after only one command.
The default is 30 seconds for migration to a proprietary Exchange, or 60 seconds for migration to Office 365.
