Archive

Posts Tagged ‘XenClient’

New #Citrix #Visio Stencils – via @djfeller – #XenApp #XenDesktop #XenClient #XenServer

January 23, 2013 Leave a comment

Thanks a lot for the great work you did on Project Accelerator, and for sharing the Visio stencils!! 🙂

By spending a little time in the Assess phase, Project Accelerator creates this awesome looking diagram

Arch

The truth is, this diagram took many, many, many revisions. We wanted to create something that was easy to follow while providing the most important information people wanted to see, which included IOPS, servers, VMs, storage space, desktop images, infrastructure components, and so much more. It took a few revisions before I had something in Visio that did all of that. Then we gave my diagram to Marta Guerra, a senior designer on the Project Accelerator team. She turned the diagram into something easy to follow and very clean with new images/icons for all of the components. I’m still impressed. I know many of you are too because you’ve asked for the Visio stencils.

Unfortunately, Project Accelerator diagrams aren’t done in Visio, but that didn’t stop us from giving you what you wanted. With the help of Marta, I’ve been able to turn these images into a new set of Citrix Visio Stencils.

Get them here

//Richard

 

#Citrix #XenClient – Securing External-Facing XenClient Synchronizers with #NetScaler

October 29, 2012 Leave a comment

Ok, an interesting blog post for you out there that are thinking of or already are using XenClient!

One of the key value propositions of XenClient is the remote image and device management capabilities of XenClient Synchronizer– the management server for XenClient devices.  Synchronizer enables customers to centrally create, manage and update images for delivery to endpoints where the image executes locally.  Synchronizer also enables administrators to specify client side policies and for users to back up their images.

A key use case for these capabilities is centralized image management for mobile users.  A common question customers pose when dealing with the issue of mobile users that travel or those that are not located in the office is: what is the best way to expose the Synchronizer to the public Internet?  Our response to date has been to offer three options:

Option A: Port Forwarding or forward requests (port 443) from the edge (firewall) to the Synchronizer.

 

 Option B: Put the Synchronizer in the DMZ.

Continue reading here.

//Richard

%d bloggers like this: