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. ...
Lost track of the service channel naming of Windows and Office Servicing? Is it “Current Branch” or “Semi-Annual Channel” now?! Or Standard Release?! Windows 10: Ready: Semi-Annual Channel (Targeted) Ready for Business: Semi-Annual Channel Office 365: Ready: Semi-Annual Channel (Targeted) (Or [Targeted Release](http://Ready: Semi-Annual Channel (Targeted) Ready for Business: Semi-Annual Channel)) Ready for Business: Semi-Annual Channel (Or [Standard Release](http://Ready: Semi-Annual Channel (Targeted) Ready for Business: Semi-Annual Channel)) 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: ...
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. .Cloud TLD 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! Cheers, Jean-Paul
**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? ...
**With the new Windows 10 Fall Creators Update, Microsoft finally added a built-in NAT Switch into Hyper-V! This gives Hyper-V Virtual Machines access to the computer’s network. **The new switch automatically assigns IP address to your Virtual Machines, so no need to run your own DHCP server anymore! In older versions of Windows 10, it was still required to create the Virtual Switch yourself, but this required static IP address assignment in the OS or the installation of a DHCP server. ...
So your Group Policy (GPO) settings do not allow you to upgrade to the Windows 10 Fall Creators Update and you have local administrative access on your machine? The registry fix from below will change this! Copy the registry fix from below and save it as fix.reg with Notepad. (Make sure you don’t save it as fix.reg.txt!) Right click on the file and click “Merge”. You should now have access to Settings -> Update & Security -> Windows Insider Program. ...
You can follow the original guide by Microsoft and manually edit all the details, or just use the variables from the script below and let PowerShell do the work for you. # Variables $InternalSwitchName = "Internal Virtual Switch" $NATGatewayPrefixLength = "24" $NATGatewayNetwork = "192.168.0.0/$NATGatewayPrefixLength" $NATGatewayIP = "192.168.0.1" $NATNetworkName = "NAT Network" # Create the VM Switch and NAT Gateway New-VMSwitch -SwitchName $InternalSwitchName -SwitchType Internal New-NetIPAddress -IPAddress $NATGatewayIP -PrefixLength $NATGatewayPrefixLength -InterfaceIndex (Get-NetAdapter -Name $("vEthernet ($InternalSwitchName)")).InterfaceIndex New-NetNat -Name $NATNetworkName -InternalIPInterfaceAddressPrefix $NATGatewayNetwork
Six months ago I received an email from our IT Department. Good news, my old 3.5 KG Dell Latitiude E6540 (with a big battery) was out of warranty. The Surface Pro wasn’t announced yet but because of the rumors, I didn’t want to go with a soon-to-be-old Surface Pro 4. And I must say I wanted a notebook that I can place on my Bobby Notebook Stand. ...
A couple of months ago I started to work on a very intensive project with very tight deadlines. This resulted in some very long days at the office and planned rest in the weekends. During that time I decided to disable the corporate email synchronization on my corporate phone. I always got triggered when I received a new email regarding project activities. It’s something you recognize when it’s not there anymore. ...