Return
-
Title
Remote PowerRUM PowerShell script Import-Module calls local PowerRUM.dll instead of remote -
Description
When running the PowerRUM cmdlets provided under "Using Resource Updating Toolkit for PowerShell Remotely" of the "Resource Updating Toolkit for PowerShell Reference" guide as a script (.ps1) file instead of line by line from the remote PowerShell, the .ps1 script fails with:cd : Cannot find path 'C:\Program Files (x86)\Quest Software\Migration Manager\PowerRUM' because it does not exist.
At line:5 char:1
+ cd "C:\Program Files (x86)\Quest Software\Migration Manager\PowerRUM"
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (C:\Program File...anager\PowerRUM:String) [Set-Location], ItemNotFoundException
+ FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.SetLocationCommand
Import-Module : The specified module '.\PowerRUM.dll' was not loaded because no valid module file was found in any module directory.
At line:6 char:1
+ Import-Module .\PowerRUM.dll
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ResourceUnavailable: (.\PowerRUM.dll:String) [Import-Module], FileNotFoundException
+ FullyQualifiedErrorId : Modules_ModuleNotFound,Microsoft.PowerShell.Commands.ImportModuleCommand
Running the cmdlets provided in the Guide work just fine if ran line by lineEnable-PSRemoting -Force
$cred = Get-Credential
Enter-PSSession -ComputerName davecam -Credential $cred -ConfigurationName Microsoft.PowerShell32
Set-Executionpolicy -ExecutionPolicy Unrestricted -Force
cd "C:\Program Files (x86)\Quest Software\Migration Manager\PowerRUM"
Import-Module .\PowerRUM.dll -
Cause
The cmdlets found in the "Resource Updating Toolkit for PowerShell Reference" were written to ran 1 by 1 and it was not intended to be a full working .ps1 script. -
Resolution
WORKAROUND
The information in the script(s) provided is known to work successfully; however, they have not been officially tested by our Quality Control.
If any of these instructions are changed and/or incorrectly used, intentionally or unintentionally, this solution becomes unsupported by our Support and Development.
For customization of the Quest Migration Manager, please contact our Professional Services Organization.Run the following script which makes use of the Import-Module with -PSSession:#Ensure you update COMPUTER with the correct computer name running RUM.
#If RUM is installed in a different path, please update in the script above.$cred = Get-Credential
$session = New-PSSession -ComputerName COMPUTER -Credential $cred -ConfigurationName Microsoft.PowerShell32
Enable-PSRemoting -Force
Set-Executionpolicy -ExecutionPolicy Unrestricted -Force
Import-Module -PSSession $session "C:\Program Files (x86)\Quest Software\Migration Manager\PowerRUM\PowerRUM.dll"NOTE:If you have a standalone RUM Console, the PowerRUM module directory may not exist on that machine. You can copy the PowerRUM directory to that standalone machine and then use PowerRUM locally, instead of creating a remote session to the main RUM Console. -
Attachments
-
Additional Information
A example of the .ps1 has been attached RemotePowerRum.ps1