Japan East (Tokyo, Saitama) now GA with Azure NV-series

Written by Thomas Poppelgaard. Posted in Autodesk, Azure, Citrix, Cloud, Datacenter and Cloud, End User Computing, GRID, Hyper-V, Microsoft, MVP, NVIDIA, RDS, Tesla, Windows Server 2012R2, Windows Server 2016

Microsoft Azure is moving really fast and 29 datacenters around the world is now online. I was in Japan some weeks ago (week 14) and did a presentation at E2EVC on NV series and how easy it is to build Virtual machines with NV-series. At that time I demonstrated live heavy graphics application such as Autodesk Revit, Navisworks running from Azure SE Asia (Singapore) with RDP10 to my Microsoft Surfacebook in Japan on hotel wifi and it worked actually really good. Some weeks later I was home in Denmark, I was preparing my speech for Azure Bootcamp in Aarhus, Denmark. I noticed that a new datacenter in Japan West (Osaka) and Japan East (Tokyo, Saitama) have gone “Operational” and more specific Japan East (Tokyo, Saitama) now was live with Azure NV6, NV12, NV24. This is really awesome and I had to try it out.

To summary up, Microsoft have made their datacenter in Japan East (Tokyo, Saitama) online some weeks ago offering NV-series (NV6,NV12,NV24) this is great for customers in Japan getting low latency from their cities to Azure GPU enabled visualization instances. 

What is Microsoft NV-series

The NV instance are optimized and designed for remote visualization, streaming, gaming, encoding and VDI scenarios utilizing frameworks such as OpenGL and DirectX, customers can use Windows Server 2016 or Windows Server 2012 and further virtualize with session sharing technologies such as Microsoft RDS / Citrix XenApp and do GPU sharing from Azure NV instances. 

The NV instances are powered by NVIDIA’s Tesla M60 GPU card and NVIDIA GRID for desktop accelerated applications and virtual desktops where customers will be able to visualize their data or simulations. Users will be able to visualize their graphics intensive workflows on the NV instances to get superior graphics capability and additionally run single precision workloads such as encoding and rendering.

NV6 instance is one half physically GPU NVIDIA Tesla M60 (GRID)
NV12 instance is 1 physically GPU NVIDIA Tesla M60 (GRID)
NV24 instance is 2 physically GPU NVIDIA Tesla M60 (GRID)

Below visual diagram highlights what technical ressources you get of each instance.

Limitations of NV-series:

Please notice that the NV-series SSD disk are available on temp disk (d: drive)  and NV-series VMs do not support VM disks that are backed by Azure premium storage. The primary disk (c: drive) is HDD data disk which is limited of 500 IOPS.

NVIDIA GRID vGPU is not supported with NV-series.

How to create a Microsoft NV-instance

When creating an NV-series VM using the Azure portal, on the Basics blade, select a VM disk type of HDD. To choose an available N-series size, on the Size blade, click View all.

When instance is started up you have to install the NVIDIA drivers for Windows Server 2016 or Windows Server 2012r2 here 

Where is Microsoft NV-series available

Microsoft NV6, NV12, NV24 is now available in following datacenters

  • East US(Virginia)
  • North Central US(Illinois)
  • South Central US(Texas)
  • West Europe (Amsterdam)
  • South East (Singapore)
  • NEW Japan East (Tokyo, Saitama)

Below is a visual diagram I have made of the NV series availability in the 6 new datacenters around the world.

Price pr hour example of Microsoft NV6

Below is a price example I have done with NV6 in all 6 datacenters with a hourly usage or with 1 month usage.

The price difference is not big but its important to understand if you design NV series in multiple datacenters. The cost is different.

Want help with NV-series

If you are interested in trying out Azure NV-series I highly recommend you try it out, if you are interested in getting help you are always welcome to reach out to me for my professional services. 

Source

https://azure.microsoft.com/en-us/overview/datacenters/how-to-choose/

https://azure.microsoft.com/en-us/regions/services/

https://azure.microsoft.com/en-us/pricing/calculator/

https://azure.microsoft.com/en-us/blog/azure-n-series-general-availability-on-december-1/

https://docs.microsoft.com/en-us/azure/virtual-machines/windows/n-series-driver-setup

 

Citrix XenApp Essentials – Microsoft Azure

Written by Thomas Poppelgaard. Posted in Azure, Citrix, Cloud, End User Computing, Essentials, HTML5, Microsoft, Netscaler, NetScaler Gateway, Receiver, Windows Server 2012R2, Windows Server 2016, XenApp

Citrix XenApp Essentials is now available on Microsoft Azure.

Citrix XenApp Essentials is replacing Microsoft Azure RemoteApp and customers can now benefit the technology from Citrix in a simplified portal on Azure to deliver published apps to any device from any Azure datacenter.

New offerings with XenApp (On-Premises, Cloud and Azure ONLY)

Below gives you an overview on how you can deploy Citrix XenApp Essentials On-Premises, in any Cloud and the new Microsoft/Citrix offering XenApp essentials in Azure ONLY.

Below gives you a visual understanding on the new offerings from Microsoft and Citrix with their new cloud offerings XenApp Essentials in Azure.

Prices for XenApp Essentials in Azure

Microsoft Azure

Citrix XenApp Essentials is today now available in all Azure datacenters around the world, this is amazing, and you can now build fast a solution, there is no wait time to buy servers, on Azure its ready to be used, you just need a creditcard 🙂

How do I find Citrix XenApp Essentials on Azure

Goto https://portal.azure.com and login with your Azure ID/pwd, under ressources click add and search for Citrix, then you will see the XenApp essentials service offering.

How do I deploy XenApp Essentials

The following graphic shows the flow of deploying XenApp Essentials.

XenApp Essentials – System Requirements

The following are the requirements to install and configure XenApp Essentials Service after you purchase the service from the Azure Marketplace.

Microsoft Azure

To provision and deploy resources in Microsoft Azure correctly, you need the following:

  • An Azure account.
  • An Azure subscription.
  • An Azure Active Directory global administrator account in the directory associated with your subscription. The user account must have Owner permission for the Azure subscription to use for provisioning resources.

For more information about how to set up an Azure Active Directory tenant, see How to get an Azure Active Directory tenant on the Microsoft website.

  • Use the Azure Resource Manager to:
    • Deploy resources such as virtual machines, storage accounts, database, and virtual network.
    • Create and manage the resource group that is a container for resources you want to manage as a group.

Note

XenApp Essentials Service supports configuring machines by using Azure Resource Manager only.

Citrix Cloud

You must have a Citrix Cloud account to configure XenApp Essentials Service.

Important

XenApp Essentials Service creates Cloud Connector virtual machines automatically.

Compatibility

XenApp Essentials supports the following web browsers:

  • Google Chrome
  • Internet Explorer

Users connect to their apps by logging on with Citrix Receiver. XenApp Essentials Service supports the current version of Citrix Receiver for each user device operating system.

You can download the latest version of Citrix Receiver from the Citrix website.

Deploying XenApp Essentials Service

Citrix Cloud hosts the XenApp Essentials Service. The XenApp Essentials offers secure access to virtual Windows apps. This service is based on XenApp and XenDesktop technology. The service includes StoreFront and the NetScaler Gateway Service along with core management services.

Your app workloads run in your Azure subscription.

The following diagram shows an architectural overview of a basic XenApp Essentials Service cloud deployment:

You can also allow users to connect to your on-premises data center. Connections between the Azure cloud and your on-premise data center occur through a VPN connection. Users connect through XenApp Essentials to your license server, file servers, or Active Directory over the VPN connection.

Known Issues

The XenApp Essentials Service has the following known issues:

  • Creating the machine catalog fails if the virtual machine size is not available for the selected region. To check the virtual machines that are available in your area, see the chart at Products available by region on the Microsoft website.
  • You cannot create and publish multiple instances of the same app from the Start menu at the same time.
    For example, from the Start menu you publish Internet Explorer. Then, you want to publish a second instance of Internet Explorer that opens a specific website on startup. To do so, publish the second app by using the path for the app instead of the Start menu.
  • XenApp Essentials Service supports linking a subscription by using an Azure Active Directory user account. XenApp Essentials does not support Live.com authenticated accounts.
  • Users cannot start an application if there is an existing Remote Desktop Protocol (RDP) session on the VDA. This behavior only happens if the RDP session starts when no other users are logged on to the VDA.
  • You cannot enter a license server address longer than server.domain.subdomain.
  • If you perform multiple sequential updates to capacity management, there is a possibility that the updated settings will not properly propagate to the VDAs.

Set up a Microsoft Azure Account

Perform the following tasks in Microsoft Azure before setting up the connection in Citrix Cloud:

  1. Create an Azure subscription.
  2. Create a user in Azure Active Directory who is a global administrator for the subscription.

NoteYou must create the global administrator account in Azure Active Directory.

After you create your Azure account, you can prepare your Azure subscription.

Prepare Your Azure Subscription

When you prepare your Azure subscription, you configure the following:

  • Create a resource group and provide the following details:
    • Resource Group name
    • Subscription name
    • Location
  • Create a virtual network in the resource group and provide a name for the network. You can leave all other default settings.
  • Create a when you create the master image.
    Note: A premium storage account is not supported.
  • Use an existing or create a domain controller. If you create a domain controller, do the following:
    • Use the A3 Standard or any other size Windows Server 2012 R2 virtual in the Resource Group and virtual network. This virtual machine becomes the domain controller. If you plan to create multiple domain controllers, create an availability set and put all the domain controllers in this set.
    • Assign a private static IP address to the network adapter of the virtual machine. You can assign the address in the Azure portal. For more information, see Configure private IP addresses for a virtual machine using the Azure portal on the Microsoft documentation website.
    • [Optional] Attach a new data disk to the virtual machine to store the Active Directory users and Groups and any Active Directory logs. For more information, see How to attach a data disk to a Windows virtual machine in the Azure portal. When you attach the disk, select all the default options to complete the wizard.
    • Add the domain controller virtual machines private IP address to the virtual network DNS server. For more information, see Manage DNS servers used by a virtual network (Classic) using the Azure portal (Classic).
    • Add a public DNS server in addition to the Microsoft DNS server. Use the IP address 168.63.129.16 for the second DNS server.
    • Add the Active Directory Domain Services role to the domain controller virtual machine. When this step is complete, promote the domain controller virtual machine to a domain controller and DNS.
    • Create a forest and add some Active Directory users. For more information, see Install a new Active Directory forest on an Azure virtual network.

If you prefer to use Azure Active Directory Domain Services instead of a domain controller, use the following guidelines. Citrix recommends reviewing the Active Directory Domain Services Documentation on the Microsoft website.

  • Create an Azure Active Directory and give it a unique name.
  • Create a classic virtual network to enable Domain Services.
    When you create the classic virtual network, choose an IP address range that is different from the one you use with the XenApp and XenDesktop Service. You need two IP addresses and can use the /24 range.
  • Enable the Azure Active Directory Domain Services by switching to the classic portal. Navigate to the Active Directory node and open the new Azure Active Directory domain.
  • Enable the domain services for the directory.
    When you complete this step, the DNS name and virtual network appear automatically. Ensure that the values are correct.
    When you save the settings, it can take 30 minutes to an hour to set up Domain Services.
  • When provisioning Domain Services is complete, a new section titled IP ADDRESS appears. Refresh the page until you see two IP addresses.
  • Add a subnet IP address for the Azure virtual network.
  • Update the DNS settings for the Azure virtual network.
    Edit the properties on the virtual network. Ensure that you enter both IP addresses created in a previous step.
  • Create an administrative group in the new Azure Active Directory domain. Use the following guidelines:
    • Create the group with the name AAD DC Administrators. The group must have this name.
    • Configure the DNS settings before adding users and groups.
    • Add members after creating the group.
  • Create a Resource Manager virtual network. Ensure that the deployment model you use is set to Resource Manager. Locate the Resource Manager virtual network in the same region as the classic virtual network.
  • Peer the Resource Manager virtual network to the classic virtual network. Peering connects the two virtual networks to the same region in Azure. After peering the networks, the two networks appear as a single virtual network. When you peer the two networks, ensure that you select the classic virtual network.
  • Add DNS servers to the Resource Manager virtual network. When you configure the DNS servers, type the IP address of the Azure Active Directory Services. Ensure that you type both IP addresses that appear in the Domain Services section on the Configure tab of your directory.

Prepare Your Master Image

You can use one of the following two images in your deployment:

  • Your own master image with your applications installed.
  • A Citrix-prepared image.

Important

Citrix does not recommend using a Citrix-prepared image for production deployments.

When you prepare the master image, the Virtual Delivery Agent (VDA) installs on the image automatically. The VDA software enables the following:

  • Registers the machine with the XenApp Essentials Service.
  • Establishes and manages the connection between the machine and the user device.
  • Verifies that a Citrix license is available for the user or session.
  • Applies any configured policies for the session.
  • Communicates session information to the XenApp and XenDesktop Service through the broker agent included in the VDA.

VDAs are available for Windows server and desktop operating systems. VDAs for Windows Server operating systems allow multiple users to connect to the server at one time.

For more information, see Configure VDAs.

Note

The VDA for Windows desktop operating systems is not supported in XenApp Essentials Service.

Prepare a Master Image

You create the master image by using the Azure Resource Manager. When you prepare your master image, the steps you must take in the Azure portal are:

  1. Log on to the Azure portal.
  2. Create a Windows Server 2012 R2 or Windows 2016 server virtual machine.
    You can also use existing server virtual machines. When you use existing machines, you can use the resource group, virtual network, and storage account associated with the machine. The storage account is where you create the virtual hard disk (VHD).
    Note: Create the VDA template with standard (non SSD) storage. Also, do not join the VDA to a domain.
  3. Connect to the virtual machine after you create it and when it is running.
    Important: Do not run Sysprep on the image.
  4. Install the applications on the virtual machine. The apps are available to your users when they log on with Citrix Receiver.
  5. Download the server OS VDA on the virtual machine from the XenApp and XenDesktop Service download page.
  6. Install the VDA on the virtual machine. When prompted for the Delivery Controller address, select Let MCS configure.
  7. Skip the installation of Citrix Receiver and App-V. Use the default settings for the remainder of the configuration steps.
  8. Restart the VDA and complete the VDA installation steps by following the instructions on the page.
  9. Test starting the applications to ensure that the configuration is correct.
  10. Shut down the virtual machine.

When you create the virtual machine, the VHD is created in the storage account you specified. When you upload the master image, you must specify the storage account location in the XenApp Essentials console.

Link Your Azure Subscription

In the Citrix Cloud, you link your XenApp Essentials Service to your Azure subscription.

To link your Azure subscription

  1. Log on to the Citrix Cloud for XenApp Essentials Service.
  2. On the Manage tab, click Subscriptions.
  3. Click +Add Subscription.
    The Azure portal opens.
  4. Log on to your Azure subscription by using your global administrator Azure credentials.
  5. Click Accept to allow XenApp Essentials Service to access your Azure account.
    XenApp Essentials service enumerates the subscriptions available in your account.
  6. Select the subscription you want to use and then click Link.
    Return to the XenApp Essentials Console to see the subscription in a linked state.

After you link your Azure subscription to XenApp Essentials, upload your master image.

To upload the master image

  1. Log on to the Citrix Cloud for the XenApp Essentials Service.
  2. On the Manage tab, click Master Images.
  3. Click Add Image.
    The Add an image page opens.
  4. Specify the location of the VHD by selecting the following:
    1. Subscription
    2. Resource group
    3. Storage account
    4. VHD location
    5. Region
    6. Name for the master image.
  5. Click Save.
    When you save the image, XenApp Essentials Service verifies the master image.
    After verification, the image appears on the Master Images > My Images page.

Create Catalogs

A catalog is similar to collections in Azure Remote App. A Citrix XenApp Essentials Service catalog lists apps and resources that you can share with users on any device.

XenApp Essentials Service catalog uses a simpler approach to the combination of a machine catalog and a Delivery Group.

Note

XenApp machine catalog and Delivery Group creation workflows are not available in XenApp Essentials Service.

When you add a catalog, you configure the following:

  • Create a name for the catalog.
  • Link your Azure subscription to the catalog.
  • Join the catalog to the domain.
  • Choose a master image.
  • Select the capacity and manage the cost of the apps.

Before you start creating your catalog, ensure that you have your Azure Active Directory credentials and your subscription ID available.

To create a catalog

  1. Log on to citrix.cloud.com.
  2. Select the XenApp and XenDesktop Service.
  3. On the Manage tab, click Catalogs, and then click +Catalog.
  4. On the Add a Catalog page, in Pick a Name, type the name of the catalog, select Domain Joined, and then click Save.
  5. In Link your Azure subscription, provide your Azure subscription details. You can use a subscription you created previously or link a new Azure subscription. To use an existing subscription, do the following:
    1. In Subscription Name, select the subscription from the list.
    2. In Resource Group (Region), select the resource group to which the Azure subscription belongs. Use the resource group you created when you prepared your Azure subscription. XenApp Essentials Service creates Cloud Connectors in the resource group.
    3. In Virtual Network, select the virtual network to which the Azure subscription belongs.
      The virtual network is the same one you configured when you prepared your Azure subscription. Ensure that the virtual network can reach your domain controller by using the DNS entries
    4. In Subnet, select the subnet to which the Azure subscription belongs and then click Save.
  6. Under Join local domain, enter the following:
    1. In Fully Qualified Domain Name, type your organizations domain name.
    2. In Organizational Unit, type the OU to which users belong.
      For example, OU=Essentials,DC=citrix,DC=com.
      Note: Adding the OU is an optional step.
    3. In Service Account Name, type the account that by using permissions to join a machine to a domain and create machine accounts.
    4. In Password and Confirm Password, type the password and then click Save.
  7. In Choose master image, do one of the following:
    1. Select Link an existing image and then do the following:
      1. In Image Name, select the image.
      2. Click Save.
    2. Select Import a new image and then do the following:
      1. In Subscription, choose the subscription.
      2. In Resource Group, choose the group.
      3. In Storage Account, choose the account
      4. In VHD, choose the location of the virtual hard disk.
      5. In Image Name, provide a name for the master image and then click Save.
  8. In Select Capacity and Manage Cost, do the following:
    1. In Pick compute, select a worker role.
      The worker role defines the resources used. When you specify a worker role, XenApp Essentials Service determines the correct load per instance for you. You can use one of the options in the list or create your own custom option. The session count is used as a scale metric.
    2. In Select scale settings, do the following:
      1. Set the minimum number of running instances. XenApp Essentials Service ensures that the minimum of virtual machines are powered on all the time.
      2. Set the maximum number of running instances. XenApp Essentials Service does not go beyond this number of virtual machines.
      3. [Optional] If you want a different number of virtual machines running during peak times, select I want to set a schedule for peak time. Then, specify the following:
      • Days of the week for the peak time
      • Start and end times for each day
      • Time zone
      • Minimum number of running instances
  9. In Set idle or disconnected session time-out, set the time for when the session ends.
    User sessions end automatically if the session remains idle or is disconnected for the specified time period. Shorter time-out values allow unused VDAs to power off and save costs.
  10. Click Save.

After you configure your catalog, click Start Deployment to start catalog creation. This step can take 1-2 hours. If you specified many virtual machines, creating the catalog can take a longer time.

When the previous step is complete, you can publish apps and assign users and user groups. You need at least one published application and one user assigned to complete creating the catalog.

To update or add applications, update the virtual machine that you used to create the catalogs master image.

To update the master image

  1. Power on the master image virtual machine.
    Powering on the virtual machine does not affect the master image installed in Microsoft Azure.
  2. Install any updates or applications to the virtual machine.
  3. After installation, shut down the virtual machine.
  4. In the XenApp Essentials Service console, add the new image that includes the path to the virtual machines VHD image.

To update a catalog

  1. On the Manage tab, click Catalogs.
  2. Click the ellipsis in the catalog that you want to update, and then click Update Catalog Image.
  3. Select either Link an existing image or Import a new image. Enter the information that is appropriate for your choice.
  4. In Time until automatic log-off, choose the amount of time before the session ends.
    When you start the update of the master image, users can continue to work in XenApp Essentials until the processing is complete. Then, users receive a warning message to save their work and close applications. After closing all active sessions on the VDA, the update finishes on that VDA. Then, if users do not log off in the amount of time given, the session closes automatically.
  5. Click Update to start updating the master image.

Publish Apps

After configuring your catalog, you can publish apps for your users. The image you installed includes apps that you can publish.

To publish apps

  1. Log on to the Citrix Cloud for the XenApp Essentials Service.
  2. On the Manage tab, click Catalogs.
  3. Click the ellipsis in the catalog for which you want to publish apps.
  4. Click Manage Publishing.
  5. On the Apps tab, click Publish Apps.
  6. In the Publish Apps for <catalog name> page, select the apps for publishing.
  7. When done, click Publish.
    The Apps tab appears by using the list of published apps.

After you publish apps, you can add users and groups.

Add Users and User Groups

  1. Log on to the Citrix Cloud for XenApp Essentials Service.
  2. On the Manage tab, click Catalogs.
  3. Click the ellipsis in the catalog for which you want to add users.
  4. Click Manage Users.
  5. On the Users tab, click +Add Users.
  6. In the Assign Users for <catalog name> page, in Domain, choose the domain.
  7. In the search box, type the name of the user or user group.
  8. Repeat step 7 until you’ve added all users and groups.
  9. Click Assign Users.
    The Users tab appears by using the list of published apps.

StoreFront and NetScaler Gateway in XenApp Essentials Service

The XenApp Essentials Service in Citrix Cloud hosts a StoreFront site for each customer. After you create the catalog, the StoreFront site is created automatically. The StoreFront URL appears under the catalog details. Hosting StoreFront in the cloud means that you do not have to deploy or maintain StoreFront. Citrix keeps StoreFront current in the cloud.

To allow users secure access to their published apps, XenApp Essentials Service uses NetScaler Gateway Service. This service does not need any configuration by you. Each user is limited to 1-GB outbound data transfer per month. You can purchase a 25 GB add-on from the Azure Marketplace. The charge for the add-on is on a monthly basis.

Monitoring the XenApp Essentials Service

To monitor the overall performance of the Citrix XenApp Essentials Service for Azure, do the following:

  1. Navigate to the XenApp and XenDesktop Service.
  2. Click the Monitor tab.
  3. Click the Catalog that you want to monitor.
    You can view information on sessions, logon duration, in addition to other information.
  4. You can choose a session and do the following tasks:
    1. Disconnect the session.
    2. Log off from the session.
    3. Send a message

You can click each session to view extra details about the session such as processes, applications running, and more.

Getting Help

If you have problems with XenApp Essentials Service, open a ticket by following instructions in How to Get Help and Support.

XenApp feature comparison



 

Source

HPE Proliant server cartridge m510 and m710x building blocks for Citrix

Written by Thomas Poppelgaard. Posted in Autodesk, Citrix, Cloud, Desktop Virtualization, Edgeline, End User Computing, HDX 3D Pro, HPE, Intel, M510, M710X, Microsoft, Moonshot, Provisioning, SCCM, VMware, vSphere, Windows 10, Windows 7, Windows 8.1, Windows Server 2008R2, Windows Server 2012R2, Windows Server 2016, XenApp, XenDesktop, XenServer

HPE have released new server cartridges m510 and m710x for HPE Moonshot and Edgeline. These new server cartridges are the first units that have built-in HPE iLO, so customers can easy manage each server cartridge.

Moonshot cartridge building blocks for Citrix workloads

Below chart describes what HPE Moonshot/Edgeline current strategy is for GPU enabled apps and desktops with Citrix XenDesktop and XenApp.

hpe_moonshot_edgeline2

Below chart describes which GPU enabled HPE Proliant server cartridges that can be used.

Interesting results is that density increases dramatically from m710p to m710x.

If companies requires non GPU enabled compute the m510-16 is a interesting server cartridge for Citrix XenApp

m710x_m510

 

Let’s look at the details of the two new server catridges.

m510 cartridge – hardware specifications

hpe_m510_specs

This server catridge is a beast, it have up to 16 core and 128GB memory and is also Windows Server 2016 ready 🙂

 M510 Citrix XenApp Office Worker with LoginVSI

Below shows some benchmark Citrix have accomplished with LoginVSI, interesting is that they get:

168 XenApp sessions per m510. <1/2 watt per session! 

m510-loginvsi

above chart is made by Tony Sanchez from Citrix

The average amount of users for Knowledge worker workloads Login VSI max was around 138 with 145 users being active at the time of the test. The baseline of 780 was consistent with  additional tests that were repeated. The High Scalability policy template was applied to the desktop group for all Login VSI users.

These test was made by Citrix internally, please read the blog here.

CPU performance of the m510 during the 145 user test. The max CPU utilization was around 93%

during the peak of the test without fully saturating the processor.

m710x catridge – hardware specifications

hpe_m710x_specs

m710x-storageoption1m710x-storageoption2

This server catridge is a beast, it have latest skylake core and 64GB memory and is also Windows 10, Windows Server 2016 and even RHEL, Ubunto ready 🙂

Then its also ready to be virtualized with Citrix XenServer and VMware vSphere and KVM, I will later blog how its working with these hypervisors.

M710x Citrix XenApp Knowledge Worker with LoginVSI

Below shows some benchmark Citrix have accomplished with LoginVSI, interesting is that they get:

67 XenApp Knowledge sessions per m710x

m510-loginvsi

These test was made by Citrix internally, please read the blog here.

 

Hardware Summary of HPE ProLiant m510 and m710x

summary_m510-m710x

I hope the above gives you a pretty good idea on where Moonshot & Edgeline is going – and this is just for Citrix XenDesktop and XenApp. I will cover how its used with Octoblu another time.

How to get Involved – HPE Global Innovation Labs

hpelabs

Partner and customer engagement, interaction, assessment and colloboration on solution development and applications.

HPE can help with

  • Build, testing and pre-validation of Edgeline systems and end-to-end solutions
  • Integrated real-life “Edge Experience Zones“ to interact with and highlight industry applications
  • On-site access or secure remote access
  • Datacenter connectivity and testing

Try here https://www.hpe.com/us/en/servers/global-innovation-lab.html

Poppelgaard.com – Professional Services

if you are interested in testing your applications on the ProLiant Server Catridges – please dont hesitate to contact me a thomas@poppelgaard.com
I can also help with above value added tasks plus much more 🙂

 

Source

Citrix Blogs – X Marks the Spot: XenApp, XenDesktop & XenServer with Intel Xeon & HPE Moonshot!

Citrix Blogs – We Choose to Go to the Moon!

 

HPE Moonshot Reinvented

Written by Thomas Poppelgaard. Posted in Autodesk, Citrix, Cloud, Collaboration and Support, Datacenter and Cloud, End User Computing, GVT-d, HDX 3D Pro, HPE, HPE Discover, Intel, Linux Virtual Desktop, LoginVSI, M510, M710X, Microsoft, Moonshot, OpenGL, RemoteFX, Windows 10, Windows 7, Windows 8.1, Windows Server 2008R2, Windows Server 2012R2, Windows Server 2016, XenDesktop, XenServer

reinvented

HPE Moonshot have been around for some time now, and I have been very lucky working together with HPE and testing their server cartridges that are compatible with Citrix solutions. Last year, at HPE Discover in London, I wrote an article about how Citrix internally are using HPE moonshot and which server cartridges were available at that time and how financial customers are benefiting from these solutions.

Now HPE has a new server catridges available and a new appliance that targets a new business opportunity for SMB/medium customers. Previously you needed to buy a Moonshot 1500 solution that was a 4.3 U chassis, where you could add up to 45 server cartridges. This have changed and new offerings are now available from HPE. These include Edgeline. HPE Edgeline EL1000 Converged IoT System support one HPE Proliant server cartridge and HPE Edgeline EL4000 Converged IoT System, which support up to four HPE Proliant server cartridges. This is great for business that would like CPU/GPU/Fast storage and IO in small capacity but require fast performance. These appliances are also built for IoT systems. This means that HPE Edgeline is a more accessible solution for companies no matter their size or demand.

How HPE is Reinventing Moonshot

Talking to Olivier Frank, Senior Director from HPE WW Business development & alliances, Moonshot & IOT system, he gave me his view on their strategy, and future plans.

The history of HPE Moonshot

Before we look at what HPE offers now, I thought it would be a great overview to hear about the story of HPE Moonshot. Olivier shares with me, HPE Moonshot is 3 years old and started as a concept to reduce energy footprint, a micro server dedicated to a single server and that would use the lowest energy and have the highest density. The first cartridge started with Intel Atom, which was very low power and competed with a “Facebook” open compute platform. That offering didn’t work out and the HPE moonshot evolved quickly toward GPU for the masses.

HPE started first with AMD to build a server cartridge that could have 4 physically servers with CPU/GPU on 1 cartridge, this was the M700. The goal was hosted desktop, targeting those customers that had not deployed VDI before and you could get a low cost notebook with physically GPU/CPU, fast flash storage, memory and 1Gbit network. VDI customers who had failed at other solutions could also adopt M700.

HPE started getting some traction, the issue was high price per user. HPE and Intel build the M710 server cartridge with Citrix XenApp certified. This was introduced 2 years ago, E3 CPU with Iris Pro Graphics 5200, 32GB memory, M.2 flash storage (september 2014). VDI on the M710 wasn’t something HPE investigated. m710p was the next generation cartridge, which brought more power and higher clock frequency CPU and GPU. HPE started to investigate trader workstation, which requested this thpe of hardware performance and the m710p was perfect for VDI (Banking and Investment). Banks could now replace physically machines to m710p cartridges because of low latency user experience, which was developed closely together with HPE, Intel and Citrix. HP also launched the T730 thin client that could take up to 6 monitors (4 on the box, and add a PCI card to take additional 2 monitors) which is a minimum requirement for traders. This solution was a huge success and some of the largest financial customers are now running on this solution.

HPE Moonshot – Seeing Great Momentum for End User Workspace

Olivier Frank shared some of the success stories with me.

Global FSI customer 1 – Up to 150K Users over 2 years

  • Currently 90 Chassis, 70 chassis published desktop/app, 20 chassis HDI XenDesktop for developers.
    Thousands of users deployed in 3 Weeks. Significant upcoming investment to grow XenApp estate to support 150k users by end of 2017.
  • Cut the cost/watt/per user in half 3W to 1.5W
  • Will save the Bank up-to $13m on their end user spend

Global FSI customer 2 – Traders to go live in FY16 Q3

  • Potential growth of up-to 15000 traders
  • 75K users need to move to VDI (non moonshot) – HPE Moonshot will cover 20% of those high end users that current VDI technology doesn’t cater for.

Global FSI customer 3- 600 Traders live

  • 600 Commodities traders, In 3 Regions – Q4 FY15
  • 600 more VDI user converting to Moonshot in FY16 Q2
  • Looking to make Moonshot there global VDI standard

Customer Video Testimonial Videos

 

HPE Edgeline

Olivier Frank, shared the general target for HPE Edgeline and what are IT Edge like mobile workplace and IoT Edge, Compute for Internet for things and gateways.

The HPE Edgeline Portfolio contains of EL1000, EL4000, EL10 and EL20.

HPE Edgeline EL1000 and El4000

The HPE Edgeline EL1000 and EL4000 Converged IoT System is the first entrant into the industry’s new product category, “Converged (Internet of Things) IoT Systems”. This system integrates unprecedented edge compute, data capture and control, datacenter-class security, device and systems management, as well as large storage capacity to provide heavy-duty analytics and insights to the edge. This enables businesses to make real-time decisions and add value to their operational processes to result in better business outcomes. The Edgeline EL1000 and EL4000 also prevents cloud lock-in by not having to send data back to the cloud or data center. It addresses latency, bandwidth, cost, security, duplication, corruption, and compliance issues, enabling three critical components of savings and success—time, money, and time to action.

edgeline_el10

The HPE Edgeline EL1000 Converged IoT System delivers a high performance and reliable solution that comes optimally configured with one Intel-based HPE ProLiant m510 (8 or 16 core) or HPE ProLiant m710x (4 core + GPU) high density server.

edgeline_el20

The HPE Edgeline EL4000 Converged IoT System delivers a high performance and reliable solution, The EL4000 comes that comes optimally configured with four Intel-based HPE ProLiant m510 (8 or 16 core) or HPE ProLiant m710x (4 core plus GPU) high density servers. The EL1000 / EL4000 have HPE iLO (Integrated Lights-Out), the same tool used to manage traditional datacenter servers.

You can up to 16 Xeon cores with EL1000 and up to 64 Xeon cores with EL4000. The El4000 is a standard 1 U rack-mounted form factor, 4 standard PCIe slots, both appliances comes optional with shock, vibration, temperature rugged.

Use cases are:

  • VDI (1-1) – Citrix XenDesktop
  • SBC (1-many) – Citrix XenApp
  • Trader workstation
  • Enginering workstation
  • Ip-TV
  • Video caching
  • Nebs Compliant (Level 3 certified)

Summary for EL4000 and the EL1000

hpe-el4000-el1000

HPE Edgeline El10, EL 20

hpe_el10hpe_el20

These devices are used to connect to sense an IT infrastructure.

The EL10 Intelligent Gateway is a value solution that comes optimally configured with an lntel® Atom® CPU, 4 GB RAM, 32 GB SDD Storage, Wi-Fi connectivity (standard on Wind River model) and an expansive I/O selection.

The HPE Edgeline EL20 Intelligent Gateway is a mid-level level ruggedized compute solution designed for light data aggregation and acquisition.

EL20 Delivers a performance solution that comes optimally configured with an lntel® i5 CPU, 8 GB RAM, 64 GB SDD Storage, Wi-Fi connectivity (standard on Wind River SKU) and an expansive I/O selection including four-port Power over Ethernet (PoE) plus 1 x 8 bit digital input/output (DIO).

 

Hardware Summary of HPE ProLiant m510 and m710x

summary_m510-m710x

I hope the above gives you a pretty good idea on where Moonshot & Edgeline is going – and this is just for Citrix XenDesktop and XenApp. I will cover how its used with Octoblu another time.

How to get Involved – HPE Global Innovation Labs

hpelabs

Partner and customer engagement, interaction, assessment and colloboration on solution development and applications.

HPE can help with

  • Build, testing and pre-validation of Edgeline systems and end-to-end solutions
  • Integrated real-life “Edge Experience Zones“ to interact with and highlight industry applications
  • On-site access or secure remote access
  • Datacenter connectivity and testing

Try here https://www.hpe.com/us/en/servers/global-innovation-lab.html

 

Poppelgaard.com – Professional Services

if you are interested in testing your applications on the ProLiant Server Catridges – please dont hesitate to contact me a thomas@poppelgaard.com
I can also help with above value added tasks plus much more 🙂

Source

I highly recommend reading following articles from Citrix Blogs from Tony Sanchez

Citrix XenDesktop 7.11 and XenApp 7.11

Written by Thomas Poppelgaard. Posted in AMD, Apple, Azure, Citrix, Cloud, Datacenter and Cloud, Desktop Virtualization, Director, End User Computing, FirePro, GRID, GRID 2.0, HDX, HDX 3D Pro, HTML5, iOS, Linux, Microsoft, NVENC, NVIDIA, OS X, Profile Management, Provisioning, Provisioning Services, Reciever, StoreFront, vGPU, Virtualization Ready, Windows 10, Windows Server 2016, XenApp, XenDesktop

7-11-logo

Citrix have released a new version of Citrix XenDesktop 7.11 and XenApp 7.11 and is now available for download.

Citrix raises the bar of for user experience and new product release of following technologies

  • Virtual Delivery Agents 7.11 for ServerOS and ClientOS
  • AppDNA 7.11
  • Storefront 3.7
  • Provisioning Services 7.11
  • Profile Management 5.5
  • License Server 11.14
  • Citrix Receiver 15.0 for Windows
  • HDX RealTime Optimization Pack 2.1.1 for Microsoft Skype® for Busines
  • Citrix SCOM Management Bundle for XenApp and XenDesktop (2016_08_24)
  • Linux Virtual Delivery Agent 1.4
  • Tech preview for HTML5 redirection

This release is an important release no matter if you are working daily with Office application such as Excel, Word or Browsers and even highend applications such as CAD. The features in 7.11 have important improved user experience from the VDA to the Receiver that improves dramtically the user experience. NVIDIA NVENC technology is now part of VDA and supports even multiple monitors. The admin can now monitor RTT within Director this feature have been something I have asked for very long time and now finally its in the product, customer will love this new feature so its fast to see where the issue is in a infrastructure with which users that have latency issues. Version 7.11 is the release that fully supports Microsoft Windows Server 2016 that is soon GA, this means you can install Delivery components on Windows Server 2016, VDA on Server 2016, use Azure N-series with support for Windows Server 2016 Hyper-V Discrete Device Assignment (DDA) or you can use it onpremises with Hyper-V. Support for UWP is HUGE and I am very excited about this technology and this also used in Microsoft Hololens so cant wait to a Receiver for hololens so you can publish UWP apps to Hololens 😉 Imagine that. I can keep going on with all these new features lets dig in below and learn whats new, its incredible that Citrix raises the bar and comes with huge improvements and they this each 3 months 🙂 yes each 3months, you read it correct. If you dont have a plan for this in your company I highly recommend you build a strategy on how you upgrade you Citrix environment frequently to get these awesome new features.

Recent Comments

Server 2016 Support

|

Wonderful website. A lot of useful info here. I am sending it to a few friends ans also sharing in delicious. And obviously, thanks for your sweat!

Server 2016 Support

Thomas Poppelgaard

|

Thanks Jose, I have corrected the map plus updated the map so 29 datacenters are now alive.

Jose Brenes

|

Your map of Australia is wrong. You have put the state of Victoria inside the West Australian state.

Tobias K

|

Note that on XenServer 7.1, installing VDA 7.13 also works to enable vGPUs running XenDesktop 7.11 even using the newer “NvFBCEnable.exe -enable -noreset” command. Tested with an M60 using various profiles.

Alex

|

So how come version 3.11 doesn’t work for application switching?