A Swede went to Finland, spoke and learned

A couple of weeks ago now, I was focused on preparing for, and speaking at, Techdays in Helsinki, Finland. I was really happy to be accepted for the conference after Alexander spoke there last year and praised the arrangement. I was also very happy that Techdays choose to accept my session on Windows Virtual Desktop, since this is one of the topics I’m most passionate about and involved in currently.

I have presented this session previously, at Igel Disrupt, but this time I had another kind of audience. With more mixed backgrounds and focused more on “regular” client management. In the end, it turned out great!

I felt that I had a very good interaction with the audience and I’ve received a number of questions during and after the event. Also, the feedback has been amazing and I’m very glad and humbled by that.

So, why do I think that WVD is such a big deal? Well, I’ve said it before and to me the first and most obvious benefit is that this till democratize the, so called, EUC (End User Compute) landscape. The technologies out there today is usually pricey and fairly complicated to configure and maintain (and yes, that includes Windows Server RDS). They usually also require you to buy a number of licenses up front, or at least do the implementation as a project.

This have prevented some, especially smaller, organizations from going down this route, even though they would like to. This is made possible with WVD. You can scale DOWN to a 1 user on 1 VM if you like, and that’s fine. You don’t have any upfront cost, you can for your consumption (even thought it actually can be cheaper to buy reserved instance and pay for it upfront). It’s a very, in the simplest configuration, an easy solution with implement and manage.

You of course get all the benefits that any, or most, EUC solutions have today in terms connect-ability, security and mobility.

One of the feedback points I received both in Munich and in Helsinki were that I almost sound overly positive and don’t present the downsides of the service. For this, I’m sorry. Its actually not intentional and therefore I would like to point out a few downsides I currently see with the service (based on publicly available fact):

  1. Its great to run apps and desktops in the cloud, but you need to consider your apps first. This will be the showstopper for many organizations. If you have systems that required connectivity to your local datacenter as an example, its perhaps not great from a performance perspective to put the client in the cloud. You can of course see this as an opportunity as well – you are moving your stuff to the cloud, but consider that first.
  2. Second, authentication. Personally, I do feel that the current solution could be highly improved, but could require more cross product group work. The RDS cant sort this out by themselves, they need help from the Windows, AD and Azure AD among others. Ill dig deeper into this in time of the public preview.
  3. Since this is some kind of hybrid if we compare it to other solutions, we need to have tools that makes it easier to manage the service, especially the VMs. You don’t need to manage and maintain the actually underlying infrastructure – but you need to configure it, secure parts of it and manage your VMs. This will also require some cross PG work, and this (as well as security) is where I see that I personally can make a difference.

There are of course other downsides as well – and I’m really looking forward to getting more information of the final decision on licensing of the service. We’ll see.

This is however feedback I’m struggling with. I do get it, I do see it as important and I do want to be better at not just look at the good sides of it, but also (in blogs or when I’m speaking) give my audience a realistic picture. Again, I’m not trying to hide anything, its just a matter of me focusing on the amazing technology.

I’ve actually had this challenge before. In the beginning of Windows 10 I did a customer presentation on Windows 10 and why that would be the best OS for this customer. They found the presentation interesting, they saw the benefits but then they asked me a question: “So, what’s bad with Windows 10? There needs to be something, or else we wont be able to trust what you are saying.” I do get that feedback, especially now a few years later. So, moving forward ill do my best to present a more nuanced picture whatever I’m presenting on.

So, we’ll for sure have reasons to get back to WVD in coming blogposts, but for now Ill be focusing a lot of my “core” technologies which is especially Windows 10 and EMS.

Take care and remember to follow the blog and listen to the Knee Deep in Tech podcast. You can find us wherever you find pods including iTunes and Spotify.

Azure ASM (Classic) and migrating to ARM

Hey, Toni here again. Some customers are still stuck on using Azure classic for their deployment. Microsoft has done a lot of work for many years to convince everyone to move over to Azure Resource Manager (ARM) model and with good success as well. Did you know that they offer good tools (well scripts actually) for the migration itself?

Microsoft has also primarily been developing all the cool new features for ARM and only maintaining the classic (ASM) model. A few years ago, not everything was available in the ARM management model but today, most of your services will run fine (better) with ARM.

The nice thing with migrating is that Microsoft actually provides you with tools to verify the success of the migration in advance, so you’ll know what you have to fix (or break, in some cases) to manage the migration successfully. The migration will check for problems, once those are fixed, it will go to a “prepare” phase. Once there, you have the option to do the migration or abort, if you wish to do that. So a very flexible operation.

One thing to note is that if you are running VM backups, those will need to be disabled before migration (and remove the extension from the VM). Once you are on the ARM model, you can re-activate your recovery plans to create new backups. The old ones will become obsolete. Also, the prerequisite check will complain about the BG-info extension, however that will be automatically removed anyway, so there is no real reason to remove it beforehand.

The only issue I’ve had with the migration thus far, was a subscription where the customer was using Azure Traffic Manager. That broke for some reason which meant I had to, quite quickly after migration, create new endpoints for the Traffic Manager. Load balancers where migrated just fine.

Once you have migrated over to ARM, you will be offered a plethora of features that you previously did not have in the portal. New services, functions, RBAC access and many, many more.

So please, consider migrating to Azure Resource Manager. It will make your life easier… and who want’s to use tech from 10 years ago anyway?

More details here:
https://docs.microsoft.com/en-us/azure/virtual-machines/windows/migration-classic-resource-manager-ps

Azure vNet peering and why it’s great

Hi, my name is Toni aka “The Finn” from some guest appearances on the show. I was invited to write some stuff here so here goes.
I have recently been doing some Azure work and want to share some of that with you.
Building your applications and infrastructure in multiple Azure networks or even regions is a common practice nowadays. But some of you might not know that you can very easily stitch together those different virtual networks by using Azure’s own back-bone instead of creating elaborate VPN solutions that used to be the case many years ago.

Let’s say you have a production network and a developer network that you want to interact in between. Pretty much all you need to do is to go to your respective network and create the peerings. Very easy and straight forward. Within an Azure Site, you can even allow a network to utilize the gateway to give access to your on-premises networks with a check-box.

Once you have your peerings connected, you will need to make sure that your network security groups allow traffic between the networks and also, don’t forget the local firewall on your server.

That’s it! Enjoy connecting your Azure regions and networks together without complex gateways or VPNs.