Hi! Sounds like you probably have a load balancer involved here. If you do you can easily just set up your 2016 servers and add them to the pool(s). Then when you're satisfied they are working fine, remove the 2012 servers from the pool. Not really migrating at all. Done this a few times with success.
↧
Re: Moving to new UEM server
↧
pvscsi vmware kernel crash
Our ESXi 6.7 crashed today with the following stack trace:
Is there anything we can do to mitigate this?
↧
↧
Re: ALSA Sound Device Failure
Yeah, my bad on that.
So I ran sudo fuser -vaf /dev/snd/pcm* and the output was
USER PID ACCESS COMMAND
/dev/snd/pcmC0D0c: pjg 2226 F...m pulseaudio
/dev/snd/pcmC0D0p: pjg 2226 F...m pulseaudio
/dev/snd/pcmC1D3p:/dev/snd/pcmC1D7p:
/dev/snd/pcmC1D8p:
Not sure what to do about pulse holding up those devices.
↧
Do we have two TEPs created if a Transport Node belongs to two overlay transport zones
Hello,
Trying to workout
- a use case why a transport node would belong to two overlay transport zones
- if the node does belong to the two transport zones, then does it create two TEPs - one for each NVDS or only one TEP?
Cheers
↧
VMware Workstation Pro 15.5 and ESXi 7.0
I have a virtual machine that I built on VMware Workstation Pro 15.5 and I have just upgrade a VMware ESXi 4.0 to 7.0. I want to upload the virtual machine to the ESXi host, but keep getting an error:Upload failed: Unknown error, please try again. If the problem persists, please contact Technical Support and provide c:/users/admin/AppData/Local/Temp?vmware-admin/ovftool.log. Any suggestions?
↧
↧
Re: Workstation Pro in Ubuntu 20.04 LTS ?
Darius,
I don't find my email response in the thread - not sure why. But yes - inserting sound.opl3.enabled = TRUE does indeed enable DOS to connect to the host audio.
Thanks again for your help.
Best regards,
Bob Kelly
↧
Re: Workstation Pro in Ubuntu 20.04 LTS ?
When did you update?
From my DOS log:
2020-05-16T18:30:39.427-04:00| vmx| I125: Log for VMware Workstation pid=60045 version=15.5.2 build=build-15785246 option=Release
When I request updates, no new updates are found.
↧
Re: VMware Workstation Pro 15.5 and ESXi 7.0
Grab that log and use the “attach“ function (in the bottom-right of the comment editor) to add it when posting your next comment.
↧
Re: Not able to access VMware ESXi free version from Ubuntu 20.04
Can Ubuntu ping the ESXi host? Does Ubuntu have a firewall configured? Is there a difference between the IP configuration of Ubuntu compared to Windows?
↧
↧
Re: Custom taskbar icon
Oh, didn't know you could customize pinned application icons that way. Would be nice to be able to change icons for different non pinned VMs, but this will do for now. Had to add shutdown script to suspend VMs rather than shutting them down, but got it all working.
Thanks!
↧
VCSA 7.0 restore issue
I am restoring VCSA 7.0 from Backup which is on FTP. while Step 1 is completed successfully step 2 is getting the error with below statement
Metadata and system validation failed.
Error: Unknown system resource type vtsdblog
Error: Unknown system resource type vtsdb
and so on attached.
I have installed the VCSA 7.0 with default settings and backup taken on FTP. Now when restoring it from backup it throws these errors any clue please ?
Thanks
Manish
↧
Re: Exporting VM Tags in readable format
LucD,
Thank you very much, that worked perfectly.
↧
Re: AppVolumes 4.0 / Writable / Network Printers
We had the exact same issue but without the writable.
Could you try and not attac the writable and create a snapvol.cfg in the following location.
C:\Program Files (x86)\CloudVolumes\Agent\Config\Custom\app\
And then add these lines in it, that did the trick for us.
exclude_registry=\REGISTRY\MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\Providers\Client Side Rendering Print Provider
exclude_path=%SystemtRoot%\System32\DriverStore\FileRepository
exclude_registry=\REGISTRY\MACHINE\SYSTEM\ControlSet001\Control\Print\Printers
exclude_registry=\REGISTRY\MACHINE\SYSTEM\ControlSet001\Control\DeviceContainers
# This should always be the last line in the policy
os=any
If this works try and attach the writable and see if it works.
If that does not work I'd suggest adding that exact same file in the following folder.
C:\Program Files (x86)\CloudVolumes\Agent\Config\Default\uia_plus_profile (or profile or uia only, depending on the template you are using for the writable).
↧
↧
Unable to get IP Address and OS details
Hi,
I am unable to get IP Address and OS details in the below script, please help.
also I dont see any error
Script
$assigned = Get-VM | Get-TagAssignment
$tagCat = $assigned.Tag.Category.Name | Sort-Object -Unique
$report = $assigned | Group-Object -Property { $_.Entity.Name } |
ForEach-Object -Process {
$vm = $_
$obj = [ordered]@{
Folder = $vm.Group[0].Entity.Folder.Name
VM = $vm.Name
IP =$vm.Entity.Guest.IPAddress
OS =$vm.Entity.Guest.OSFullName
}
$tagCat | ForEach-Object -Process {
$cat = $_
$tags = ($vm.Group | Where-Object { $_.Tag.Category.Name -eq $cat }).Tag.Name -join '|'
$obj.Add($cat, $tags)
}
New-Object PSObject -Property $obj
}
$colTab = @{ }
$report | Get-Member -MemberType NoteProperty | Where-Object { 'VM', 'Folder', 'IP', 'OS' -notcontains $_.Name } |
ForEach-Object -Process {
$column = $report."$($_.Name)"
$columnMax = ($column | Where-Object { $_ -ne '' } | ForEach-Object {
$_.Split('|').Count
} | Measure-Object -Maximum).Maximum
$colTab.Add($_.Name, $columnMax)
}
$report | ForEach-Object -Process {
$row = $_
$obj = [ordered]@{
Folder = $_.Folder
VM = $_.VM
IP =$_.IP
OS =$_.OS
}
$colTab.GetEnumerator() | Sort-Object -Property Name | ForEach-Object -Process {
if ($_.Value -gt 1) {
$col = $_
$values = ($row."$($_.Name)").Split('|')
1..($_.Value) | ForEach-Object -Process {
$obj.Add("$($col.Name)-$_", $values[$_ - 1])`
}
} else {
$obj.Add($_.Name, $row."$($_.Name)")
}
}
New-Object PSObject -Property $obj
} | ft -auto
Output
| Folder | VM | IP OS Application | Department Owner | ||||||||
| ------ | -- | -- -- ----------- | ---------- ----- | ||||||||
| Testing | HADOOP | Hadoop | Ops | Karl |
↧
Re: Migrate Writeable Volumes from 2.x to 4.x
To be honest I don't think you can migrate them.
What you could try is create 1 writable on 4.0, it will then create a new folder on the datastore which is called Appvolumes\writable.
You could then try and move (or copy, that might be a better idea) from Cloudvolumes\writables to that folder and import the writables in 4.0.
To be honest I have no idea if this is actually supported.. But you woul have to ask GSS for that info.
↧
Re: Unable to get IP Address and OS details
Try like this
$assigned=Get-VM|Get-TagAssignment
$tagCat=$assigned.Tag.Category.Name|Sort-Object-Unique
$report=$assigned|Group-Object-Property {$_.Entity.Name}|
ForEach-Object-Process {
$vm=$_
$obj=[ordered]@{
Folder=$vm.Group[0].Entity.Folder.Name
VM =$vm.Name
IP =$vm.Group[0].Entity.Guest.IPAddress -join'|'
OS =$vm.Group[0].Entity.Guest.OSFullName
}
$tagCat|ForEach-Object-Process {
$cat=$_
$tags=($vm.Group|Where-Object{$_.Tag.Category.Name-eq$cat}).Tag.Name -join'|'
$obj.Add($cat,$tags)
}
New-Object PSObject -Property $obj
}
$colTab=@{}
$report|Get-Member-MemberType NoteProperty |Where-Object{'VM','Folder','IP','OS'-notcontains$_.Name}|
ForEach-Object-Process {
$column=$report."$($_.Name)"
$columnMax=($column|Where-Object{$_-ne''}|ForEach-Object{
$_.Split('|').Count
}|Measure-Object-Maximum).Maximum
$colTab.Add($_.Name,$columnMax)
}
$report|ForEach-Object-Process {
$row=$_
$obj=[ordered]@{
Folder=$_.Folder
VM =$_.VM
IP =$_.IP
OS =$_.OS
}
$colTab.GetEnumerator()|Sort-Object-Property Name |ForEach-Object-Process {
if($_.Value-gt1){
$col=$_
$values=($row."$($_.Name)").Split('|')
1..($_.Value)|ForEach-Object-Process {
$obj.Add("$($col.Name)-$_",$values[$_-1])`
}
}else{
$obj.Add($_.Name,$row."$($_.Name)")
}
}
New-Object PSObject -Property $obj
}|Format-Table-auto
↧
Re: Upgrade ESXi 6.0u2 to u3
What was the error message and you should attach esxupdate.log.
Without additional information no one can help you.
Regards,
Joerg
↧
↧
whether the NSX -T 3.0 work with vSphere 6.7 ?
looks like the NSX-T 3.0 will support the vSphere 7.0, but will it support the vSphere 6.7 ?
↧
Re: whether the NSX -T 3.0 work with vSphere 6.7 ?
Yes it is supported. However you to use NVDS based integration since DVS 7.0 is not supported.
↧
Re: customization and Administrator password
Might be related to newer, then 1803.
Pending VmWare support case for confirmation.
↧
