Subscribe RSS Feed | Follow on Twitter

Archive for the ‘Network’ tag

Networks Ports Diagramm for Horizon Workspace

without comments

Horizon Workspace comes as a vApp containing several virtual appliances which handle different jobs. The first rule for installing Horizon Workspace is: Get your DNS working! After that the configuration is quite easy. All setup for the vApp is done on the Configurator virtual appliance which propagates the settings to the other appliances. This information is sent via the SSH port which means that all appliances must be reachable from the Configurator via port 22. But what about the other services on the appliances? How do they communicate to each other? The following diagram gives you an overview of the open ports needed in your Horizon environment.

Untitled drawing

Please note that a few ports are configurable. This includes the connection to the database, the Active Directory, theView and SMTP server and last but not least the vCenter.

Written by Christoph Harding

April 15th, 2013 at 10:49 pm

Riverbed expands support for VMware Horizon View

without comments

News from Riverbed at PEX. The vendor is expanding their support for virtual desktops combining of it’s Stingray, Cascade und Granite platforms.

Riverbed Technology is filling out its WAN optimisation line for VMware’s virtual desktop infrastructure (VDI) platform.

The company said the combination of its Stingray, Cascade and Granite platforms will allow companies to deploy hosted desktops at branch offices and other remote locations.


Written by Christoph Harding

February 27th, 2013 at 10:07 am

VMware Mirage Series Part 4 – Client Installation and Centralization

with 2 comments

Today I had a great journey into the past. I’ve installed Microsoft Windows XP from scratch in a virtual machine. But I only did it for one reason – to have a desktop running Windows XP for my first Mirage Client installation and centralization. The initial installation of Windows XP was done very quickly but I’ve also wanted to install all available patches for SP3 so it took quite a while. After a reboot I had a nice and fresh XP installation. A great start for the next step in my Mirage home lab series here on That’s my View. If you haven’t seen the other articles before please go through them first.

Can you remember this?


I’m sure you can and maybe your company is still on Windows XP as about 40-45% of companies in the world. But as you know Windows XP support is ending in April 2014 which is a good reason to migrate your desktops soon because Microsoft but also 3rd party software vendors won’t support the old Windows platform anymore.

Windows Migration and Hardware Migration are two of the use cases of VMware Mirage. There is probably no easier way of migrating from one OS to the OS or from one hardware platform to another. If you want to learn more about the migration use case in general you can check this whitepaper or read more about a reference story VMware did with ADAC, Europes largest automobile insurance association.

Enough marketing, no let’s dive into the Mirage Client installation piece.

As already mentioned in another article Mirage is a Client/Server application which can centralize the data of an endpoint and rollout new operating systems and applications in form of layers. To be able to do that you need the Mirage Management Server and Mirage Server I’ve installed last time and the Mirage Client which runs on the endpoint. The installation of the client application is quite easy.

Get the installation package in 32-Bit or 64-Bit (there are two MSI files) and then start the installer. If you’ve the .NEt Framework 3.5 not installed on the Windows XP, the installer will immediately stop at the first dialog. Install the framework and you’ll be fine. After accepting the license agreement you’re asked for a Mirage Server location. Enter the FQDN or IP address of the server into the text box and select the checkbox for an SSL connection if you’ve configured your server with SSL before.


As I’ve not configured SSL I just clicked Next which brought me to last step of the wizard. Just click Install and the wizard will finish, starting the Mirage Client installation. That’s it! In the task bar you’ll find the Mirage icon. Now I’ll give you a quick overview of the client’s functionality.

11 12 13

As you can see there are only a few options in the Mirage Client task bar app. Mainly the fronted helps the user to see if the Mirage client is working or idling. The user can check this clicking on Show Status. The other options help to create log files and the user can snooze the complete client operations for 15 minutes, 2 hours or 4 hours. But this doesn’t mean that the client does affect the user that much so he needs to snooze it. The Mirage Client is designed to only work in the background not affecting the user experience. But let’s go back to the Status windows quickly. Her’s a screenshot.


The Mirage Client is connected to the server but the status is Pending Assignment what means that the Mirage Administrator needs to activate this client first using the Mirage Management Console. Going back into the Mirage Management Console you can see the pending devices.


Right clicking on Centralize Endpoint you can start the wizard which leads you through the activation and first centralization of the Mirage Client. It’s just a 4-step wizard which asks for a few configuration parameters.

  • The upload policy
  • The base layer to configure
  • The default volume where the client is being stored

What does that mean? The upload policy can be configured in the Management Console but I left it with the defaults. The policy is a rule which enabled you to control what type of data is centralized and which not. i.e. you could control that MP3 or video files are not going to be synchronized into the datacenter. The next option is the base layer configuration. The base layer is the first layer of a CVD which includes the operating system and the core applications. In my home lab I first wanted to just centralize desktop without assigning a base layer as I haven’t installed my reference machine with Windows 7 yet. I’ll do that later! Last step is the storage volume to store the CVD on. My server has only one volumes so this was a no-brainer.

After finishing the wizard you can see the client being transferred from the pending devices to the assigned devices node.


In that screenshot you can also see that the upload is initializing at the moment. This means that the Mirage Client is now kicking in. On that side you can see this:


After a while, depending on your network speed the whole desktop is available in the data center as a CVD. Quite easy! In my example the Windows XP installation had a total size of 2.3 GB which is not that much but there was only the plain operating system installed in my desktop. One of the most important functions of Mirage is the network optimization and the file and block based de-duplication. That means that if you’ve centralized your first Windows desktop, next time a client is being centralized, the server checks which part of the data is already available on the Mirage Server volumes and then only synchronizes the delta. Think about migrating a whole branch with 50 desktops. The network traffic will be reduced loads.

But centralizing the endpoint is only the first step. In my next article I’m going to setup the reference machine with a Windows 7 operating system and then create the base layer with it. Assigning this base layer to my Windows XP desktop means migrating it from one OS to the other. Mirage offers a few wizards which will handle all steps of the migration.

I hope this article has given you a great overview of the Client Installation and first centralization. If you have any questions please just comment on this article and I’ll come back to you as soon as possible.

Part 1:

Part 2:

Part 3:

Written by Christoph Harding

February 5th, 2013 at 9:00 pm

In-Place Windows XP to Windows 7 Migration using VMware Mirage

without comments

I’ve learned that a Windows Xp to Windows 7 Migration is tough for loads of customers as the tools they mostly use aren’t easy to work with. Check out this video about an In-Place migration of Windows XP to Windows 7 with VMware Mirage.

Written by Christoph Harding

January 14th, 2013 at 1:00 pm

VMware View Network Port Table

without comments

Kudos to Matt Lesak who posted a link to the VMware View 5.0 Documentation Center. He pusblished a link on Twitter which forwards you to the TCP and UDP Ports needed for VMware View. As I get tons of requests about the networking ports I thought it might be a good idea to pusblish this link on the blog.

The article gives you an overview of all ports with Source, Target, Port number, protocol and a brief description.


Security server


View Agent 4.5 or earlier

50002 (can be changed by group policy)


PCoIP (AES-128-GCM only) if PCoIP Secure Gateway is used.


Original Tweet by Matt: #VMwareView network port table #VDI #VMware

Written by Christoph Harding

December 14th, 2011 at 4:59 pm

Posted in View Manager,VMware View

Tagged with , , ,

Riverbed to optimize PCoIP network traffic

with one comment

During VMworld in Las Vegas, Teradici announced a new partner program to enable network optimization for PCoIP traffic. The first company to joint the Network Solution partner program is Riverbed. Please see the press announcement attached.

VMworld Las Vegas — August 30, 2011 —Today at VMworld® 2011, Teradici Corporation, the developer of the innovative PC-over-IP® (PCoIP®) protocol that enables a true PC experience for desktop virtualization, today announced the Teradici Network Solutions Partner Program. First to join the program will be charter program partner Riverbed Technology (NASDAQ: RVBD), the IT performance company and market leader in wide area network (WAN) optimization. Teradici and Riverbed® will engage in a strategic partnership to ensure the high performance of Virtual Desktop Infrastructure for VMware View™ environments.

The Teradici Network Solutions Partner Program has been developed to help build technical partnerships with network OEMs to enable the integration and optimization of PCoIP® technology. The program allows network OEMs to access the PCoIP protocol and protocol interfaces, allowing for network optimization of UDP-based PCoIP traffic.


“We see our future collaboration with Teradici and the Network Solutions Partner Program as a great way to show our continued commitment to accelerating Virtual Desktop Infrastructure,” said Venugopal Pai, vice president of global alliances at Riverbed. “We’re looking forward to our partnership with Teradici since they are the developer of the PCoIP protocol, offering uncompromised VMware View desktop experiences for all user types.”


“We’re thrilled to be announcing our Network Solutions Partner Program and the planned partnership with industry leader Riverbed Technology,” said Trent Punnett, vice president of marketing, product management and systems engineering, Teradici. “The goal of the program is to provide members with access to PCoIP technology and a roadmap of features, products and platform offerings, thus allowing Network OEMs to differentiate and build value added into PCoIP® based VDI optimization and management solutions.”


Partner Program members receive numerous benefits including: access to Teradici PCoIP technology, network solutions and support; advanced input into PCoIP solution architecture and features; reserved access to alpha, beta, and RC releases; and access to documentation and technical guidance from the Teradici engineering team. Other program elements include “PCoIP Optimized” certification for partner solutions.


“The strategic partnership being developed by Teradici and Riverbed is a strong example of the industry commitment to solving IT pain points and optimizing networks,” said Vittorio Viarengo, vice president, End-User Computing, VMware. “We are committed to delivering industry-leading, high-performance VDI for VMware View™ environments to empower a more agile, productive and connected enterprise, and this alliance will help us to achieve this goal.”


To learn more about the Teradici and the PCoIP protocol, please visit


About PCoIP Technology

Teradici’s PCoIP protocol is an innovative remote display technology that allows the user’s desktop operating system, applications, and data to reside in the datacenter, eliminating the need for traditional desktop workstations, PCs and thin clients, and delivers an uncompromised user experience to each person, anywhere, over any network and to any type of device without incurring the security risks associated with having data reside in remote PCs, laptops, or tablets. PCoIP technology provides high resolution, full frame rate 3D graphics and high-definition media, with full USB peripheral interoperability, locally over LAN or remotely over high-latency WAN networks. It compresses, encrypts and encodes the entire computing experience at the datacenter and transmits it ‘pixels only’ across a standard IP network to secure, stateless PCoIP zero clients, thin clients, and mobile devices.


The PCoIP protocol is implemented in several software configurations, including VMware View™, the industry leading desktop virtualization platform as well as in silicon for hardware accelerated performance and enhanced security. A growing ecosystem of over 30 third-party vendors provide a wide variety of PCoIP products including server plug-in cards, rack and tower workstations, blade PCs, zero clients, integrated monitors, and IP phones with PCoIP capability.


About Teradici

Teradici Corporation has developed PCoIP® (PC-over-IP®) protocol, a unique remote display technology which makes network delivered computing a viable corporate computing reality. Founded in 2004 and headquartered in Burnaby, BC, Canada, Teradici for the first time enables an exceptional end user experience for datacenter-based computing. Through a combination of unique graphics algorithms, flexible software solutions and high-performance silicon processing, and workstation/server add-in cards, the company is changing how personal computers are used, deployed and managed. For more information visit:


PCoIP and PC-over-IP are registered trademarks of Teradici Corporation in the United States and/or other countries. Any other trademarks or registered trademarks mentioned in this release are the intellectual property of their respective owners.







Written by Christoph Harding

September 1st, 2011 at 9:06 pm

How to disable weak ciphers in View 3.1

without comments

A colleague of mine had a requirement from his security-department to disable the ability to use “weak ciphers” to connect to the security server.

Read the rest of this entry »

Written by Joel Lindberg

August 28th, 2009 at 2:40 pm

By continuing to use the site, you agree to the use of cookies. more information

The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.