What is that you are trying to achieve using vMA?
Cheers,
Supreet
↧
Re: resxtop failed
↧
Re: vSAN licensing
If your 10 Hosts are already licensed with vSphere ESXi than you need of course additional vSAN (3 editions available) licenses.
If not... depending on the use case of your Cluster several special Bundle or Addons are available.
VMware HCI Kit = 1 ESXi + 1 vSAN Lic
VMware vSAN Desktop = all inclusive bundle for VDI only
VMware vSAN ROBO = max 25vm per Site
External JBOD arent a valid configuration for VSAN (i only see some special for HPE Blade with external SAS)
Reuse of existing HW doesnt work well in most cases (for Lab or Testing maybe).
Regards,
Joerg
↧
↧
Re: Attached existing disk to a Vm already created
Looks like there is a typo in the datastore name. Actual name is VD-VM1_v002 whereas, you have used VD-VM1-v002.
Cheers,
Supreet
↧
Re: AppVols 2.14 error installing with embedded SQL Express
we just had the same issue : a workaround is to copy the install files locally on a local drive instead of launching on the CD iso image
↧
Re: ESXI 5.1升级到6.0后usb设备不能使用，系统启动后键盘也不能使用，键盘灯灭掉
#vm-support
此命令结束时，你会看到我们需要的*.tgz 文件。
↧
↧
RDS farm with RDP connection type from horizon client
We are having a problem with our RDS farm when using RDP connection type and the horizon client.
When using this protocol we get failed connection attempts and the message "The connection to the remote computer failed. It is possible that remote connections are not enabled on the remote computer or that the computer or network is too busy." This only happens when using the RDP connection type from the Horizon client.
I can connect to the same RDS farm using remote desktop with no issues.
I can connect to the RDS farm with the horizon client if I use vmware blast or PCOIP.
I reboot the servers and the problem seems to go away for a bit, but that is getting quite annoying and doesn't work well with our 24 hour manufacturing environment.
Horizon client is currently 4.8.1, tried with 4.7 also.
Connecton server and horizon agents are 7.3.2-7161118
This problem did not occur when there was only a single RDS server.
Any help is appreciated.
Here is part of the horizon client log.
2018-09-12 14:05:45.531+-6:00 INFO (48D8) [WinCDK] DesktopToolBar::DesktopToolBar : Launch item id: cn=fft-rds,ou=applications,dc=vdi,dc=vmware,dc=int.
2018-09-12 14:05:45.533+-6:00 INFO (48D8) [WinCDK] DesktopWindow::OnInitDialog : [User] Enter Init.
2018-09-12 14:05:45.543+-6:00 INFO (48D8) [WinCDK] DesktopWindow::OnInitDialog : [User] Exit Init.
2018-09-12 14:05:45.543+-6:00 INFO (48D8) [WinCDK] DesktopWindow::Connect : [User] Enter DesktopWindow::Connect.
2018-09-12 14:05:45.543+-6:00 INFO (48D8) [WinCDK] RDPWindow::OnCreate : [User] Enter CreateRDPWindow.
2018-09-12 14:05:45.543+-6:00 INFO (48D8) [WinCDK] RDPWindow::CreateEventAndMutexForUsbd : Succeeded to create event : Event_cn=fft-rds,ou=applications,dc=vdi,dc=vmware,dc=int@16932_{DEE7EADF-DB03-4a42-9552-44024218BC2C}
2018-09-12 14:05:45.543+-6:00 INFO (48D8) [WinCDK] RDPWindow::CreateEventAndMutexForUsbd : Succeeded to create mutex : Mutex_cn=fft-rds,ou=applications,dc=vdi,dc=vmware,dc=int@16932_{DEE7EADF-DB03-4a42-9552-44024218BC2C}
2018-09-12 14:05:45.543+-6:00 INFO (48D8) [WinCDK] RDPWindow::GetUsbdLoaderPath : Using 64 bit path for USBD loader.
2018-09-12 14:05:45.543+-6:00 INFO (48D8) [WinCDK] RDPWindow::CreateProcessForUsbd : Create process for USBD loader with command : x64\vmware-view-usbdloader.exe FALSE cn=fft-rds,ou=applications,dc=vdi,dc=vmware,dc=int@16932 Event_cn=fft-rds,ou=applications,dc=vdi,dc=vmware,dc=int@16932_{DEE7EADF-DB03-4a42-9552-44024218BC2C} Mutex_cn=fft-rds,ou=applications,dc=vdi,dc=vmware,dc=int@16932_{DEE7EADF-DB03-4a42-9552-44024218BC2C}.
2018-09-12 14:05:45.546+-6:00 INFO (48D8) [WinCDK] RDPWindow::CreateProcessForUsbd : Succeeded to create process for USBD loader.
2018-09-12 14:05:45.579+-6:00 INFO (48D8) [WinCDK] RDPWindow::OnCreate : RDP control version is '10.0.10586'.
2018-09-12 14:05:45.681+-6:00 INFO (6C88) [WinCDK] RDPWindow::OnUsbdInitDone : USBD initialization is done with negotiated desktop PID set as cn=fft-rds,ou=applications,dc=vdi,dc=vmware,dc=int@16932@17932.
2018-09-12 14:05:46.975+-6:00 INFO (48D8) [WinCDK] RDPWindow::OnCreate : [User] Exit CreateRDPWindow.
2018-09-12 14:05:46.975+-6:00 INFO (48D8) [WinCDK] DesktopWindow::Connect : Create remote window successful.
2018-09-12 14:05:46.992+-6:00 INFO (48D8) [WinCDK] DesktopWindow::Connect : [User] Exit DesktopWindow::Connect.
2018-09-12 14:05:46.992+-6:00 INFO (48D8) [WinCDK] BaseServices::LaunchItemSessionCallback : CdkLaunchItemTask Callback: Exit.
2018-09-12 14:05:46.992+-6:00 INFO (48D8) [libcdk] TaskCombiner: CdkGetLaunchItemConnectionTask(DONE) removed, group task num:0, total task num:0.
2018-09-12 14:05:46.992+-6:00 INFO (48D8) [libcdk] TaskCombiner: SetResult for CdkGetLaunchItemConnectionTask(DONE).
2018-09-12 14:05:46.992+-6:00 INFO (48D8) [WinCDK] DesktopWindow::OnUsbdInitDone : USBD service initialized successfully, will try to connect it with desktop PID cn=fft-rds,ou=applications,dc=vdi,dc=vmware,dc=int@16932@17932
2018-09-12 14:05:46.992+-6:00 INFO (48D8) [WinCDK] USBDevices::Initialize : Initialize USB instance. The broker is 'blabla.com'. The desktop is 'FFT-RDS'.
2018-09-12 14:05:46.992+-6:00 INFO (48D8) [vmware-view-usbd] CdkViewUsb_Log: ViewUsblib log: ViewUsb_GetClient: desktop PID is cn=fft-rds,ou=applications,dc=vdi,dc=vmware,dc=int@16932@17932.
2018-09-12 14:05:46.992+-6:00 INFO (48D8) [vmware-view-usbd] CdkViewUsb_Log: ViewUsblib log: ViewUsb_GetClient: client instance not tracked
2018-09-12 14:05:46.992+-6:00 DEBUG (48D8) [vmware-view-usbd] CdkViewUsb_Log: ViewUsblib log: ViewUsb_InitialiseHandleHeader: 044F46F0
2018-09-12 14:05:46.992+-6:00 INFO (48D8) [vmware-view-usbd] CdkViewUsb_Log: ViewUsblib log: mmfw_GetNamedPipeName: Named Pipe name is \\.\pipe\cn=fft-rds,ou=applications,dc=vdi,dc=vmware,dc=int@16932@17932
2018-09-12 14:05:46.992+-6:00 DEBUG (48D8) [vmware-view-usbd] CdkViewUsb_Log: ViewUsblib log: mmfw_PostMsg_Tracked
2018-09-12 14:05:46.992+-6:00 DEBUG (48D8) [vmware-view-usbd] CdkViewUsb_Log: ViewUsblib log: mmfw_GetMsgWaitTimeout: using default timeout of 1000 msec.
2018-09-12 14:05:46.993+-6:00 INFO (2248) [vmware-view-usbd] CdkViewUsb_Log: ViewUsblib log: mmfw_client_dispatcher called (client @ 045D7148, comms @ 000014B4)
2018-09-12 14:05:46.993+-6:00 INFO (48D8) [vmware-view-usbd] CdkViewUsb_Log: ViewUsblib log: ViewUsb_GetClient: desktop PID is cn=fft-rds,ou=applications,dc=vdi,dc=vmware,dc=int@16932@17932.
2018-09-12 14:05:46.993+-6:00 INFO (48D8) [vmware-view-usbd] CdkViewUsb_Log: ViewUsblib log: ViewUsb_GetClient: client handle is 044F46F0
2018-09-12 14:05:46.993+-6:00 DEBUG (48D8) [vmware-view-usbd] CdkViewUsb_Log: ViewUsblib log: mmfw_PostMsg_Tracked
2018-09-12 14:05:46.993+-6:00 INFO (48D8) [libcdk] CdkViewUsb_OpenDesktop: certificate thumbprint set, desktop="cn=fft-rds,ou=applications,dc=vdi,dc=vmware,dc=int@16932@17932"
2018-09-12 14:05:46.993+-6:00 DEBUG (48D8) [vmware-view-usbd] CdkViewUsb_Log: ViewUsblib log: ViewUsb_ValidateHandle: 044F46F0 (CLIENT, ref:1)
2018-09-12 14:05:46.993+-6:00 DEBUG (48D8) [vmware-view-usbd] CdkViewUsb_Log: ViewUsblib log: ViewUsb_InitialiseHandleHeader: 04574A10
2018-09-12 14:05:46.993+-6:00 DEBUG (48D8) [vmware-view-usbd] CdkViewUsb_Log: ViewUsblib log: ViewUsb_Hold: 044F46F0
2018-09-12 14:05:46.993+-6:00 DEBUG (48D8) [vmware-view-usbd] CdkViewUsb_Log: ViewUsblib log: ViewUsb_ValidateHandle: 044F46F0 (CLIENT, ref:1)
2018-09-12 14:05:46.993+-6:00 DEBUG (48D8) [vmware-view-usbd] CdkViewUsb_Log: ViewUsblib log: ViewUsb_ValidateHandle: 04574A10 (DESKTOP, ref:1)
2018-09-12 14:05:46.993+-6:00 DEBUG (48D8) [vmware-view-usbd] CdkViewUsb_Log: ViewUsblib log: mmfw_PostMsg_Tracked
2018-09-12 14:05:46.994+-6:00 DEBUG (48D8) [vmware-view-usbd] CdkViewUsb_Log: ViewUsblib log: ViewUsb_GetReconnectTicket: 04574A10
2018-09-12 14:05:46.994+-6:00 DEBUG (48D8) [vmware-view-usbd] CdkViewUsb_Log: ViewUsblib log: mmfw_PostMsg
2018-09-12 14:05:46.994+-6:00 DEBUG (48D8) [vmware-view-usbd] CdkViewUsb_Log: ViewUsblib log: mmfw_PostMsg_Tracked
2018-09-12 14:05:46.997+-6:00 DEBUG (48D8) [(null)] Creating new channel "1" to listener "Port2" for connection 1 of 0.
2018-09-12 14:05:47.003+-6:00 DEBUG (48D8) [(null)] Creating new channel "2" to listener "Port1" for connection 1 of 1.
2018-09-12 14:05:47.003+-6:00 DEBUG (48D8) [(null)] Tunnel listener "Port1" has reached its max connections (1); closing listening socket and disallowing further connections.
2018-09-12 14:05:47.213+-6:00 DEBUG (2248) [vmware-view-usbd] CdkViewUsb_Log: ViewUsblib log: ViewUsb_FindDesktopInCB: handle=00000001, desktop=00000000, connection is 04574A10
2018-09-12 14:05:47.213+-6:00 DEBUG (2248) [vmware-view-usbd] CdkViewUsb_Log: ViewUsblib log: ViewUsb_GetReconnectTicket: 04574A10
2018-09-12 14:05:47.213+-6:00 DEBUG (2248) [vmware-view-usbd] CdkViewUsb_Log: ViewUsblib log: mmfw_PostMsg
2018-09-12 14:05:47.213+-6:00 DEBUG (2248) [vmware-view-usbd] CdkViewUsb_Log: ViewUsblib log: mmfw_PostMsg_Tracked
2018-09-12 14:05:47.213+-6:00 INFO (2248) [vmware-view-usbd] CdkViewUsb_Log: ViewUsblib log: ReconnectTicket CB
2018-09-12 14:05:47.213+-6:00 DEBUG (2248) [vmware-view-usbd] CdkViewUsb_Log: ViewUsblib log: ViewUsb_FindDesktopInCB: handle=00000001, desktop=00000000, connection is 04574A10
2018-09-12 14:05:47.213+-6:00 INFO (2248) [vmware-view-usbd] CdkViewUsb_Log: ViewUsblib log: ViewUsb_Error_CB: desktop found
2018-09-12 14:05:47.214+-6:00 WARN (2248) [libcdk] CdkViewUsbCbFunc: callback called, reason=VIEWUSB_CB_ERROR, desktopHandle=04574A10, msgId=213, msgString="IDS_DROPDOWN_DEVICES_NOT_AVAILABLE"
2018-09-12 14:05:47.214+-6:00 INFO (48D8) [WinCDK] USBDevices::HandleUSBError : USB remoting is disabled for this desktop because the USB component is not available in the agent. The broker is 'blabla.com'. The desktop is 'FFT-RDS'.
2018-09-12 14:05:47.815+-6:00 INFO (48D8) [WinCDK] Services::LaunchItemConnectionSucceeded : (cn=fft-rds,ou=applications,dc=vdi,dc=vmware,dc=int) connection succeeded with new connection Callback: Entry.
2018-09-12 14:05:47.815+-6:00 INFO (48D8) [WinCDK] BaseAppWindowController::EnterWindowState : Valid transition from state 'Launching Desktop' to state 'Logged in'.
2018-09-12 14:05:48.082+-6:00 INFO (48D8) [WinCDK] Services::LaunchItemConnectionSucceeded : (cn=fft-rds,ou=applications,dc=vdi,dc=vmware,dc=int) connection succeeded with new connection Callback: Exit.
2018-09-12 14:05:49.510+-6:00 WARN (48D8) [libcdk] CdkDebug_PrintErr: Error reading from tunnel HTTP socket: An existing connection was forcibly closed by the remote host.
2018-09-12 14:05:49.510+-6:00 DEBUG (48D8) [(null)] Closing 1-use listener "Port1" after channel "2" disconnect.
2018-09-12 14:06:00.560+-6:00 INFO (48D8) [WinCDK] DesktopWindow::OnSysCommand : [User] Enter SysCommand:UnhandledType.
2018-09-12 14:06:00.560+-6:00 INFO (48D8) [WinCDK] DesktopWindow::OnSysCommand : [User] Exit SysCommand:UnhandledType.
2018-09-12 14:06:09.830+-6:00 INFO (48D8) [WinCDK] AutoHideMessageBox::ShowAutoHideMessageBox : Show auto hide message:The connection to the remote computer failed.
It is possible that remote connections are not enabled on the remote computer or that the computer or network is too busy..
2018-09-12 14:06:11.910+-6:00 INFO (48D8) [WinCDK] DesktopWindow::OnClose : [User] Enter CloseWindow.
2018-09-12 14:06:11.910+-6:00 INFO (48D8) [WinCDK] RDPWindow::PreDestroy : To Destroy RDP Window.
↧
Re: Powercli Script to Capture Cluster utilization
Is that 15% reserved RAM a hard-coded value for your environment?
The VSAN Usage is that the datastores on VSAN usage?
And how can the script detect these VSAN datastores? Do they have specific names?
Or does the script need to discover which datastores are sitting on VSAN?
↧
Re: vSphere 6.5 shows MSA 2050 4.360 TB volumes as 4TB.
Where is 300+ GB?
It's in the maths, i.e. the conversion from TB to TiB.
Maybe Units converter - convert TB into TiB can help to explain this better.
Simply enter 4.4 TB TiB into the input filed, and you'll see that you end up with ~4TiB.
Btw. it's the same for the disks that you mentioned. A 1.2TB disk has a capacity of ~1.09TiB.
André
↧
Re: Unregister a vCenter extension with a space and special character in the name
Yes, you'd normally click on the extension and use the "key" value as shown below. In your case, it's converting spaces to HTML codes which may be breaking it. You might want to work with support to see how to go about unregistering that extension in this case.
↧
↧
Re: vSphere 6.5 shows MSA 2050 4.360 TB volumes as 4TB.
So that means vSphere shows in TiB?
Why then not to write TiB intead of TB.
Confusing things.
↧
Re: (Windows 8.1, 64x) Why isn't "Easy Install" an option in Set-Up Wizard?/ also "Operating System Not Found" message (see pic)
Welcome to the Community,
VMware only offers the platform to install virtual machines. No matter how you are going to install an operating system (manually, or via Easy Install), you'll always need the original vendor's installation image/media.
Including all operating systems in e.g. the VMware Workstation setup would not only make the installation image huge, but would likely also violate several vendors' license agreements.
André
↧
Re: Script to attach VMware tools and HW version update baselines to a set of VMs (from csv file)?
How about using the same VM target list for this one to run against??
Also, trying to find a script/command set to clone a VM 100 times (with a number after the name) for our test set. These won't have any live network since they're just to be used to see how long it will take to execute the script against that many VMs. Mostly so we have a solid idea of how long these runs will take. I found one script, but it failed (badly). It looks like I need to update the PowerShell and then PowerCLI versions (to be current since PowerShell is 4.0) first.
Also need this to export as a csv file for our records (dictated from higher up).
vSphere environment is still 6.5u1.
↧
Re: Powercli Script to Capture Cluster utilization
Hi LucD,
I have a vsan script but i need to put the name manually, and for multiple vcenters is a hard task. All the vsan datastores in all the vcenters got the word VSAN in the name.
↧
↧
Horizon 7 certification 2v0-751
What version will be on the test? Horizon 7 or 7.7, what level is to expect?
↧
Re: Powercli Script to Capture Cluster utilization
I also manage to get the datastore capacity this way. If i can add the other stuff here that will work for me (Total CPU, CPU Usage, CPU Free, Total RAM, RAM Usage, RAM Free N° Hosts, N°VMs), but i don't know how to add them to the script below and to do it for multiple vcenters at the same time
Get-Datacenter -PipelineVariable dc |
Get-Cluster -PipelineVariable cl -ErrorAction SilentlyContinue |
Get-Datastore -PipelineVariable ds|
Get-VMHost -PipelineVariable VMHost |
Get-VM -PipelineVariable vm |
Select-Object
@{N='Datacenter';E={$dc.Name}},
@{N='Cluster';E={$cl.Name}},
@{N="Host Memory Size GB";E={[math]::Round($cl.ExtensionData.Hardware.MemorySize/1073741824)}},
@{N="Host Num CPU Cores";E={[math]::Round($cl.ExtensionData.Hardware.CpuInfo.NumCpuCores)}},
@{N="N° VMs";E={($vm | measure-object).Count}},
@{N="VM Datastores";E={
$script:vmds = Get-View -Id $vm.DatastoreIdList -Property Name,Summary.Capacity,Summary.FreeSpace
$script:vmds.Name -join '|'}},
@{N='VM Datastores CapacityGB';E={
[math]::Round(($script:vmds.Summary.Capacity | Measure-Object -Sum | Select -ExpandProperty Sum)/1GB,0)}},
@{N=" VM Datastores UsedSpaceGB";E={
[Math]::Round((($script:vmds.Summary.Capacity | Measure-Object -Sum | Select -ExpandProperty Sum)-($script:vmds.Summary.FreeSpace | Measure-Object -Sum | Select -ExpandProperty Sum))/1GB,0)}},
@{N='VM Datastores FreeGB';E={
[math]::Round(($script:vmds.Summary.FreeSpace | Measure-Object -Sum | Select -ExpandProperty Sum)/1GB,0)}} |
↧
Re: Script to attach VMware tools and HW version update baselines to a set of VMs (from csv file)?
Ok, like this you mean?
$vmNames=Import-Csv-Path.\vmnames.csv-UseCulture
Get-VM-Name$vmNames.Name |
SelectName,HardwareVersion,
@{N='ToolsStatus';E={$_.ExtensionData.Guest.ToolsStatus}},
@{N='ToolsRunningStatus';E={$_.ExtensionData.Guest.ToolsRunningStatus}},
@{N='ToolsVersion';E={$_.ExtensionData.Guest.ToolsVersion}},
@{N='ToolsInstallType';E={$_.ExtensionData.Guest.ToolsInstallType}} |
Export-Csv-Path.\report.csv-NoTypeInformation-UseCulture
On the cloning script, what are you using, and what goes wrong?
Otherwise any code I provide will be a shot in the dark.
↧
Re: Powercli Script to Capture Cluster utilization
Ok, got it, I can use the datastorenames in that case.
Do you need to have the total VSAN storage per cluster, or per datastore?
↧
↧
Re: Powercli Script to Capture Cluster utilization
I think that per datastore will be more precise as i'll know that is only collecting the vsan datastore and nothing else.
↧
Re: Powercli Script to Capture Cluster utilization
Does that mean you have only 1 datastore on VSAN per cluster?
↧
Re: vSphere 6.5 shows MSA 2050 4.360 TB volumes as 4TB.
So that means vSphere shows in TiB?
Yes, they show the real technical size.
Why then not to write TiB intead of TB.
Sorry, I can't answer this.
It's indeed confusing to have such a distinction anyway. In the early IT times 1kB equaled 1,024 Bytes, and nobody ever thought of 1kB = 1,000 Bytes, or s.th. like TB vs. TiB.
André
↧