Metro Apps, Modern Apps, Windows Store Apps, AppX, Universal Apps. Whatever you want to call them they have become a substantial part of Windows. If you’re having trouble understanding how they work and why, you are not alone. If you’re interested check out this quick read that may help clear things up a bit here. Some AppX Apps are the Tiles you see on the Start Menu or in the list that come preinstalled or even automatically installed by the Windows Store.
As the title suggests, if not handled properly these Apps can cause Sysprep to fail. Sysprep in Windows 8 and 10 has a validation mechanism that checks each of these installed Apps and determines if they’re provisioned for All Users or if they’re just installed for a single user. If for some reason you remove provisioning on an app that was installed for a user (VMware OS Optimization Tool comes to mind, but more on this later) it can cause the validation to fail and Sysprep won’t succeed. Continue reading
Generally speaking the App Volumes Manager and Agent install process is ridiculously simple. A series of Next, Next, Next, Next, Finish for the most part. The big difference that’s in the documentation but hasn’t been covered much for App Volumes 2.12 is the Certificate Validation feature. If you upgrade the App Volumes Manager and go with the defaults, all communication between the App Volumes Manager and Agents is over HTTPS (SSL). This probably sounds like no big deal, unfortunately it is. Continue reading
If you work with VMware Horizon View and you aren’t familiar with App Volumes yet, I urge you to check out this video. It’s pretty awesome. The latest and greatest version yet was just released a few weeks ago. App Volumes 2.12 has a number of feature enhancements and added compatibility that is sure to be good news for those trying to do non-persistent Windows 10 deployments. Continue reading
Building a Windows 10 image for a Horizon View deployment I found Windows Update stuck on this Definition Update for Windows Defender. It failed with the following Error 0x80070643 numerous times. Continue reading
I decided to add a calculator to demonstrate the licensing components of the per core Windows Server 2016 Licensing Model. The intent here is to give you a general idea of how many 2-Core Packs you may need and what it may cost to license Windows Server 2016. If you want more information on how the licensing works please check out my first article. Have fun!
Disclaimer: All pricing on here is MSRP. Actual pricing may vary greatly. This is not a quote nor should it be considered factual. This is a hypothetical guess at what pricing and core pack licensing is based on the MSRP pricing available at the time. You should contact your Reseller or LSP to get actual pricing or quotes. I didn’t include Single CPU (Socket) or less than 8-Cores as options because of the 16-Core Minimum. The Software Assurance costs are based on 2 years Open License or 3 Years Open Value and it’s ~25% per year. I picked the higher cost User CALs for this calculator at ~$43 per CAL, Device CALs are ~$38 per CAL.
So I’m sure everyone has seen, heard or read something about the new licensing model for Microsoft’s flagship Windows Server 2016. People have been talking about it or reposting Microsoft’s publicly released information… Read more »
Hi there. My name is Shawn. I’ll be your host for this blog. I work as a Senior Systems Engineer for a reseller/VAR/integrator/channel partner in the Kansas City area. I work with many businesses in the KC area and beyond to sort through their constantly changing technology landscapes. I get to see and work with a lot of cool technology which I’ll be posting about here. I work through all sorts of interesting and challenging technical designs and issues that I will be posting about. Anyway, check out my About page and welcome. I hope you enjoy reading my blog.