display user's ad group 


net user john /domain

留言

張貼留言

這個網誌中的熱門文章

Update X710 firmware

Go to the below website and download the update utility. https://downloadcenter.intel.com/download/24769#help You will want the XL710_NVMUpdatePackage_v5_04_ESX.tar.gz Copy this onto a datastore accessible by the ESXi server and extract with the command  tar -zxvf  XL710_NVMUpdatePackage_v5_04_ESX.tar.gz [root@coloesx25:/vmfs/volumes/dd478478-16edd549/XL710/ESXi_x64] chmod 755 nvmupdate64e [root@coloesx25:/vmfs/volumes/dd478478-16edd549/XL710/ESXi_x64] ./nvmupdate64e Intel(R) Ethernet NVM Update Tool NVMUpdate version 1.26.17.11 Copyright (C) 2013 - 2016 Intel Corporation. WARNING: To avoid damage to your device, do not stop the update or reboot or power off the system during this update. Inventory in progress. Please wait [******+...] Num Description                            Device-Id B:D   Adapter Status === ====================================== ========= ===== ==================== 01) Intel(R) Ethernet Controller X710 for  8086-1581 03:00 Upda
閱讀完整內容

Installing the VMware View PCoIP Client on Linux

圖片
I am happy to report that I have managed to get the VMware View PCoIP Client to work on openSUSE Linux 12 with the GNOME 3 desktop environment. The first client I tried was the VMware View Open Client, which is an open source project. However the View Open Client does not support PCoIP and only connects to the View desktops using RDP. As I am not a fan of RDP, I was keen on getting PCoIP to work. Some background as to why I needed the PCoIP View Client to work on Linux: Generally for remote access to my lab, I use the VMware View PCoIP Client for Windows, Android and iOS (on the iPad). VMware has made the PCoIP client available on all of these platforms, but no Linux PCoIP client has been released. This article should get you up and running, but bear in mind that it is not supported by VMware. I have a laptop running a Linux Desktop that is connected to my Boeing 737NG flight simulator. The simulator heavily relies on several components that run on virtual machines on ESXi. Th
閱讀完整內容

Manually deleting linked clones or stale virtual desktop entries from VMware View Manager 3.x and 4.0.x

Manually deleting linked clones or stale virtual desktop entries from VMware View Manager 3.x and 4.0.x Symptoms You cannot provision a linked clone desktop pool You see the error: Desktop Composer Fault: 'Virtual Machine with Input Specification already exists' Provisioning a linked clone desktop pool fails with the error: Virtual machine with Input Specification already exists The Connection Server shows that linked clone virtual machines are stuck in a Deleting state Cause This issue occurs when:   a table in the database contains incorrect data.  the virtual machine name has been changed in the vCenter Server manually after the pool has been created, causing View Composer and vCenter Server to refer to the same virtual machine with different names.     Resolution This solution applies to VMware View 3.x and 4.0.x.  For View 4.5 and later, see  Manually deleting linked clones or stale desktop entries from VMware View Manager 4.5 and later (2
閱讀完整內容