Happy New Year all! A new workplace is a great way to start the new year. As some of you may know, I’ve moved to a new apartment in 2016. My new apartment has a quite large living room but no extra room for a workplace. I work full time at Avanade and I like to work from home every now and then. I’m also aiming on finishing my Bachelor studies in Q1 2019, so all this requires a good workplace.
As an Xbox 360 fanatic, I switched to PC gaming in 2011. After moving to a new house in 2016, there was no room for Triple Screen PC Gaming. I wanted a new and stable platform with 4K capabilities. The PS4 Pro released with 4K support and I wanted to see what they had to offer. During that time, rumors were telling me that the Xbox Scorpio wasn’t going to release soon. When the Xbox One X – Scorpio Edition was available for pre-order a year later, I decided to switch. In this blog post, I’ll explain why and what my current experiences are. Continue reading
With Windows Servicing, Microsoft is forcing consumers and businesses to upgrade to a Windows 10 Build twice a year. Theoretically you could go for one build per year, but that forces you to upgrade to a new build within 6 months. Otherwise you will end up without support for the old build.
This introduces quite some issues within both SMBs and large organizations. Recently a friend asked me about a recent printer that stopped working. The printer was 2 months old and from a large vendor. I directly checked the build of the machine and yes, it was recently upgraded to the Fall Creators Update. The printer was identified as an “Unknown USB Device”. Updating the driver of the printer didn’t help. Luckily the Technical Support was responding quickly to help, but this means manual processing of orders for the next couple of weeks. Yes I can revert the machine back to the old build, but will that fix the issue or create more issues? And because it’s not a Windows 10 Enterprise machine, Microsoft will try to update the machine later on.
Lost track of the service channel naming of Windows and Office Servicing? Is it “Current Branch” or “Semi-Annual Channel” now?! Or Standard Release?!
Ready: Semi-Annual Channel (Targeted)
Ready for Business: Semi-Annual Channel
Ready: Semi-Annual Channel (Targeted) (Or Targeted Release)
Ready for Business: Semi-Annual Channel (Or Standard Release)
Last update: recently… 🙂
Every day is a new day to change these again, so stay tuned!
So you are signing your PowerShell scripts as a Best Practice from Microsoft. Good job! You’ve configured the PowerShell Execution Policy as AllSigned and you’ve created an application in SCCM where you run the signed script as:
PowerShell.exe -File .\Script.ps1
The application installs just fine on your machine from the Software Center. During the Task Sequence, the application cannot be installed and in the Event Viewer. You’ll find the following error message:
PowerShell.exe: File <Filename> cannot be loaded because running scripts is disabled on this system. For more information, see about_execution_policies at…”
You open up PowerShell to see the current ExecutionPolicy. “Get-ExecutionPolicy -List” shows that all scopes have undefined execution policies. With “Get-Help about_Execution_Policies” you find out that Undefined policy is equal to a restricted policy and that “Permits individual commands, but will not run scripts”.
Go back to your application in SCCM and make sure you set the ExecutionPolicy to AllSigned so it will work both during a Task Sequence and while working in OS.
PowerShell.exe -ExecutionPolicy AllSigned -File .\Script.ps1
Frequent visitors of my blog may have noticed that the domain name of the blog has changed from jvrtech.net to jvr.cloud. You can still reach my blog on jvrtech.net, but within a couple of years, that redirect may disappear.
Most of my short nicknames or my full name aren’t available anymore on the TLDs like .com, .net or .org. When the .cloud TLD was introduced, I saw an opportunity to buy this very short domain name. Tech in a domain name tells people that it has something to do with technology which I like, but Cloud will hopefully do that too.
Thank you for visiting my blog!
This article describes the licensing options you have when you want to deploy Windows Server Virtual Machines in Azure. It’s getting complicated when you start using the Hybrid Use Benefit solution, so always contact Microsoft or your licensing supplier. Please note that I will not answer any licensing questions.
Built-in Licensing for Windows Server
This type of licensing is by-far the most easy to use but it can be an expensive solution. You deploy an Azure Virtual Machine from the Portal or PowerShell and the licensing costs are automatically included with the Virtual Machine costs. But what if you want to use your existing KMS licenses which you’ve bought with your Enterprise Agreement? Or you want to use Windows Server Standard licenses instead of Datacenter licenses?