This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Quest Support ............................................................................................................................................... 4
How can I verify that Remote Powershell To Exchange 2010 Is Working Properly? .................................... 6
Example Of Remote Powershell Working ................................................................................................. 6
The Remote Powershell Test Failed, What Do I Do Now? ............................................................................ 7
Powershell Version ................................................................................................................................... 7
Get-Host Showing Powershell Version ................................................................................................. 7
P a g e | 4 Copyright 2010 – Quest Software Inc. All Rights Reserved
Quest Support
Quest Support is available to customers who have a trial version of a Quest product or who have purchased a commercial version and have a valid maintenance contract. Quest Support provides around the clock coverage with SupportLink, our web self-service. Visit SupportLink at www.quest.com/support From SupportLink, you can do the following: Quickly find thousands of solutions (Knowledgebase articles/documents) Download patches and upgrades. Seek help from a Support engineer. Log and update your case, and check its status. View the Global Support Guide for a detailed explanation of support programs, online services, contact information, and policy and procedures.
P a g e | 5 Copyright 2010 – Quest Software Inc. All Rights Reserved
Purpose The Quest Notes Migrator for Exchange User Guide makes reference to Exchange 2010, Remote powershell and how to enable it. Remote powershell is a new feature in Powershell 2.0 and Exchange 2010. Notes Migrator for Exchange no longer needs the Exchange Management Tools to migrate to Exchange 2010 but does require some extra configuration. This document will attempt to give high-level detail on some ways to troubleshoot and verify that
remote powershell is working from the migration console. It will also include some of the Exchange
powershell cmdlets that Notes Migrator for Exchange is using during its actions.
Note: Powershell 2.0 can be downloaded from the following website.
http://support.microsoft.com/kb/968929
Note: A list of Exchange 2010 cmdlets can be obtained from the following website.
P a g e | 12 Copyright 2010 – Quest Software Inc. All Rights Reserved
Connection Succeeds But Get-Organizationconfig Fails Figures 12 and 13 below show that Get-OrgranizationConfig cannot be found. Typically there can be two
reasons for this to happen:
1. The user is not a member of the View-Only Organization Management
2. The remote powershell session could not be initiated.
Notes Migrator will require a domain user account in Active Directory, with Read/Write delegate access on all OUs where users and groups will be provisioned. On the Exchange server, this account will need Exchange Administration delegate access to the Administrative Group where the users’ mailboxes will be created. This account must then be used to login to the migration workstation.
Get-OrganizationConfig Failing On Mailbox Enable In NME
Figure 12 – Get-OrganizationConfig Failing During Mailbox-Enable
Get-OrganizationConfig Failing Due To Missing cmdlet
Figure 13 – Get-OrganizationConfig Failing Due To cmdlet Missing
P a g e | 13 Copyright 2010 – Quest Software Inc. All Rights Reserved
Remote Powershell Is Working But Notes Migrator Is Still Giving Me
Errors. What Should I Do?
PSHME.DLL/PSHMEV2.DLL For NME to function with Powershell and Exchange 2010, Two DLL files need to be registered and are
usually registered during installation. There are instances where the DLL’s fail to register due to
powershell not being installed or a permissions issue of some type.
Figures 14 and 15 below show two common issues if the DLL files have not been registered.
Figure 14 – ESM Must Be Installed
Figure 14 says that the Exchange System Manager needs to be installed. Exchange System Manager is
for Exchange 2003 and usually appears when powershell was installed after Notes MIgrator. The
Exchange tools for Exchange 2010 are not needed as all the powershell commands are called remotely
P a g e | 14 Copyright 2010 – Quest Software Inc. All Rights Reserved
Figure 15 – Mailbox Databases are empty
In Figure 15, the mailbox database dropdown is empty. This can mean that you do not have access to
the get-mailboxdatabase cmdlet but is more commonly found when the DLL files are not registered
properly. To re-register the DLL files, close Notes Migrator and run the following two commands from a
command prompt.
1. "C:\windows\microsoft.net\framework\v2.0.XXXXX\regasm.exe "c:\program files\quest software\quest notes migrator for exchange\pshme.dll"
2. "C:\windows\microsoft.net\framework\v2.0.XXXXX\regasm.exe "c:\program files\quest software\quest notes migrator for exchange\pshmev2.dll"
Replace the XXXXX with the version number from the directory found in