IT Interview regarding windows 2003/2008

fazsnatch

Hi,

I have got an interview coming for windows 2003/2008 and windows implementation who will ask a few basic questions. Just wondering what should i cover and revise regarding this?

I do have a year of experience with 2003 and 2008 but i am not sure what they may cover in terms of the basics as there is a lot to cover.

Just wondering if anyone give me some advice or tips be greatly appreciated.

Thanks all

MrAgent

I would imagine that they would ask you about FSMO roles and DNS. DNS is by far the thing that caused the most problems for me.

-Foxer-

A lot of the interviews I've been in lately are less technical in nature, and they ask me about things I've worked with, and things I've done; what kind of projects I've worked on, etc. So I'd be ready for that too.

fazsnatch

This is going to be a telephone interview and they said it will cover basics of windows 2003/2008 but i am not sure what that be. I did a lot of server management, just nervous i may screw up as i telephone interviews can be a pain

phoeneous

fazsnatch wrote: »

This is going to be a telephone interview and they said it will cover basics of windows 2003/2008 but i am not sure what that be. I did a lot of server management, just nervous i may screw up as i telephone interviews can be a pain

Whats to screw up? If they ask you something that you dont know then just say "I dont know". Always answer honestly.

erpadmin

phoeneous wrote: »

Whats to screw up? If they ask you something that you dont know then just say "I dont know". Always answer honestly.

With all due respect, "I don't know" is a sure way to not get hired. Seriously, anyone could hire anyone with that logic.

Yes, one should always be honest about a skillset they may be lacking in, but merely saying "I don't know" is never good. You should focus on your strengths in something you are not sure of, and demonstrate that you are willing to shore up on something you're lacking.


Not for nothing, but every job has a minimum spec that they are asking for. Be willing to at a minimum be familiar with what an interviewer is asking you. However, focus on your strengths.

There wasn't any interview I've been on where I knew everything. Anyone who claims they know everything about everything is full of ---- and that will show. Interviewers are aware of this and as long as you demonstrate a willingness to show that you are competent will put you ahead of any candidate. Sell your strengths and be aware of your weaknesses and show you can overcome them. But never say "I don't know...."

mark_s0

I'd guess at revising basic services - AD, DNS basics i.e. record types, lookup process, DHCP, permissions. The last interview for a sys-admin position I had, I had those plus RAID concepts, restoring a broken DC and basic networking.

As others have said, focus on strengths and be honest. If you don't know something, showing you're willing and resourceful is better than just saying I don't know. It didn't stop me from getting a 2nd interview.

Everyone

MrAgent wrote: »

I would imagine that they would ask you about FSMO roles and DNS. DNS is by far the thing that caused the most problems for me.

Having a solid understanding of DNS will get you far. It always amazes me how many people just don't seem to get DNS. It always seemed simple to me.

When it comes to Windows environments, you need to take your DNS knowledge a step further and learn AD integrated DNS. Knowing what SRV records are, where they are, and what needs them, is really useful.

Devilsbane

erpadmin wrote: »

With all due respect, "I don't know" is a sure way to not get hired. Seriously, anyone could hire anyone with that logic.

Making something up and being wrong is a sure way not to get hired. Honesty is always the best policy.

If you answer "I don't know" to every question then you don't deserve the job. If it happens once or twice, no big deal. If you answer a question incorrectly? Even a single one and your name is probably crossed off the list.

It can be worded better than I don't know, something along the lines of... "You know, I have never had the chance to work with XYZ but it has been something that has been on my todo list for awhile now and I would look forward to learning how to use it."

Everyone wrote: »

Having a solid understanding of DNS will get you far. It always amazes me how many people just don't seem to get DNS. It always seemed simple to me.

When it comes to Windows environments, you need to take your DNS knowledge a step further and learn AD integrated DNS. Knowing what SRV records are, where they are, and what needs them, is really useful.

+1 to this. People like to ask DNS questions because they aren't overly complicated but can knock a number of people on their butts.

rsutton

It's broad topic but you could expect questions on DNS, Active Directory, Exchange, backup and restore procedures, Virtulization, RAID, Storage, RRAS, IIS, Power Shell and DHCP, to name a few. Each subject could have it's own book written on it, so hopefully you have at least basic understanding of these technologies.

Everyone

Instead of just "I don't know", try:
"I don't know, but I will find out."
"I'm not sure off the top of my head, but I know where to look for the right answer."

etc.

Devilsbane

Everyone wrote: »

Instead of just "I don't know", try:
"I don't know, but I will find out."
"I'm not sure off the top of my head, but I know where to look for the right answer."

etc.

That is a great way to handle once on the job, I question how it would work in an interview. Just my $.02

Everyone

Devilsbane wrote: »

That is a great way to handle once on the job, I question how it would work in an interview. Just my $.02

Worked great for me.

killwar

I really don't think you should be given the job ... firstly are you even mcsa/mcse or mcitp sa/ea certified ? i guess not, that's why you don't know simple things.

if i were your recruiter i wouldn't want to waste your time and mine doing this intertiew.my suggestion is leave that job offer to someone else and attend a mcse/mcitp training , till you get a similar job offer and hopefully that will make you more confident about just more that basic things instead of learning bits and bits of answers about what to cover or not.

pham0329

killwar wrote: »

I really don't think you should be given the job ... firstly are you even mcsa/mcse or mcitp sa/ea certified ? i guess not, that's why you don't know simple things.

if i were your recruiter i wouldn't want to waste your time and mine doing this intertiew.my suggestion is leave that job offer to someone else and attend a mcse/mcitp training , till you get a similar job offer and hopefully that will make you more confident about just more that basic things instead of learning bits and bits of answers about what to cover or not.

Wow, what a stupid advice. Whether he has an MCSE or MCITP is irrelevant, there are plenty of people out there who knows what they're doing, and doesn't have the cert.

You haven't read the job description, nor do you know how much the OP knows, so how do you know it won't be a good fit? Part of the reason where I am today is that I took jobs that had me working with technologies that I haven't worked with before. Learning on the job is one of the best ways to learn.

erpadmin

Devilsbane wrote: »

Making something up and being wrong is a sure way not to get hired. Honesty is always the best policy.

If you answer "I don't know" to every question then you don't deserve the job. If it happens once or twice, no big deal. If you answer a question incorrectly? Even a single one and your name is probably crossed off the list.

It can be worded better than I don't know, something along the lines of... "You know, I have never had the chance to work with XYZ but it has been something that has been on my todo list for awhile now and I would look forward to learning how to use it."

That's pretty much the gist of my answer....I did not imply you "make something up and be wrong" at all...in fact you shouldn't. My whole issue if you start answering a bunch of questions with I don't know (especially with no follow through), that offer letter is pretty much not going to come.

My point was to not have the phrase "I don't know" in your vocabulary. Just offer some familiarity with what's being asked and always be truthful with what is stated.

WiseWun

Make sure you know a little bit of Exchange, I'm sure their going to ask. Also command line tools such as nslookup, and oh dont forget GPO's! Good luck and report back on whatbthey asked.

Blackout

erpadmin wrote: »

With all due respect, "I don't know" is a sure way to not get hired. Seriously, anyone could hire anyone with that logic.

Yes, one should always be honest about a skillset they may be lacking in, but merely saying "I don't know" is never good. You should focus on your strengths in something you are not sure of, and demonstrate that you are willing to shore up on something you're lacking.


Not for nothing, but every job has a minimum spec that they are asking for. Be willing to at a minimum be familiar with what an interviewer is asking you. However, focus on your strengths.

There wasn't any interview I've been on where I knew everything. Anyone who claims they know everything about everything is full of ---- and that will show. Interviewers are aware of this and as long as you demonstrate a willingness to show that you are competent will put you ahead of any candidate. Sell your strengths and be aware of your weaknesses and show you can overcome them. But never say "I don't know...."

I would have to disagree with this statement, Im not in networking atm but human nature is the same everywhere you go. When I got my first CDQAR as a parachute inspector, our QA officer sat me down for two hours asking me questions about procedures, the namp publications, if I didn't know the answer I told him that I would need to read up more and get a better in depth knowledge of that particular system.
If you show your Honest and sincere they will respect that more than trying a bullshit answer, Im not perfect, and I don't know everything about a parachute, when I don't know you bet your ass my face is in a book learning it.

pham0329

Blackout wrote: »

I would have to disagree with this statement, Im not in networking atm but human nature is the same everywhere you go. When I got my first CDQAR as a parachute inspector, our QA officer sat me down for two hours asking me questions about procedures, the namp publications, if I didn't know the answer I told him that I would need to read up more and get a better in depth knowledge of that particular system.
If you show your Honest and sincere they will respect that more than trying a bullshit answer, Im not perfect, and I don't know everything about a parachute, when I don't know you bet your ass my face is in a book learning it.

I don't think erpadmin is telling the OP to BS his way through the interview if he doesn't know the question, he's simply stating that an "I don't know" respond to multiple questions will unlikely lead to an offer letter.

Blackout

pham0329 wrote: »

I don't think erpadmin is telling the OP to BS his way through the interview if he doesn't know the question, he's simply stating that an "I don't know" respond to multiple questions will unlikely lead to an offer letter.

Cool I understand

erpadmin

pham0329 wrote: »

I don't think erpadmin is telling the OP to BS his way through the interview if he doesn't know the question, he's simply stating that an "I don't know" respond to multiple questions will unlikely lead to an offer letter.

Exactly, thank you, and rep.

Edit: Apparently I repped you for something else that I agreed with. Will have to spread the love. LOL. Thank you for the clarification all the same.