OK. Here is how I deployed the AlwaysOn VPN in device tunnel (rather than user tunnel) using PowerShell. Continue on for the steps...

If you're like me, you've run into the following set of errors when trying to use CMake on Windows and especially when trying to compile Python code:

-- Building for: NMake Makefiles
-- The CXX compiler identification is unknown
-- The C compiler identification is unknown
CMake Error at CMakeLists.txt:131 (project):
  The CMAKE_CXX_COMPILER:

    cl

  is not a full path and was not found in the PATH.

  To use the NMake generator with Visual C++, cmake must be run from a shell
  that can use the compiler cl from the command line.  This environment is
  unable to invoke the cl compiler.  To fix this problem, run cmake from the
  Visual Studio Command Prompt (vcvarsall.bat).

  Tell CMake where to find the compiler by setting either the environment
  variable "CXX" or the CMake cache entry CMAKE_CXX_COMPILER to the full path
  to the compiler, or to the compiler name if it is in the PATH.

CMake Error at CMakeLists.txt:131 (project):
  The CMAKE_C_COMPILER:

    cl

  is not a full path and was not found in the PATH.

  To use the NMake generator with Visual C++, cmake must be run from a shell
  that can use the compiler cl from the command line.  This environment is
  unable to invoke the cl compiler.  To fix this problem, run cmake from the
  Visual Studio Command Prompt (vcvarsall.bat).

  Tell CMake where to find the compiler by setting either the environment
  variable "CC" or the CMake cache entry CMAKE_C_COMPILER to the full path to
  the compiler, or to the compiler name if it is in the PATH.

Read on for instructions on how to get past this error...

Once in a while, when using the built-in VPN client in Windows 10, we would be able to begin to connect and actually authenticate, but not complete the connection. We would have an error similar to the following in the Application Event Log:

Even rebooting alone wouldn't fix the issue. But, the fix for us was easy. We only needed to delete and have windows recreate some items in the Device Manager. Try the following:

1. Open Windows Device Manager
2. Navigate to Network adapters
3. Uninstall all of the WAN Miniport (XXXX) devices
   • Or at least the one related to your VPN connection
4. Right-click on any item and choose to Scan for hardware changes
5. The WAN Miniport adapters should have re-created themselves.
6. Try connecting to your VPN again.

That seems to clear out the necessary bit of whatever the VPN service was hung up on.

If you've been having issues with your Windows 10 machines not connecting for a minute or even at all after a boot or reboot, you may have been hit with a bug that has affected Windows 10 since version 1709 rolled out. Even if you have a network SSID set to "Connect Automatically," Windows would not connect reliably after a cold boot. This would affect users using pre-shared keys and also 802.1x policies (for example using RADIUS or Windows NPS Server) and all flavors of Windows including Home, Professional, Enterprise, & Education editions.

One way to fix this is by disabling the "Microsoft Wi-Fi Direct Virtual Adapter" in Device Manager, but this came with some side-effects such as disabling the ability to wirelessly project through Miracast (also Intel's WiDi). Those who couldn't or didn't want to do that have had limited success making the issue less likely to occur by disabling the "EnableActiveProbing" registry parameter and/or using Group Policy to enable the "Turn off Windows Network Connectivity Status Indicator Active Tests" & "Do Not Show the Local Access Only Network Icon" policies.

Fortunately, Microsoft has just released a cumulative patch for Windows 10 1803 that seems to have fixed the Wi-Fi issue introduced with the 1709 feature upgrade. It is the October 24, 2018—KB4462933 (OS Build 17134.376) update. Microsoft also recently released an update for Windows 10 1709, but we have not yet tested to see if it fixes this issue. As for the recently released Windows 10 1809, we do not recommend upgraded to that feature update quite yet due to the major issues that still need to be resolved.

Please comment below and let us know if you have had success with the KB4462933 update!

Did you know that you can, with one easy PowerShell command, extract all 3rd-party Windows drivers from a computer to a folder? It uses the DISM module and is built into newer versions of Windows.

1. Create a folder location that you want to save the driver files to. In the example we will use C:\Drivers
2. Open PowerShell elevated (as Admin)
   • Tip 1: Right-click on the Start Menu Button and click "Windows PowerShell (Admin)"
   • Tip 2: Or do it all with your keyboard >> Press Windows Key + X and then press the A key
3. Type the following command:  Export-WindowsDriver -Online -Destination C:\Drivers | Out-File -FilePath C:\Drivers\Drivers.txt
4. Wait a minute and now you have a folder of all your current drivers backed up or to use for deployment

All the details and switches for this are available from Microsoft's PowerShell Documentation at https://docs.microsoft.com/en-us/powershell/module/dism/export-windowsdriver

In Windows Update, when you haven't installed patches for a little while, you will receive a notification in the system tray and also in Windows Update Settings that says "Your device is missing important security and quality fixes." In some cases, your computer might say this message, but when you check for updates from Microsoft servers, it says there are none available.

The possible solution is that your computer is only checking for Windows updates and not for updates to programs such as Microsoft Office. Even if you are up-to-date on updates for Windows itself, the message will still appear if you are behind on Office updates, etc.

To change the setting, go to Start > Settings > Update & Security and click the Advanced options link. Make sure "Give me updates for other Microsoft products when I update Windows" is turned On. After you do that, go back and recheck for updates. Once installed, the warning message should be gone.

The thing about Windows Update services (WU or WUS) is that so many things can go wrong. Microsoft provides a Windows Update Troubleshooter that you may want to try before messing around with items manually, but we've found it rarely solves issues when Windows Update is acting up.

First off, look in the Application event log for events with Event ID 1001 and the "Information" level. The Event Name for WU issues is "WindowsUpdateFailure3" and typically paired with a fault bucket of type 5. In the problem signature, look for the code in the P2 line (such as 80246008 or 800706d9). Those are the codes you will want to include in your Web searches to see if you can find the exact cause of your issue.

If that fails to provide you a solution or you just want to reset Windows Update without having to troubleshoot too much, we've found that the following general steps fix ~90% of Windows Update errors. This should work in Windows 7, 8, 8.1, 10 and most flavors of Windows Server.

Continue on for the steps and some great tips...

If your Veeam backups are failing with the following or similar errors:

It lis likely that there is something messed up with the SQL Server. Even if you didn't install SQL, some programs use an instance of Microsoft SQL Express LocalDB. You will also see errors in the Application Event log such as:

Continue on for the simple solution...

Trying to log into an Apple ID, I was met with the request to answer a couple security questions. Of course, I document and encrypt not only my login information when I create accounts, but all the relevant information such as account numbers, email address on file, and... security questions. I had 5 security questions and answers written down for this account, but one of the questions that I was asked was not in my list. Okay. That's weird. I can't log in Apple. Thanks.

But, thinking about it perhaps I made a mistake in documenting or clicked the wrong dropdown. So, I try a couple of my other answers to different questions for my "First Pet". After two failed attempts I decided I didn't want to lock myself out. I clicked the button to reset security questions and they prompt me with an option to... answer security questions. I was intrigued at how this would work, so I clicked it. From there I was prompted with... a SINGLE security question. I answered that one and then it allowed me to choose three new security questions and answers for the account.

So, Apple ID people: Why do I need TWO security questions answered correctly to log in, but only ONE security question answered correctly to reset my security questions?

And so, I think either Apple or I were havening problems.

Update (2017-06-27): We release a patched version (1.5.4) that implements a couple other minor updates and changes.

We've finally released the next version of Screensaver Operations.

Screensaver Operations is an application for Microsoft Windows systems that allows you to perform configurable actions after a computer has been left idle for a specified amount of time (e.g., log off, shut down, run a process).

Download Screensaver Operations 1.5

There are a lot of new bug fixes and a couple features in the latest release:

• Bug/Security Fixes
  • Fixed issue where when enabling RunProcessEnabled, the default title and message texts were incorrect.
  • [Window XP & Windows Server 2003 Only] When using the RunProcessEnabled flag, older versions of Windows (XP, 2003) close the process when the screensaver ends. This is due to multiple factors. Windows XP, etc. closes child processes along with the screensaver. It also puts the screensaver in a separate Virtual Desktop and kills all processes in that desktop when the screensaver ends! We have implemented a workaround and running a process in older versions of Windows should work. This issues took many days to fix so we are glad that we got it to work!
  • Changed action button on process run to "Start Now" rather than "Start Process Now" (which was cut off as it only showed "Start Process").
  • Opens "Configure" properly from right-click context menu on SCR file.
  • Fixed some issues with double-quotes in process path or process argument.
  • Fixed issue where sometimes the Keyboard Filter "DisableSpecialKeys" would crash the program when a special key (e.g., the Windows key) was pressed.
• New Features
  • Added: BackgroundOpacity registry value - Setting allows you to modify background opacity from the default of 75%. Some organizations might want to completely hide content. Note that this setting is not yet available from the Configuration GUI and can only be set via registry and ADMX. (Note: In Windows 8 and newer, Windows always shows an opaque background color as a security feature)
  • Added: A "Snow" Easter Egg. See the README for more information. :-)