Sep 202018

We recently had a Mid 2010 Mac Pro in the shop which had three 3TB hard drives.  We did a fresh install of High Sierra on the first 3TB drive.  The goal was to install Windows 7 on the second 3TB drive.  The third 3TB drive was to be added to the macOS installation as a data disk.

To install Windows 7 on this old Mac Pro, the drive needs to be formatted with a MBR partition scheme.  If you formatted it with Apple’s Disk Utility, you might get the following error message when trying to install Windows: “Windows cannot be installed to this disk.  The selected disk is of the GPT partition style”.

If you attempt to format a 3TB drive MBR using the Apple Disk Utility in High Sierra, you’ll get the error message “The disk is too large to be supported by the given partition scheme.  Operation failed…”. What a pickle.

There’s no shortage of blog post hacks out there describing methods of how to install Windows 7 on old Mac Pros.  Boot Camp was completely useless.  It would have been much easier with a 2TB drive. Here’s what I did:

  1. Formatted the disk intended for Windows 7 as Mac OS extended (Journaled) with Guid Partition Map in Apple’s Disk Utility for the fun of it.
  2. Boot to the Windows 7 installation DVD.  Note: Bootable Windows 7 USB sticks and external USB optical drives will not work on this old Mac.  You need to boot the Windows 7 installer from your internal DVD drive.
  3.  When Windows Setup asks you “Where do you want to install Windows”, press Shift F10 to get a command prompt.
  4.  Format the drive intended for Windows MBR using the Windows command line.  Be careful to select the correct disk.

list disk
select disk n (where n is the disk you want to install Windows 7 to)
convert mbr

The result is the selected drive will be erased and formatted MBR.  You’ll have a 2.2TB partition which is the maximum size for MBR.  The rest of the disk will be unused space.  Click Refresh on the Windows installer to see your changes.  You can now format that partition NTFS and select it as your Windows 7 installation destination.

But wait… after clicking Next, I immediately got the message “Windows is unable to install to the selected location.  Error 0x8030024”.  This is a Windows 7 installer issue.  Power down the machine, disconnect any other drives attached to the system, reboot to the Windows 7 DVD again, and you’ll be able to complete the installation.  When finished, re-attach the other drives, no issues.

When the Windows installation is complete, you can download the Boot Camp Windows support software manually.  For more info, check the Compatibility Tables. Here’s the link applicable to this mid 2010 Mac Pro: Boot Camp Support Software 5.1.5621.  For this old Mac Pro, I only needed to install the Windows Bluetooth, ATI video, Realtek sound and Intel chipset drivers.

I’m confident this Windows 7 installation could be upgraded to Windows 10 since it’s on its own disk.  That’s an experiment for another day.

Dec 262017

We recently had the need to establish a Site to Site VPN connection with our Meraki MX65w security appliance.  Meraki security appliances have the option to establish a Site to Site VPN connection to other security appliances as well as other third-party routers.  In our scenario, we successfully configured a connection between our security appliance and a Cisco RV325.  Configuring the Site to Site VPN on the security appliance is well documented by Meraki.  This documentation can be found in the link below.

Unfortunately, there is no documentation with configuring this connection specifically with a Cisco RV325.  Our initial attempts were unsuccessful and upon examining the logs we found we kept receiving the same error message “phase 1 failed due to time up.”  Upon researching into this error, we stumbled upon documentation from Meraki entitled “Troubleshooting Site to Site VPN Connections with Non-Meraki Peers” (link below).

This article had a description of the error messages and a proposed solution.  Unfortunately for us, the solution provided for our problem was generic and not very useful.  As a result, it forced us to escalate this issue with Meraki support and do a scheduled call.  Meraki support had access to our cloud configuration and could troubleshoot the issue by examining logs and performing a packet capture on the inbound traffic to our MX65w.  The support was very useful and we had the issue resolved very promptly.

Below are our settings for a successful Site to Site VPN connection between these two devices.

The Meraki Mx65w provides the ability to pass multiple subnets over the VPN which can be configured with the Use VPN yes/no drop down menu.  In our scenario, we are only passing through one subnet.

By default, both devices allow all traffic over the VPN unless configured otherwise.  Meraki does not allow the configuration of inbound firewall rules over the VPN and allows all traffic.  Hopefully this feature will be allowed in the future as sometimes you might not have access to both devices and only want to allow certain inbound traffic through the VPN.  With the current inbound allow all rule inbound rules would have to be done on all clients.

 Posted by at 9:54 am