mdcarson's Posts

You were correct. I reinstalled UpdateManager PowerCLI to resolve the missing snapin problem. I think I created that problem troubleshooting the other error. Unfortunately, I still can't get... See more...
You were correct. I reinstalled UpdateManager PowerCLI to resolve the missing snapin problem. I think I created that problem troubleshooting the other error. Unfortunately, I still can't get the script to work. I'm a little confused by the usage comments at the begining. It looks like the intention was pass the source, destination and baseline name as command line parameters, but the example only includes 2 of the three. I tried uncommenting the declarations for $destinationServer, $sourceServer, and $baselines, and plugging in the appropriate addresses and baseline name. Now when I run the script I get this error: The term 'param' is not recognized as a cmdlet, function, operable program, or script file. Verify the term and try again. At D:\PowerCLI\Scripts\ExportImportBaselines_40U1_mod.ps1:22 char:6 + Param( <<<< [VMware.VumAutomation.Types.Baseline[]] $baselines, [VMware.VimAutomation.ViCore.Impl.V1.VIServerImpl[]]$destinationServers)
Thanks for the response. I tried your suggestion. No joy. It looks like the types for Update Manager Power CLI have also changed in 4.1. Now I get, "Unable to find type [VMware.VumAutomatio... See more...
Thanks for the response. I tried your suggestion. No joy. It looks like the types for Update Manager Power CLI have also changed in 4.1. Now I get, "Unable to find type [VMware.VumAutomation.Types.Patch[]]: make sure that the assembly containing this type is loaded. At D:\PowerCLI\Scripts\ExportImportBaselines_40U1.ps1:28 char:71 + function ExtractPatchesFromServer([VMware.VumAutomation.Types.Patch[]]$ <<<< patches, $destinationServer){" I'm not sure where to find a cross reference to get the new object type.
This isn't working for me. I found PowerCLI while looking for a VUM export/import script. It's new to me. My vCenter servers are new builds of WS2K8x64 and vCenter 4.1. I have powershell inst... See more...
This isn't working for me. I found PowerCLI while looking for a VUM export/import script. It's new to me. My vCenter servers are new builds of WS2K8x64 and vCenter 4.1. I have powershell installed and the 4.1 versions of PowerCLI and Update Manager PowerCLI. The error I get is "Unable to find type : make sure that the a ssembly containing this type is loaded. At D:\PowerCLI\SCripts\ExportImportBaselines_40U1.ps1:28 char:118 + function ExtractPatchesFromServer([VMware.VumAutomation.Types.Patch[]]$patches,VMware.VimAutomation.Types.VIServer]$ <<<< destinationServer){" Any suggestions?
We recently migrated WS2K3 VM's from ESX 2.x hosts to new ESX 3.0.2 hosts. Two of the VMs we migrated were part of a Microsoft cluster. They were working fine on the old host systems. Now we... See more...
We recently migrated WS2K3 VM's from ESX 2.x hosts to new ESX 3.0.2 hosts. Two of the VMs we migrated were part of a Microsoft cluster. They were working fine on the old host systems. Now we're getting the " Reservation of cluster disk... has been lost" errors. I noticed we're also getting occasional cluster communication lost errors too, but not nearly as frequently as the disk problems. The shared virtual disks were on locally attached storage and the VM's were hosted by the same parent server in the old environment. The new environment has 5 hosts servers in the cluster, and the datastores are on SAN. In searching for a resolution, I found this post, but I also found this KB document: "Insight Manager causes excessive SCSI reservation conflicts" (1003534) and I wondered if it might be related. All of our VMWare host systems are HP and have 7.8 agents installed. Is anyone else experiencing this issue using HP hardware?