Hi amakki.. Once you run this and export to .csv $esxName = "bdesx03.dev.ops" Connect-VIServer vcnp02.dev.ops New-VIProperty -Name lunDatastoreName -ObjectType ScsiLun -Value { p...
See more...
Hi amakki.. Once you run this and export to .csv $esxName = "bdesx03.dev.ops" Connect-VIServer vcnp02.dev.ops New-VIProperty -Name lunDatastoreName -ObjectType ScsiLun -Value { param($lun) $ds = $lun.VMHost.ExtensionData.Datastore | %{Get-View $_} | ` where {$_.Summary.Type -eq "VMFS" -and ($_.Info.Vmfs.Extent | where {$_.DiskName -eq $lun.CanonicalName})} if($ds){ $ds.Name } } -Force | Out-Null Get-VMHost -Name $esxName | Get-ScsiLun | Select CanonicalName, CapacityMB, lunDatastoreName
Hi Tom, As we have newer file systems, so we have plenty of new features and more robust for infrastructure of VM environment. Please find below some of new features along with versions incre...
See more...
Hi Tom, As we have newer file systems, so we have plenty of new features and more robust for infrastructure of VM environment. Please find below some of new features along with versions increments.
Hi, As per VMware below are the recommended , however requirement are simple,request you go through the VMware VSAN Hardware requirement guide for VSAN,
Hi Govirag, Check the DNS name resolutions of each components of SRM and vcenter, and Try to check if there are any firewall profiles have been hindering the communication.( much times it wo...
See more...
Hi Govirag, Check the DNS name resolutions of each components of SRM and vcenter, and Try to check if there are any firewall profiles have been hindering the communication.( much times it would be cause,especially SRM PORTS) Regards Basavnav@yahoo.co9m
Hi Raoul, As error is not taking us to pin point any particular issue, how about reinstalling the windows server,?? However. Please update if you have already issue has been resolved and h...
See more...
Hi Raoul, As error is not taking us to pin point any particular issue, how about reinstalling the windows server,?? However. Please update if you have already issue has been resolved and how as we are bit curious to know the resolution.Thanks Regards Basavaraj.R Navalgund banavalg@yahoo.com
Hi Raoul, Have verified the health of the database, like proper creds are being used. test the database. test the schema is having appropriate permission. Regards Basavaraj.R Navalgund ...
See more...
Hi Raoul, Have verified the health of the database, like proper creds are being used. test the database. test the schema is having appropriate permission. Regards Basavaraj.R Navalgund Banavalg@yahoo.com
Hi A07, You have below options here. 1. you can use the ip address.(temporarily you can use it ) however it is not recommended. 2.you can go ahead and change the vCenter name and DNS ent...
See more...
Hi A07, You have below options here. 1. you can use the ip address.(temporarily you can use it ) however it is not recommended. 2.you can go ahead and change the vCenter name and DNS entries on the server along with other components of the vcenter such as SSO, VUM if they are configured to use the older name and change is required where there is option to change the new name. make sure using nslookup to verify the correctness of the name resolutions. and lastly as per my personal experience point of view, it is always best to use the FQDN for vCenter and related products are concern. Regards Basavaraj.R Navalgund
Hi Sanithsadanandan, If you consider Condition 1. this as ideal condition leaving workstation networking ( hosted, internal and bridged) as 2 different ip 's are in different subnet the...
See more...
Hi Sanithsadanandan, If you consider Condition 1. this as ideal condition leaving workstation networking ( hosted, internal and bridged) as 2 different ip 's are in different subnet they will not communicate without the router between them. Condition 2. If there are any changes needs to be done on the workstation those are internal only. bridged, hosted ..Please correct this and place routing device in between so that 2 devices on the network will pass different ip and they can communicate. Regards Basavaraj.R Navalgund banavalg@yahoo.com
Hi Krishvmware, If you have not installed web client on the vCenter server install webclient only by using ISO of vCenter and connect via webclient. Regards Raj Navalgund banavalg@yah...
See more...
Hi Krishvmware, If you have not installed web client on the vCenter server install webclient only by using ISO of vCenter and connect via webclient. Regards Raj Navalgund banavalg@yahoo.com
Hi Jesi, you cannot upgrade from file system 5.60 to 5.61, you need reformat datastore manually that's preciously .Thanks Regards Basavaraj.R Navalgund
Hi Frineds. On enterprise environment and that spans us and india N/w. one of my team member on the different site not able open vm console( windows vm) and not able to telnet one particular esxi...
See more...
Hi Frineds. On enterprise environment and that spans us and india N/w. one of my team member on the different site not able open vm console( windows vm) and not able to telnet one particular esxi host on one of cluster out of bunch of clusters. However different user from different desktop are able to open vm console without error and able to telnet Host without any error. Regards Raj Navalgund