Desktop operating systems
In announcing a preview of its Microsoft Virtual Desktop Azure-based technology, MS sneakily offers another free Win7 life extension. Very interesting!
When S Win7 Cert Exams expire July 31 they signal that today's reigning Windows version is nearing the end of its lifecycle. With 900-plus million devices still running Win7, lots of change is at hand.
When one of my laptops balks at completing the update check for a current cumulative update, WUMT resolves update woes yet again for Windows 10.
MS Answers offers 1803 networking resolution for those seeking to make nodes or network resources visible or available using File Explorer and other tools.
Depending on the workload and applications in use Win10 Hyper-V VMs benefit from more VRAM (virtual RAM), easily allocated using the Hyper-V manager.
When the default Ctrl+Shift+F3 won't do it, try the Sysprep Audit Mode alternate key sequence instead: Ctrl+Fn+Shift+F3. Works for me!
After the 1803 upgrade monkey with LAN visibility for some nodes, NirSoft NetBScanner offers Win10 LAN insights to help get things running again. Good stuff!
I don't normally write much about the Insider Preview builds for this blog post. Practicing Enterprise admins have enough on their hands keeping up with current branch versions of the OS. But when ...
When I first saw the news, I was stunned. But on further analysis, AdDuplex-based Win10 uptake projections mostly bogus, reflecting an incomplete and off-kilter subset of the user base.
If you build conventional Win10 installation media, you'll find two Win10 Setup.exes offer differing capabilities. One is good to upgrades or repair an existing Win10 install, the other for ...
When I say Win10 NetBIOS names get weirder I mean two things: they are indeed case sensitive, and sometimes the actual defined case-correct name string won't resolve properly.
As I troubleshoot an inexplicable inability to remote into one of my office PCs, I figure out how to bring back PING in Win10 1803. In short, my recent spate of networking issues continue!
When the certificate warning shows up, I finally figure out why Windows machine names are case-sensitive in RDP. The machine name isn't case-sensitive, but the certificate name most certainly is!
By checking which commands work in PowerShell and which have PowerShell aliases, I compile an interesting set of Windows Command Line Reference observations.
Finally! A Microsoft Support note explicitly confirms what I've long suspected: Win10 DCOM 10016 errors are mostly benign. They occur by deliberate design, in fact.