Category Archives: Tech Tips

What Is ?

The domain is owned and operated by Google.  This domain is used by programs to talk to Google services.

Subdomains – This is the service that hosts Google Cloud Storage. – This was the previous name for accessing Google Cloud Storage. – Google Maps. – TBC

SharePoint 2010 – Usage Files Are Not Deleted And may Cause Timer Service Problems

The .usage logs are never deleted. There should typically be no more than 6 .usage files at any given time, but when you have this problem, you may find hundreds or thousands of usage logs in the logging directory.

You’ll see errors like this in the SharePoint ULS logs when the Usage Import timer job runs:

OWSTIMER.EXE (0x51A0) 0x59E4 SharePoint Foundation Usage Infrastructure a5rv High Failed to delete usage log file‘E:\Logs\ServerName-20130701-2117.usage’ after data import. Exception: System.IO.IOException: The process cannot access the file because it is being used by another process. at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.FileInfo.MoveTo(String destFileName) at Microsoft.SharePoint.Administration.SPProvisioningAssistant.MoveFileOrDirectory(FileSystemInfo fi, String newPath) at Microsoft.SharePoint.Administration.SPProvisioningAssistant.DeleteFileOrDirectory(FileSystemInfo fi) at Microsoft.SharePoint.Administration.SPUsageLogImporter.ImportUsageLogFiles(List`1 usageLogFileList)

Other symptoms include:
• Missing or incomplete Web Analytics data
• The “Microsoft SharePoint Foundation Usage Data Import” timer job never completes.
• The “Timer Service Recycle” timer job is never able to actually restart the timer service. It tries to pause the Usage Data Import job and cannot, so after ten minutes it skips the recycle.
• Memory bloat (leak) within owstimer.exe. You may see the timer service consume much more memory than normal. Restarting the timer service will bring it back to normal, but it will build up again over time.
• The “Diagnostic Data Provider: Trace Log” timer job intermittently does not import the ULS log data into the Logging database.


This happens when Windows updates KB2775511 or KB2682011 or KB2882822 are applied to the SharePoint servers.


The fix is in the December 2013 Cumulative Update for SharePoint 2010.  

If you look at the description for the Foundation package (which is included in the SharePoint server package) here:, you will see this description for one of the issues that are fixed:

“After you install hotfix 2775511 or hotfix 2682011 on a SharePoint Server 2010 server, the Usage Provider (.usage) files are not deleted from the file system. Additionally, the .usage files keep growing.”

This is a somewhat generic summarization of the problem that does not include all the known symptoms, but it does fix the issues described in this KB.

Here is the link to the KB and download:

How To Enable HD Video And Photo Uploads On Facebook [Mobile App]

Here we will show you how to enable HD video and photo uploads via the Facebook mobile app.  We have found by default HD is not turned on.  Here is how to enable this.

Press the menu button Image result for menu button

Scroll down and select “App Settings”

    Turn on “Upload photos in HD” and “Upload vidoes in HD” by default this is off.


    You can now upload photo’s and video in HD.

Image result for facebook

Sophos UTM 9.506 For AWS – Release Notes

Sophos has just released Sophos UTM 9.506 on AWS. They have added several new features specifically designed for customers in AWS. With this release, they have introduced the usage of an AWS Profile for deploying OGW, a new update page in WebAdmin, the reduction of permissions needed for Auto Scaling deployments, and included InSpec for checking the health state of a UTM instance. In addition to that, the failover time for the High Availability deployments has been significantly improved.

AWS Profile for OGW

To increase flexibility when it comes to permissions and roles used by the UTM on AWS Auto Scaling deployment, they have introduced the possibility to attach an AWS Profile to deploy and monitor the Outbound Gateway. This makes it possible for customers to establish privilege separation in their OGW installations. Please see the knowledge base article How to create an AWS profile for automatically deployed OGWs for further details.

Customers already using OGW will also need to follow the KBA to create a new profile and attach it to their existing OGW configuration. Without the profile the OGWs still work as expected and are listed in the WebAdmin, but managing them won’t be possible any longer.

New update page in WebAdmin

Sophos have restructured the update page in WebAdmin for the High Availability and Auto Scaling customers. They have learned that most of the customers use modified templates to deploy UTM on AWS products. In order to avoid overwriting of their modified templates, they have removed the automated update but added helpful details to the page to ease the process.

The page now shows the AMI ID, a link to the release notes as well as the option to directly navigate to the current stack in the AWS Management Console. In addition to that, links to the most recent template for the deployment type and the changelog are provided.

If no update is available, the WebAdmin page shows information about the current version as well as the details stated above.

Reduced permissions needed for Auto Scaling deployments

Sophos have listened to the customers who were stating that the permissions needed for the Auto Scaling deployment are too broad and potentially aggressive. Thus, they have further reduced the permissions needed for the Auto Scaling deployments in order to align with the principle of least privilege. Please see the changelog and the updated documentation of the permissions on GitHub for more details.

InSpec on UTM on AWS

In order to make it possible for the customers to verify that the UTM on AWS works as expected, they have introduced InSpec on the UTM on AWS. InSpec is an audit and test framework developed by Chef.

InSpec will be used to check whether:

  • S3 resources are available and accessible.
  • System services are running.
  • Important ports are accessible.
  • PostgreSQL databases exist and contain the correct schema.
  • System configuration files exist.
  • Log files do not contain any severe errors.

The knowledge base article How to use InSpec on the UTM on AWS covers the usage of InSpec as well as how to write custom profiles to extend the solution.

Faster failover for High Availability

Customers relying on our High Availability deployment will now see a reduced failover time resulting in lower downtime.

Disable backend pooling for the WAF on Auto Scaling

Sophos have disabled the backend pooling for the Web Application Firewall for the Auto Scaling deployment now by default. This supports scenarios where load balancers with quickly changing DNS entries reside behind the UTM on AWS.

Included issues

NUTM-8039 [AWS]               Conversion after updating to 9.501 was not possible
NUTM-7148 [AWS]              Conversion fails due to AWS rate limit exceeded
NUTM-7199 [AWS]     logs to own log file
NUTM-7741 [AWS]              Removing password from user data
NUTM-7891 [AWS]              awslogsd.log is being flooded with log messages
NUTM-7896 [AWS]              Better Messaging for Conversion Utility
NUTM-7979 [AWS]              Renaming of “Conversion” to “Conversion Utility”
NUTM-7995 [AWS]              Decreased failover time for HA
NUTM-8041 [AWS]              Restore overwrites applied license from license pooling
NUTM-8233 [AWS]              AWS Profile settings for CloudWatch are overwritten after update
NUTM-8388 [AWS]              Inspec on UTM on AWS
NUTM-8438 [AWS]              CloudFormation input can harm basic setup
NUTM-8626 [AWS]              New update mechanism and page in WebAdmin
NUTM-8874 [AWS]              dns-resolver stopped working after updating to 9.503 on AWS
NUTM-7608 [AWS]              Reduction of IAM permissions for Auto Scaling deployments
NUTM-8141 [AWS]              Disable backend pooling by default within the WAF on Auto Scaling
NUTM-8207 [AWS]              WAF statistics are inaccurate in Auto Scaling deployment
NUTM-8518 [AWS]              aws_resource_management is sometimes killed due to timing issue
NUTM-8785 [AWS]              Authorization token for OGW stated in the template is not validated
NUTM-8793 [AWS]              aws_egw_stack.log is not uploaded to cloudwatch
NUTM-9043 [AWS]              Backupd was not started

Sophos UTM 9.506 also includes bug fixes of the following general releases:

You can update to UTM 9.506 by running up2date for UTM Standalone or by updating your CloudFormation stacks for High Availability and Auto Scaling deployments. Let us know what you think about our new release by posting to our user community forums.

How To Spot A Fake USB Charger

You don’t need to be an electronics expert to spot the difference between a genuine and fake USB charger.  This guide will tell you everything you need to know.

Plug Pin Finish

This can be another fairly obvious indicator of a fake. The finish on a genuine charger is high quality, matte and uniform. On counterfeit chargers the finish maybe glossy or shiny with imperfections.

USB Port

The USB port on a counterfeit charger might be upside down, or in a different place. A genuine charger may also have a serial number.


Testing has shown that the pins on counterfeit plugs are much weaker than required by the standard. This is typically because they are metal-coated hollow plastic, rather than the solid metal used in genuine products. An easy check for this is to simply flick the largest pin and listen to the noise it makes. A genuine plug will sound and feel solid, while counterfeit products will make a ‘plastic’ noise and feel hollow.


Counterfeit chargers contain few, if any, of the higher quality components required for safety, they are usually significantly lighter than genuine chargers.

Plug Fit

Do not connect up to your phone etc just yet.  Does it plug in easily? If the charger does not easily plug into a socket, the pins may be the wrong size or length, or the distance between the pins may be wrong. If pins do not fit properly into the socket, overheating, arcing and mechanical damage can occur to both the socket and the charger, which can be dangerous.


Look for a manufacturer’s brand name or logo, model and batch number.

Check for a CE mark.  But do not rely on a CE mark alone as a guarantee of safety – it’s simply a declaration by the manufacturer that the product meets all the safety requirements of European law, but they can be easily forged.

Check that the output voltage and current ratings marked on the charger and your electrical device are the same.

Warnings and Instructions

Adequate warnings and instructions must be provided. As a minimum, user instructions should provide information on conditions and limitations of use, how to operate the charger safely, basic electrical safety guidance and details of how to safely dispose of the charger when it is no longer required.

Useful Information

Apple has produced this document that will help you identify fake apple products.

Dont -kill -your -phone -v2

The above image and some information in this page has been taken from

Sophos UTM Up2Date 9.506 Released

Sophos have released Sophos UTM 9.506. The release will be rolled out in phases. In phase 1 you can download the update package via their FTP server, in phase 2 itwill spread via the Up2Date servers.


  • System will be rebooted
  • Connected APs will perform firmware upgrade
  • Connected REDs will perform firmware upgrade


  • NUTM-8651 [AWS] AWS Permission for “Import Via Amazon Credentials”
  • NUTM-7678 [Access & Identity] Pluto dies with coredump at L2TP connections
  • NUTM-8211 [Access & Identity] SSL VPN connection issue with prefetched AD groups
  • NUTM-8756 [Access & Identity] AUA debug log contains plain text passwords
  • NUTM-8889 [Access & Identity] ESPdump with algorithm GCM does not work
  • NUTM-8912 [Access & Identity] HTML5 VPN: keyboard input not working on Android devices
  • NUTM-7670 [Basesystem] Update to BIND 9.10.6
  • NUTM-8427 [Basesystem] postgres[xxxxx]: [x-x] FATAL:  could not create shared memory segment: No space left on device
  • NUTM-8769 [Basesystem] Small models of  SG105 / SG115 / SG125 / SG135 take over 5 minutes to accept network connection
  • NUTM-9063 [Configuration Management] Regenerating the Web Proxy CA breaks all SSL VPN clients
  • NUTM-8313 [Email] POP3 Proxy generate core dumps in versions v9.414 and v9.501
  • NUTM-8509 [Email] Remove 3DES and SHA1 from SMIME
  • NUTM-8645 [Email] MIME Type Detection 9.5
  • NUTM-9061 [Email] User cannot open the SMTP Routing tab
  • NUTM-8419 [Logging] “Search Log Files” has different search result in spite of same time frame
  • NUTM-8783 [Logging] SMBv1 still required for remote logging to a smb share
  • NUTM-8341 [Network] Network monitor core dump
  • NUTM-8685 [Network] Some clients display an “Unknown” vendor on the wireless client list
  • NUTM-8738 [Network] Error messages in fallback log about damaged static routes
  • NUTM-8838 [Network] Watchdog consumes constantly 100% CPU
  • NUTM-7396 [RED] UTM RED kernel log shows “seq invalid” messages
  • NUTM-6968 [REST API] Insert REFs of new objects into single REF node
  • NUTM-7981 [Reporting] WAF-reporter logs irrelevant information
  • NUTM-8359 [Reporting] SMTP log on Mail Manager is empty after upgrading postgres to 64bit
  • NUTM-7802 [Sandboxd] If using a ‘ character in the email address, postgres is not able to insert this to the TransactionLog (Sandbox)
  • NUTM-8715 [UI Framework] Unable to access “Manage Computers” page
  • NUTM-8061 [WAF] WAF still reporting virus found when AV engine on the UTM is updating
  • NUTM-8751 [WAF] Newly created web server listens on the slave node instead of the master node
  • NUTM-8806 [WAF] Issue with TLS settings for virtual webserver
  • NUTM-8861 [WAF] Leftover of shm files cause a WAF restart loop
  • NUTM-5964 [WebAdmin] Support Access: WebAdmin not properly displayed after login via APU
  • NUTM-8512 [WebAdmin] Can’t use string (“0”) as a HASH ref while “strict refs” in use at /wfe/asg/modules/asg_ca.pmline 1105
  • NUTM-8571 [WebAdmin] User with only “Report Auditor” rights receives strict refs error after login into WebAdmin
  • NUTM-8807 [WebAdmin] External link to Sophos UTM Knowledge Base is not correct
  • NUTM-8871 [WebAdmin] Year of Single Time Events cannot be later than 2019
  • NUTM-7994 [Web] Customized templates do not allow to accept quota and access site
  • NUTM-8037 [Web] HA: Low disk space alert from slave
  • NUTM-8107 [Web] CONFD.PLX is taking high CPU load
  • NUTM-8502 [Web] HTTP Proxy coredumps with CentralFreeList in v9.413
  • NUTM-8687 [Web] Segfault and coredump from HTTP proxy
  • NUTM-8691 [Web] Certificate error on accessing sites with https scanning enabled
  • NUTM-8752 [Web] NTLM Issue with AD SSO in Transparent Mode
  • NUTM-8771 [Web] Wrong country showing up in Web proxy requests
  • NUTM-8826 [Web] Teamviewer via Standard Mode with AD-SSO not possible since v9.502
  • NUTM-8834 [Web] iOS11 user agent string is not detected as iOS
  • NUTM-8849 [Web] Can’t download with HTTP proxy in Transparent Mode
  • NUTM-3129 [Wireless] SG125w failed to create interface wifi0: -23 (Too many open files in system)
  • NUTM-4720 [Wireless] Issues with 2.4 GHz channel 12 and 13 / inconsistent channel availibility / AWE_DEVICE_CHANNEL_INVALID
  • NUTM-8288 [Wireless] Roaming issues with iPhone7 and RADIUS authentication
  • NUTM-8391 [Wireless] AP55C/AP100X disconnecting from UTM repeatedly

Sophos UTM Up2Date 9.415 Released

Sophos has today released UTM 9.415. The release will be rolled out in phases.

In phase 1 you can download the update package from the FTP server, in phase 2 it will spread via the Sophos Up2Date servers.


  • System will be rebooted
  • Connected APs will perform firmware upgrade


  • NUTM-8987 [Basesystem] System doesn’t boot if Posgtresql database cannot start – UTM 9.4
  • NUTM-9021 [Wireless] WPA2 KRACK vulnerability fixes (Sophos details here)

Updates –

The Law – Using Mobile Phones When Driving

It’s illegal to use your phone while driving or riding a motorcycle unless you have hands-free access, such as:

  • a bluetooth headset
  • voice command
  • a dashboard holder

The law still applies to you if you’re:

  • stopped at traffic lights
  • queuing in traffic
  • supervising a learner driver


If you use your phone hands-free, you must stay in full control of your vehicle at all times.

The police can stop you if they think you’re not in control because you’re distracted and you can be prosecuted.

When you can use a hand-held phone

You can use a hand-held phone if either of these apply:

  • you’re safely parked
  • you need to call 999 or 112 in an emergency and it’s unsafe or impractical to stop


You can get 6 penalty points and a £200 fine if you use a hand-held phone.

You can also be taken to court where you can:

If you passed your driving test in the last 2 years, you’ll lose your licence.

This page is correct as of November 6th 2017.

How To Find The Cisco WLC Software Release

To determine which release of Cisco WLC Software is running on a device, administrators can use the web interface or the CLI.

To use the web interface, log in to the web interface, click the Monitor tab, and then click Summary in the left pane. The Software Version field shows the release number of the software that is currently running on the device.

To use the CLI, issue the show sysinfo command, and then refer to the value in the Product Version field of the command output.

The following example shows the output of the command for a device that is running Cisco WLC Software Release

(wlc)> show sysinfo

Manufacturer’s Name…………………….Cisco Systems Inc.
Product Name………………………………. Cisco Controller
Product Version…………………………….
Bootloader Version………………………..1.0.1
Field Recovery Image Version…………
Firmware Version…………………………..FPGA 1.3, Env 1.6, USB console 1.27
Build Type……………………………………. DATA + WPS

Image result for Cisco WLC

Sophos UTM Wrong Count Of SSH Logins In Summary In Executive Reports

If you get a wrong count of ssh logins in summary in executive reports :-

At some point an Accu file could get broken and all reporting data of the last 30 days gets lost.

Every 5 minutes the Reporter is updating the Accu file. If the file is not readable (because of being missing or corrupt) a new one is created and reporting starts from beginning.

The Accu files are binary and are located – /var/log/reporting/accu