vmware_view_pilot-5132020[1]Recently spun up a new Windows 7 virtual machine on an ESX cluster. After installing VMware Tools and rebooting the machine , the NIC card would stay unconnected. You would tick the connected box , restart the machine and the Tick would untick.

The default port limit on a vSwitch if you don’t use VLAN’s to segment traffic is 120. So when you hit this limit the above happens. I increased the port limit on each host to double. The VSphere client says you need to reboot the host to apply this , but I just vMotioned the machines from one to another which seemed to fix the problem.

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

Opening OWA produced the following error : A mailbox couldn’t be found for Domain\User. If the problem continues, contact your helpdesk.

Opening Outlook produced  Outlook cannot open the file because it is not associated with the default

Even though the user was in the GAL , Sending a user an email produced the following bounce back:

#554-5.2.1 mailbox disabled 554 5.2.1 STOREDRV.Deliver.Exception:AccountDisabledException.MapiExceptionMailboxDisabled;

Run this after Disabling a Mailbox ( it’s a nightly job otherwise ) 

Get-MailboxDatabase | Clean-MailboxDatabase


VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

imageServletA MSL2024  came up with the following error on the screen. It sounded like a tape had fallen out on the track. You  will need to take the device apart to remove the tape 


Releasing the magazines manually: If you cannot remove the magazines via the OCP or RMI, do the following: 1. Unplug the power cord from the device. 2. From the back of the autoloader, find the access holes for the right and left magazines.


Manual magazine release holes
Manual magazine release holes

2) Unscreen the 2 screws on the top and 3 bottom of the front of the unit which should let you remove the screen and get access to the gang way to remove the tape


VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)


316NYS8Bn9L[1]USB Compatibility can be found here http://docs.fortinet.com/uploaded/files/2440/fortigate-modem-compatibility-matrix.pdf

A fortinet device does not recognise a Sierra Wireless 320U IMEI , you will need the following config

config system lte-modem
    set status enable
    set apn “Telstra.internet”
config system modem
    set status enable
    set auto-dial enable
    set connect-timeout 30
    set wireless-port 4
    set phone1 "*99#"
    set extra-init1 "at+cgdcont=1,\"IP\",\"telstra.internet\""
    set extra-init2 "at+cgdcont=1,\"IP\",\"telstra.internet\""
    set altmode disable
config system 3g-modem custom
    edit 1
        set vendor "Sierra Wireless"
        set model "320U"
        set vendor-id 1199
        set product-id 68aa


Enable 4G/LTE:

#config system global
#set usb-lte enable


#diagnose sys modem detect wireless
#diagnose sys modem external-modem


Create a Policy allowing outbound through the Modem

Change the static route to via Modem

Make sure DNS is set on DHCP

VN:F [1.9.22_1171]
Rating: 8.0/10 (2 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

OneDriveForBiz2After installing One Drive for Business 2016 and trying to Sync a Library the following error was brought up :

The server you are trying to access is using an authentication protocol not supported by this version of Office


Close Microsoft OneDrive for Busuiness ( Kill Groove.exe ) 

Close Microsoft Offline Cache Process 




Open Word and Click File , Account , Sign Out and Back In

Open One Drive for Business ( search for it ) 

Open the one drive folder via the web browser and click sync

**If this does not work, try opening the Sharepoint for 365 Library inside of word ( File , Open , Add Library ) 

Add the library with your login details , then try clicking on the sync button again

VN:F [1.9.22_1171]
Rating: 9.9/10 (7 votes cast)
VN:F [1.9.22_1171]
Rating: +4 (from 6 votes)

OneDriveForBiz2Just had a customer install office 2016 Home which wiped the 2013 installation of One drive for Business

Turns out this is a bug where both Office 365 (2016) and One Drive for Business 2013 cannot coexisting on the same computer

Work around : Install Office 365 ( 2016 ) for Home , then after download and run the easy fix located on this site.


It has to re-package the office installer and re download Office for Business 2016 so it can take 30 minutes depending on the installer.

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

Windows 10Recently we had a problem where network shares were dropping in and out on some windows 10 machines. We used pings to make sure network connectivity was not to blame which it wasn’t ( no pings dropped ) some people online where complaining about having to roll back drivers for network cards to older versions

I have seen this on Vista before , so we forced it to use a lower version of Samba : 

To access said setting go to the control panel in Windows 10 (or 7), in Category view click on the text “System and Security”, then click on the text “Administrative Tools”.

Now double click and open “Local Security Policy”.

In the Local Security Policy screen on the left navigation tree, expand the “Local Policies –> Security Options” then about 2/3rd’s the way down the list you’ll see a Policy called “Network Security: LAN Manager authentication level”. Double click and change the setting to be “Send LM & NTLM – use NTLMv2 session security if negotiated.”

Then just press OK and close all of the open windows and then try again


n the case of Windows 10 Home, Local Security Policy does not exist; therefore make the change in the registry (use regedit).
Value Type: REG_DWORD – Number (32 bit, hexadecimal)
Valid Range 0-5
Default: 0, Set to 1 (Use NTLMv2 session security if negotiated)
Description: This parameter specifies the type of authentication to be used.


VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

thesecuritydatabaseontheserverdoesnothaveacomputeraccountWhen tying to log into a machine on another domain which has a link with a One Way Active Directory domain trust the follow error was displayed on login : 

“The security database on the server does not have a computer account for this workstation trust relationship”

Checking the Incoming and Outgoing link properties on Active Directory proved there was an incoming however the outgoing was not present. I had to delete the incoming trust , save the password , then recreate the outgoing trust on the returning domain. The returning domain also did not have a conditional forwarder setup for the other domain , which needs to be added in DNS and point to a Active Directory server at the other end ( that must be routable ) 

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

Bootcamp_selectOSIt seems after certain windows update the following happens : 

Windows 8.1 PC Can’t Boot, Error Code 0xc000000d 

The Boot Configuration Data File is missing some required information.
File: \BCD
Error code: 0xc000000d
Boot up into repair mode and open command prompt 
  1. C:
  2. bootrec /rebuildbcd
  3. A (When prompted for options to add to boot list)
  4. Exit (to close the command prompt)
VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

Recently we had an issue where a Aggrigate on a netapp grew by 10% over the weekend. A check on the volumes showed nothing had grown which suggested something in the Aggrigate layer.


aggr status -v
df -Agr

We called NetApp Support who confirmed it was a known bug


 Deduplication identifies and removes duplicate blocks in a volume, storing only unique blocks.

Deduplication requires the use of a certain amount of metadata, including a ‘fingerprint‘ summary to keep track of data in the blocks. When the data in the blocks changes frequently, the fingerprints become stale.

When the sis start command is running, any stale fingerprint metadata is normally detected and removed. If the deletion of stale fingerprint metadata fails, the stale fingerprint data will linger and consume space in the volume, and can significantly slow deduplication processing.

Issue Description

When the sis start command is running on a flex volume, the deduplication subsystem of Data ONTAP performs in several phases:

  • Fingerprint gathering
  • Fingerprint sorting
  • Fingerprint compressing
  • Block sharing

Normally, if the fraction of stale fingerprints in the database increases to greater than 20 percent, an additional ‘fingerprint checking’ phase is also performed, which cleans up the data. However, there is an issue in some releases of Data ONTAP (Data ONTAP 8.1, 8.1.1 and 8.1.2 and P/D-patch derivatives) that might cause the percentage to be calculated incorrectly, such that the checking phase is never performed. For more information, see BUG ID: 657692.


The stale fingerprints in the fingerprint database are not deleted; the excess data lingers and consumes space in the volume.

As more stale fingerprints accumulate, the increasing size of the fingerprint metadata increases the deduplication workload on the system, with the sorting and merging phases running for a long time. In aggravated cases, storage clients might experience a slow response.

This issue is more likely to be observed on a volume where there is a lot of file delete activity.

To determine if a flex volume on a storage system is experiencing this issue, the output of two administrative commands can be examined for numeric values from which a calculation can be made. The commands are:

  • sis check  -c <vol>
  • sis status -l <vol>

Note: Run the sis check command from the diag node.

For Example:
The output of sis check -c for a volume includes the following lines:
Checking fingerprint  ...  18115836411 records
Number of Segments: 3
Number of Records:  18003077302, 53607122, 59151987
Checking fingerprint.vvol  ...  56538330 records
Checking fingerprint.vvol.delta  ...  2665604040 records

The important value is in the first line, the total of checked records, 18115836411, which will be called ‘TOTALCHECKED’ here.

In the output of sis status -l for the same volume, the following line is included:
Logical Data:                    3509 GB/49 TB (7%)

The important value is displayed first, the size of the logical data, 3509.

Take the logical-data size (in gigabytes) and apply the following calculation, which yields the number of storage blocks occupied by the logical data.
In this case, (3509 * 1024 * 1024) / 4 = 919863296 is the LOGICALBLOCKS value.

To calculate the percentage of stale fingerprints, take the total of checked records from the sis check -c output and use it in the following equation:

In this case, ((18115836411 - 919863296) * 100) / 919863296 gives a PERCENTSTALE result of 1869.

As the result, 1869 is much larger than 20. The conclusion is that the triggering of sis check at 20 percent stale did not occur, and thus the volume and storage system are experiencing the issue.


A cleanup of the fingerprint database on a volume impacted by this issue is accomplished by running the following command:
sis start -s <vol>

This is resource intensive and a very long-running process as it deletes (entirely) the old Fingerprint Database to reclaim volume space and then builds a brand new copy of the Fingerprint Database.

If the workload imposed on the storage system by running sis start -s is extremely large, a NetApp Support Engineer can guide the user to use the following advanced-mode command on the impacted volume:
sis check -d <vol>

Note: Dedupe operations for any new data will not be performed while ‘sis check -d‘ is running, expect to use more space from the volume until this command finishes.

In addition, the ‘sis check -d’ command requires an amount of free space in the volume greater than or equal to twice the size of the Fingerprint Database files. You can estimate the size of the Fingerprint Database by running ‘sis check -c‘ and adding the number of records in three files, then multiplying by 32 bytes which is the size of each record. To estimate the amount of free space required, in bytes, use this formula:
Number of records in [fingerprint.vvol + fingerprint.vvol.delta + fingerprint.vvol.delta.old (if present)  ] * 32bytes = records (or database size)

Ensure that there is sufficient free space prior to running ‘sis check -d’.

'sis check -d' is invalid on a snapvault secondary


Users should upgrade to Data ONTAP release 8.1.2P4 or later.

After upgrading to a release with the fix, running deduplication twice (sis start) on each volume will automatically remove these stale fingerprints.
Note: If there is no new data added to the volume, deduplication will not go through all its phases, including the phase responsible for cleaning up stale fingerprints (Verify Phase). Deletes on the volume would not cause deduplication to initiate. Data deletions from the volume will definitely create stale fingerprint metadata in the volume.

The first deduplication job post upgrade might take longer time than expected. Subsequent operations will complete at normal operating times. This process of removing the stale fingerprints will temporarily consume additional space in both the deduplication enabled FlexVol volumes and their containing aggregates.

Also, to confirm that the controller running Data ONTAP version with the fix is not witnessing this issue, please check sis logs. Logs should have the following two lines mentioned:
<timestamp> /vol/<volname> Begin (sis check)
<timestamp> /vol/<volname> Sis Verify Phase 1


You can do the formula in the Link to check if it’s applying to you to check PERCENTSTALE is over 20


Run theses on all of the volumes which come back with PERCENTSTALE is over 20 , run once at a time to stop high I/O on San


priv set advanced 
sis check -c /vol/volume
sis status -l /vol/volume


Upgrade Ontap to new version



VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)