Would you take this position? My thoughts..

Mrock4

Hey all, quick question, I'd like your opinions. As most know, I'm in the military, so bear this in mind. We can "apply" for almost any position in the military, but you have to be very careful not to step on anyones toes..commanders are very protective over their people, and rightfully so. They hate to lose someone. That being said...

I called up a guy I worked with in Iraq, who is a server room guy. He is pretty on point with Windows Server, Active directory, exchange, retina, etc..lots other server-based software. My function in Iraq with him was that I was the network tech. We performed two different jobs, but worked together. He outranked (and still does) me, but he was not my supervisor. Pretty cool guy. I asked him how things were going, and he said that there was a new NCOIC (supervisor, basically), and she was looking for guys to fill the slots up there. He said he could put a good word in for me, and get me in his shop. Soon, we will be the same rank, but of course, he's been the rank longer, so I would essentially work for him, but it'd probably be pretty laid back. My question is:

Would you take that kind of a position? It seems like it'd be a LOT more server based stuff than what I know, but that may be a good thing I guess. I am working on my CCNP now, and this guy is trying to branch INTO cisco stuff, so he even suggested that maybe we could cross train each other, since we both get out of the service around the same time.

I guess I am just a bit hesitant to really dive into server technology. The stuff we use up there is pretty high end stuff, and I do have basic experience on it..I ran it many nights while no server room people were available, but I am definitely no server admin by any means.

I guess we are all scared of the unknown huh? Part of me also doesn't want to leave my subordinates..they are networking folks as well, so it is my job in the next few months to train them on cisco gear. Training is often the best way to ensure you know your stuff but....

Just needed to clear my mind. I have 24 hours to really make a choice. For what it's worth, I've worked with most of the people already up where he's at, and have a stellar reputation, but...who knows.

Thanks for putting up with me fella's.

Mike

remyforbes777

The big question is, what do you see yourself doing for the next few years? Do you like the server administration thing more than networking?

Mrock4

Not at all. I am definitely not a server admin. Can I do it..and do a good job? Absolutely. As of right now, I am pretty intent on finishing my service, and (eventually) being a network engineer..looking at CCNP, then maybe some VOIP stuff. I just want to be a well-rounded IT guy.

Netstudent

IF you are a networking guy then stick with that.

mikej412

Would you be The Network Guy in that new environment? Would it give you a bigger network environment to work with? Would it advance your Networking Career better than your current position?

If the new position allowed you to branch out your skills into some other areas, that could be useful, since it would open up a broader range of jobs to you when you left the military. But if you have to give up some Networking experience and only gain server or server room experience -- and doing that part of the job isn't as interesting as your Network position -- then pass.

But don't worry to much about your subordinates -- if you did leave, wouldn't someone else get to step up?

It's always nice being asked or offered a new position.

Mrock4

Someone else would step up if I left my current unit, I just worry. It's a bit different than a regular job really, since we were in Iraq together. It's kind of a loyalty thing. They'd probably understand I'm sure.


My take is, I would basically be the "resident" network 'expert', but be working mostly on servers. Meaning really, this guy would handle the heavier server-based tasks, and I- the networking side when needed, but it'd be a lot of cross-training. I can't say I'd be exposed to more difficult issues than I faced in my past job, because we all worked in the same office, so it was pretty much equal. This would just shift my primary function, and my networking experience would come into play when there was an issue, generally.

The network size is exactly the same, since as I said, we are in the same place. The difference is, when I was at my previous role, we were the network operations guys, so any network outages, we were the ones to make the call. The server room people were more "in-house". Because they had no one with networking experience, they usually called me to check the in house stuff out, so as I said, that may not change. But, I'd no longer be taking calls because of network outages. Let me elaborate:

In Iraq..my current role, we reacted to network outages, and got them up fast, wherever they were. LOTS of hands on experience. Here, in Hawaii...my unit has no real function, so most of our time is sitting around..I wish I was kidding. If I stay, I'd like to set up some training for the newer, less experienced guys. We have so many "network specialists" that can't execute basic commands on a router without notes.

In Iraq, the new role ran the server room and pushed updates, handled IA, etc. Here in Hawaii, they have the same role, so they work full days. I wonder if since there is no longer my unit to answer the calls, if maybe it's the server room team who does. It generally consists of 2-3 people. Right now, they have one, and I would become the second.