Movin' on up

-
We have 4 Admins on my department's Network & Systems Administration team. The Security Admin and Network Engineer also manage Linux/Unix stuff while the other 2 admins are our Windows Admins, which is where most of our services run. One Windows Admin oversees the NOC (where I currently work) while the other manages our VMWare infrastructure as well as Mailmeter, our Cisco UCS blade systems, backups, etc.

One Windows Admin has the NOC as well as a small team of student assistants that handle support duties to our residents under him. Security Admin, Network Engineer, and Other Windows Admin all have their own Jr Admins as well. Chris is a Jr Admin under our Security Admin and Steven is Jr Admin under our Network Engineer. Chris and Steven were both working in the NOC when I started and were 1 by 1 promoted to Jr Admin positions. Our other Windows Admin had Patrick, an older IT guy who worked here for almost a year. Patrick recently took a job elsewhere so I asked Other Windows Admin about the job.

I'd worked with Other Windows Admin on things before. He showed me how to use Treesize, our disk usage reporting software that runs on our file server. He's also worked with me on issues that've come up since I'd started. I've even chatted him up about my home server I'm planning on getting soon. He talked with Sr Admin and within a week I had an interview! 

Long story short (or is it too late for that?) I got the job. He's already given me access to and documentation for our DPM server (Data Protection Manager, part of MS's System Center suite of management programs). 

Unfortunately, because I'm a "senior" member of the NOC, I can't just up and leave for this new position. $Boss and our Windows Admin are now working out a transition period until we get a new member for NOC hired and trained. I'm glad to be such an integral part of the operation but I really want to jump head first into my new role. I'm very excited. It also pleased our Sr Admin to see that we've now promoted 3 members of the NOC to our Network Administration team. The job also came with more money. More money is always nice. 

Mostly, I'm excited to finally be rising to the next level. I plan to make good use of the time spent and experience gained from this new opportunity. 

Comments

Post a Comment

Popular posts from this blog

Installing CentOS 7 on a Raspberry Pi 3

-
Image
The Raspberry Pi is awesome. If you're like me, you bought one to tool around with for educational purposes. You can run Kodi or gaming console emulators on it or you can combine some together for a tiny OpenStack cluster. At, $50-$60, they're easy on the wallet and running off of 5v USB power makes them pretty energy efficient. Sure, it's only a 1Ghz ARM processor which limits your OS choices but I'd rather have a Pi than running an old Dell PowerEdge or HP Proliant that I bought off of Craigslist. Instead of installing the usual Raspbian OS, this guide is on installing CentOS 7. However, the process described below is relatively universal to whatever OS you want to install on your Pi.
Read more

Modifying the Zebra F-701 & F-402 pens

-
Image
I've been carrying a pen as part of my (mostly) every-day-carry, or EDC, for a couple years now. I bought the Zebra F-701 and after a few other pen purchases, the 701 is still my favorite of all. At first, I just wanted a pen that looked nice and for the moments I needed to sign something. I recall attending meetings when I worked at the university where the attendees were asked to sign-in on the attendance sheet: I tended to be the only one that didn't have a pen so I felt unprepared when I had to ask one of the other attendees if I could borrow theirs. Once I started college, I found myself using a pen much more often, so it had to be comfortable, relatively inexpensive (nice pens can cost hundreds of dollars), and still stylish enough to live in the pocket of a dress shirt.
Read more

How to fix DPM Auto-Protection failures of SQL servers

-
For longer than I care to admit, my DPM server has had the same error every night about an auto-protection failure on one of my SQL servers. I've looked into it before but never came away with anything useful until recently. I've finally found information on how to fix this annoying issue. The Advanced Information link in the error will tell you to make sure WMI is in a good state on the machine. The error itself isn't very descriptive. It'll look something like "DPM could not enumerate SQL Server instances using Windows Management Instrumentation on the protected computer $serverFQDN."
Read more