General LAN networking fix for Windows
article #1143, updated 19 days ago

The Beard (alias Hunsinger the Mike) reported just now:

I may have just found a heck of a trick. If you run across PC’s who are getting spotty GPO adherence, and possibly unreliable network connection, as well as their network explorer folder in windows only shows a handful of the actual PC’s on the lan. Try this powershell command:

PS U:\> set-service -Name fdPHost -startuptype Automatic
PS U:\> Start-service -name fdPHost

The above fixed a very longstanding unpleasantry we had been working on, where Network Neighborhood would not show up and other items just would not work normally over a VPN. Oddly, it turns out that fdPHost is some sort of omnibus networking control service, set to Manual by default, but which lords it over several different sets of protocols.

It’s probably not to be enabled generally or lightly, there could be potential for major addition of network traffic, and security questions too. But on the other hand, it’s there, it’s normally Manual not disabled, and it fixed!

Mike later found a companion service, FDResPub, which reportedly is responsible for broadcasting the presence of network resources, by a Windows machine serving them to its LAN. Although it too is by default set to Manual, a reference gives its description as “Publishes your computer and resources attached to your computer so they can be discovered over the network. If this service is stopped, network resources will no longer be published and they will not be discovered by other computers on the network.” And it stops sometimes with no known reasons, even on domain controllers. So this one too, at least on real servers, is a help if kept set Automatic.

Categories:   Windows OS-Level Issues   

==============

Upgrade (make visible) Snapshots in a ReadyNAS, and Delete Them
article #1147, updated 19 days ago

When ReadyNAS firmware is upgraded, snapshots can become invisible, losing much space. To fix that:

  1. Turn on SSH, in System / Settings / Services.
  2. Using putty, SSH to root@nas , where “nas” is the IP of the NAS, using the admin password.
  3. Do this:
touch /.force_snapshots_upgrade
systemctl restart readynasd
  1. The GUI will report upgrade in progress. Wait for it.
  2. We have now fixed it so we can do things to the snapshots. Let’s make them visible in the filesystem. Browse to Shares, click on the share name (often Backup), click the gear icon on the right, and check Allow Snapshot Access, Apply and OK.
  3. We can now see them at \\NAS\Backup\snapshots. If we create a blank directory on the Windows server’s hard drive, say C:\B, and do the following, we will wipe all of the snapshots on that share and begin recovery of all of the space:
    ROBOCOPY C:\B \\NAS\Backup\snapshots /MIR /R:1 /W:1
    Full recovery of the space actually takes a bit more, there are automatic elements which initiate after the above is done, and also after the next step is done.
  4. Then we run a Balance operation which Netgear recommends. Browse to System, then Volumes, and then click the Gear icon inside the NAS object, and choose Balance. This will take a while, and more space will be recovered. A weekly Scrub and Balance are both recommended. Scrub actually takes longer.

References:

https://community.netgear.com/t5/Backing-up-to-your-ReadyNAS/Deleting-snapshots-over-SSH/td-p/1046740

https://kb.netgear.com/30068/ReadyNAS-OS-6-SSH-access-support-and-configuration-guides

Categories:   Miscellaneous   

==============

Tweaking for On-Prem Exchange
article #1146, updated 20 days ago

Great input:

https://technet.microsoft.com/en-us/library/dn879075%28v=exchg.150%29.aspx

Categories:   Exchange and Exchange Online   

==============

FSUTIL Tweaks for NTFS Performance and Reliability
article #1145, updated 20 days ago

FSUTIL is a general-purpose NTFS tweak tool. Here is a set of changes which appears to be helpful in general towards performance:

fsutil 8dot3name set 1
fsutil behavior set memoryusage 2
fsutil behavior set disablelastaccess 1
fsutil resource setavailable C:\
fsutil resource setlog shrink 10 C:\

In order:

  • Turns off 8dot3name creation. Does not invalidate existing 8dot3names.
  • Increases RAM cache devoted to NTFS.
  • Turns off “last access” timestamp storage for files. Disindicated for some older backup systems.
  • Makes the filesystem more focussed on “availability” and less on “consistency”.

And here are some which increase reliability:

fsutil repair set C: 0x01
fsutil resource setautoreset true C:\
fsutil resource setconsistent C:\

In order again:

  • Turns autorepair on for C: drive.
  • Cleans transactional metadata on next mount
  • Makes the filesystem more focussed on “consistency” and less on “availability”.

Do be aware that “resource setavailable” and “resource setconsistent” are opposites, both do not get set at the same time :-) Also neither of them appear to be valid on system volumes, errors are thrown.

Here is one set which seems to balance reliability and performance boost:

fsutil 8dot3name set 1
fsutil behavior set memoryusage 2
fsutil behavior set disablelastaccess 1
fsutil repair set C: 0x01
fsutil resource setautoreset true C:\
fsutil resource setconsistent C:\
fsutil resource setlog shrink 10 C:\

Categories:   NTFS   Windows OS-Level Issues

==============

Strip 8dot3 / 8.3 Filenames from a Running Windows for Performance
article #1144, updated 20 days ago

Very interesting, not tested by this writer yet; appears to be able to handle registry to some extent. One can turn off creation of new 8.3 filenames, and one can also strip existing 8.3 filenames from a filesystem and from the registry:

https://ss64.com/nt/fsutil.html

Categories:   Performance   

==============

Download OneDrive for Business
article #1142, updated 25 days ago

Right here:

https://onedrive.live.com/about/en-us/download/

Categories:   Web Sites   

==============

A web tool to test DKIM
article #1141, updated 25 days ago

Here is one:

http://www.appmaildev.com/en/dkim

Categories:   Email   

==============

Convert many sorts of files
article #1140, updated 26 days ago

This one is great:

https://www.zamzar.com

Categories:   Tools   

==============

CATE: (C)lean (A)ll system and user profile (T)emp folders, (E)tcetera
article #484, updated 28 days ago

For quite a while I had been curious as to why a simple method to do this was not available. CCLEANER and others do not reach into every user profile, and on many machines this is crucial, e.g., terminal servers. CATE was originated as a .VBS by the excellent David Barrett ( http://www.cedit.biz ) and has been rewritten thoroughly by yours truly (JEB of Ponderworthy). The current VBS is here.
The most recent version is a PowerShell script, which adds removal of Ask Partner Network folders from user profiles, and a good bit of speed and clean running. Future development will be in PowerShell, as part of the ponderworthy-tools set.

One thing discovered along the way, is even in XP there was a user profile called the “System Profile” — XP had it in C:\WINDOWS\System32\config\systemprofile — and some malware dumps junk into it, and sometimes many gigs of unwanted files can be found in its temporary storage. CATE cleans all user profiles including those, as well as the Windows Error Reporting cache, and the .NET caches, and the system TEMP folders, and in recent versions, many Windows log files which are often found in many thousands of fragments.

The tool is designed for Windows 10 down through XP. As of 2017-10-10, it is self-elevating if run non-administratively.

It is licensed as follows:

The 3-Clause BSD License

SPDX short identifier: BSD-3-Clause

Note: This license has also been called the “New BSD License” or “Modified BSD License”. See also the 2-clause BSD License.

Copyright 2017 Jonathan E. Brickman

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

3. Neither the name of the copyright holder nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Categories:   Cleanup   

==============

Optimize Service Work Items and Additional/Delayed Worker Threads
article #1084, updated 28 days ago

OWTAS sets a number of additional critical and delayed worker threads, plus service work items. The changes are autocalculated according to a combination of RAM and OS bit-width (32 vs. 64). Performance will increase, more so with more RAM. Available as VBS and as PowerShell 3 and up. Future development will be in PowerShell, as part of the ponderworthy-tools set.

The tool is designed for Windows 10 down through XP. As of 2017-10-10, it is self-elevating if run non-administratively.

Categories:   Windows OS-Level Issues