I’ve been diving a bit deeper into the Nano waters now that Windows Server 2016 is out the door. As I deployed a few servers I realized there was a potential long-term management issue. During the technical preview, Nano installations were recognized by their Tuva designation. But now, a Nano server is just another Windows Server 2016 installation. So how can I tell if a server is a Nano installation? Here’s the solution I came up with.
I’ve been in IT for a long time. It has been exciting to see how the industry has changed and how it as adapted to new technologies. Even so, I appreciate situations where sometimes the “old ways” are still the best ways. For example, we no longer really need the ancient lmhosts file to help resolve NETBIOS names to IP addresses. However, there may be a few cases where lmhosts solves a problem and then wouldn’t it be nice to manage it with PowerShell?
Recently a reader, Matt Penny, shared a tip in a comment on one of my articles. He had a short and simple PowerShell function that he used to insert ToDo commands into his Pester test scripts. Although you could easily use it for other PowerShell work. Of course, I am always on the look out for inspiration so I took Matt’s idea and overworked it.
I don’t know about you but I always have a PowerShell session open and find it easier to manage my day right from a prompt. I find ways to use PowerShell whenever I can. Recently I started a project to help me manage my work and of course I created it in PowerShell. I had been keeping daily to-do lists on paper with little tasks or reminders. I work from home and don’t have an assistant or anything so I am responsible for my own schedule. Sometimes I need a little help remembering what to work on next or what’s upcoming. so I created a PowerShell module called MyTasks.
I expect that most of you with enterprise wide antivirus installations probably have vendor tools for managing all of your clients. If so, don’t go away just yet. Even though I’m going to demonstrate how to get antivirus product status with PowerShell, the scripting techniques might still be useful. Or you might learn a bit more about WMI and the CIM cmdlets. Let me start with a simple command to get antivirus information from your local computer, assuming you are running PowerShell 3.0 or later.