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

 

NVIDIA GRID 4.2 released (367.92/369.95)

Written by Thomas Poppelgaard. Posted in CentOS, Citrix, Datacenter and Cloud, Desktop Virtualization, End User Computing, GRID, HDX, HDX 3D, HDX 3D Pro, Horizon, Linux, Microsoft, NVENC, NVIDIA, Quadro, RHEL, Tesla, Ubuntu, vDGA, vGPU, VMware, vSphere, Windows 10, Windows 7, Windows 8, Windows 8.1, Windows Server 2008R2, Windows Server 2012R2, Windows Server 2016, XenApp, XenDesktop, XenServer

nvidiagrid

Hi All

Its time to update your NVIDIA GRID K1, K2, M10, M6, M60 environment.

NVIDIA have released new drivers for NVIDIA GRID 4.2 for March 2017.

New in this Release:

  • NVIDIA GRID 4.2 has multiple fixes that improve memory management and NVFBC optimizations that ensure that surface allocations in the Frame Buffer are managed more efficiently to increase stability. The latest release includes frame buffer residency optimizations. Now, during high-memory pressure situations where there is a lack of or high competition for frame buffer, users remain resident-in.
  • Miscellaneous bug fixes
  • Support for Citrix XenServer 7.1
  • Support for the following Linux guest OS versions:
    • Red Hat Enterprise Linux 7.3
    • CentOS 7.3
    • Ubuntu 16.04 LTS

Important notes – Note: XenServer 7.1 is the last XenServer release supported on GRID K1 and K2. Citrix XenServer 6.2 is no longer supported.

Whats new in vGPU 367.92-369.95

NVIDIA have released a new version of vGPU 367.92-369.95 for NVIDIA GRID  (K1, K2, Tesla M6, M10 and M60 platform)

Included in this release is

  • NVIDIA GRID Virtual GPU Manager versions 367.92 for Citrix XenServer 6.5 SP1
  • NVIDIA GRID Virtual GPU Manager versions 367.92 for Citrix XenServer 7
  • NVIDIA GRID Virtual GPU Manager versions 367.92 for Citrix XenServer 7.1
  • NVIDIA GRID Virtual GPU Manager version 367.92 for VMware vSphere 6.0 Hypervisor (ESXi)
  • NVIDIA GRID Virtual GPU Manager version 367.92 for VMware vSphere 6.5 Hypervisor (ESXi)
  • NVIDIA Windows drivers for vGPU version 369.95
  • NVIDIA Linux drivers for vGPU version 367.92.

Important:

The GRID vGPU Manager and Windows guest VM drivers must be installed together. Older VM drivers will not function correctly with this release of GRID vGPU Manager. Similarly, older GRID vGPU Managers will not function correctly with this release of Windows guest drivers

Windows Guest OS support in vGPU 369.95

GRID vGPU 369.95 supports following Windows release as a guest OS

  • Microsoft Windowss 7 (32/64bit)
  • Microsoft Windows 8 (32/64bit)
  • Microsoft Windows 8.1 (32/64bit)
  • Microsoft Windows 10 (32/64bit)
  • Microsoft Windows Server 2008R2
  • Microsoft Windows Server 2012 R2
  • Microsoft Windows Server 2016

Linux Guest OS support in vGPU 367.92

GRID vGPU 367.92 supports following Linux distributions as a guest OS only on supported Tesla GPUs
Import: GRID K1/K2 do not support vGPU on Linux guest os.

  • Red Hat Enterprise Linux 7.0-7.3
  • CentOS 7.0-7.3
  • Ubuntu 16.04 LTS
  • Ubuntu 14.04 LTS

Guide – Update existing vGPU GRID Manager (Hypervisor)

 

GRID vGPU Manager 367.92 for Citrix XenServer 6.5

If you have a NVIDIA GRID K1, K2, M6, M60 vGPU GRID manager installed in Citrix XenServer. Upgrade with one of below methodology:

Methodology 1 – the manual way “No GUI”

Upgrading an existing installation of the NVIDIA driver on Citrix XenServer 6.5, use the rpm -U command to upgrade:

If you have NVIDIA GRID K1 / K2
[root@localhost ~]# rpm -Uv NVIDIA-vGPU-kepler-xenserver-6.5-367.92.x86_64.rpm 
Preparing packages for installation...
If you have NVIDIA GRID TESLA M10 / M6 / M60
[root@localhost ~]# rpm -Uv NVIDIA-vGPU-xenserver-6.5-367.92.x86_64.rpm 
Preparing packages for installation...

The recommendation from NVIDIA is to shutdown all VMs using a GPU. The machine does continue to work during the update, but since you need to reboot the XenServer itself, it’s better to gracefully shutdown the VMs. So after your VMs have been shutdown and you upgraded the NVIDIA driver, you can reboot your host.

[root@localhost ~]# xe host-disable
[root@localhost ~]# xe host-reboot

Methodology 2 – the “GUI” way

Select Install Update… from the Tools menu
 Click Next after going through the instructions on the Before You Start section
 Click Add on the Select Update section and open NVIDIA’s XenServer Supplemental Pack ISO

If you have NVIDIA GRID K1 / K2 select following file:

“NVIDIA-vGPU-kepler-xenserver-6.5-367.92.x86_64.iso ”

If you have NVIDIA GRID M10/ M6/M60 select following file:

“NVIDIA-vGPU-xenserver-6.5-352.83.x86_64.iso ”

Click Next on the Select Update section
 In the Select Servers section select all the XenServer hosts on which the Supplemental Pack should be installed on and click Next
 Click Next on the Upload section once the Supplemental Pack has been uploaded to all the XenServer hosts
Getting Started
 Click Next on the Prechecks section
 Click Install Update on the Update Mode section
 Click Finish on the Install Update section

After the XenServer platform has rebooted, verify that the GRID package installed and loaded correctly by checking for the NVIDIA kernel driver in the list of kernel loaded modules.

Validate from putty or XenCenter CLI

run lsmod | grep nvidia

Verify that the NVIDIA kernel driver can successfully communicate with the GRID physical GPUs in your system by running the nvidia-smi command, which should produce a listing of the GPUs in your platform:

Check driver version is 367.92, if it is then your host is ready for GPU awesomeness and make your VM rock.

GRID vGPU Manager 367.92 for Citrix XenServer 7

If you have a NVIDIA GRID K1, K2, M6, M60 vGPU GRID manager installed in Citrix XenServer. Upgrade with one of below methodology:

Methodology 1 – the manual way “No GUI”

Upgrading an existing installation of the NVIDIA driver on Citrix XenServer 7, use the rpm -U command to upgrade:

If you have NVIDIA GRID K1 / K2
[root@localhost ~]# rpm -Uv NVIDIA-vGPU-kepler-xenserver-7.0-367.92.x86_64.rpm 
Preparing packages for installation...
If you have NVIDIA GRID TESLA M10 / M6 / M60
[root@localhost ~]# rpm -Uv NVIDIA-vGPU-xenserver-7.0-367.92.x86_64.rpm 
Preparing packages for installation...

The recommendation from NVIDIA is to shutdown all VMs using a GPU. The machine does continue to work during the update, but since you need to reboot the XenServer itself, it’s better to gracefully shutdown the VMs. So after your VMs have been shutdown and you upgraded the NVIDIA driver, you can reboot your host.

[root@localhost ~]# xe host-disable
[root@localhost ~]# xe host-reboot

Methodology 2 – the “GUI” way

Select Install Update… from the Tools menu
 Click Next after going through the instructions on the Before You Start section
 Click Add on the Select Update section and open NVIDIA’s XenServer Supplemental Pack ISO

If you have NVIDIA GRID K1 / K2 select following file:

“NVIDIA-vGPU-kepler-xenserver-7.0-367.92.x86_64.iso ”

If you have NVIDIA GRID M10/ M6/M60 select following file:

“NVIDIA-vGPU-xenserver-7.0-352.83.x86_64.iso ”

Click Next on the Select Update section
 In the Select Servers section select all the XenServer hosts on which the Supplemental Pack should be installed on and click Next
 Click Next on the Upload section once the Supplemental Pack has been uploaded to all the XenServer hosts
Getting Started
 Click Next on the Prechecks section
 Click Install Update on the Update Mode section
 Click Finish on the Install Update section

After the XenServer platform has rebooted, verify that the GRID package installed and loaded correctly by checking for the NVIDIA kernel driver in the list of kernel loaded modules.

Validate from putty or XenCenter CLI

run lsmod | grep nvidia

Verify that the NVIDIA kernel driver can successfully communicate with the GRID physical GPUs in your system by running the nvidia-smi command, which should produce a listing of the GPUs in your platform:

Check driver version is 367.92, if it is then your host is ready for GPU awesomeness and make your VM rock.

GRID vGPU Manager 367.92 for Citrix XenServer 7.1

If you have a NVIDIA GRID K1, K2, M6, M60 vGPU GRID manager installed in Citrix XenServer. Upgrade with one of below methodology:

Methodology 1 – the manual way “No GUI”

Upgrading an existing installation of the NVIDIA driver on Citrix XenServer 7.1, use the rpm -U command to upgrade:

If you have NVIDIA GRID K1 / K2
[root@localhost ~]# rpm -Uv NVIDIA-vGPU-kepler-xenserver-7.1-367.92.x86_64.rpm 
Preparing packages for installation...
If you have NVIDIA GRID TESLA M10 / M6 / M60
[root@localhost ~]# rpm -Uv NVIDIA-vGPU-xenserver-7.1-367.92.x86_64.rpm 
Preparing packages for installation...

The recommendation from NVIDIA is to shutdown all VMs using a GPU. The machine does continue to work during the update, but since you need to reboot the XenServer itself, it’s better to gracefully shutdown the VMs. So after your VMs have been shutdown and you upgraded the NVIDIA driver, you can reboot your host.

[root@localhost ~]# xe host-disable
[root@localhost ~]# xe host-reboot

Methodology 2 – the “GUI” way

Select Install Update… from the Tools menu
 Click Next after going through the instructions on the Before You Start section
 Click Add on the Select Update section and open NVIDIA’s XenServer Supplemental Pack ISO

If you have NVIDIA GRID K1 / K2 select following file:

“NVIDIA-vGPU-kepler-xenserver-7.1-367.92.x86_64.iso ”

If you have NVIDIA GRID M10/ M6/M60 select following file:

“NVIDIA-vGPU-xenserver-7.1-352.83.x86_64.iso ”

Click Next on the Select Update section
 In the Select Servers section select all the XenServer hosts on which the Supplemental Pack should be installed on and click Next
 Click Next on the Upload section once the Supplemental Pack has been uploaded to all the XenServer hosts
Getting Started
 Click Next on the Prechecks section
 Click Install Update on the Update Mode section
 Click Finish on the Install Update section

After the XenServer platform has rebooted, verify that the GRID package installed and loaded correctly by checking for the NVIDIA kernel driver in the list of kernel loaded modules.

Validate from putty or XenCenter CLI

run lsmod | grep nvidia

Verify that the NVIDIA kernel driver can successfully communicate with the GRID physical GPUs in your system by running the nvidia-smi command, which should produce a listing of the GPUs in your platform:

Check driver version is 367.92, if it is then your host is ready for GPU awesomeness and make your VM rock.

GRID vGPU Manager 367.92 for VMware vSphere 6.0

To update the NVIDIA GPU VIB, you must uninstall the currently installed VIB and install the new VIB.

To uninstall the currently installed VIB:

  1. Stop all virtual machines using 3D acceleration.
  2. Place the ESXi host into Maintenance mode.
  3. Open a command prompt on the ESXi host.
  4. Stop the xorg service by running the command:/etc/init.d/xorg stop
  5. Remove the NVIDIA VMkernel driver by running the command:vmkload_mod -u nvidia
  6. Identify the NVIDIA VIB name by running this command:esxcli software vib list | grep NVIDIA
  7. Remove the VIB by running the command:esxcli software vib remove -n nameofNVIDIAVIBYou can now install a new NVIDIA GPU VIB
  8. Use the esxcli command to install the vGPU Manager package:
If you have NVIDIA GRID K1 / K2 select following file:
[root@lesxi ~] esxcli software vib install -v /NVIDIA-vGPU-kepler-VMware_ESXi_6.0_Host_Driver_367.92-1OEM.600.0.0.2494585.vib
If you have NVIDIA GRID TESLA M10 / M6 / M60 select following file:
[root@lesxi ~] esxcli software vib install -v /NVIDIA-vGPU-VMware_ESXi_6.0_Host_Driver_367.92-1OEM.600.0.0.2494585.vib

After the ESXi host has rebooted, verify that the GRID package installed and loaded correctly by checking for the NVIDIA kernel driver in the list of kernel loaded modules.

[root@lesxi ~]# vmkload_mod -l | grep nvidia 
Preparing packages for installation...

Validate

run nvidia-smi

Verify that the NVIDIA kernel driver can successfully communicate with the GRID physical GPUs in your system by running the nvidia-smi command, which should produce a listing of the GPUs in your platform:

Check driver version is 367.92, if it is then your host is ready for GPU awesomeness and make your VM rock.

GRID vGPU Manager 367.92 for VMware vSphere 6.5

To update the NVIDIA GPU VIB, you must uninstall the currently installed VIB and install the new VIB.

To uninstall the currently installed VIB:

  1. Stop all virtual machines using 3D acceleration.
  2. Place the ESXi host into Maintenance mode.
  3. Open a command prompt on the ESXi host.
  4. Stop the xorg service by running the command:/etc/init.d/xorg stop
  5. Remove the NVIDIA VMkernel driver by running the command:vmkload_mod -u nvidia
  6. Identify the NVIDIA VIB name by running this command:esxcli software vib list | grep NVIDIA
  7. Remove the VIB by running the command:esxcli software vib remove -n nameofNVIDIAVIBYou can now install a new NVIDIA GPU VIB
  8. Use the esxcli command to install the vGPU Manager package:
If you have NVIDIA GRID K1 / K2 select following file:
[root@lesxi ~] esxcli software vib install -v /NVIDIA-vGPU-kepler-VMware_ESXi_6.5_Host_Driver_367.92-1OEM.650.0.0.2494585.vib
If you have NVIDIA GRID TESLA M10 / M6 / M60 select following file:
[root@lesxi ~] esxcli software vib install -v /NVIDIA-vGPU-VMware_ESXi_6.5_Host_Driver_367.92-1OEM.650.0.0.2494585.vib

After the ESXi host has rebooted, verify that the GRID package installed and loaded correctly by checking for the NVIDIA kernel driver in the list of kernel loaded modules.

[root@lesxi ~]# vmkload_mod -l | grep nvidia 
Preparing packages for installation...

Validate

run nvidia-smi

Verify that the NVIDIA kernel driver can successfully communicate with the GRID physical GPUs in your system by running the nvidia-smi command, which should produce a listing of the GPUs in your platform:

Check driver version is 367.92, if it is then your host is ready for GPU awesomeness and make your VM rock.

Update existing vGPU Driver (Virtual Machine)

When the hypervisor vGPU GRID manager is updated next is updating the Virtual Machines vGPU driver.

  • 369.95_grid_win8_win7_32bit_international.exe
  • 369.95_grid_win8_win7_server2012R2_server2008R2_64bit_international.exe
  • 369.95_grid_win10_32bit_international.exe
  • 369.95_grid_win10_server2016_64bit_international.exe
  • NVIDIA-Linux-x86_64-367.92-grid.run (only available with M10/M6/M60)

The vGPU driver for Windows 7, 8, 8.1, 10 is available with NVIDIA GRID vGPU download. This is available for both K1/K2/M10/M6/M60

The vGPU driver for Linux is only available for vGPU with following Tesla GPU M10/M6/M60

Update your Golden Images and reprovisioning the new virtual machines with updated vGPU drivers, if you have stateless machines update vGPU drivers on each.

#HINT – Express upgrade of drivers is the recommended option according to the setup. If you use the “Custom” option, you will have the option to do a “clean” installation. The downside of the “clean installation” is that it will remove all profiles and custom settings. The pro of using the clean installation option is that it will reinstall the complete driver, meaning that there will be no old driver files left on the system. I most of the time recommends using a “Clean” installation to keep it vanilla 🙂

#HINT (Citrix XenDesktop 7.6-7.11 customers)

The NVIDIA GRID API provides direct access to the frame buffer of the GPU, providing the fastest possible frame rate for a smooth and interactive user experience. If you install NVIDIA drivers before you install a VDA with HDX 3D Pro, NVIDIA GRID is enabled by default.

To enable NVIDIA GRID on a VM, disable Microsoft Basic Display Adapter from the Device Manager. Run the following command and then restart the VDA: Montereyenable.exe -enable -noreset

If you install NVIDIA drivers after you install a VDA with HDX 3D Pro, NVIDIA GRID is disabled. Enable NVIDIA GRID by using the Montereyenable tool provided by NVIDIA.

To disable NVIDIA GRID, run the following command and then restart the VDA: Montereyenable.exe -disable -noreset

#HINT (Citrix XenDesktop 7.12/7.13 customers)

The NVIDIA GRID API provides direct access to the frame buffer of the GPU, providing the fastest possible frame rate for a smooth and interactive user experience. If you install NVIDIA drivers before you install a VDA with HDX 3D Pro, NVIDIA GRID is enabled by default.

To enable NVIDIA GRID on a VM, disable Microsoft Basic Display Adapter from the Device Manager. Run the following command and then restart the VDA: NVFBCEnable.exe -enable -noreset

If you install NVIDIA drivers after you install a VDA with HDX 3D Pro, NVIDIA GRID is disabled. Enable NVIDIA GRID by using the NVFBCEnable tool provided by NVIDIA.

To disable NVIDIA GRID, run the following command and then restart the VDA: NVFBCEnable.exe -disable -noreset

 

Source

GRID K1/K2 – sources

Download vGPU 352.83-354.80 for XenServer 6.5 for GRID K1 / K2 here

Download vGPU 352.83-354.80 for XenServer 7.0 for GRID K1 / K2 here

Download vGPU 367.92-369.95 for XenServer 7.1 for GRID K1 / K2 here

Download vGPU 367.92-369.95 for vSphere 6 for GRID K1 / K2 here

Download vGPU 367.92-369.95 for vSphere 6.5 for GRID K1 / K2 here

Tesla M10/M6/M60 – sources

vGPU Grid Manager + Drivers are only available to customers and NVIDIA NPN partners for M10/M6/M60.

Download if you are a NPN partner

Download if you are a GRID M10, M6, M60 customer

vGPU 367.92-369.95 for XenServer 6.5 for Tesla M10 / M6 / M60

vGPU 367.92-369.95 for XenServer 7 for Tesla M10 / M6 / M60

vGPU 367.92-369.95 for XenServer 7.1 for Tesla M10 / M6 / M60

vGPU 367.92-396.95 for vSphere 6 for Tesla M10 / M6 / M60

vGPU 367.92-396.95 for vSphere 6.5 for Tesla M10 / M6 / M60

Other Sources

NVIDIA blog – https://blogs.nvidia.com/blog/2017/03/10/nvidia-grid-march-2017/ 

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.

Microsoft Hololens Commercial Edition

Written by Thomas Poppelgaard. Posted in Augmented Reality, Citrix, Cloud, Datacenter and Cloud, Desktop Virtualization, End User Computing, Microsoft, Virtualization Ready

Hi All

I have been having the Microsoft Hololens developer edition for some weeks now and I am amazed how a great product it is, when I got unbox the package I could quickly see that this was not a typical “developer” product aka “beta” product it seem finish and ready for shipping for the masses.

IMG_9017

I created a video of how great Citrix is working together with Hololens, you can see it below

In the nearest future you will be able to run Published applications from Azure such as the new announced service Citrix XenApp “express” instead of the discontinued “Azure RemoteApp” – read more about this annoncement here

Below video gives you an idea how it might look like working on either a Word document or heavy GPU CAD application such as Autodesk AutoCAD from the Hololens. The applications are not installed on the Microsoft Hololens, they are running from servers securely and pixels are only streamed to the Microsoft Hololens, this is what is called remote graphics, and now possible in Augmented Reality. Powerful technology and many use cases for this new workstyle.

 

Today Microsoft is now shipping the Hololens Commercial edition.

 

The Commercial Suite includes the Development Edition, enterprise features for added security and device management, and a warranty. Transform your business with Microsoft HoloLens.

Contact your Microsoft account representative or email mpcsales@microsoft.com.

hololens

Unboxing Microsoft HoloLens Development Edition

IMG_8904

IMG_8905IMG_8906IMG_8907

What’s in the box

  • Microsoft HoloLens Development Edition
  • Clicker
  • Carrying case
  • Microfiber cloth
  • Charger
  • Micro-USB 2.0 cable

Enterprise features

  • Kiosk mode. With HoloLens kiosk mode, you can limit which apps to run to enable demo or showcase experiences.
  • Mobile Device Management (MDM) for HoloLens. Your IT department can manage multiple HoloLens devices simultaneously using solutions like Microsoft InTune. You will be able to manage settings, select apps to install and set security configurations tailored to your organization’s need.
  • Identity. Azure Active Directory and next generation credentials with PIN unlock.
  • Windows Update for Business. Controlled operating system updates to devices and support for long term servicing branch.
  • Data security. BitLocker data encryption and secure boot is enabled on HoloLens to provide the same level of security protection as any other Windows device.
  • Work access. Anyone in your organization can remotely connect to the corporate network through a virtual private network on a HoloLens. HoloLens can also access Wi-Fi networks that require credentials.
  • Windows Store for Business. Your IT department can also set up an enterprise private store, containing only your company’s apps for your specific HoloLens usage. Securely distribute your enterprise software to selected group of enterprise users.

Source

https://www.microsoft.com/microsoft-hololens/en-us/commercial-suite

 

Recent Comments

MarilynToush

|

This message is posted here using XRumer + XEvil 3.0
XEvil 3.0 is a revolutionary application that can bypass almost any anti-botnet protection.
Captcha Recognition Google, Facebook, Yandex, VKontakte, Captcha Com and over 8.4 million other types!
You read this – it means it works! 😉
Details on the official website of XEvil.Net, there is a free demo version.

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.