Oxford County Community Health Centre - Logo

New Client: Oxford County Community Health Centre

Oxford County Community Health Centre - Logo

Oxford County Community Health Centre - Logo

Builtbymike.ca IT Services - Logo

Builtbymike.ca IT Services - Logo

Builtbymike.ca IT Services is now providing IT Management services to the Oxford County Community Health Centre (OCCHC) in Woodstock, Tillsonburg and Ingersoll.

Builtbymike will use the same focus that has been working for four years at the Ingersoll Nurse Practitioner-Led Clinic to also help the OCCHC get more from their current IT resources while working to decrease the overall IT budget to allow the OCCHC to spend those funds to provide better services to the community.

Please visit the OCCHC website (new website soon to be released) to see the amazing services that they offer to improve the lives and health of the people within our community.


Builtbymikedotca IT Services - Large Logo

Happy Holidays!

Wishing you a happy holiday and a joyful and prosperous year to come!


The end of the year brings me the great joy of being able to acknowledge those who have helped to make a successful year for Builtbymike.ca IT Services. This year has seen many new business and residential clients coming to me for IT services. More importantly to me is that most of my clients have been repeat clients or have found me through word of mouth. This is the best indicator to me that I am providing a great service to my clients.

To help make 2017 an even better year for my business (and your IT service) I ask that you feel free to send comments and suggestions for Builtbymike.ca IT Services to mikepage@builtbymike.ca or if you are willing to have comments posted to my website you can e-mail those as well or visit www.builtbymike.ca/submit-testimonial.

Once again, I can’t thank you enough for your business and support in 2016. Cheers to you!


Builtbymikedotca IT Services - Large Logo




Reboot DD-WRT

Remotely reboot DD-WRT routers

Reboot DD-WRT

With my network monitoring powershell script I have noticed that the DD-WRT routers that a client uses will become unresponsive. Because of this I wanted an easy way for my client to reboot DD-WRT wireless routers without having to get physical access to the routers, especially since some of them aren’t easily accessible. There are two types of problems that happen with these wireless routers. The first problem is that they become completely unresponsive and fail the ping check that is done with my powershell script. In this case the router likely requires a physical reboot in order to function again. There is not much that can be done otherwise. The second problem that happens, as seems to happen with any wireless router, is that the wireless will randomly stop working. One way I have set up to reduce this problem is to have the routers reboot daily in the middle of the night. Despite this, the wireless will occasionally stop working throughout the day. This problem can be fixed by sending a reboot command to the router through a wired connection. This type of problem and the solution may be ideal for home users that have their desktop wired to their DD-WRT but have many wireless devices or like my situation where I want clients to be able to easily reboot wireless routers without my intervention. Once you have this set up you can double click a file to reboot your wireless as opposed to doing a physical reboot. That is what we will look at here.


The first part of the setup is to enable SSH on DD-WRT.

  1. Log in to your router.
  2. Navigate to Services –> Services
  3. Enable SSHd under the Secure Shell section.
  4. Ensure that Password Login is enabled.
  5. Navigate to Administrator –> Management
  6. Enable SSH Management and ensure SSH Remote Port is set to 22.
  7. If you skip steps 2 through 4 then it will not be possible to enable SSH Management in the Administration section.

Download and prepare Plink

  1. Now that you have SSH enabled on your device you must download Plink.exe from here.
  2. Place the “plink.exe” file somewhere that is accessible by everyone that may use your DD-WRT batch file reboot program. For my application it is done in an office setting so I placed the file in a share location that is accessible by everyone.

Create your batch file

  1. Open your text editor (Notepad).
  2. The command looks as follows:

PLINK-PATH -ssh ###.###.###.### -l USERNAME -pw PASSWORD “reboot”

Where PLINK-PATH is the location of “plink.exe”, example C:\DD-WRT\plink.exe.

###.###.###.### is the local address of the dd-wrt router you wish to reboot. It may look something like

USERNAME and PASSWORD are the username and password of your dd-wrt router.

  1. For my batch file I also added a second line so that the person rebooting the router can get visual confirmation that the router is rebooting. That line is the following:

Ping ###.###.###.### -t

This line will bring up a command prompt window that will continuously ping your router. It will start with lines beginning with “Reply from ###.###.###.###…” to show the router responding prior to reboot. Once the reboot command executes on the router it will show “Request timed out” as the router reboots itself. Lastly you should see “Reply from ###.###.###.###…” after the router is back online.

  1. Example batch file:

C:\Example\Location\plink.exe -ssh -l Administrator -pw Password1 “reboot”
ping -t

  1. Save your file with a “.bat” extension.
Execute Reboot DD-WRT Batch File

Execute Reboot DD-WRT Batch File

Your batch file to reboot your dd-wrt should now work. If you have any questions or comments please feel free to reply below!

Example Setup

This is how I have it set up for my office client so that the wireless routers can be easily rebooted as needed and provides warnings to not reboot particular wireless routers unless they are sure that they aren’t being used.

Reboot DD-WRT - Example Folder

Reboot DD-WRT – Example Folder


Symantec Backup Exec 2010 R3

Backup Exec 2010 VSS Snapshot error

VSS Snapshot Error Description

One of my clients was having an issue with Veritas (formally Symantec) Backup Exec with a “VSS Snapshot error”. This problem has many different solutions. The error message is pretty generic for any problem causing the VSS writers in Windows to crash. The error message I received was as follows:

AOFO: Initialization failure on: “Shadow?Copy?Components”. Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).

V-79-10000-11226 – VSS Snapshot error. The Microsoft Volume Shadow Copy Service (VSS) snapshot provider selected returned: “Unexpected provider error”. Ensure that all provider services are enabled and can be started. Check the Windows Event Viewer for details.

I tried about half a dozen potential solutions to this VSS error. The solutions I tried included:

  • Adding and removing windows updates and hot fixes
  • Restarting the server and services within the server
  • Modifying Windows registry settings
  • Looking up to the heavens and cursing Backup Exec.

All of these solutions were somewhat complicated. Some of the solutions that included editing Windows registry were also very risky.

The solution that ended up working was one that was posted to the Veritas website shortly after my client began having backup issues. This leads me to believe that something happened around that time with Windows Server or Backup Exec that caused them to become incompatible for VSS Snapshots.


  1. Go to “Computer” on the server in question and right click a hard disk.
  2. Select “Configure Shadow Copies…”
  3. For each volume select it and click settings.
  4. If maximum size is set to a limit select the radio button for “No limit”.
  5. Click OK and repeat.

Since doing this extremely simple solution I have been able to run backups successfully again. The article referenced below suggested that if the volumes were already set to “No Limit” to add a limited temporarily and then go back and set them again to no limit.


The solution for this came from here.

I came across that link through this forum post here.


VSS Snapshot Error