At work this morning, I had to make a list of managed computers with 32-bit operating systems which were not checking into a console. In this article from ExtendOffice, they walked through the process of comparing two columns for duplicate data by using a formula in the third column.
Once I had the formula in place, I formatted the data as a table. Clicking the third column’s header provided the option to uncheck “Select All”, then scroll down and select (Blanks). The resulting view showed the items missing from my list.
Back in the 90’s and 00’s, using encrypted e-mail and 2FA to secure systems were stigmatized as something only hackers and paranoid people used.
Increasingly, encrypted e-mail and Two-Factor Authentication (2FA), also called Multi-Factor Authentication (MFA) by Microsoft, has become more common, and more necessary.
I would document the process to enable and use 2FA for Office 365, but there’s a problem: Microsoft is continuously updating O365, so the steps and setting names this month may not be the same when you read these words. Instead, I will link to Microsoft’s documentation (and hope they keep the URL’s the same).
The pages I feel are most useful are Documentation for Administrators to set up the system, and Documentation for End Users on what to expect and how to set their authentication method(s).
In practice, enabling 2FA is pretty straightforward, but the initial user experience can be bumpy. While documentation says Office 2016 does not require an app password, that’s not correct. The morning after I enabled this on my account, upon login I was prompted for credentials when opening both the Office 365 versions of Skype for Business and Outlook.
Back in 2016, Apple discontinued QuickTime for Windows computers. Here is their official page:
“QuickTime 7 for Windows is no longer supported by Apple.”
“If you no longer need QuickTime 7 on your PC, follow the instructions for uninstalling QuickTime 7 for Windows.”
I was installing Windows 7 on a Dell notebook today, and got an error that this computer, which had Win 7 before the hard drive crashed, could not be configured to install Windows 7. I found a Dell tech note that advised OOBE had to be manually executed and then all would be fine. Yeesh, Windows.
"Windows setup could not configure to run on this computer's hardware" error during Windows 7 or Windows 10 installation
- At the error screen, press Shift+F10 to open a command prompt.
- Type cd \ and press Enter.
- Type cd c:\windows\system32\oobe and press Enter.
- Type msoobe and press Enter. The installation process should now automatically continue.
- Remove the installation media and the system should finish the installation and boot into Windows.
- While on the screen where the error appears, press Shift+F10 to bring up the command prompt.
- Type CD C:\windows\system32\oobe and hit Enter.
- Type msoobe and hit Enter.
- You may then be prompted to create an account name and password, and set the time and date. Click Finish when done.
For SBS 2011 and Server 2008 R2, this Microsoft article has a fairly quick walk-through of the required steps.
To view and close open files
- Open the Server Manager
- In the Actions pane, click Manage Open Files
- To close a specific file, select the file and click Close Selected
- To close all files, click Close All
Need to have a computer log into a user account on Windows 10?
This page walks through the process. The TL;DR version is Start> Run> netplwiz (or control userpasswords2)
The process to disable the Action Center in Windows 10 requires a trip into the Local Policy Editor.
This page has a walkthrough on the process.
Need a program to launch upon logging into Windows?
The TL;DR version: Start> Run and type shell:startup
This page has a great walk-through of the process
This site has several interesting tools designed to improve working with ConnectWise Automate.
To fix Windows Update issues, Windows 8 and newer have the built-in DISM command. Windows 7 has a System Update Readiness tool that can be downloaded.
This page has information on both tools.