Some Notes on the Machines

This is “Cornell Chicken Barbecue Sauce”, created in 1950 by Robert C. Baker in order to encourage certain kinds of agriculture, especially that of chicken. The sauce remains extremely popular in certain places. And it has no added sugar, unlike every BBQ sauce this writer has ever seen in many supermarkets.

1 cup cooking oil
1 pint cider vinegar
3 tablespoons salt
1 tablespoon poultry seasoning
1/2 teaspoon pepper
1 egg

Beat the egg, then add the oil and beat again. Add other ingredients and stir. The recipe can be varied to suit individual tastes. Leftover sauce can be stored in a glass jar in a refrigerator for several weeks.

There are multiple ways to set printers up by group policy in Windows. There is a printer administration role which can make things easier or harder, depending on how well everything is working. The simplest way, is to open the Group Policy Management Console from a domain controller, open up an appropriate policy, and open it to here:

then right-click in the white box, you’ll get a menu, choose “New”, choose “Shared Printer”, Action should be “Update” or “Replace” if “Update” doesn’t work, and you’ll choose the printer by “Share Path”. You can leave everything else alone unless you need something special. Sometimes it works better to do a Delete and then Create for each printer. The vagueness here is due to unknown but widely experienced vagaries in behavior of Group Policy which are addressed in no known documentation.

Please do note that we set these up under “User Configuration” not “Computer Configuration”. It is possible to do it under Computer, but removals can be far more difficult if we do, there have been messes seen.

This tool appears to be made for this, among several other things:

https://www.bitvise.com/tunnelier

Some firsthand reports:

https://superuser.com/questions/235395/automatic-ssh-tunneling-from-windows

There are a few others options on that page also.

1. Turn on.
2. Move mouse and press buttons until done.
3. Turn off.

These are not very documented, and at least at this writing, the informatives in the console were incomplete. Here’s the steps I have working at this writing, postulating the domain at hand being “emaildomain.com”:

1. First, in the O365 Exchange administrative console, go to the Protection area, and the rightmost tab is “dkim”, click on that. Then try to Enable any which are disabled. You will see an error message which says you need to create two CNAMEs. The two strings given, are the alias targets, the alias names are not given. Use these in the next step.

2. Set CNAMEs in Internet DNS. The alias names are the same every time; the targets are taken from the error message in step 1. They are not always entirely predictable, sometimes you will see “0i” buried within and there may be other variations. But the result will not be very distant from this:

selector1._domainkey.emaildomain.com
CNAME to
selector1-emaildomain-com._domainkey.emaildomain.onmicrosoft.com.
TTL 3600

selector2._domainkey.emaildomain.com
CNAME to
selector2-emaildomain-com._domainkey.emaildomain.onmicrosoft.com.
TTL 3600

3. Once your DNS changes have propagated thoroughly, go back to step #1 and try to enable DKIM again for the domain whose records you have just changed. If you have done your CNAMEs correctly, O365 will turn DKIM on. You may need to wait for DNS propagation.

From the indefatigable Matt Quick:

Sometimes, trying to install .NET 3.5 either via Add/Remove Programs or via the standalone offline installer produces an error code. This is due to WSUS not having the files for .NET 3.5. Use the following workaround to avoid taking the machine off the domain, installing .NET 3.5, then putting it back on the domain:

This worked for me. Windows has to download the 3.5 installation files, but the server is configured not to use Windows Update (common for managed servers), but WSUS. The above article describes how to fix this. In a nutshell:

1. Start the Local Group Policy Editor or Group Policy Management Console.
2. Expand Computer Configuration, expand Administrative Templates, and then select System.
3. Open the Specify settings for optional component installation and component repairGroup Policy setting, and then select Enabled.
4. Select the Contact Windows Update directly to download repair content instead of Windows Server Update Services (WSUS) check box.

Make sure Windows Updates Service is set to Manual or Automatic to apply this fix.

A great place for general DNS lookup info:

http://www.dnsstuff.com/

The best WHOIS:

https://whois.icann.org/en

And one for info about IP addresses:

http://www.arin.net/index.shtml

This is a very long list, the most complete list I’ve seen:

https://www.howto-outlook.com/howto/commandlineswitches.htm

Lots of possibilities for cleanup and fixup.

Try this:

https://www.7digital.com/

There is a way:

https://autohotkey.com/docs/commands/Run.htm#RunAs

http://www.kellestine.com/self-elevate-vbscript/