CNI0's Posts

We are having similar problems. I have just found this: VMware KB: Joining an ESXi 6.0 host to Active Directory fails with error: 40286 (symbol: LW_ERROR_LDAP_SERVER_DOWN)
Hi Did you ever find a solution on this? I have a similar problem When the VM has poor CPU performance, i can migrate it to another ESX in the cluster, the CPU performance is back to nor... See more...
Hi Did you ever find a solution on this? I have a similar problem When the VM has poor CPU performance, i can migrate it to another ESX in the cluster, the CPU performance is back to normal. If I imediatly migrate it back to the first ESX again, it is still ok. :smileyconfused: I am running newest build ESX 5.5 (2718055) Hardware is IBM x3850X6 (with 4 * 10 core E7-8891V2 CPU) and 1.5TB RAM Regards Claus
Hi Sorry for the slow response, but i did not get a notification mail :smileyplain: Outputs from the 2 commands are similar on all threads. It looks like this: VMThread - PSModulePath: C:\... See more...
Hi Sorry for the slow response, but i did not get a notification mail :smileyplain: Outputs from the 2 commands are similar on all threads. It looks like this: VMThread - PSModulePath: C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules\;C:\Program Files\Microsoft Monitoring Agent \Agent\PowerShell\;C:\Program Files (x86)\Microsoft SQL Server\110\Tools\PowerShell\Modules\ VMThread - Get-Module: VMware.VimAutomation.Cis.Core VMware.VimAutomation.Cloud VMware.VimAutomation.Core VMware.VimAuto mation.HA VMware.VimAutomation.PCloud VMware.VimAutomation.SDK VMware.VimAutomation.Storage VMware.VimAutomation.Vds App Locker Appx BestPractices BitsTransfer BranchCache CimCmdlets DirectAccessClientComponents Dism DnsClient International iSCSI IscsiTarget ISE Kds Microsoft.PowerShell.Diagnostics Microsoft.PowerShell.Host Microsoft.PowerShell.Management Mic rosoft.PowerShell.Security Microsoft.PowerShell.Utility Microsoft.WSMan.Management MMAgent MsDtc NetAdapter NetConnectio n NetEventPacketCapture NetLbfo NetNat NetQos NetSecurity NetSwitchTeam NetTCPIP NetworkConnectivityStatus NetworkTransi tion NFS PcsvDevice PKI PrintManagement PSDesiredStateConfiguration PSDiagnostics PSLog PSScheduledJob PSWorkflow PSWork flowUtility RemoteDesktop ScheduledTasks SecureBoot ServerCore ServerManager ServerManagerTasks SmbShare SmbWitness Soft wareInventoryLogging StartScreen Storage TLS TroubleshootingPack TrustedPlatformModule UserAccessLogging VpnClient Wdac Whea WindowsDeveloperLicense WindowsErrorReporting WindowsSearch Microsoft.MonitoringAgent.PowerShell SQLASCMDLETS SQLPS
I am trying to create a script that collect a lot of info from VM's and also set info if needed. That is not my problem. The problem is that there is alot of VM's and it takes about 5-8 sec pr VM... See more...
I am trying to create a script that collect a lot of info from VM's and also set info if needed. That is not my problem. The problem is that there is alot of VM's and it takes about 5-8 sec pr VM. I have create a small sample script to run a process on several VM's at the same time, but it fails in mysterious ways :smileycry: If I only allow 1 thread everything is behaving as expected. More than one thread, it fails with messages that states the PowerCLI cmdlet are not known "The term 'Set-PowerCLIConfiguration' is not recognized as the name of a cmdlet" I am using PowerCLI 6 Any ideas on whats wrong? Below is my sample code (some of it is from Google ) # The per VM codeblock sample $scriptBlock = {   param($VMName, $vcenter, $session)   Write-Host "VMThread - Start for: $($VMName)"   Import-Module VMware.VimAutomation.Core -Global   Write-Host "VMThread - Modules loaded: $(Get-Module)"   $Temp = Set-PowerCLIConfiguration -InvalidCertificateAction Ignore -Scope Session -Confirm:$false   $myVI = Connect-VIServer -Server $vcenter -Session $session   $Myvm = Get-VM -Name $VMName   if($Myvm)   {   Write-Host "VMThread - Getting VM info: $($Myvm.Name)"   $newInfo = New-Object PSObject   $newInfo | Add-Member -Type noteproperty -Name VMName -Value $Myvm.Name   $newInfo | Add-Member -Type noteproperty -Name MemMB -Value $Myvm.MemoryMB   $newInfo   Start-Sleep -Seconds 3   }   else   {   Write-Host "VMThread - No info for VM: $($VMName) - Modules: $(Get-Module)" -ForegroundColor Red   }   Write-Host "VMThread - Done: $($VMName) - Error Count: $($Error.Count) - $Error" } #Start the threads and wait for result function RunTest{   param   (   $VMs,   $Throttle = 1 #threads   )   process   {   $sessionstate = [System.Management.Automation.Runspaces.InitialSessionState]::CreateDefault()   $sessionstate.ImportPSModule("VMware.VimAutomation.Core")   $RunspacePool = [runspacefactory]::CreateRunspacePool(1, $Throttle, $sessionstate, $Host)   $RunspacePool.Open()   $Jobs = @()   Write-Host "Starting threads.."   foreach ($oneVM in $VMs)   {     $Job = [powershell]::Create().AddScript($ScriptBlock).AddArgument($oneVM.Name).AddArgument($global:DefaultVIServer.Name).AddArgument($global:DefaultVIServer.SessionSecret)     $Job.RunspacePool = $RunspacePool     $Jobs += New-Object PSObject -Property @{RunVM = $_.Name; Pipe = $Job; Result = $Job.BeginInvoke()}   }     Write-Host "Start waiting.."   Do   {     Start-Sleep -Seconds 1   }   While ( $Jobs.Result.IsCompleted -contains $false)   Write-Host "All jobs completed!"     $Results = @()   ForEach ($Job in $Jobs)   {   $Results += $Job.Pipe.EndInvoke($Job.Result)   }   $RunspacePool.Close()   Write-Host "`n`nReturning $($Results.Count) objects..." -ForegroundColor Cyan   $Results   } } # Logon to vcenter $user = Get-Credential domain\user $vi = connect-viserver myvCenter -Credential $user $AllVM = Get-VM                     # Return all my VM's, 2 in my test vcenter RunTest -VMs $AllVM -Throttle 1     # Runs OK, returns one object for each VM RunTest -VMs $AllVM -Throttle 2     # Fails
Did you ever find a way to do this?
The Move-VM Cmdlet does not take any Network adapter migration parameters, so i don't think it will work. The article by William Lam is very helpfull Thanks
Any ideas on how to use PowerCLI to do vSphere 6 vMotion across vCenters?
Now, more than two years and 2-3 versions later the "Import-Patch" cmdlet is still missing. This really sucks...
Hi Anyone known how to get a list of vCloud stranded items from PowerCLI? Regards Claus
Hi Alan The SR is 14535091209. I am glad to hear that I can support If I run the "esxcli storage vmfs unmap" command through a SSH session the command completed successfully in 2:34 h... See more...
Hi Alan The SR is 14535091209. I am glad to hear that I can support If I run the "esxcli storage vmfs unmap" command through a SSH session the command completed successfully in 2:34 hours. Regards Claus
Yes, I did set the timeout with Set-PowerCLIConfiguration like this: Set-PowerCLIConfiguration -WebOperationTimeoutSeconds -1 -Scope Session -Confirm:$false This is an exact copy/paste from... See more...
Yes, I did set the timeout with Set-PowerCLIConfiguration like this: Set-PowerCLIConfiguration -WebOperationTimeoutSeconds -1 -Scope Session -Confirm:$false This is an exact copy/paste from my SR: "Thank you for your Support Request. Through GSS we do not support Power cli problems." Regards Claus
If i log in to the ESXi with SSH and run the same command everything runs as expected. esxcli storage vmfs unmap -l <Datastore label> The command completed successfully in about 75 minutes. ... See more...
If i log in to the ESXi with SSH and run the same command everything runs as expected. esxcli storage vmfs unmap -l <Datastore label> The command completed successfully in about 75 minutes. I guess there is some kind of flaw in PowerCLI version of esxcli that makes it timeout after exactly 30 minutes And PowerCLI is not covered by GSS so no result from the SR i created.
Hi I have the exact same problem as LarsB13. Anyone found a solution for this? Regards Claus
Hi I had the same issues and filed a SR. They came back with this. You can specify Version 5.1 compatibility with this line: [VMware.VimAutomation.Cloud.Views.CloudClient]::ApiVersionRestric... See more...
Hi I had the same issues and filed a SR. They came back with this. You can specify Version 5.1 compatibility with this line: [VMware.VimAutomation.Cloud.Views.CloudClient]::ApiVersionRestriction.ForceCompatibility("5.1") And revert back to version 5.5 [VMware.VimAutomation.Cloud.Views.CloudClient]::ApiVersionRestriction.RevertCompatibility()
The workaround works for me to
I will verify the workaround monday. I have also filed a SR 14461770804 on this issue
Hi I have the exact same problem after upgrade from vCD 5.1 to 5.5u1.(and Powercli 5.5 R2) I can reproduce the problem as simple as this: $civapp = get-civapp "MyVapp" $civm = $civapp | g... See more...
Hi I have the exact same problem after upgrade from vCD 5.1 to 5.5u1.(and Powercli 5.5 R2) I can reproduce the problem as simple as this: $civapp = get-civapp "MyVapp" $civm = $civapp | get-civm $guest = $civm.ExtensionData.GetGuestCustomizationSection() $guest.UpdateServerData() Exception calling "UpdateServerData" with "0" argument(s): "Bad request  - Unex pected JAXB Exception  - cvc-complex-type.2.4.a: Invalid content was found star ting with element 'AdminAutoLogonEnabled'. One of '{"http://www.vmware.com/vclo ud/v1.5":Link, WC[##other:"http://www.vmware.com/vcloud/v1.5"]}' is expected." At line:1 char:1 + $guest.UpdateServerData() + ~~~~~~~~~~~~~~~~~~~~~~~~~     + CategoryInfo          : NotSpecified: (:) [], MethodInvocationException     + FullyQualifiedErrorId : CloudException Any ideas whats wrong???
It also fixed my system. Now my next problem is that it does not work with Powershell Version 3. In my eyes this is a very embarrassing fault....
I would prefer that VMware would upgrade the PowerCLI VUM to support Powershell Version 3 directly. In my eyes this is a very embarrassing fault....