#XenMobile and the #Citrix Mobile Workspaces Architecture – #BYOD

This is a great blog post by Christopher Campbell and good picture to show the overall capabilities and architecture of the Citrix offering!

You’ve heard us talk about Mobile Workspaces and if you’re a techie you’re probably wondering if Citrix really has the architectural components (a complete, comprehensive and fully integrated architecture) that can deliver any app and data to any user on any device over any network?

Well let’s first identify a few of the market leading technologies that make up the Citrix Mobile Workspaces solution:

  • XenApp mobilizes and secures Windows apps on any device
  • XenDesktop securely delivers virtual Windows desktops and apps on any device
  • XenMobile manages and secures mobile, web and SaaS apps on mobile devices
  • GoToMeeting empowers people to meet and collaborate with anyone, anywhere
  • ShareFile shares and syncs corporate data securely from any location
  • NetScaler optimizes and secures app delivery and on any network
  • CloudPlatform orchestrates and provisions apps, desktops and IT services from any cloud

OK, OK. We know you have the products but do they really integrate?

Yes. Don’t believe me? Well as they say a picture is worth a thousand words. This is what the Mobile Workspace Architecture looks like.

OK. I get it.  You have the architecture but that doesn’t necessarily translate to a seamless user experience.

Still don’t believe huh? Well this is what the user experience looks like.

XenMobile is a key ingredient in delivering a mobile workspace.  Along with XenApp and XenDesktop it allows organizations to deliver on giving users access to any app from any device. In fact, if you’re an existing XenApp or XenDesktop customer, XenMobile seamlessly plugs into your existing architecture.

If you’re a XenDesktop or XenApp customer this is what your environment probably looks like.

Now this is what you need to enable EMM for BYO and COPE (Corporate Owned, Personally Enabled) devices and add that MDM, MAM, Secure Email, Secure Data…

Continue reading here!

//Richard

 

#Citrix #XenApp and #XenDesktop 7.5 is released

Finally it’s released, just go and download and enjoy (hopefully)! ;-)

https://www.citrix.com/downloads/xendesktop/product-software/xendesktop-75-platinum.html

Documentation is available online in Citrix eDocs. Keeping in mind that the online documentation will be periodically updated, you may also download a PDF file with a current snapshot for offline use:

Admin Guide
Upgrade Guide
Install Guide

This single package contains the Core and components needed to deploy the server-side infrastructure supporting Windows 8.1 and Server 2012 R2 and includes Director, Studio, Delivery Controller, Virtual Delivery Agent, Personal vDisk, Universal Print Server, Receiver and StoreFront, Profile Management, HDX, Migration tool, License Server and CloudBridge (Branch Repeater) plug in.

//Richard

Multi-Factor Authentication for Office 365 – #Office365, #IAM

This is cool!

Paul Andrew is a technical product manager on the Office 365 team working on identity.

Today we’re adding Multi-Factor Authentication for Office 365 to Office 365 Midsize Business, Enterprise plans, Academic plans, Nonprofit plans, and standalone Office 365 plans, including Exchange Online and SharePoint Online. This will allow organizations with these subscriptions to enable multi-factor authentication for their Office 365 users without requiring any additional purchase or subscription.

Multi-factor authentication increases the security of user logins for cloud services above and beyond just a password. With Multi-Factor Authentication for Office 365, users are required to acknowledge a phone call, text message, or an app notification on their smartphone after correctly entering their password. Only after this second authentication factor has been satisfied can a user sign in.

Multi-factor authentication has been available for Office 365 administrative roles since June 2013, and today we’re extending this capability to any Office 365 user. We’re also enhancing the capabilities that have been available since June. We’re adding App Passwords for users so they can authenticate from Office desktop applications as these are not yet updated to enable multi-factor authentication. And we’re enabling users who are authenticated from a federated on-premises directory to be enabled for multi-factor authentication.

This addition of multi-factor authentication is part of our ongoing effort to enhance security for Office 365, and we’re already working on Office desktop application improvements to Multi-Factor Authentication for Office 365, which we’ll introduce later in this post. Office 365 offers many robust built-in security features for all customers and also optional controls that enable subscribers to customize their security preferences. More information about security in Office 365 is available inthe Office 365 Trust Center.

Let’s take a look at how Office 365 customers can take advantage of multi-factor authentication and configure it, including using App Passwords for Office desktop applications.

mfa_01

After entering your account password, you see a message like this while your phone is being called for acknowledgement.

Multi-Factor Authentication for Office 365

Office 365 administrators enroll users for multi-factor authentication through the Office 365 admin center.

Read more…

Configuring #XenMobile Device Manager HA Clustering – #MDM, #Citrix

March 7, 2014 1 comment

A couple of nice videos from Albert Alvarez  here about how to cluster XenMobile device manager!

In my previous post we configured clustered Node 1.  In this second Part we will complete the cluster configuration in Node 2  and will validate and test the configuration..

//Richard

Bug in Citrix Receiver 13 for Linux – cannot connect with multiple STAs – @CitrixSupport, @CitrixReceiver, #Citrix

Ok, we’ve had some issues with Citrix Receiver version 13 for Linux.. and it’s not just ONE issue. I found one that I thought I just have to share… so it’s lab Saturday for me at the office in a true geek manner with two XenClients and my favourite MacBook!

Bugg_finding_geek_Saturday

I guess that some of you have tried the Linux Receiver and knows how hard it is to get working, especially on a 64-bit distribution of Linux like Ubuntu 12.04 LTS och 13.10 LTS.

If you follow these instructions you can get it onto the device and then login through a browser (local Receiver UI may still not be full functioning!)..

https://help.ubuntu.com/community/CitrixICAClientHowTo

What I’m about to show you is that it’s not just only getting Receiver on the device and ensuring that the SSL certificates are trusted. You then have to be able to use it as well externally through a NetScaler Gateway (NSG) into StoreFront and your XenApp/XenDesktop VDA’s.

Just assume that you have a production environment that consists of a NetScaler Gateway and a StoreFront server, if you then in StoreFront have configured your NetScaler Gateway correctly and the appropriate STA configuration (with MULTIPLE STA’s) then you will notice that you can’t launch a session.

BTW, the recommendation from Citrix is to use multiple STA’s, right! See this from edocs:

For all deployments, if you are making resources provided by XenDesktop, XenApp, or VDI-in-a-Box available in the store, list on the Secure Ticket Authority (STA) page URLs for servers running the STA. Add URLs for multiple STAs to enable fault tolerance, listing the servers in order of priority to set the failover sequence. If you configured a grid-wide virtual IP address for your VDI-in-a-Box deployment, you need only specify this address to enable fault tolerance.

Important: VDI-in-a-Box STA URLs must be entered in the form https://serveraddress/dt/sta in the Add Secure Ticket Authority URL dialog box, where serveraddress is the FQDN or IP address of the VDI-in-a-Box server, or the grid-wide virtual IP address.

The STA is hosted on XenDesktop, XenApp, and VDI-in-a-Box servers and issues session tickets in response to connection requests. These session tickets form the basis of authentication and authorization for access to XenDesktop, XenApp, and VDI-in-a-Box resources.

If you want XenDesktop, XenApp, and VDI-in-a-Box to keep disconnected sessions open while Citrix Receiver attempts to reconnect automatically, select theEnable session reliability check box. If you configured multiple STAs and want to ensure that session reliability is always available, select the Request tickets from two STAs, where available check box. Read more…

#XenMobile on Android and MicroVPN issue unless you really synch Worx releases…

February 26, 2014 Leave a comment

Hi,

If you’ve worked with XenMobile and especially the AppController to deploy WorxMail and WorxWeb you know that these establish  a MicroVPN tunnel to reach internal resources when needed.

One thing that I noted today was that when you upgrade your AppController and NetScalers and people also upgrade their Worx Home app on Android you can run into an issue unless you upgrade and align your Worx Home and WorxWeb apps.

The new Worx Home 8.6.1 on Android requires that you run WorxWeb 1.3.3 from Citrix, otherwise the MicroVPN tunnel won’t be established and you won’t reach your internal resources through it.

So it’s more important than ever to ensure that you try your NetScaler, AppController and Worx apps and align their releases.. once they work then you see this great progress and tunnel being established.

Android_MicroVPN_tunnel_established

It would be nice to get a good table of which versions of each product/component that you should run and which ones that can support all use cases like; XenMobile , ShareFile on prem, ICA/HDX proxy, SSL VPN and SmartAccess for RfW and proxy! I’ve not yet found one combination that delivers everything. ;-)

Happy XenMobile’ing!

//Richard

#App-V 5.0 Capacity Planning – #Microsoft via @micheroth and @vkleinerde

February 21, 2014 Leave a comment

This is a good article, have a look at this if you’re planning some App-V 5.0 capabilities!

The following recommendations can be used as a baseline to help determine capacity planning information that is appropriate to your organization’s App-V 5.0 infrastructure.

ImportantImportant
Use the information in this section only as a general guide for planning your App-V 5.0 deployment. Your system capacity requirements will depend on the specific details of your hardware and application environment. Additionally, the performance numbers displayed in this document are examples and your results may vary. 

Determine the Project Scope

Before you design the App-V 5.0 infrastructure, you must determine the project’s scope. The scope consists of determining which applications will be available virtually and to also identify the target users, and their locations. This information will help determine what type of App-V 5.0 infrastructure should be implemented. Decisions about the scope of the project must be based on the specific needs of your organization. 

Task More Information
Determine Application Scope Depending on the applications to be virtualized, the App-V 5.0 infrastructure can be set up in different ways. The first task is to define what applications you want to virtualize.
Determine Location Scope Location scope refers to the physical locations (for example, enterprise-wide or a specific geographic location) where you plan to run the virtualized applications. It can also refer to the user population (for example, a single department) who will run the virtual applications. You should obtain a network map that includes the connection paths as well as available bandwidth to each location and the number of users using virtualized applications and the WAN link speed.

Determine Which App-V 5.0 Infrastructure is Required

ImportantImportant
Both of the following models require the App-V 5.0 client to be installed on the computer where you plan to run virtual applications. You can also manage your App-V 5.0 environment using an Electronic Software Distribution (ESD) solution such as Microsoft Systems Center Configuration Manager. For more information see Deploying App-V 5.0 Packages by Using Electronic Software Distribution (ESD). 
  • Standalone Model - The standalone model allows virtual applications to be Windows Installer-enabled for distribution without streaming. App-V 5.0 in Standalone Mode consists of the sequencer and the client; no additional components are required. Applications are prepared for virtualization using a process called sequencing. For more information see, Planning for the App-V 5.0 Sequencer and Client Deployment. The stand-alone model is recommended for the following scenarios:Full Infrastructure Model - The full infrastructure model provides for software distribution, management, and reporting capabilities; it also includes the streaming of applications across the network. The App-V 5.0..
    • With disconnected remote users who cannot connect to the App-V 5.0 infrastructure.
    • When you are running a software management system, such as Configuration Manager 2012.
    • When network bandwidth limitations inhibit electronic software distribution.

Continue reading here!

//Richard

Follow

Get every new post delivered to your Inbox.

Join 239 other followers

%d bloggers like this: