This has been happening on long-installed machines for quite a while. But in the last week, four different sets of Windows 7 64-bit install media, over seven different reloads, have had Windows Update get stuck, or freeze, while searching for Windows updates, eating 100% of one CPU core. Several changes in reload pattern were attempted, some of which included WSUSoffline, without success. Profoundly expert help provided the following. Before deliberately attempting Windows Update, we are to install these, in this order:
- Servicing stack update for Windows 7 SP1 and Windows Server 2008 R2 SP1: September 20, 2016:
- July 2016 update rollup for Windows 7 SP1 and Windows Server 2008 R2 SP1:
- September 2016 update rollup for Windows 7 SP1 and Windows Server 2008 R2 SP1:
Windows Update may get stuck again, searching for new updates, the first time any of the above is attempted. If this occurs, each time, we do this:
- In TASKMGR, terminate process
- Restart service
- Try the install again.
The second time we do each install (after the termination and service restart), the popup for searching for Windows updates comes up for 3-10 seconds, and then we are asked whether we want to install. We then say yes, and it installs. Then we move to the next one of the three!
Google is a good place to start:
OpenDNS is often good too:
And one new to us, is Level 3. Level 3 provides DNS to most ISPs in the U.S.A., and does provide geo-routing for speed and compatibility.
Increasingly, nslookup is not installed by default in major Linux distros. On Arch-based and Debian-based distros, it’s in package dnsutils,
Here are settings useful to maximize performance of a hardware network interface. Virtual guests benefit by these being applied to their virtual host, only. Not all of these exist on every NIC. There are also many settings which should not be touched, or should be touched only when the toucher knows what they are doing! The below have always helped when this writer has found them available to try. Do be warned, the NIC will go offline for 2-10 seconds after you Apply most of these.
- Install the most current drivers for NICs and also motherboard chipset. In at least one case, the server vendor had only an outdated and unreliable driver available for download, the one which worked well for years came from Intel’s web site.
- “DMA Coalescing” on.
- “Enable PME” off.
- “Energy Efficient Ethernet” off.
- “Green Ethernet” off.
- “Gigabit Lite” off.
- “Adaptive Inter-Frame Spacing” on.
- All offloading on.
- “Interrupt Moderation” on.
- “Interrupt Moderation Rate” should be “Adaptive”.
- “Scaling”, should be “on” or “Enabled”.
- “Receive Side Scaling” on.
- “Receive Side Scaling Queues” to maximum.
- There are cache settings on all server-class NICs, separate for send and receive. They are usually called “Receive Buffers” and “Transmit Buffers”, or “Receive Descriptors” and “Transmit Descriptors”. Set them to the maximum. For current Intel server NICs the defaults are usually 256 or 512, and the maximums are 2048; for a few other kinds, one or the other is 5000 or more; for others it is much less. Each descriptor takes 2K of RAM, which in today’s multigigabyte world is well worthwhile. Some older Broadcom gigabit NICs will yellow-flag if they are set to 2048; for these, set receive to 750, transmit to 1500.
- In the NIC’s “Power Management” tab, turn everything off. This may have to be abridged if Wake-On-LAN is used. Some NICs, notably some Realtek, will automatically turn power management back on at boot; this needs to be fixed through group policy.
- In SBS 2008, only one NIC (or one NIC team) is permitted to represent the server on the network. If there are two active NICs, you will have to turn one off, or crashes and unpredictable behavior will result sooner or later.
Cleaning up VSS, can improve server performance a whole lot. Start an administrative CMD, and then…
vssadmin delete shadows /all
If there are orphan shadows, you will be asked whether you want to delete them. If there are and you delete them, you will see immediate performance benefit. Reportedly, Windows autodeletes them only after there are 64 per volume. We prefer to see zero!
vssadmin Add ShadowStorage /For=C: /On=C: /MaxSize=20%
Do the above for C: and any other drives local to the server, provided you have the disk space (30% free or more probably). If you don’t have the disk space on one volume, you can use the /On parameter to place the preallocated space for that one, on another volume. This does not reserve the space, it just preallocates it, makes it ready for use, so that whenever Windows wants to do any of the bajillions of things it does with VSS, things ranging from tiny to enormous, it can skip that step. On some servers, this will increase performance very impressively, immediately. In general it keeps them smooth and stable and prevents hesitations.
More info here:
When this happens to OWA, do this in Exchange PowerShell:
Remove-OwaVirtualDirectory "EXCHANGESERVERNAME\owa (default web site)"
This came from here:
VirtualBox, portable, on Windows. Amazing.
Adobe is supporting Flash less and less on Linux. Google Chrome was the way to do it for a while, but then Google abandoned 32-bit platforms, and there are a lot of 32-bit users who want full Flash web-site compatibility. There still is 32-bit Flash code out there, but making it work can still be very confusing on many Linux platforms. Happily, as is the wonderful modus operandi in the Linux world, an enquiring mind figured it out, and gave us a way. It’s here:
A quick way to apply it, is to run these commands in order:
chmod +x latest-pepper-flash.sh
Flash does not show up as an Extension, but it appears to work very well, you can verify it on Adobe’s check page.
As of “Wave 15” of Office 365, there is enterprise-wide, a.k.a. global, automatic signature capability. It’s in Exchange -> mail flow -> rules, and it involves setting a disclaimer message, but there is extensive user-data variable substitution. A full description is here: