Some Notes on the Machines

Here’s a tool. Run this once as administrator on the drive to check, wait 20 seconds and do it again, and if it says you’re good, you are.

http://files.thecybershadow.net/trimcheck/

The current one, official, is described here:

https://blog.resilio.com/official-linux-packages-for-sync-now-available/

This one’s new and comes recommended, I have not tested it yet:

https://www.pcloud.com/cloud-storage-pricing-plans.html

This is very interesting:

http://anydesk.com/

The automatic crawl scheduler in Windows Search Server sometimes fails; you can get far more positive and creative control with scripting. Here’s how.

First you’ll need the name of the “Search Service Application”. I found these under “Farm Search Administration” in the SharePoint site; the default/built-in is named “Search Service Application”, but on the server being worked there was a second custom one for production work, which for this document we will call “SSAXYZ”.

Now we need the “Content Sources” list. Here’s where we learn whether it’s working or not.

Next step is to create the scripts below. You may want all of them. A usually working location and filename is in each initial comment. If your server doesn’t have an E:, you will need to rewrite just a tad.

The way it works is, you set your scheduled task to run the CMD, and the CMD starts up the PowerShell. It is possible to have the scheduled task run the PowerShell directly, but it’s much harder to read that way. There are two pairs of scripts below, one pair for incremental crawls, and one for full. It is often recommendable to run the incremental daily and the full weekly, if available server horsepower (most of all RAID) is enough for the fileset(s) involved.

The PowerShell comes from here, it stops any crawling which may be going on (or stalled) and restarts the desired (full or incremental), for every Search Service Application. So if you have multiple SSA’s you may want to modify so that it only does what you want.

REM E:\Search Server Scripts\Initiate-Full-Crawl.cmd
C:\Windows\System32\WindowsPowerShell\v1.0\PowerShell.exe  " & ' E:\Search Server Scripts\\Initiate-Full-Crawl.ps1 ' "

# E:\Search Server Scripts\Initiate-Full-Crawl.ps1
Add-PSSnapin Microsoft.SharePoint.PowerShell -erroraction SilentlyContinue
Get-SPEnterpriseSearchCrawlContentSource -SearchApplication "SSAXYZ" | ForEach-Object {
    if ($_.CrawlStatus -ne "Idle")
    {
        Write-Host "Stopping currently running crawl for content source $($_.Name)..."
        $_.StopCrawl()
        do { Start-Sleep -Seconds 1 }
        while ($_.CrawlStatus -ne "Idle")
    }
    Write-Host "Starting full crawl for content source $($_.Name)..."
    $_.StartFullCrawl()
}

REM E:\Search Server Scripts\Initiate-Incremental-Crawl.cmd
C:\Windows\System32\WindowsPowerShell\v1.0\PowerShell.exe  " & ' E:\Search Server Scripts\\Initiate-Incremental-Crawl.ps1 ' "

# E:\Search Server Scripts\Initiate-Incremental-Crawl.ps1
Add-PSSnapin Microsoft.SharePoint.PowerShell -erroraction SilentlyContinue
Get-SPEnterpriseSearchCrawlContentSource -SearchApplication "SSAXYZ" | ForEach-Object {
    if ($_.CrawlStatus -ne "Idle")
    {
        Write-Host "Stopping currently running crawl for content source $($_.Name)..."
        $_.StopCrawl()        
        do { Start-Sleep -Seconds 1 }
        while ($_.CrawlStatus -ne "Idle")
    }
    Write-Host "Starting full crawl for content source $($_.Name)..."
    $_.StartIncrementalCrawl()
}

‘atop’ seems to have some extraordinary depth.

http://linux.die.net/man/1/atop

AutoComplete, in Outlook, has a maximum number of contacts by default. This is either 1,000 or 2,000, depending on version, and can be changed by registry entry. One of the symptoms which shows up, is AutoComplete showing email addresses only for some entries, and not names.

The fix is here:

https://support.microsoft.com/en-us/kb/2199226

If you were using Exchange 2013 or later with Outlook 2013 or later, it is thought that AutoComplete may repair itself once the maximum has been sufficiently set. If automatic repair doesn’t occur, you’ll have to manually remove AutoComplete items and recreate.

If you’re working remotely, you don’t want your connection to go down, so we need to do it all in one command. So:

netsh interface ip set address "Local Area Connection" static <PC-IP> <Subnet-Mask> <Default-Gateway> & netsh interface ip set dns name="Local Area Connection" static <Primary-DNS> primary & netsh interface ip add dns "Local Area Connection" <Secondary-DNS> index=2

Be sure not to include the <> characters when replacing!

First, set the primary DNS as a static primary, bypassing DHCP for DNS only:

netsh interface ip set dns name="Local Area Connection" static 8.8.8.8 primary

Then, add the secondary DNS:

netsh interface ip add dns name="Local Area Connection" 8.8.4.4 index=2

In the example above, 8.8.8.8 is being set as primary, and 8.8.4.4 as secondary; these are Google’s public DNS servers, quite useful in some circumstances. On many systems the names of the interfaces (above, “Local Area Connection”) will have to be changed, either to “Local Area Connection 2” or something more different for wireless; you can get the names using ‘ipconfig’ (they are prefixed with “Ethernet adapter”, take those two words off and you have it) or GUI.

Lots of options available for control in PowerShell, both per-user and across the enterprise:

http://o365info.com/manage-clutter-by-using-powershell-office-365/