The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

  • My badges

  • Twitter Updates

  • My Flickr Stream

  • Pages

  • All categories

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 1,603 other followers

Archive for the ‘View’ Category

airbus-seclab/crashos

Posted by jpluimers on 2018/10/30

Cool repository, but contact your cloud provider before trying…: [WayBack]¬†airbus-seclab/crashos.

via:

–jeroen

Posted in Fusion, Hyper-V, KVM, Power User, Proxmox, View, VirtualBox, Virtualization, VMware, VMware ESXi, VMware Workstation | Leave a Comment »

Check If A Linux System Is Physical Or Virtual Machine

Posted by jpluimers on 2018/10/08

One day I am going to try to extend this for a few other virtualisation environments and Linux distributions: [WayBack] Check If A Linux System Is Physical Or Virtual Machine

Via: [WayBack] Check If A Linux System Is Physical Or Virtual Machine #Linux РJoe C. Hecht РGoogle+

–jeroen

Posted in *nix, *nix-tools, Fusion, Hyper-V, KVM, Power User, Proxmox, View, VirtualBox, Virtualization, VMware, VMware ESXi, VMware Workstation | Leave a Comment »

SysInternals sdelete: zero wipe free space is called -z instead of -c

Posted by jpluimers on 2016/09/20

In the 2009 past, sdelete used the -c parameter to zero wipe clean a hard drive and -z would clean it with a random pattern.

That has changed. Somewhere along the lines, -c and -z has swapped meaning¬†which I didn’t notice.

This resulted in many of my virtual machines image backups were a lot larger than they needed to be.

The reason is that now:

  • -c does a clean free space with a random DoD conformant pattern (which does not compress well)
  • -z writes zeros in the free space

Incidently, -c is a lot slower than -z as well.

TL;DR: use this command

sdelete -z C:

Where C: is the drive to zero clean the free space.

–jeroen

Posted in Batch-Files, Development, Fusion, Hyper-V, Power User, Proxmox, Scripting, sdelete, Software Development, SysInternals, View, VirtualBox, Virtualization, VMware, VMware ESXi, VMware Workstation, Windows | Leave a Comment »

VMware View Client uses PCoIP; please network admins read the PCoIP checklist!

Posted by jpluimers on 2012/02/24

Somehow, I have the impression that not all VMware View Client network admins fully read and understand the “PCoIP Protocol Virtual Desktop Network Design¬†Checklist

That checklist is important, as it is easy to get things wrong and dissatisfy your users without reason (heck, they get worse than mediocre RDP performance experience, so you could’ve saved you the work of PCoIP in the first place).

So please do read the “PCoIP Protocol Virtual Desktop Network Design¬†Checklist“.

It starts with

The PCoIP protocol provides a real-time delivery of a rich user desktop experience in virtual desktop and remote workstation environments.

To ensure a responsive desktop, the PCoIP protocol must be deployed across a properly architected virtual desktop network infrastructure that meets bandwidth, QoS, latency, jitter, and packet loss requirements.

CheckPoint VPN sometimes can be a dork combined with PCoIP. and at least make sure UDP works well over your VPN.

–jeroen

via:¬†“PCoIP Protocol Virtual Desktop Network Design¬†Checklist

(Some more backgorund reading and even more)

(fixed typo: one of the PCoIP occurances was PCiOP, luckily, Google knows better :)

Posted in Power User, View, VMware | 2 Comments »

Very odd cause (and solution) for VMware View Client “Connect Desktop Failed”: Event Log could not start because of Access Denied error 5.

Posted by jpluimers on 2012/02/09

Lets start post 800 by mentioning it took quite a bit of time to solve the connection problem to VDI. I hope it will help others, and if I ever run into this again myself: now I know where to look :)

Some clients make heavy use of VMware VDI (Virtual Desktop Infrastructure) which moves the desktop into the VMs in the data center.

A while ago I spent most of the day tracking down a “Connect Desktop Failed” error with VMware View Client running on a Windows 7 x64 workstation to connect to a VDI VM. It would connect to the VDI server, authenticate, start the Desktop, but could not connect to the Desktop.

The amazing thing is that the VMware view client worked fine on an XP VM workstation (with and without SNX) XP physical machine with SNX, and another Windows 7 x64 VM workstation (also with and without SNX) and Windows 7 x64 physical machine with SNX.

Clearly something was wrong with this particular Windows 7 x64 workstation that is host of most of my development VMs so I didn’t want to do a¬†re-install.

I tried many obvious things on the Windows 7 x64 workstation:

  1. reboot
  2. disable firewall
    (that would have indicated some of the ports required by VMware view were not open: in practice not all ports mentioned in the list are used)
  3. uninstall software from various vendors that might interfere with network activity
  4. disabled virus scanner
  5. step down from VMware View Manager 5 client to VMware View Manager 4.6 client
  6. circumvented SNX (CheckPoint SSL VPN extender) making sure I was on the same WAN and later LAN of the VDI
  7. verified twice I had indeed Windows 7 SP1 applied
  8. laughed about the SSE support required by VMware view client

Since the “Connect desktop failed”¬†does not return many English search results, I started browsing the Russian ones. Read the rest of this entry »

Posted in Power User, View, VMware | Leave a Comment »

 
%d bloggers like this: