New CentOS7 cannot access network

This post was originally published on this site

  1. I added a new hp blade dl460c gen8 blade to an existing C7000 chassis. The HP BladeSystem recognizes it without issue.
  2. I have installed ESXi 6.5 on the new blade without issue.
  3. Created a new CentOS7 VM using the vSphere Client GUI and I cannot access the network. I can ping myself but not the GW or outside world. I do see that that the existing blades access the network via a VLAN, but the gui doesn’t give me an option to attach to that VLAN.


Webcam quality, VM’s and Thin Clients

This post was originally published on this site



We have been struggling with camera quality in our virtual environment. It seems that no matter what we do, quality of a webcam ends up very choppy and pixelated. After a fair amount of research, we came to the conclusion that it is best to run cameras on Thin Clients, as opposed to Zero Clients. Still, when logged into a virtual machine, there is no improvement to the quality of the picture when run on a Thin Client.


While most of our environment is running PCoIP, we have also tested with BLAST. RTAV is another avenue that we’ve explored. We are running nVidia Grid cards, and have plenty or resources to put toward video quality (graphic intensive programs such as AutoCAD, Photoshop and BlueBeam work just fine). What’s alarming to me is that, no matter what we test (RTAV, BLAST, Thin/Zero Client, PCoIP, etc…), there is absolutely no change, negative or positive, in camera quality.


I am also confused about the benefits of using a Thin Client. I was told early on that running a camera from a Thin Client allows the video to be processed locally before passing through to the VDI. My understanding is that a Thin Client is nothing more than a PC running the Horizon View Client (or Citrix, RDP, etc…), but did find recently that there are RTAV settings in the registry of our 10zig Thin Clients. I’m just wondering if there is something that needs to be done on the Client itself in order to utilize RTAV in the virtual environment.


My suspicion is that we HAVE the tools we need, but are missing some critical information on how to use them. I apologize for the lack of information/context… I’m not sure I know the VDI lingo well enough to communicate a question like this. I’m hoping that someone can offer some advice based on similar experiences. We NEED to give our users acceptable camera quality, and they do not want to take extra steps to leave their virtual machine to do so.


Currently running:

nVidia GRID (M and K series)

VMWare Agent version 7.4

Logitech 1080p cameras

10Zig 5800/5900 Thin and Zero Clients




Need to gather information about VMs in specific datacenters in environment

This post was originally published on this site

I need to pull up a bunch of information for the VMs living in specific datacenters within a vCenter (5.1, ugh) environment right now. There are three datacenters with clusters within each (plus some hosts not in clusters, but still within the datacenter items). With about 4000 VMs total, I really need a solid way to pull the information from just one datacenter, or even from a single cluster/host within each set. The first target is the smallest, with only 18 hosts and 111 VMs listed in the summary of the DC.


I’ve found some scripts to pull the information (or a good chunk of it) but I really need it to be more specific (instead of shotgunning to everything).


Information I really need to pull:

VM name (obviously)

vNIC with portgroup connected to, plus how many of them (if more than one at least) along with the adapter type selected (e1000, etc.)

VMDK information including how many and which datastore it’s on as well as what the type of datastore it is (VMFS, NAS, etc.).

Snapshot if present (I’d also prefer to have the total snapshot size if easy, but I can always gather that later).

Affinity rule(s) applied against the VM(s). If this can include which rule is applied, that would be great.



IMO, easy stuff to add would be the OS inside the VM, IP address, and power state. I’d also like to have the location information for the VM. Such as which datacenter, cluster and host. Or at least have that available and either enabled or disabled easily (add/remove # in front of the lines).


I’ve been asked to get all of this for the first target before end of the week. I’d like to have it sometime before EOD tomorrow. One of the scripts I found earlier today is still runnning.


Get-VM | Select-Object Name, Powerstate, NumCPU, MemoryGB, @{N=”Noofdisk”; E={($_ | Get-HardDisk).count}}, HardDisks, @{N=”Datastore”; E={($_ | Get-Datastore).Name}}, @{N=”DiskState”; E={($_ | Get-HardDisk).storageformat}}, ProvisionedSpaceGB,  @{N=”Snapshot”; E={($_ | Get-snapshot).count}}, VMHost,   @{N=”OS”; E={$_.ExtensionData.summary.config.guestfullname}} | Export-Csv -NoTypeInformation -UseCulture -Path “C:powercli_reportsInventory4Result.csv$(Get-Date -f MM-dd-yyyy-H-mm-ss).csv”


The above script just finished and pulled up all the info listed in it (good sign). Can I simply add “NetworkAdapter,” to the list to get the adapter type for each VM?? I’d still like to narrow down the target to just the DC/cluster I need to focus on (at each run time). Even if it means altering the script to be target specific. I’m also going to still need the rest of the info I listed above added to this. With each run taking over an hour (around 1-1/4 to 1-1/2 hours) it would be better. Especially when I can target a smaller group and get the results faster.


Hopefully someone will answer up soon (like LucD).


update: added the “Get-Datacenter =”<datacenter>” | ” at the start to narrow it down. I can change it to a cluster later when I start hitting the one with over 3000 VMs in it (so it takes less time).

Still trying to figure out how to get the Network Adapter Type added to the list. I’ve tried added “@{N=”NetworkAdapter”; E={($_ | Get-NetworkAdapter)}}” but it’s not giving me the desired result…


Update2: changed the NIC line to “@{N=”NetworkAdapter”; E={($_ | Get-NetworkAdapter).type}}” and that pulls the info needed for that section… Need to figure out how to add a NIC count line to this too (hope what I’m thinking will work, but will see).


Update3: I’ve managed to get almost everything needed. Except for a way to get the DRS affinity rule for any VMs they are applied against. Since this is going against a DC, is that just not possible? I’ll consider pushing the script against a cluster tomorrow.


Message was edited by: golddiggie

Issues delivering USB Device from the Internal USB port of a Dell Poweredge R430 server, to an ESXi 6.5 Update 2 Guest Debian VM

This post was originally published on this site

Hy everyone.


Hope I’m in the right place to be asking this question, if not, please be kind enough to redirect me.


So, in a setup where we have a USB device connected to the Internal USB port of a Dell Poweredge R430 server and want to deliver it to an ESXi 6.5 Guest Debian VM (we know this is not best practices but please try to disregard the reasons, it’s where we’re at), we’re having an issue where in some situations, if the device is disassociated from a VM and we reboot the server we then start getting “USB Enumeration failed” errors or other USB related errors if we attempt to add the USB device to a VM, this happens until we are completely unable to find the device as available to be added to the VM, like greyed out in the interface. For what we gather to be able to find the device again we have to remove it physically, inserting it again and boot the server.


Really weird situation. Anyone has any ideas? We’re out. We tried with USB Passthrough options, disabled vmkusb drivers and we could not find much else to try.




Sync computer accounts still has old machines

This post was originally published on this site

Hi All,


Currently playing in my DEV environment.

Which is running AppVolumes 2.14


My Production is running AppVolumes 2.13.2 but I seem to have over 5000 machines even tho I only have 300 online working.


So doing a test in DEV before we deploy to production.

Currently I have 24 machines running online so to make sure the Database is fine I created multiple desktop pools to get the numbers up I currently have 85 machines.


So I have deleted my test pools and should be back to only 24 machines again but each time the system Syncs with AD its syncing 85 machine even tho we only have 24 ??


Now my Home page on Appvolumes shows Computer Utilization 85 machines which I’m expecting that number to come down to 24 again.


Am I doing something wrong here I thought Appvolumes 2.13.3 had this issue sorted or at least now 2.14.


Thanks in advanced