Often a call for papers for big events will be issued about six months in advance, whereas with user groups might be ..during the previous session.
A Short Synergy 2016 Review
Anyhoo, Synergy. I thought this year was better than last year in terms of deliverable announcements. I'd pick out a key partnership with Atlantis Computing for Hyper-Converged Infrastructure, Atlantis's Two Citrix Synergy Awards but it would be fair to say that I work for Atlantis Computing :)
What I found interesting was the refocus of Citrix being an application enablement company - for Microsoft and the focus away from AWS to be much more firmly behind Azure, That said, VMware were on the Synergy floor showing some interesting services. I very much liked the new version of XenServer 7, and I'll have blog on that later. If there was a pick out feature within the native Citrix stack it was the Federated Authentication feature for me. I've delivered services in the past where the delivery would've been faster, cheaper, easier if this functionality had been available. I am very impressed.
The Raspberry PI thin client is pretty neat as a device, very compact - but I can't see it being the storm for new take up of TCs, and could likely cause confusion with existing TC partners. I saw a lot of love and desire to move Windows 10 into the VDI space - we will see what 2016 will bring given the higher demands of the OS and complexity in making a consumer OS designed to sell applications directly conformant with enterprise workspace delivery.
If it there was one thing that could be different at a future synergy environment (besides it being in Europe) it would have the Citrix User Group Community be more visible on the Synergy show floor, as they were the previous year.
That was like... Pearl and Dean wasn't isn't?
Where is the PVS stuff?
Preventing Possible PVS Performance Pain Points
The synopsis of the session discussed the fact that Citrix Provisioning Services has been invigorated with new storage optimisations. Every storage vendor that got into business providing a solution to I/O problems may have to think twice about the value they add given new services within PVS. But, does that mean that creating a viable PVS service has become a breeze? In Preventing Possible PVS Performance Pain Points we set out to look at the performance of PVS server including networking, host configuration, the importance of being earnest about memory, the good, bad and ugly of RAM+HDD write cache and Windows Storage or hyper converged environments, migration and availability.
This session appeared as part of the community geek speak sessions.
To summarise the contents of SYN306:
- All new Visio template options for PVS diagrams
- PVS Write Cache types and why you’d want to utilise RAM+HDD; how to monitor that cache type, and if you didn’t want to move to that cache type how to avoid issues with Address Space Randomization Layout.
- Considerations for networking throughout and demand
- Monitoring RAM for PVS servers to ensure best performance
- Introduction of PVS improvements for booting PVS instances
- Improvements in technology to improve merge and creation time - with thanks to Dane Young for background content
- Replication of images
- The importance of Hyper-Converged in delivering Pod based architecture and Pod based architecture's importance for scaling out PVS service delivery
- And automation of services - particularly for PVS image management such as Aaron Parker's Gold Image Automation or Trond Haavarstein's PVS Image Automation with MDT