They simply cannot grasp the concept of not being able to reach the systems in your cloud. They say that you can continue working, because 'it is the cloud man'. That is my reality that is simply not understood by pro-cloud persons. As some power/internet failures are fixed within an hour, while others can take 24 hours. While it is simply a case of being able to continue working when internet fails and/or electricity is gone (diesel generator). You have no idea how many times I have been called an old-fashioned fossil by the pro-cloud people over in Europe. Over here internet (and the electricity grid) is not that fast or reliable, so I like things to be on-premise. Internet over there is great, so everyone is there on the 'Cloud' band wagon. So that would be another reason to re-install instead of upgrade.Īs I live and work in South America, I work for a company in Europe.
That won't work when you upgrade your Windows 10 installation to Windows 11. Simply do not connect to any WiFi node and continue.
In my next post, I show you how you can use the Set-PinnedApplication function of Jan Egil Ring’s module in a logon script so you can unpin the Store app on all computers in your network.ĭuring the Windows install procedure, you are asked to select a WiFi radio station to connect to for network/internet access. Wouldn’t it be wonderful if you could unpin the Store app from the Taskbar with PowerShell? It is not easy as one might think. The example below demonstrates how you can pin Notepad to the Taskbar: PS C:\> Set-PinnedApplication -Action PinToTaskbar -FilePath C:\Windows\system32\notepad.exe
However, in my tests, the actions PinToStartMenu and UnPinFromStartMenu didn’t work on Windows 8.1 but worked well on a Windows 7 machine. I tried the module with Windows 8.1, and it appears to work fine for pinning and unpinning apps to the Taskbar. The synopsis indicates that the cmdlet was made for Windows 7 and Windows 2008 R2. With Get-Help Set-PinnedApplication, you get an overview of the cmdlet. PS C:\> Get-Command -Module PinnedApplicationsįunction Set-PinnedApplication PinnedApplicationsįrom now on, you can use Set-PinnedApplication to pin and unpin apps to the Windows Taskbar. Use the Get-Command cmdlet to check what commands the module contains. If no error message appears, you are fine. Next, you can import the module with the Import-Module cmdlet. Make sure your execution policy is set to unrestricted (Set-ExecutionPolicy Unrestricted). This would be the file path: C:\Users\Administrator\Documents\WindowsPowerShell\Modules\PinnedApplications\PinnedApplications.psm1 You have to create a folder with the name PinnedApplications in the module folder and then save the file as PinnedApplications.psm1 to this folder. In this example, we use C:\Users\Administrator\Documents\WindowsPowerShell\Modules. If you don’t have an Active Directory Environment you can also use gpedit.msc before you image your golden.C:\Users\administrator\Documents\WindowsPowerShell\Modules C:\Program Files\WindowsPowerShell\Modules C:\Windows\system32\WindowsPowerShell\v1.0\Modules\ I also used powershell to add a taskbar layout and had to find painfully out that changes are not persistant. If you use Group Policy and your configuration includes taskbar and a partial Start layout, users can make changes to the taskbar and to tile groups not defined in the partial Start layout.
If you use Group Policy and your configuration includes taskbar and a full Start layout, users can only make changes to the taskbar. If you use Group Policy and your configuration only contains a taskbar layout, the default Windows tile layout will be applied and cannot be changed by users. To apply a taskbar configuration that allows users to make changes that will persist, apply your configuration by using Group Policy. If your configuration pins an app and the user then unpins that app, the user’s change will be overwritten the next time the configuration is applied. If you use a provisioning package or import-startlayout to configure the taskbar, your configuration will be reapplied each time the explorer.exe process restarts.