Archive
10 Mobile Device Management Leaders That Help IT Control #BYOD, #Gartner, #Citrix, #MDM
Consumers love their smartphones and tablets, so it should come as no surprise that they want to use their devices at work. The pressure to develop and deploy a bring-your-own-device (BYOD) policy is on and coming from every direction, including the ‘C’ suite of executives who tend to be especially keen on using smartphones and tablets for their work.
Managing devices in a BYOD environment is no small feat, and the right mobile device management (MDM) product is a key component in making it work. Here are 10 leading MDM vendors in the market today, drawn from the leaders and visionaries in Gartner’s 2013 Magic Quadrant for Mobile Device Management Software.
Magic Quadrant
#App-V and #XenDesktop 7 – #Citrix, #AppV
A couple of good posts from Citrix (Ram Kumar Mantena & Nagendra Kumar) around the support for App-V on XenDesktop 7 and what to think of etc.
Tips/Tricks for Using App-V Integration with XenDesktop 7.0
XenDesktop 7.0 is released and it supports both Apps and Desktop Virtualization. One of the key features of this release is support for Microsoft App-V. As this is the first release for App-V support, here are some tips/things to consider for an easy deployment of App-V 5.0 in a XenDesktop Environment.
- XenDesktop 7.0 supports Server based App-V deployment scenario where Admin uses App-V Publishing Server and Management Server to manage apps.
- Microsoft App-V client does not support more than 5 Publishing Servers. In Citrix Desktop Studio, although the admin can add one Management and one Publishing server through Studio UI, he can also add multiple Publishing Servers using low level SDKs. It is recommended to add only 5 Publishing Servers. Though Studio low level SDKs take more than five Publishing Servers, studio enumerates App-V apps from first 5 Publishing Servers.
- When adding the Management Server and Publishing Server in App-V publishing node, if the test connection fails and App-V Server is up and running, make sure WinRm is up and running.
- Once the Virtual Desktop Agent is installed on Server/Client, make sure CtxAppVCOMAdmin is member of Administrator group. This is required as some of the App-V operations on VDA side need administrator privileges. This is the user account pre-created by Citrix XenDesktop VDA installation. [CTX138057]
- It is recommended to enable SharedContentStoreMode…. Read more…
#Microsoft finds a new way to deliver a private #cloud in a box – #Azure via @maryjofoley
Interesting!!!! 🙂
It took three years from when it was first announced, but Microsoft may have found a way to deliver a private cloud in a box.

The company’s vision and strategy for doing this has gone through many twists and turns.
Microsoft’s original plan was to provide its largest partners and even a few, select enterprise users a so-called Azure Appliance. Announced in 2010, the Azure Appliances were to be carried by Dell, Fujitsu and HP. These OEMs were to provide the servers which could be installed in partner and select enterprise customers’ datacenters. Microsoft was supposed to provide and maintain Windows Azure as a service to these servers.
The only partner that ever delivered an Azure Appliance was Fujitsu, which announced availability in August 2011. But some time in the past few months, Microsoft ended up dropping its Azure Appliance plans, without ever officially announcing it was dead.
Simplified VDI Architecture – #Citrix, #XenDesktop
This is a great start of a blog series from Citrix!
There’s a perception that VDI is complicated. I’m far from being a rocket scientist, and I’ve managed to implement many successful VDI projects over the past ten years. I truly believe that VDI is one of those things that is only as complicated as you make it.
It’s like saying that driving is complicated. You’d have to be crazy [or very brave] to take your first lesson in Manhattan…during rush hour. That’s why your driving instructor starts you off on a quiet street. You need to know your boundaries. Being successful with VDI is the same – keep things simple to start with and slowly increase complexity at your own pace, when you’re ready for it.
This raises the question – what’s the quiet street equivalent of a beginner’s VDI architecture? It might not be the most optimized and efficient solution, but it would be quick to implement, do the job well and wouldn’t require specialist knowledge or skills. I’ve been thinking about this a lot lately, and I’d like to share my thoughts.
There’s a lot to consider, so I’m going to break this up over four different blog posts:
- Simplified VDI Architecture – Introduction & FlexCast
- Simplified VDI Architecture – Storage
- Simplified VDI Architecture – Provisioning
- Simplified VDI Architecture – Reference Architecture
Martin Zugec will be helping me out with this blog series and will be referring to his experience on actual customer projects that followed many of these recommendations.
XenDesktop or VDI in a Box?
First up, you need to make a decision on VDI in a Box or XenDesktop. VDI in a Box is easier to setup but does have some limitations. Check out Allen Furmanski’s excellent blog post for guidance on how to make this decision. I’m going to concentrate on XenDesktop for this post.
FlexCast
Although each FlexCast model has its own unique advantages, each additional model included adds complexity to the overall project. There is a great table in the Virtual Desktop Handbook (FlexCast Model Selection – Table 11) that provides guidance on the capabilities of each model. The main thing to note is that all scenarios, apart from offline, can be accommodated using the Hosted VDI model (XenDesktop), either with or without a Personal vDisk. It may not be the optimal selection in every instance, but it is almost always a viable solution.
There are a number of reasons why I think that XenDesktop is simpler than XenApp, including:
- Desktop applications are developed to run on desktop operating systems such as Windows XP or Windows 7. There aren’t many developers that test their applications on Windows Server 2003 or 2008. Therefore, you’re far less likely to run into application issues with XenDesktop than you are with XenApp. Even if your applications run okay on 2008 with XenApp, you’re probably going to have issues getting support from the application vendors.
- Hosting applications on multi-user operating systems can introduce additional application compatibility challenges. Users may share the same configuration files and registry hives, especially if the applications are not multi-user aware. This means that one user may change a setting that affects all other users of that server. There are a ton of tips and tricks to get these apps working correctly but we want to keep things simple and choosing XenDesktop helps us achieve this goal.
- As multiple users are hosted on the same operating system, it is important that XenApp desktops are locked down to prevent security breaches and misconfiguration that could impact all users sharing the environment. Typically, this results in an extremely controlled and restricted user experience, hindering user satisfaction and acceptance.
- With XenApp desktops, a single user can consume a disproportionate amount of resources, impacting the performance of other users sharing the same XenApp server. XenDesktop, on the other hand, allows vCPU and RAM assignments to be controlled on a per-user basis. For this reason, I strongly recommend that heavy users are hosted on XenDesktop rather than XenApp.
- With XenDesktop, it is possible to provide users with fully personalized desktops. This includes the ability for users to install their own applications.
- Unlike XenApp, XenDesktop supports generic USB redirection:
I’m a huge fan of Remote PC, especially when you consider just how simple it is to deploy. However, there are some things Remote PC just can’t do, including:
- You don’t have the flexibility to quickly provision or de-provision desktops based on business demands.
- Image management is more complicated than a virtual desktop because you can’t use MCS and PVS can be challenging with desktops outside of the data center
- You need to have a good connection between your XenDesktop Controllers and the physical desktops. Something not always available for WAN users.
Regardless, Remote PC is a great solution in many scenarios. Consider deploying Remote PC at the very start of your project. It allows you to realize immediate value while you’re designing and implementing your full VDI solution.
If XenDesktop is so much simpler why do so many projects still standardize on XenApp? It all comes down to cost – XenApp offers significantly higher levels of scalability than XenDesktop (some sources quote 300% more users). Let’s take a look at this in more detail.
Processor
The Virtual Desktop Handbook provides us with guidelines on processor requirements for both XenApp and XenDesktop (Processor Requirements by Workload – Table 22):
If processor is the bottleneck, we can estimate the scalability of XenApp and XenDesktop for a fairly typical server configuration (2×8 cores):
As you can see, XenApp offers between 17% (heavy user) and 28% (light user) more users than XenDesktop – but nowhere near 300%! Let’s put this into context, if you had 1,000 concurrent normal users, you would need seven physical servers for ‘XenDesktop: Windows 7’ and six physical servers for ‘XenApp: 2008 R2’. Is one additional server per ~1,000 users enough to justify the additional complexity of XenApp?
RAM
For RAM, the Virtual Desktop Handbook table (Memory Requirements by Workload – Table 23) shows us that ‘XenDesktop: Windows 7’ requires significantly…
Continue reading here!
//Richard
Demystifying Citrix Excalibur Architecture – via @kbaggerman
A great blog post by Kees Baggerman! 🙂
For all XenApp admins and consultants out there Project Avalon will bring a big change as we are used to having XenApp servers running on the (what seemed to be) everlasting Citrix Independent Management Architecture and we’re heading to Citrix FlexCast Management Architecture (already included in XenDesktop at this moment) and will be included in the Citrix Excalibur Architecture.
IMA
When looking up IMA in the eDocs you’ll find:
Independent Management Architecture (IMA) is the underlying architecture used in XenApp for configuring, monitoring, and operating all XenApp functions. The IMA data store stores all XenApp configurations.
Basically IMA exists to manage the XenApp or Presentation Server farms by enabling the communications between servers. As stated it transfers information about all XenApp functions like licenses, policies, sessions and server loads. All management tooling within these versions of Citrix’s PS/XA rely on this service for information.
According to Communication ports used by Citrix Technologies IMA uses the following ports:
| Ports | Source | Prot. | Comment |
| 2512 | Common Citrix Communication Ports | TCP | Independent Management Architecture (IMA) |
| 2513 | Access Gateway 5.0 Controller administration | TCP | IMA-based Communication |
As we can see IMA uses 2512 (by default) to communicate with other servers and the Access Gateway Controller uses 2513 (by default) for IMA-based communication. The port IMA uses can be changed or queried via the commandline tool IMAPORT.
Brian Madden did a blogpost way back in 2007 but it’s definition of IMA is still current:
Independent Management Architecture is:
- A data store, which is a database for storing MetaFrame XP server configuration information, such as published applications, total licenses, load balancing configuration, MetaFrame XP security rights, and printer configuration.
- A protocol for transferring the ever-changing background information between MetaFrame XP servers, including server load, current users and connections, and licenses in use
FMA
With the introduction of XenDesktop we got a new architecture called Flexcast Management Architecture. This new architecture has got an agent-based setup where we can install the operating system including the basic applications that need to be installed and after that we can install an agent. This agent registers itself to a controller and is offered through StoreFront to the end user.
This will be delivered by two different types of agents, one to support Windows Server OS’s and one for Windows Desktop OS’s.
Andrew Wood did an article on Excalibur and used this diagram to explain the architecture:
Citrix FlexCast Management Architecture
- Receiver provides users with self-service access to published resources.
- StoreFront authenticates users to site(s) hosting resources and manages stores of desktops and applications that users access – Web Interface as a platform is essentially resting, but it will cease to be.
- Studio is a single management console that enables you to configure and manage your deployment, a dramatic reduction over the 23 consoles you could well have today. Studio provides various wizards to guide you through the process of setting up an environment, creating workloads to host applications and desktops, and assigning applications and desktops to users.
- Delivery Controller distributes applications and desktops, manages user access, and optimizes…
Continue reading here!
//Richard
Windows #Intune – Toyota rolls out to more than 3000 clients
Automotive Retailer Avoids $1.3 Million in IT Costs with Cloud-Based PC Management Tool
Toyota Motor Europe (TME) had no tools to manage 3,500 car-diagnostic PCs running outside the corporate domain at 3,000 dealerships. TME chose Windows Intune to manage the PCs remotely from a web-based console. It can standardize software deployments to ensure consistent customer service and enhance the security of managed computers to reduce downtime at dealerships. Remote assistance capabilities will also help reduce on-site support costs.
Business Needs
Toyota Motor Europe (TME) manages a network of 30 national marketing and sales companies (NMSC) across Europe. These organizations oversee more than 3,000 dealerships.
In early 2012, TME replaced its stand-alone car-diagnostic tool called IT2 with 3,500 new PCs running more up-to-date software, including Tech Stream and Picoscope. The PCs also store technical documentation. Mechanics attach the PCs to a Vehicle Information Module that connects to a vehicle’s engine to provide critical maintenance information, such as how to reprogram and update a vehicle’s computer chip. The PCs were installed by an external company. The computers are not joined to the domain and operate outside the corporate firewall.
TME did not have a management solution for these 3,500 computers. “We wanted everyone to use the new tools, but we had no visibility into how the dealerships were working with the PCs,” says Niels Svaerke, Manager, Business Process Office, After Sales at Toyota Motor Europe.
NMSC staff downloaded diagnostic software to the PCs from a Toyota intranet site. However, there was no way for headquarters to verify that all dealerships received and installed the software updates concurrently. “It was difficult to ensure that everyone was providing the same level of service by using the same corporate systems and auto diagnostics,” says Dirk Christiaens, Manager of Enterprise Architecture at Toyota Motor Europe. “Also, the head office had no way of knowing if the dealerships deployed an antivirus solution for their PCs, a worrying scenario as they were connected directly to the Internet.”
NMSC employees performed on-site support for mechanics, which often entails travel time. Sometimes, NMSC staff called an external company to reinstall all the software on the PC. Either scenario incurred wasteful downtime at the dealerships.
Solution
To solve these issues, Toyota Motor Europe decided to evaluate Windows Intune, the cloud-based PC management service from Microsoft. Staff at the NMSC can use the web-based Administration console in Windows Intune to run PC management tasks remotely, including software distribution. All that is required is a standard Internet connection, a browser running Microsoft Silverlight, and the Windows Intune client software installed on the PCs at the dealerships. The client returns information on the PC, including software and hardware inventory, and endpoint protection and update status to the Administration console.“We wanted to move into cloud computing, so Windows Intune met our needs perfectly,” says Christiaens. “Windows Intune had a more flexible, pay-as-you-go model, with no additional bandwidth or server costs.”
Read the whole case study here!
//Richard
XenMobile product overview… and It’s nice! via @BasvanKaam – #BYOD, #MDM, #Citrix
Wow! I must say that Bas van Kaam has done a great wrap-up here! I highly recommend you to read this blog post!!! 🙂
It was only about a month ago when I was writing my Blog about the CloudGateway that I wondered which route Citrix would take now that they acquired Zenprise, well… here it is… XenMobile, another Xen sibling sees the light! Lets jump right in…
I had the opportunity to make use of one of Citrix’s demo environments to have a closer look at MDM, which is an awesome way to explore new and existing products by the way, if your company is a Citrix partner and has access I definitely recommend having a look. Besides that I used the Citrix E-Docs website as well as Citrix.com to find as much information as possible.
The main focus of this article will be on XenMobile MDM as the Mobile Solutions Bundle (one of the two editions available) focuses primarily on the CloudGateway which I already discussed in one of my previous blogs.
MDM?
MDM stand for Mobile Device Management and it’s just that! Here’s what Citrix has to say about it: As per Citrix: XenMobile MDM is a robust mobile device management solution that delivers role-based management, configuration, and security for both corporate and employee-owned devices. Upon user device enrollment, IT can provision policies and apps to devices automatically, blacklist or whitelist apps, detect and protect against jailbroken or rooted devices, and selectively wipe a device that is lost, stolen, or out of compliance. Users can use any device they choose, while IT can ensure compliance of corporate assets and secure corporate content on the device.
Editions
There are two editions: XenMobile MDM and the Mobile Solutions Bundle. XenMobile MDM primarily focuses on (hardware) device management, more on it’s extensive feature set shortly. Every major platform is supported including: iPhone, iPad, Android, BlackBerry, Symbian and Microsoft Windows 8. It includes the XenMobile Secure Mobile Gateway (SMG) and XenMobile SharePoint Data Leak Prevention (DLP) as well as the XenMobile Mobile Service Provider (ZSM) and the XenMobile Remote Support Application Toolset.
#Citrix Nails Its Enterprise Mobility Strategy – #XenMobile, #BYOD – via @ekhnaser
Read this great article and see if you agree! 😉
Citrix Nails Its Enterprise Mobility Strategy
I have been very pleased with the strategy, execution and the road map that Citrix has developed around Enterprise Mobility. With the announcement of XenMobile MDM and the Mobile Solutions bundle, I can very easily say that the Citrix solution is the most complete and feature-rich offering on the market today.
XenMobile MDM is simply a name change for Zenprise, which Citrix acquired a few months earlier. I expected Citrix to simply change the “Z” to “X” and keep the name, but I guess Citrix marketing did not find that as amusing. That is not the only change that occurred: A new version of “Zenprise” also accompanies this release, and XenMobile MDM now brings it to version 8.0.1.
Many customers and colleagues have asked me why Citrix acquired an MDM provider — what are the value-adds and isn’t the world moving towards MAM anyway? To answer, we have to make a clear distinction between the use cases. I agree and concur that for BYOD initiatives, MAM is a better, cleaner way of doing this things and that MDM is not the ideal solution.
That being said, there are plenty of use cases where MDM is the only solution that makes sense and I will give you real-world examples. Have you heard of the “Belly” card? It is a customer recognition and rewards program from a company HQ’ed in Chicago that offers merchants a locked down iPad for display in their place of business. Customers can come in and scan their mobile phones on the iPad provided and after a certain number of check-ins they are offered a reward for their loyalty. In this case, belly would have very little use for MAM; they need an MDM solution to manage the thousands of iPads they have deployed.
Another example: United Airlines and American Airlines allow customers to use mobile devices in the cabin to purchase goods in-flight. Obviously, the airlines don’t want the flight attendants to use their own device for this, MDM shines again here.
Finally, what about financial institutions that want to continue to issue corporate-managed devices of different flavors? It’d be for security reasons, obviously. In this case, MDM shines.
When I see bloggers and analysts disqualify MDM, they are not thinking beyond BYOD, where the business world could have a use case built around an application they issue on a mobile device.
Did Citrix strike gold with its acquisition of Zenprise? I will say this much: It was one of the best acquisitions the company has ever made. The natural follow-up question is, what about CloudGateway? And my answer is, it is the glue that holds everything together and is the most important product in the Citrix solution today. Everything will go through CloudGateway moving forward and at version 2.5 has the following features:
- Enterprise app store with identity management capabilities for a single sign-on like experience
- Windows Applications and Desktops through XenApp and XenDesktop
- Mobile applications integration, provisioning, etc.
- SaaS applications integration, provisioning, etc
- Integration with Citrix ShareFile for enterprise DropBox functionality
CloudGateway also has a connector for Citrix Podio, and here I’ll be critical of Citrix the same way I’m critical of VMware for not integrating SocialCast. Why Citrix doesn’t make Podio…
Continue reading here!
//Richard








