I'm trying to use a PowerShell script to monitor the size of ClusterSharedVolumes. I have a working script that I've tested, that just pulls the CSVs' total sizes. I was going to add their sizes to $monitor.Details, but couldn't even get that far. I can run this script on the remote Cluster from my desktop, and verified that I also do so from the server running PA Server Mon. However, when I try to add the script via PA Server mon, testing fails. Please see attached image for screenshot of failure (not recognizing Get-ClusterSharedVolume) and another screenshot of the cmdlet being run successfully on the PA server mon Host. Any help is much appreciated. https://www.dropbox.com/s/1taxyvyx11nllt5/Capture1.PNG?dl=0 https://www.dropbox.com/s/30v8sfqormao1xh/Capture2.PNG?dl=0 asked 10 May '16, 13:08 davidrobertlong |
Hi David, There have been a few others that have had issue importing modules. One found that the service couldn't find the modules in the default location and then tryied using the fully qualified path. See if that will work for you and if not try loading the moduel from another location using the fully qualified path. Thanks Please make sure to mark your questions accepted when you have your answer by clicking the gray check mark to the left of the answer. answered 11 May '16, 13:54 Quinn ♦♦ Thanks for getting back to me Quinn. I was initially playing around with this, and attempted to solve the issue by installing Remote Server Admin Tools on all involved computers. Now I'm having an issue with the .dll that is being loaded: https://www.dropbox.com/s/dxocchv1t7vzn4k/Capture3.PNG?dl=0 I also tried specifying the Full path to the module to import-- Import-Module C:WindowsSystem32WindowsPowerShellv1.0ModulesFailoverClusters
(11 May '16, 18:12)
davidrobertlong
Did you try putting a copy of the .dll in another location and load it from there.
(12 May '16, 15:59)
Quinn ♦♦
I haven't moved the .dll in question anywhere else, but it's already in place on all the computers in question. Sorry if this is a lame question, but how would I be specifying where to find the .dll in its new location if I moved it? Thanks again, Dave
(12 May '16, 17:09)
davidrobertlong
|