How can I move out of Apple support and into the Windows/Linux field?

Hi, all.

I currently work as an Apple Certified Macintosh Technician and Apple Certified Support Specialist for an Apple reseller. I do on-site support and hardware repair, as well as some small business stuff.

I'd really like to get into Networking or Server Administration. The problem, however, is that my Apple experience doesn't get me very far. Most places require MS Server or Linux. Now, I have personal experience with Linux servers (I've deployed both CentOS and Ubuntu servers at home, running various services), but very little experience with Windows server. I do, however, have personal experience with Windows systems. I've built gaming PCs and personal machines for friends and family, have done troubleshooting on Windows from time to time personally, and feel that I could pick up more Windows or Linux stuff fairly easily if someone were to give me a chance.

So, I guess, in a nutshell my question is this: What would be the best path for me to take to transition away from the Apple world and into a Microsoft- or Linux-based position where I can eventually move into a Network or Systems admin role?

Thanks in advance!

Find more posts tagged with

Save $250 on 2025 certification boot camps from Infosec!

Book now with code EOY2025

Button

Comments

matt333

download https://www.virtualbox.org/
get some window server 2008 ISO images and start building there is a lot of tutorials out there to fill in the gaps. just like anything you need to play around with it so you can used to the GUIs. I'm sure you can find some workbooks that will help.

As far as certs Microsoft seems like the way to go, might take a while to learn it all but new skills are not something that can be rushed. Jobs you might have to start at the bottom eg. help desk. be ready for a pay cut and the time commitment.

docrice

One of my earlier jobs was supporting an environment which was primarily Mac-based (this is prior to OS X). If your Mac experience involves command-line work, then transitioning to Linux should be somewhat more straight-forward than getting used to Windows unless you're already familiar with Windows as well. Most Linux environments that I've seen generally don't install X so you should be able to configure and troubleshoot things strictly at the CLI.

However, my background might be reverse of yours as I started my computing experience in DOS (then to Windows 3.x, etc.). In order for you to migrate to working in a Windows environment in a business, you need to understand the conventions of how a domain model works under Active Directory. Fundamentally it's similar to how NT 4.0 worked except you have much more complexity and feature set built-in. At a basic level for supporting Windows as a client itself, you need to know how permissions, user profiles, local policies, running services, some basic CLI, etc., as well as obviously getting accustomed to the GUI.

In a client-server environment, you'll need to recognize authentication events such as Kerberos, LDAP dependencies, SMB (which OS X supports, but generally people don't think about it aside from, "Oh, that's how you access files, printers, and resources on remote hosts."), remote procedure call (DCE-RPC / MS-RPC), etc.. In my experience most folks at the desktop support level aren't aware of these underlying transactions, but having been there and now looking back I think it would've benefited me greatly if I had known about those things a bit more in-depth as my troubleshooting turnaround would've been that much better.

Certs-wise, start with Network+ and look at the Microsoft client OS certs (like 70-680). If you really want to dive deep and get a head start, also peek through Windows Internals by Mark Russinovich. It's overkill at the beginning, but it'll give you a leg up on your peers if you understand some of the basics behind it. I can't begin to tell you how many Microsoft admins still don't really understand how a security token is handled and why UAC functions the way it does.

ptilsen

Since you don't have any professional experience outside of Apple, there are several things you can do to try to highlight skill in other areas. Realistically, you should do all of them if you want to get away from what you're doing now. These are in no particular order.

First, get certifications in either Linux, Windows, or Cisco. CCNA, Windows 7, and Linux+ are probably good starting goals. Pick a direction you think interests you more and head there. If you're really not sure, focus on the more vendor-neutral A+ and Net+ certifications.

Second, get real skills and experience with these systems. Pursuing the certifications will help a lot, but don't do it halfheartedly. If you go for CCENT or CCNA, get real routers and switches and lab on them. If you go for Microsoft or Linux certs, build VMs and do stuff with them. Use them for production purposes at home. Take DHCP and DNS off of your SOHO router appliance.

Third, build a skills-oriented resume. For experienced professionals -- especially those already experienced in the fields in which they desire to work -- I recommend an experience-oriented resume that shows skills and strengths in experience description. This has more credence and value than simply listing vague technical skills. However, for an inexperienced professional or one seeking to make a major career move, you really have to focus on trying to show real knowledge and understanding. As such, you'll want a significant skills section on your resume.

Realistically, your next position is probably going to be helpdesk. In some ways, that's almost a step down from what you do -- almost. If you're lucky, you can find more of a desktop support role, but a business-oriented (as opposed to consumer-oriented) helpdesk is what you're most likely to move to for the growth you seek.

wellnowwhat

docrice wrote: »

One of my earlier jobs was supporting an environment which was primarily Mac-based (this is prior to OS X). If your Mac experience involves command-line work, then transitioning to Linux should be somewhat more straight-forward than getting used to Windows unless you're already familiar with Windows as well. Most Linux environments that I've seen generally don't install X so you should be able to configure and troubleshoot things strictly at the CLI.

However, my background might be reverse of yours as I started my computing experience in DOS (then to Windows 3.x, etc.). In order for you to migrate to working in a Windows environment in a business, you need to understand the conventions of how a domain model works under Active Directory. Fundamentally it's similar to how NT 4.0 worked except you have much more complexity and feature set built-in. At a basic level for supporting Windows as a client itself, you need to know how permissions, user profiles, local policies, running services, some basic CLI, etc., as well as obviously getting accustomed to the GUI.

In a client-server environment, you'll need to recognize authentication events such as Kerberos, LDAP dependencies, SMB (which OS X supports, but generally people don't think about it aside from, "Oh, that's how you access files, printers, and resources on remote hosts."), remote procedure call (DCE-RPC / MS-RPC), etc.. In my experience most folks at the desktop support level aren't aware of these underlying transactions, but having been there and now looking back I think it would've benefited me greatly if I had known about those things a bit more in-depth as my troubleshooting turnaround would've been that much better.

Certs-wise, start with Network+ and look at the Microsoft client OS certs (like 70-680). If you really want to dive deep and get a head start, also peek through Windows Internals by Mark Russinovich. It's overkill at the beginning, but it'll give you a leg up on your peers if you understand some of the basics behind it. I can't begin to tell you how many Microsoft admins still don't really understand how a security token is handled and why UAC functions the way it does.

I do a lot of stuff from the CLI in Mac OS X. I've been playing around with Ruby lately and most of the configuration and what-not has been done through the CLI. I also troubleshoot web server, permissions, and other issues through the CLI just because it's easier to do it that way, so I'm familiar with Unix-style commands and syntax. I honestly would be more interested in going into the Linux field, but most employers seem to want Microsoft trained or certified people.. I have some experience with Windows, but it's mostly client-side (Windows XP and Windows 7).

Thanks for the great advice.

wellnowwhat

First, get certifications in either Linux, Windows, or Cisco. CCNA, Windows 7, and Linux+ are probably good starting goals. Pick a direction you think interests you more and head there. If you're really not sure, focus on the more vendor-neutral A+ and Net+ certifications.

I bought a Network+ book, a CCNA book, and the 70-680 Certification book. I'm currently working through the Network+ stuff and it seems fairly straightforward, so hopefully that's a good starting point..

Second, get real skills and experience with these systems. Pursuing the certifications will help a lot, but don't do it halfheartedly. If you go for CCENT or CCNA, get real routers and switches and lab on them. If you go for Microsoft or Linux certs, build VMs and do stuff with them. Use them for production purposes at home. Take DHCP and DNS off of your SOHO router appliance.

Where's a good place to get routers and switches? Which models would be a good starting point? I don't have a whole lot of money but I have enough to afford tests and books, so if a Cisco setup isn't too expensive I can probably fit it into my budget. And I have run Linux systems in VM systems, namely CentOS and Ubuntu servers. I'm looking into getting a copy of Windows Server 2008 as we speak, so hopefully I can get that up and running and play around with it.

Realistically, your next position is probably going to be helpdesk. In some ways, that's almost a step down from what you do -- almost. If you're lucky, you can find more of a desktop support role, but a business-oriented (as opposed to consumer-oriented) helpdesk is what you're most likely to move to for the growth you seek.

Honestly, what I do right now is glorified helpdesk. The company for whom I work doesn't pay very much, so even a "lateral" transition to another helpdesk spot would be great if it meant more room for growth and opportunities outside of the Apple stuff.

Apple is just such a niche market and I feel very stuck with my current career path. I'd rather branch off and take my Apple experience with me as a supplement rather than continue to have it be the main focus of my career..

docrice

For Cisco training, you can use GNS3 (assuming you have access to some IOS images) or just buy cheap stuff off eBay - 2600 series routers and 2950 series switches will do just fine for starters. Last I checked we're talking about $30 per device.

ptilsen

wellnowwhat wrote: »

I bought a Network+ book, a CCNA book, and the 70-680 Certification book. I'm currently working through the Network+ stuff and it seems fairly straightforward, so hopefully that's a good starting point..

Those are great starting points. Do all three. Windows 7 + Network+ is most likely to help you into a DST role and actually help you with that role. Getting these three will give you a well-rounded start, and from there you can focus on whatever you want.