Monthly Archive: August 2015

rdy 01 0

Virtual Machine CPU RDY Alarm – PowerCLI Script

As I know and I have read it in many blogs that DRS is not sensitive to CPU ready time and when your cluster has enough CPU frequency and memory, cluster is balanced. There is a simple solution to resolve the issue or reduce the issue in your environment. Of course, this is not true solution and you need to analyze your platform, calculate your requirements especially CPU cores for your VMs and add more physical cores to by adding more physical servers. Create Alarm At first step, you need to define an alarm in your vCenter for virtual machine CPU ready: Create a user-defined alarm and enter a name as you wish. In Triggers tab, select “VM CPU Ready Time (ms) and define waning and error values and condition length. Default values are fine for most platforms. Just that, click on OK and our job is done. If you have virtual machines with high CPU ready, it will be detected by vCenter and alarm will be generated. Note: Please copy your alarm name and paste it in the below script. Also you can change exception time, if you need to run it after working hours. The Script Further Reading...

Run ESXi Commands Via PowerShell And SSH 1

Run ESXi Commands Via PowerShell And SSH

Some ESXi CLI commands have no alternative in PowerCLI and you have to run the commands on ESXi via SSH or locally. But there is another easier way to run batch commands and get result. You can use PLINK on this regard. Plink is one of Putty components, so you need to have plink.exe on your local drive or any location which to be accessed. Change the below script parameters and run your commands as you like: $User = <User> $Pswd = <Host Password> $hostName = <Host> $plink = <PLink Path> “\plink.exe” $plinkoptions = ” -v -pw $Pswd” $cmd1 = ‘ esxcli vm process list’ $remoteCommand = ‘”‘ + $cmd1 + ‘”‘ $command = “Echo Yes| “+$plink + ” ” + $plinkoptions + ” ” + $User + “@” + $hostName + ” ” + $remoteCommand $result = Invoke-Expression -command $command $result [quotes_and_tips]

Remove MSOCache from VDI template 0

Remove MSOCache from VDI template

If you are going to deploy VDI for your users and you have to install Microsoft Office for the users, you need to keep 1GB free space for the software installation cache files on the virtual machine’s C drive. One gigabyte space is important when you have plan to deploy the VMs as Linked-Clone VMs and it can reduce your storage cost and you can create more VMs. Now, what is solution to remove the files without any impact: At first step, install Office components as you want and take a backup from this folder “C:\MSOCache” on a network shared folder our another drive. Remove the folder from the VM’s C drive. Make an ISO file from the backup folder. You can also rename the folder, it doesn’t matter. Create a symbolic link by MKLINK command and make a “Directory Junction” on C drive, for example: MKLINK /J C:\MSOCahce E:\MSOCache E: is your CD-ROM drive your VM. Then, if you need to modify Office components, you can mount the ISO file and do your modification. Of course, you can make the symbolic link when you need to this. There is another solution but it’s very difficult, you have to change...

PCoIP Configurations – Client Side 1

PCoIP Configurations – Client Side

I have made a registry file based on PCoIP recommendation for apply on all virtual desktops in our company 2 years ago. The settings covers image quality, bandwidth, analog sound channel and USB permission. You can apply the below configuration on your template ad there is no need to apply configuration on Zero Clients: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Teradici\PCoIP\pcoip_admin_defaults] “pcoip.transport_session_priority”=dword:00000001 “pcoip.server_clipboard_state”=dword:00000001 “pcoip.enable_build_to_lossless”=dword:00000000 “pcoip.max_link_rate”=dword:00015f90 “pcoip.mtu_size”=dword:00000514 “pcoip.device_bandwidth_floor”=dword:00002710 “pcoip.enable_audio”=dword:00000001 “pcoip.enable_micin_noise_filter”=dword:00000001 “pcoip.audio_bandwidth_limit”=dword:000001f4 “pcoip.usb_auth_table”=”23XXXXXX” “pcoip.usb_unauth_table”=”2208XXXX” “pcoip.minimum_image_quality”=dword:00000032 “pcoip.maximum_initial_image_quality”=dword:0000005a “pcoip.maximum_frame_rate”=dword:0000000f “pcoip.use_client_img_settings”=dword:00000001 “pcoip.image_cache_size_mb”=dword:0000012c You can change MTU size, sound bandwidth and bandwidth floor regarding to your network bandwidth. Our users are happy with the above configurations and I think, these settings are fine for any LAN environment. You can read VMware KB and VMware Network Optimization for more information and optimize your platform.   [quotes_and_tips]