life's a game that you're bound to lose / like using a hammer to pound in screws
fuck up once and you break your thumb / if you're happy at all then you're god damn dumb
that's right we're on a fucked up cruise / God is dead but at least we have booze
bad things happen, no one knows why / the sun burns out and everyone dies
+1
Mr_Rose83 Blue Ridge Protects the HolyRegistered Userregular
Addendum: the original update also randomly breaks windows 7 touchscreens to the point that you can't log in from the console; any click input drops you back on the user select screen. Only reliable fix is logging in remotely and rolling back the update or removing the specific patch.
Any grizzled admins willing to impart some knowledge on an aspiring admin? I've been searching for opportunities and studying on my own time and I could use some advice on what kind of jobs I should be looking for and what I should be doing to develop myself.
Any grizzled admins willing to impart some knowledge on an aspiring admin? I've been searching for opportunities and studying on my own time and I could use some advice on what kind of jobs I should be looking for and what I should be doing to develop myself.
in a more serious answer, which also comes with a question, what kind of education/experience do you actually have? If you're 100% self taught, you're going to have to start on a help desk role, and even then you're likely going to need someone to "take a chance" on you. It's a bit unfortunate but in a lot of cases people who hire look for education first, experience second.
if you have an education but no experience, you're most likely to get in on help desk still, even a jr. sysadmin role will be a bit of a stretch for someone with zero IT experience.
But here is the key: don't be complacent in what you do. Even if you're working help desk, ask to learn/take on more things. "oh, this [non help desk thing] needs to be taken care of this week? Let me take a look at it when I have some extra time." Ask to help out on projects, take on extra tasks. sit in on meetings/project planning that might not necessarily be in your wheelhouse.
The key is: learn. Never stop learning. Ask questions. Any sysadmin/IT person worth a damn will be more than happy to help/share/pawn work off, because it means less work for them.
Any grizzled admins willing to impart some knowledge on an aspiring admin? I've been searching for opportunities and studying on my own time and I could use some advice on what kind of jobs I should be looking for and what I should be doing to develop myself.
in a more serious answer, which also comes with a question, what kind of education/experience do you actually have? If you're 100% self taught, you're going to have to start on a help desk role, and even then you're likely going to need someone to "take a chance" on you. It's a bit unfortunate but in a lot of cases people who hire look for education first, experience second.
if you have an education but no experience, you're most likely to get in on help desk still, even a jr. sysadmin role will be a bit of a stretch for someone with zero IT experience.
But here is the key: don't be complacent in what you do. Even if you're working help desk, ask to learn/take on more things. "oh, this [non help desk thing] needs to be taken care of this week? Let me take a look at it when I have some extra time." Ask to help out on projects, take on extra tasks. sit in on meetings/project planning that might not necessarily be in your wheelhouse.
The key is: learn. Never stop learning. Ask questions. Any sysadmin/IT person worth a damn will be more than happy to help/share/pawn work off, because it means less work for them.
Yea, I don't have a degree
I currently work for Geek Squad doing advanced work, I was working toward management but am tired of the bureaucratic BS, I've been doing that for 5 years now. I've been studying on my own and do stuff like penetration testing with some coworkers as a hobby. I write articles for the knowledge base and do face to face and phone support. I pretty much fall under "Jack of all trades" when it comes to IT. I know a bit of everything but more importantly I have the skills to find out anything I don't know and I'm not afraid to ask questions. I've been looking for enterprise help desk work but the search is pretty slow. I'm looking for Junior/Associate admin stuff so that I can work with something and get a clear path to the knowledge that I need to work on, I've been mentoring people in GS so long and not had a mentor of my own that I've just kind of hit a wall and am having trouble developing further.
I know I need to learn SQL, and I'm not sure where to fit that in. I get a couple hours a week to study stuff on my own and its currently going to Redhat, I have a working understanding of *nix systems and really am trying to find a way to put my knowledge to use because reading text books and doing little projects here and there isn't a replacement for practical application.
Any grizzled admins willing to impart some knowledge on an aspiring admin? I've been searching for opportunities and studying on my own time and I could use some advice on what kind of jobs I should be looking for and what I should be doing to develop myself.
Going along with what @wunderbar said, help desk will actually be kind of key to becoming a sysadmin. Even through all of the education (college, A+, Network+, MCSE, etc.), there is no way any of those could really prepare you for what you encounter in the field. Being an expert at research via Google is a massive skill that is pretty much a requirement. You'll run across issues that aren't easy to search for. Using that research, you'll need to deduce what is causing the problem(s) and how to fix them appropriately. Communication is also a must have, because you have to be able to describe technological issues to those who calling "technically savvy" is too much of a complement. One good way I remember someone putting it to me is this: try describing to someone over the phone how to tie a shoe. It seems simple, but it isn't.
The thing is that nowadays, sysadmin is such a vague term. Some of us are fantastic with Cisco products; some aren't. Some know backups inside and out; some know enough to just get by. Some deal with a lot of SQL; some barely touch it. Hell, some sysadmins are that because no one else knows how to do it.
If you are really wanting to get into the sysadmin territory, your best bet would be to look for a place that has the ability to train you on the finer aspects, which means you'll still be starting out at help desk and working your way up. Speaking from personal experience, make sure it is a place that actually has an up. There is nothing more demoralizing that not having the ability to climb the ladder; either that or your ladder is like mine, which is a step stool with wheels, so as soon as you're on, that's the highest you can go.
Once you get into a place and start to solidify yourself as a member of the team, start talking to your superiors about what knowledge would help you help them, and then see if your company will pay for training; totally take advantage of them if it is available.
EDIT: Another big thing to get smart on is virtualization. That's a pretty big these days. If you can expose yourself to virtualization, it's a good talking point. Also Exchange... definitely exchange management.
Le_Goat on
While I agree that being insensitive is an issue, so is being oversensitive.
Are there any decent resources for virtualization? Honestly all I know about that is VMware, VBOX and Parallels, I've never worked with or even seen AWS or AZURE.
The two big local virtualization technologies (in my opinion) are VMware and Hyper-V. That doesn't mean the others aren't up to par; those are just the two big ones. You may be able to just toy around with the free version of Hyper-V and see what it does, how to use it, how to change settings. You won't get too deep into the inner workings of how it operates in a corporate environment with servers and shit, but you at least then have exposure to it, so it's not completely foreign to you.
Cloud virtualization is a whole different boat. I can't speak for Azure, but AWS uses weird jargon that takes some used to getting used to. It's not terribly hard, just crazy annoying.
Also, when it comes time to have an interview, do not be ashamed to admit you don't know something. Trying to say you know something that you know zero about is just going to fuck you over.
While I agree that being insensitive is an issue, so is being oversensitive.
I'm not sure how many of you are versed in Microsoft KMS, which is Key Management Service. It's a volume license tool for microsoft products, allows you to have your VL versions of windows phone home to a server to stay activated. They've been using it since Server 2008/Vista for most of their volume license setups. It's just a service you run on 1 or 2 servers on the domain. You basically stick a KMS key into that OS, and then it can successfully activate any version of windows. i.e. for Server 2012 R2 you stick in the KMS key for 2012 R2 and it'll activate every server/client OS Vista and up.
I've learned a lot about it in the past week because all of the sudden most of the computers we have suddently decided they weren't activated anymore, including our servers.
KMS had been set up here long before either myself or my cohort worked here, and neither of us knew anything about it. There's no real UI for it anywhere, it only exists as a CLI level service that takes about 4 commands to turn on, and one DNS entry. Now, this thing doesn't have to phone home constantly. A PC that's authenticated against KMS is good for 180 days, so it only has to check in twice a year really. It'll try to check in once a week, and has 6 months to ping the server before Windows starts yelling.
So, about a month ago we had a couple computers lose their activateion, but they were field machines that haven't been seen in forever but whatever. Then we had a computer on the domain bitch about activation, which was weird but whatever. Then suddenly one day I log onto a server and it tells me that I need to activate windows. Then by the end of the day I had 20 calls from users about it. I traced it back to KMS, then had to figure out how KMS worked, and found the DNS entry for the KMS server in the domain.....a old domain controller we decommissioned about 6 months ago, not having any idea KMS was actually running on it. So, set up a KMS server on the new domain controller, Server 2012 R2 actually has a bit of a gui for adding it as a role now, which is kinda nice, and boom it was done. After I confirmed machines were starting to check in, I set it up on the secondary domain controller as well as a backup. That's when you'd think the story is done.
The next day, today, I look at a test machine to see if it is activated, and it isn't, and won't activate. So I go look into it. When I set up the second KMS server from the GUI, instead of it auto creating another DNS entry, it replaced the one from the primary server. Apparently that's a bug/feature in KMS in 2012 R2. Now you'd think that it shouldn't matter as the devices should authenticate against the backup server then. Except that, for some reason, the firewall on the second domain controller was on(we normally keep it off), and that port was blocked. unblocked the port and machines started to authenticate to the backup. Added the DNS rule back for the primary, and that came back up as well.
So now all of our client machines, and our servers, are activated again. :rotate:
I have no degree, no certs, nothing. I knew a guy and he wanted some help setting up workstations one summer at the local bank, and I got a really low-end job in their Datacenter. Several years later, I'm a sysadmin.
I'm not saying that's the way to do it, because there are some huge hurdles I've had to deal with because of this, and that point of entry is definitely a lottery ticket. But given your current experience with what you do, I don't see any reason you couldn't throw 5 years of Geek Squad experience on a resume to get a Help Desk I or II position at a company that has higher positions available.
And like wunderbar said, grab projects. Ask if you can help. That's how almost everyone promotes in this industry, is they display aptitude with more than consoling a grieving coworker over their missing spreadsheet. This biz can be kinda competitive, but in my experience people also tend to know the score, and lean on you if you keep delivering results. Just make sure you lean on them for your pay and time, when that happens.
Are there any decent resources for virtualization? Honestly all I know about that is VMware, VBOX and Parallels, I've never worked with or even seen AWS or AZURE.
yea if you have a Windows Pro license you can install hyper-v onto it. Gleam what you can from that.
Also, don't be super afraid if there are big holes in your skillset. I've been workign in IT for almsot 10 years and I still have holes, partly because some of it are things I haven't had to do for my job, partly because some parts of it I don't like/want to do. Most IT teams are teams, with different people who are good at different things. My cohort is going to be the one looking at most of the SQL stuff, while if there's something related to our IP phone system it'll probably be best that I take it. things like that. And like I said, pretty much anyone worth a damn in IT will be willing to help you learn/take on what you want to learn.
That's a bit of a long way of saying that I wouldn't necessarily try to learning everything before you go in. Focus on a few things, even if they're just an extension of help desk. If you can go into an interview and say "I've worked at best buy on the geek squad for 5 years and have all this experience dealing with users, and I also can do [these things] and am willing to learn these other things", You'll get some looks. With your geek squad experience though your ticket in will definitely be help desk. IT skills can be taught, especially to those who want to learn them. Someone who can actually deal with the users: that's actually a super important skill that's a lot harder to find.
I don't know if this is good advice or not (open to the thread to decide), but if you can get interviewed by an IT guy, let them know that you want to move past Geek Squad.
They will understand what the fuck you mean, and may rally to your side in that endeavor, like you're a goddamn child on the Titanic, they will get you to that lifeboat.
And on top of that, be honest when you don't know something you're being asked about. Then communicate that you want to learn and are willing to learn about anything you don't know. I think most of us would rather work with someone that knows their limitations and is willing to learn and be taught over someone that thinks they know everything.
Yea, all my cover letters basically state "I've been with Geek Squad for 5 years now and I'm looking to expand my career and look for a new challenge."
edit: Yea, I tend to hire people that say "I can use a computer but don't know a lot about fixing it" with a resume to match over guys that say "Yea I'm awesome at all the things" when their experience doesn't tell the same story.
Coincidentally i've only been allowed to hire one dude this year and out of 8 new people we've had he's the only one left :rotate:
But the management team has exiled me for being critical of their methods so i'm now brought in on any of these decisions anymore.
I don't know if this is good advice or not (open to the thread to decide), but if you can get interviewed by an IT guy, let them know that you want to move past Geek Squad.
They will understand what the fuck you mean, and may rally to your side in that endeavor, like you're a goddamn child on the Titanic, they will get you to that lifeboat.
I know I would.
This is not wrong, but it would come up in an interview anyway more than likely. "why do you want to leave your current job" or whatever variation of that question on that paticular interview will be.
Hell, even put it in your cover letter if an application requires one. "Working at the Best Buy Geek squad has been a great experience for getting my foot into the door working in a role in Information Technology, but I am ready to move on and apply those skills to a new and exciting challenge within the profession."
can you tell I've been writing a few cover letters recently? I just BS'd that in one go and it came out pretty well
I don't know if this is good advice or not (open to the thread to decide), but if you can get interviewed by an IT guy, let them know that you want to move past Geek Squad.
They will understand what the fuck you mean, and may rally to your side in that endeavor, like you're a goddamn child on the Titanic, they will get you to that lifeboat.
I know I would.
This is not wrong, but it would come up in an interview anyway more than likely. "why do you want to leave your current job" or whatever variation of that question on that paticular interview will be.
Hell, even put it in your cover letter if an application requires one. "Working at the Best Buy Geek squad has been a great experience for getting my foot into the door working in a role in Information Technology, but I am ready to move on and apply those skills to a new and exciting challenge within the profession."
can you tell I've been writing a few cover letters recently? I just BS'd that in one go and it came out pretty well
I've written that sentence in probably 12 different varieties over the last few weeks. Hell I wrote it 3 times today.
I fucking hate cover letters, but the potential job I'm aiming for is making it easy to do. Their job description pretty much did all of the work for me, lol.
While I agree that being insensitive is an issue, so is being oversensitive.
So in my resume I normally just put my work experience, education and published works. I address any skill set requirements in the cover letter explaining how my experience relates to what they are after. Should I be summing up my skill set in the resume as well? I've toyed with it but it feels clunky to me.
I fucking hate cover letters, but the potential job I'm aiming for is making it easy to do. Their job description pretty much did all of the work for me, lol.
yea, cover letters are stupid, and all they do is allow another vector for HR to search for keywords. In a prior job when I was in on the hiring process our HR department asked for cover letters, I never read one.
So in my resume I normally just put my work experience, education and published works. I address any skill set requirements in the cover letter explaining how my experience relates to what they are after. Should I be summing up my skill set in the resume as well? I've toyed with it but it feels clunky to me.
I generally list my skills, from most powerful to least powerful in a skill row.
Then I list my jobs, and what I did at each job (related to my skills), if I know numbers I put those too. "Saved $20,000 optimizing storage system" or "Designed and lead project to expand data center while under budget" or some shit.
Numbers are super powerful on resumes and cover letters.
not a doctor, not a lawyer, examples I use may not be fully researched so don't take out of context plz, don't @ me
"Successfully built and deployed the domain-wide password policy, enforcing by effectively ripping out a user's heart and devouring it in front of staff to show that my authority would be respected."
Le_Goat on
While I agree that being insensitive is an issue, so is being oversensitive.
"Successfully built and deployed the domain-wide password policy, enforcing by effectively ripping out a user's heart and devouring it in front of staff to show that my authority would be respected."
When can you start?
+3
lwt1973King of ThievesSyndicationRegistered Userregular
I just got the hiring process checklist.
IT notification seems to have been omitted.
"He's sulking in his tent like Achilles! It's the Iliad?...from Homer?! READ A BOOK!!" -Handy
life's a game that you're bound to lose / like using a hammer to pound in screws
fuck up once and you break your thumb / if you're happy at all then you're god damn dumb
that's right we're on a fucked up cruise / God is dead but at least we have booze
bad things happen, no one knows why / the sun burns out and everyone dies
Got a user to finally admit they weren't actually using that Win2k3 server VM that's been shitting up our SCOM.
Decom time!
life's a game that you're bound to lose / like using a hammer to pound in screws
fuck up once and you break your thumb / if you're happy at all then you're god damn dumb
that's right we're on a fucked up cruise / God is dead but at least we have booze
bad things happen, no one knows why / the sun burns out and everyone dies
0
Apothe0sisHave you ever questioned the nature of your reality?Registered Userregular
Exchange 2016 still contains the issue that I discovered all the years ago in Exchange 2010.
Find Public Folders does not work, it just never returns.
Even on a completely and utterly fresh environment.
file a bug
I'm...
*stifled laughter*
I'm sure they'll fix it.
life's a game that you're bound to lose / like using a hammer to pound in screws
fuck up once and you break your thumb / if you're happy at all then you're god damn dumb
that's right we're on a fucked up cruise / God is dead but at least we have booze
bad things happen, no one knows why / the sun burns out and everyone dies
+4
Apothe0sisHave you ever questioned the nature of your reality?Registered Userregular
I think I re-installed and then rolled back Exchange 2010 about 20 times over the course of the summer in which I discovered that issue.
It was over the holidays so I had little to do except play Left4Dead2 while it installed, then smash my face against the keyboard for 3 hours after it didn't work and all the recommendations failed.
0
Apothe0sisHave you ever questioned the nature of your reality?Registered Userregular
No one ever listens to me
I don't understand how I can make requirements like "YOU HAVE TO DOCUMENT THE PROCESS SO IT CAN BE REPRODUCED ON THE PRODUCTION SERVER" or explain that the same username and password will work everywhere abundantly clear, repeat it about 5 times across different conversations and within various emails and yet...
Posts
fuck up once and you break your thumb / if you're happy at all then you're god damn dumb
that's right we're on a fucked up cruise / God is dead but at least we have booze
bad things happen, no one knows why / the sun burns out and everyone dies
Nintendo Network ID: AzraelRose
DropBox invite link - get 500MB extra free.
in a more serious answer, which also comes with a question, what kind of education/experience do you actually have? If you're 100% self taught, you're going to have to start on a help desk role, and even then you're likely going to need someone to "take a chance" on you. It's a bit unfortunate but in a lot of cases people who hire look for education first, experience second.
if you have an education but no experience, you're most likely to get in on help desk still, even a jr. sysadmin role will be a bit of a stretch for someone with zero IT experience.
But here is the key: don't be complacent in what you do. Even if you're working help desk, ask to learn/take on more things. "oh, this [non help desk thing] needs to be taken care of this week? Let me take a look at it when I have some extra time." Ask to help out on projects, take on extra tasks. sit in on meetings/project planning that might not necessarily be in your wheelhouse.
The key is: learn. Never stop learning. Ask questions. Any sysadmin/IT person worth a damn will be more than happy to help/share/pawn work off, because it means less work for them.
*may not be for everyone
Yea, I don't have a degree
I currently work for Geek Squad doing advanced work, I was working toward management but am tired of the bureaucratic BS, I've been doing that for 5 years now. I've been studying on my own and do stuff like penetration testing with some coworkers as a hobby. I write articles for the knowledge base and do face to face and phone support. I pretty much fall under "Jack of all trades" when it comes to IT. I know a bit of everything but more importantly I have the skills to find out anything I don't know and I'm not afraid to ask questions. I've been looking for enterprise help desk work but the search is pretty slow. I'm looking for Junior/Associate admin stuff so that I can work with something and get a clear path to the knowledge that I need to work on, I've been mentoring people in GS so long and not had a mentor of my own that I've just kind of hit a wall and am having trouble developing further.
I know I need to learn SQL, and I'm not sure where to fit that in. I get a couple hours a week to study stuff on my own and its currently going to Redhat, I have a working understanding of *nix systems and really am trying to find a way to put my knowledge to use because reading text books and doing little projects here and there isn't a replacement for practical application.
The thing is that nowadays, sysadmin is such a vague term. Some of us are fantastic with Cisco products; some aren't. Some know backups inside and out; some know enough to just get by. Some deal with a lot of SQL; some barely touch it. Hell, some sysadmins are that because no one else knows how to do it.
If you are really wanting to get into the sysadmin territory, your best bet would be to look for a place that has the ability to train you on the finer aspects, which means you'll still be starting out at help desk and working your way up. Speaking from personal experience, make sure it is a place that actually has an up. There is nothing more demoralizing that not having the ability to climb the ladder; either that or your ladder is like mine, which is a step stool with wheels, so as soon as you're on, that's the highest you can go.
Once you get into a place and start to solidify yourself as a member of the team, start talking to your superiors about what knowledge would help you help them, and then see if your company will pay for training; totally take advantage of them if it is available.
EDIT: Another big thing to get smart on is virtualization. That's a pretty big these days. If you can expose yourself to virtualization, it's a good talking point. Also Exchange... definitely exchange management.
Cloud virtualization is a whole different boat. I can't speak for Azure, but AWS uses weird jargon that takes some used to getting used to. It's not terribly hard, just crazy annoying.
Also, when it comes time to have an interview, do not be ashamed to admit you don't know something. Trying to say you know something that you know zero about is just going to fuck you over.
I work the counter at a geek squad in Seattle, I talk to my clients the same way I talk to my 2 year old.
I'm not sure how many of you are versed in Microsoft KMS, which is Key Management Service. It's a volume license tool for microsoft products, allows you to have your VL versions of windows phone home to a server to stay activated. They've been using it since Server 2008/Vista for most of their volume license setups. It's just a service you run on 1 or 2 servers on the domain. You basically stick a KMS key into that OS, and then it can successfully activate any version of windows. i.e. for Server 2012 R2 you stick in the KMS key for 2012 R2 and it'll activate every server/client OS Vista and up.
I've learned a lot about it in the past week because all of the sudden most of the computers we have suddently decided they weren't activated anymore, including our servers.
KMS had been set up here long before either myself or my cohort worked here, and neither of us knew anything about it. There's no real UI for it anywhere, it only exists as a CLI level service that takes about 4 commands to turn on, and one DNS entry. Now, this thing doesn't have to phone home constantly. A PC that's authenticated against KMS is good for 180 days, so it only has to check in twice a year really. It'll try to check in once a week, and has 6 months to ping the server before Windows starts yelling.
So, about a month ago we had a couple computers lose their activateion, but they were field machines that haven't been seen in forever but whatever. Then we had a computer on the domain bitch about activation, which was weird but whatever. Then suddenly one day I log onto a server and it tells me that I need to activate windows. Then by the end of the day I had 20 calls from users about it. I traced it back to KMS, then had to figure out how KMS worked, and found the DNS entry for the KMS server in the domain.....a old domain controller we decommissioned about 6 months ago, not having any idea KMS was actually running on it. So, set up a KMS server on the new domain controller, Server 2012 R2 actually has a bit of a gui for adding it as a role now, which is kinda nice, and boom it was done. After I confirmed machines were starting to check in, I set it up on the secondary domain controller as well as a backup. That's when you'd think the story is done.
The next day, today, I look at a test machine to see if it is activated, and it isn't, and won't activate. So I go look into it. When I set up the second KMS server from the GUI, instead of it auto creating another DNS entry, it replaced the one from the primary server. Apparently that's a bug/feature in KMS in 2012 R2. Now you'd think that it shouldn't matter as the devices should authenticate against the backup server then. Except that, for some reason, the firewall on the second domain controller was on(we normally keep it off), and that port was blocked. unblocked the port and machines started to authenticate to the backup. Added the DNS rule back for the primary, and that came back up as well.
So now all of our client machines, and our servers, are activated again. :rotate:
So there you have it.
I'm not saying that's the way to do it, because there are some huge hurdles I've had to deal with because of this, and that point of entry is definitely a lottery ticket. But given your current experience with what you do, I don't see any reason you couldn't throw 5 years of Geek Squad experience on a resume to get a Help Desk I or II position at a company that has higher positions available.
And like wunderbar said, grab projects. Ask if you can help. That's how almost everyone promotes in this industry, is they display aptitude with more than consoling a grieving coworker over their missing spreadsheet. This biz can be kinda competitive, but in my experience people also tend to know the score, and lean on you if you keep delivering results. Just make sure you lean on them for your pay and time, when that happens.
yea if you have a Windows Pro license you can install hyper-v onto it. Gleam what you can from that.
Also, don't be super afraid if there are big holes in your skillset. I've been workign in IT for almsot 10 years and I still have holes, partly because some of it are things I haven't had to do for my job, partly because some parts of it I don't like/want to do. Most IT teams are teams, with different people who are good at different things. My cohort is going to be the one looking at most of the SQL stuff, while if there's something related to our IP phone system it'll probably be best that I take it. things like that. And like I said, pretty much anyone worth a damn in IT will be willing to help you learn/take on what you want to learn.
That's a bit of a long way of saying that I wouldn't necessarily try to learning everything before you go in. Focus on a few things, even if they're just an extension of help desk. If you can go into an interview and say "I've worked at best buy on the geek squad for 5 years and have all this experience dealing with users, and I also can do [these things] and am willing to learn these other things", You'll get some looks. With your geek squad experience though your ticket in will definitely be help desk. IT skills can be taught, especially to those who want to learn them. Someone who can actually deal with the users: that's actually a super important skill that's a lot harder to find.
They will understand what the fuck you mean, and may rally to your side in that endeavor, like you're a goddamn child on the Titanic, they will get you to that lifeboat.
I know I would.
edit: Yea, I tend to hire people that say "I can use a computer but don't know a lot about fixing it" with a resume to match over guys that say "Yea I'm awesome at all the things" when their experience doesn't tell the same story.
Coincidentally i've only been allowed to hire one dude this year and out of 8 new people we've had he's the only one left :rotate:
But the management team has exiled me for being critical of their methods so i'm now brought in on any of these decisions anymore.
This is not wrong, but it would come up in an interview anyway more than likely. "why do you want to leave your current job" or whatever variation of that question on that paticular interview will be.
Hell, even put it in your cover letter if an application requires one. "Working at the Best Buy Geek squad has been a great experience for getting my foot into the door working in a role in Information Technology, but I am ready to move on and apply those skills to a new and exciting challenge within the profession."
I've written that sentence in probably 12 different varieties over the last few weeks. Hell I wrote it 3 times today.
yea, cover letters are stupid, and all they do is allow another vector for HR to search for keywords. In a prior job when I was in on the hiring process our HR department asked for cover letters, I never read one.
I generally list my skills, from most powerful to least powerful in a skill row.
Then I list my jobs, and what I did at each job (related to my skills), if I know numbers I put those too. "Saved $20,000 optimizing storage system" or "Designed and lead project to expand data center while under budget" or some shit.
Numbers are super powerful on resumes and cover letters.
When can you start?
IT notification seems to have been omitted.
:hydra:
fuck up once and you break your thumb / if you're happy at all then you're god damn dumb
that's right we're on a fucked up cruise / God is dead but at least we have booze
bad things happen, no one knows why / the sun burns out and everyone dies
What are you going to do? Set up an account for them or something stupid like that?
XBL:Phenyhelm - 3DS:Phenyhelm
Sounds like every place I've ever worked.
3 possibilities exist:
1. They are never going to hire nor fire anyone, ever again. And if someone quits, they will chain them to their desk.
2. They are going to just stop notifying you, and passive-aggressively put notes on your desk letting you know that the new users can't log in.
3. Your department no longer exists!
I mean, there might be other explanations, but I prefer these.
I thought notification was the call on Monday (or whatever) morning demanding answers as to why:
New hire doesn't have:
a-computer
b-cell phone
c-account
d-badge access
e-world peace)
Got a user to finally admit they weren't actually using that Win2k3 server VM that's been shitting up our SCOM.
Decom time!
fuck up once and you break your thumb / if you're happy at all then you're god damn dumb
that's right we're on a fucked up cruise / God is dead but at least we have booze
bad things happen, no one knows why / the sun burns out and everyone dies
it worked.
go little server, go
Exchange 2016 still contains the issue that I discovered all the years ago in Exchange 2010.
Find Public Folders does not work, it just never returns.
Even on a completely and utterly fresh environment.
file a bug
I'm...
*stifled laughter*
I'm sure they'll fix it.
fuck up once and you break your thumb / if you're happy at all then you're god damn dumb
that's right we're on a fucked up cruise / God is dead but at least we have booze
bad things happen, no one knows why / the sun burns out and everyone dies
It was over the holidays so I had little to do except play Left4Dead2 while it installed, then smash my face against the keyboard for 3 hours after it didn't work and all the recommendations failed.
I don't understand how I can make requirements like "YOU HAVE TO DOCUMENT THE PROCESS SO IT CAN BE REPRODUCED ON THE PRODUCTION SERVER" or explain that the same username and password will work everywhere abundantly clear, repeat it about 5 times across different conversations and within various emails and yet...