Slashdot Mirror
Ask Slashdot: What Should a Unix Fan Look For In a Windows Expert?
andy5555 writes "I am hardcore Unix (and recently storage) fan responsible for our server department. Most of the servers run (you guessed it) different types of Unix. For quite a long time, Windows servers played very little role, but sometimes we get applications from our business departments which run only under Windows. So it seems that we have to take it seriously and hire a few Windows fans who would be able to take care of the (still small but growing) number of Windows servers. Since I am Unix fan, I have very little knowledge of Windows (some of my teammates may have more, but we are not experts). If I have to hire such a person I would like to find someone who is passionate about Windows. It is easy for me to recognize a Windows fan, but I don't know how to test his/her knowledge. There are some sites with typical Windows interview questions, but everybody can read them and prepare. How would you recommend the hiring process to proceed? What should I ask?"
Someone who has exp with multiple versions of windows servers. 2000 is a good cutoff point. They should understand Active Directory. Thoroughly. If doing anything web based, know about asp and .net configurations, as well as how to use the new (awful) IIS manager. If storing dll components for software over the network (including aforementioned web based stuff), they should know about permissions hassles of trusting policies from network drives.
Exchange and or MS SQL experience is also a plus, but only if the windows boxes will be running them.
What is this 'fan' shit? You want to hire someone who has studied Windows architecture and know how it works. Not someone who wants to blow the OS.
then it's pretty probable they'll end up with some unix guy who also just happens to like gaming and has a windows side affair. I mean, pure-windows guys aren't that likely to know how it works, those are the guys to go for if you want arguments about if windows server kernels are meaningfully different than regular windows line kernels or if ms just raised an arbitrary connection limit on them.
otoh. I heard delta makes good fans, but I read also somewhere that steelers fans are awful.
world was created 5 seconds before this post as it is.
You will be faced with a lot of candidates. After you've culled the ones with actual experience and positive or neutral recommendations, this is where you can start in phone interviews:
1. Ask them to describe DHCP. An amazing number of candidates will not do well with this. Extra points for the ones who can expand slightly and describe the implications of static addressing, but they are probably older than you are l;ooking for, despite the blatant discrimination that implies. Deduct for those who treat this question with disdain - they are perhaps being too imperious to get along, and getting along is second only to knowing stuff. Maybe more important.
2. Ask them to discuss Active Directory design from a high level, the forest and trees, for example. Big points if they ask about your current structure. More points if they discuss the disadvantages of ripping up your current directory. Deduct points for those who seem to use an axe in the forest. You willl know.
3. Ask them about roaming profiles. No, you aren't using them, but you're interested in both their general reaction and their questions about why you are asking at all. Deduct points here for those who go 'poo-poo' and describe their loathing for roaming profiles. More deductions for focusing on the limitations.
4. Did any of them ask about your environment? Did any of them perk up at the mention of Linux? Did any of them expand unprovked about Windows' servers potential for integration with a Linux enviuronemnt? More points to these. Fewer points to those who are not at all curious about yoru Linux environment, and how you got saddled with some mongrel Windows severs in the mix.
I would be very interested in this position if it is in the Phoenix area, but I love my pool, and besides, you already know me too well. Ah.
deleting the extra space after periods so i can stay relevant, yeah.
This comment is spot on. I work in a heterogeneous shop, and our best results have been in training a Unix admin to take on additional Windows roles. It isn't just about being good at Windows, there are plenty of Windows professionals who can fulfill that role as a consultant or FTE. The problem is finding one who can integrate Windows environments to work well with your existing Unix infrastructure, much of which probably doesn't need to be duplicated under a separate Windows domain. To do that well, you need someone with a deep Unix background as well as the Windows training.
Ask a few network questions. Can you make a subnet? What's the difference between a tree and a forest? AD is important, what UI tool do you use to manage it and you may want to ask a few questions around permissions, and security. As the parent said, you can find them online. Certs are fine, but make certain the candidate actually wen to a real school to get training and not some cert factory. A bit of Cisco education is also useful as a side with your Windows main course. For sure they should have a clue about Linux and BSD (if you get someone who can do Solaris and another *nix flavor or two all the better.) They should have more than a passing understanding of Windows 7, maybe XP (depending on how many XP diehards in your environment.) If they are already playing with Win 8, you have ago getter. Server 2008 for sure. Perhaps Server 2003. You can ask about virtualization, powershell, net tools, command line interface, its all good. A well rounded engineer will know Exchange, SQL Server, .Net, Sharepoint (she said with a pained grimace), and Outlook.
Contact a local IT company that does windows and ask them how they hire their guys.