Aug 27

The presenter has certifications from Microsoft, VMware, and Citrix. Sounds like a great setup to put the Smackdown on a VDI solution recommendation.

The business consumer wants it all and wants it now. Focusing on the business consumer and how they want to work is a good starting point.

Where are my applications?
Where is my data?
How do I manage it?

Ten points to implement VDI is shown, the main one I see as important is end user experience and perception which is going to lead to adoption.

Success will come with vision, execution, adoption.

Good, bad, ugly:
Pay attention to the following that can be bad or ugly.
Voice, webcam, VoIP, unified communications.
Networking, latency, bandwidth, QoS.
Rich media, audio , video.
2D/3D graphics
Mobile and touch/tablets oriented devices.
Overall cost reduction of technology stack
Overall complexity in complete technology stack
Streamline management between VDI me classic clients
Total cost of ownership and return on investment
Licensing (SA, VDA, CDL, in tune)
Html5 as remote access solution
Skills and mindsets from IT organization
End user perception

VDI and Storage impact
Vendors say 70-90% read and 30-10% write
Real world is 20 percent read and 80 percent write

Windows 7 and 8 are typically 4K blocks.

VDI workload for storage is different that normal backend storage.

In the beginning of he VM desktop life cycle the VM will be mostly read then progress to write io during production use. The beginning and end is logging on and logging off.

Write iops are king.

Look out for lunch storms. This is when people are at their desk during lunch using YouTube. This was 240KB blocks. Causing 64 iops of 4KB for each block for YouTube. This just an example and you will need to understand the environment and have enough capacity for storms.

Storage solutions for VDI
Minimize IOPS check project VRC
Solid State Drives
Io consolidation, deduplication
Random to sequential
Auto tiring
Memory (NAND)

Citrix and VMware are the 2 big players in VDI. This is the landscape. Microsoft is trying. Quest is not moving much. The battle today is Citrix and VMware.

Which product is the best? Flip a 2 Euro coin. It’s a toss up. If you have good requirements then the clear winner will be uncovered.

Benefits, strengths, etc

Citrix XenDesktop 5.6 FP1:
Good vision and strategic acquisitions in enterprise mobility
Image management
VI and management platform
remote pc
UX 3d applications
extensive endpoint support
deep integration with secure access and secure network solutions.
VDI assessment software included
Personal vDisk, intelli cache,

No GPU sharing
Client side and server hosted RDP
Personal vDisk no real image management
Way too many deployment solutions in Citrix Stack
Amount of consoles
VDI + edge sight is edge sigh

What is new in XenDesktop 7
Flexcast management
Windows 8 and 2012 support
2 consoles, director and studio
Citrix application streaming

Microsoft 2012/8:
It’s Microsoft.
It’s good enough, why pay more?
Easy deployment of 2012 roles.
No SCVMM required
Active active connection broker
Pooled VM’s, shared and local storage scenarios.
RFX is the first GPU sharing solution
RFX progressive display
Server 2012 hyper v performs well and is mature

Is Microsoft as a company interested RDVH?
Enterprise management functionality
RFX = Hyper-V only.
RDP and RFX limited endpoint support
User profile disk
No shadowing
No process kill for central console
Limited documentation

Windows 2012 R2 Server brings back shadowing
Quick reconnect in WAN scenarios
Can restrict iops/VM
Tiered storage
Online disk-deduplication

VMware Horizon view 5.2:
Clear vision and communication
Solid name in virtualization space
Application virtualization is part of stack
Thin app and VDI is good combination
Enterprise reference architectures
Image management is easy and strong (pooled VM’s)
Hardware accelerated 3D graphics
Teradici Server offload card for PCoIP
PCoIP is doing well in LAN and WAN
PCoIP server side rendering
Clientless access via html5
UPM is part of solution
View composer array integration
Virtual storage accelerator

Impact of PCoIP on server side
UPM is UPM only
Scalability in larger (10,000) environments can be challenging
Clientless access is basic.
ViewClient for WinRT is RDP only
Mirage is not part of VDI
Automatic PCoIP tuning

Ingredients for success with VDI
Focus on end user and scenarios
What is your desktop strategy
Focus on user experience
Reality checks and proof of concept
Understand VDI and storage impact
Do not focus instantly on vendor features

Wow what a good sessions. Lots of content and slides. Definitely a slide deck to review.

Thanks Rubin Sprujit!

Feb 14
Windows 8
icon1 Trace | icon2 Technical | icon4 02 14th, 2012| icon3No Comments »

I got to play around with Microsoft Windows 8 client with Metro on a few devices. This new OS from Microsoft seems to have a very few improvements over Windows 7. There is new dashboard type interface that appears to be focused on touch devices. In all honesty this seems to be the only improvement of note.

The touch interface is good. The soft keyboard performed well. The interface was easy to navigate and intuitive. I found the use for it to be mostly eye candy though. Anytime you opened a useful application you were taken back over to a Windows 7 feeling desktop. I looked inside regedit and control panel, I found nothing really new here. In fact many things looked exactly like Windows 7.

The lack of finding anything really different in the desktop side of Windows 8 has lead me to believe that maybe Metro was just a skin on Windows. As I later discovered, Metro is in fact not just a skin on Windows 8. The Internet Explorer appears to run in a separate space on Metro vs. the desktop.

I asked myself, what is the benefit of Windows 8 to the average corporate worker in an office? The answer is nothing. The real benefits are for mobile workers and those who wish to consume Windows 8 with a touch device. I could easily see using an iPad or other touch device to consume a Windows 8 virtual desktop with ease. This of course would depend on the swipe and other touch capabilities working via remote desktop.

There are a few other remote worker beneficial technologies in Windows 8. As I discover their real benefits in the future I am sure we will discuss them. For now I am anxiously awaiting the release of Windows 8 client for use in the home.

Aug 24

When using Outlook 2007 with Exchange 2007 some of our users would get prompted to login to the client access server. Clicking cancel would still allow them in their mailbox with what appeared to be all functionality. However the prompt would return after a few minutes. This was very annoying as you can imagine. After some web searching I was able to find the problem a long with a solution.

First open up Exchange 2007 powershell. We’ll check on the problem and verify it is the same as well as fix it from here.

Run the following command.
[PS] C:\Windows\System32>Get-ClientAccessServer | fl

Name : EXCH03
OutlookAnywhereEnabled : False
AutoDiscoverServiceCN : exch03
AutoDiscoverServiceClassName : ms-Exchange-AutoDiscover-Service
AutoDiscoverServiceInternalUri :
AutoDiscoverServiceGuid : 77378f46-2c66-4aa9-a6a6-3e7a48b19596
AutoDiscoverSiteScope : {DownTown}
IsValid : True
OriginatingServer :
ExchangeVersion : 0.1 (8.0.535.0)
DistinguishedName : CN=EXCH03,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administ
rative Groups,CN=PHE,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=company,D
Identity : EXCH03
Guid : 341169c4-dd14-47b2-b3e6-01ca8653dfbb
ObjectCategory :
ObjectClass : {top, server, msExchExchangeServer}
WhenChanged : 4/22/2009 10:03:06 AM
WhenCreated : 4/7/2009 10:37:52 AM

Name : EXCH04
OutlookAnywhereEnabled : False
AutoDiscoverServiceCN : EXCH04
AutoDiscoverServiceClassName : ms-Exchange-AutoDiscover-Service
AutoDiscoverServiceInternalUri :
AutoDiscoverServiceGuid : 77378f46-2c66-4aa9-a6a6-3e7a48b19596
AutoDiscoverSiteScope : {DownTown}
IsValid : True
OriginatingServer :
ExchangeVersion : 0.1 (8.0.535.0)
DistinguishedName : CN=EXCH04,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administ
rative Groups,CN=PHE,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=company,D
Identity : EXCH04
Guid : 4857fd2e-da32-4a7c-a97a-cfb0135d2875
ObjectCategory :
ObjectClass : {top, server, msExchExchangeServer}
WhenChanged : 4/13/2009 12:46:00 PM
WhenCreated : 4/13/2009 10:07:00 AM

You should notice here that our AutoDiscoverServiceInternalUri points to our external dns name for Outlook Web Access. This is our problem. This should be the internal dns name for our client access server. Here is the command to set it to what we want.

[PS] C:\Windows\System32>Set-ClientAccessServer -Identity "EXCH04" -AutodiscoverServiceInternalURI "https://exch04"
[PS] C:\Windows\System32>

« Previous Entries