Parallels on a Windows Network


I've been in the same office for 15 years. For giggles I decided to move to another office recently. It is a little bigger and has a better view. Also, it is good to shake things up once in awhile. Unfortunately, I didn't realize until after I got all my furniture moved that there is no ethernet into my new digs and as far as the network is concerned, I fell out the window.

So my PC box sits in my computer stand with its two monitors silent while I attempt to get someone to wire it up. Mainly out of necessity but also out of Mac geekiness, I decided to see if I could exist on a windows network with nothing but my MacBook Pro. Turns out I can.

We use a specific program that is a relational database for lawyers called TimeMatters. It is PC only and although the program can be frustrating, one thing it does very well is keep all of your data on the server. So I booted up parallels and had an extended call with a very smart PC friend of mine and in about an hour we had my Mac securely on the network with TimeMatters installed on my laptop and working flawlessly in Parallels. For the last few days I've been doing most word processing in Pages and jumping over to Parallels for the database management stuff. I'm very pleased at this newfound ability and amazed why I didn't take steps to make this happen earlier.

I've frequently used Parallels for another legal PC only program, CaseMap, but interacting with the office database on my Mac seems to step it up a notch. It makes me feel a little bit of a rebel. The lone wolf.

lone wolf.jpg

Okay, maybe I'm laying it on a bit thick, but I've had very few problems. Once Parallels sent one of my cores spinning up for no apparent reason. I logged out of windows and rebooted the virtual machine and everything sorted itself out. Other than that, no complaints. And the fact that my cable installer seems to be busy doesn't really bother me so much either.