Which of the many scripts in this thread are you referring to?
↧
Re: PowerCli script with Get-View to report on VMs and specifications
↧
Re: Disable Application Blocking
Right. So can I then use the Global Configuration to tell it to only apply to a specific pool or pools.
Example: Horizon Client Property - Property "Pool Name" is equal to "Pool-1"
So then Pool-2 will not have it enabled?
I only really need application blocking for two specific environment out of my 20 plus environments.
↧
↧
Re: Disable cut & paste for external homeuser
When your users login to vdi, do they use Domain credentials to authenticate to VDI?
↧
Re: script to create a host profile for each Host on Vcenter
it have error
xxxxxxx 443 VSPHERE.LOCAL\Administrator
New-VMHostProfile : Cannot convert 'System.Object[]' to the type 'VMware.VimAutomation.ViCore.Types.V1.Inventory.VMHost' required by
parameter 'ReferenceHost'. Specified method is not supported.
At line:9 char:113
+ ... on "This is my test profile based on $vmhost." -ReferenceHost $vmhost
+ ~~~~~~~
+ CategoryInfo : InvalidArgument: (:) [New-VMHostProfile], ParameterBindingException
+ FullyQualifiedErrorId : CannotConvertArgument,VMware.VimAutomation.ViCore.Cmdlets.Commands.Host.NewVMHostProfile
i`ve the right license----
↧
Re: script to create a host profile for each Host on Vcenter
Try something like this
Get-VMHost|
ForEach-Object-Process {
New-VMHostProfile-Name "$($_.Name)-Profile"-Description "This is my test profile based on $($_.Name))."-ReferenceHost $_-Confirm:$false
}
↧
↧
Re: DLR will not forward traffic
Hello Dr.Virt,
I am also facing the same exact problem. Did you find a solution or workaround?
I have 4 ESXi (6.7 U1) hosts in the vCenter. vSAN is configured. NSX 6.4.4 is deployed.
Thank you,
Ravi
↧
Re: PSL script can not load module when run from C# code.
This is the question.
Module NOT effectively imported if I try to run script from service ( C# code) and loaded ( and script make its work)it I run it from console.
May be problem really that in this computer $env:PSModuleP differ if i run it from different processes?
Or- can it occur because code is 32bit?
It is one specific computer- in other clients ( and in my development computer -windows 7) system works. And we can not fix the problem
↧
Re: How to force VMware ESXi to reclaim memory (manually with script)
there ist no substitute for memory except to add more memory.
if the vm´s don´t fit into the host memory you have the risk of performance issues. don´t allow the host to do other memory optimizations than tpm or compression. ballooning or swapping is always an indicator of insufficient memory
↧
Re: script to create a host profile for each Host on Vcenter
Great thx sir.. u da men!!!
↧
↧
Re: How to force VMware ESXi to reclaim memory (manually with script)
a typo - i mean tps
↧
Re: Critical HP SSD bug requires firmware update for certain models- Drives may brick at 32,768 hrs
Unfortunately not the first issue found with HPD firmware this year either (and I have suspicions that the impact of the below one as per the advisory is inaccurate):
https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00070779en_us
Everyone please update your firmware if your devices are on the affected lists as otherwise this may result in a very sad support call.
Bob
↧
Re: PSL script can not load module when run from C# code.
Did you check in your script what the content of the $env:PSModulePath variable is?
One way of doing that would be to use the Start-Transcript cmdlet and then just display the content of the variable.
That way you can find back in the transcript log what it shows.
32- or 64-bit normally shouldn't make a difference.
↧
Re: vCenter LDAP binding and signing
Hello LucFullenwarth
it seems the command you posted (I had to use Developer Tools in my Chrome to view the entire row because truncated) configures the Identity Provider to use AD over LDAPS; exactly the same configuration that could be added, graphically, via web gui.
Currently, we have the Identity Provider configured as Active Directory (Windows Integrated Authentication) - it makes unsigned SASL requests against AD. I'd like to know from VMware if they planned to support signed SASL before January 2020 or not.
If not, then, the only way currently supported is to switch from Active Directory (Windows Integrated Authentication) to AD over LDAP using LDAPS (LDAP over SSL) like you are currently using.
Bye,
Luca
↧
↧
Re: vCenter Inaccessible After Updating Cluster To 6.7 U3 (Migrating vCenter VM Between Hosts On vSAN)
Hello smittytech,
While you can add an existing vSAN cluster to a new/different vCenter, I would generally not advise starting from scratch and instead figure out why the vCenter VM is having issues.
In most cases vCenter has too much SEAT data and configurations to simply be discarded (but then again anyone that values it has current backups of it), if this is just a home-lab and/or you don't care about vCenters data then by all means make a new one, but otherwise please contact support to get the original one functional.
If you don't have a support contract and want to troubleshoot it yourself I would advise starting with validating that the VM is not registered/running on other hosts (and thus getting marked as invalid when attempting to run it on current host) - is it getting marked as invalid on registration or on power-on attempt? If the latter then check the vmware.log that should have been generated for the reason (e.g. can't create vswp, missing vmdk etc.).
Bob
↧
Re: vCenter Inaccessible After Updating Cluster To 6.7 U3 (Migrating vCenter VM Between Hosts On vSAN)
Thanks for the help!
(I meant to respond on Monday, but due to recent changes pushed to my computer, the reply box doesn't show up and I need to use another computer.)
Oddly, vCenter was working fine when I got to the office. Maybe it was still working on something that wasn't showing up.
Thank you
↧
Hide all VMs to a user but one
Hi everyone,
I have an ESXi 6.5 that hosts several servers. I need to create a user that has the grant to view only a single Virtual Machine and do nothing else.
The steps I have done are:
- I have firstly created the user;
- I have created a role "Virtual Machine"
- Right click on the VM, then granted this permission to the user;
But when I try to login with that user, I have this error:
Connection to ESXi host timed out
If instead I give the same permission at the Host level, it logs in but I see all the VMs.
How can achive this objective?
Thank you.
↧
Re: Hide all VMs to a user but one
Hi,
can you describe what permissions you selected for your newly created role?
↧
↧
Re: 仮想マシンの ハードウェアバージョン を 複数仮想マシン同時に上げる方法について
こんにちは。
仮想マシンのハードウェアバージョンは、vSphere Web Client / vSphere Client以外にも、
ESXi のvim-cmdコマンドや、PowerCLI などでUPすることができます。
1000台規模になると、ESXi に個別ログインが必要なvim-cmdなどでは現実的ではないので、
vCenter経由で設定変更できる PowerCLI を利用するとよいかなと思います。
仮想マシンを停止した状態であれば、割と簡単なコマンドラインで変更できます。
v7（vmx-07）のパワーオフされた仮想マシン vm01とvm02があるとします。
PowerCLI> Get-VM vm01,vm02 | select Name,PowerState,Version
Name PowerState Version
---- ---------- -------
vm02 PoweredOff v7
vm01 PoweredOff v7
下記のように v8 にバージョンアップできます。
PowerCLI> Get-VM vm01,vm02 | Set-VM -Version "v8" -Confirm:$false
Name PowerState Num CPUs MemoryGB
---- ---------- -------- --------
vm01 PoweredOff 1 4.000
vm02 PoweredOff 1 4.000
PowerCLI> Get-VM vm01,vm02 | select Name,PowerState,Version
Name PowerState Version
---- ---------- -------
vm02 PoweredOff v8
vm01 PoweredOff v8
ただし、パワーオンの仮想マシンでハードウェアバージョンをUPしようとするとエラーになります。
パワーオンのまま、GUI で可能なスケジュールでの（仮想マシン再起動時の）アップグレードをするには、
ちょうどよいコマンドレット／オプションがなく、スクリプトを作成する必要がありそうです。
Scheduling VM Compatibility Upgrade from Power Cli ?
以上です。ご参考まで・・・
↧
Re: Critical HP SSD bug requires firmware update for certain models- Drives may brick at 32,768 hrs
Maybe other vedors will come with similar advisories, because HPE was notified about this issue by one of its OEM partners.
↧
Re: Migrate Windows Failover cluster servers to vSAN
Do you want to virtualize these three physical servers? Depending on the applications that run on this WFSC, I recommend to move from Fibre-Channel to iSCSI (supplied by vSAN) and then add new, virtual cluster nodes. Then remove the old physical servers from the WFC. If this is not possible, P2V migrate the cluster nodes after migrating from FC to iSCSI.
↧