I will be wrapping up my W2k MCSE cert soon. I need 2 more exams. I have a
question for those of you who are network admins already. I have a solid
knowledge of all things microsoft sofar (DNS,DHCP,WINS,TCPIP etc.) I have
limited network exp.( small NT4 peer to peer at work, home network w/4
computers). My question is what are the most common things administrators
and their assistants do on a day to day basis. I know this is a broad
question but since I am so close to getting the MCSE I would like to make
sure I am proficient on some of the everyday tasks. I know I won't be
designing networks right away and will have to pay my dues but I want to be
prepared and ready to do the basics. Any comments would be appreciated.
TIA....Dave

Report this post to a moderator

Helping people log in to the network. Really. Either they've forgotten
their password, or someone else has logged on through their computer, and
they can't remember their username (by default the last username to
successfully log in remains in the box), or the domain isn't correct. I've
been doing PC support at a company for about 3 years now, and this is
probably my #1 call.

smackedass


My question is what are the most common things administrators
>and their assistants do on a day to day basis.

Report this post to a moderator

You asked for it! You're getting it....

Daily:
--------
Check event log of every server, fix/try to fix as needed.
Creating new directories, shares, and security groups, new accounts,
disabling/deleting old accounts, managing account policies.
Make sure backup runs and verify the files.
Plugging Security holes.
Exchange Management including DL's, users, etc.
Train the training people, helpdesk people, and end users.
Answer all important emails from CFO/CEO/IT-MIS Director.
Glance over DSU/TSU, switches, hubs, make sure everything is green.
Check router logs.
Check firewall logs.
Various calls to MS Support for things that really aren't your fault.
Check for free space on all servers, for file pollution and quotas.
Ensure that all server services are running.
Ensure that antivirus definitions are up-to-date.
Run defrag and chkdsk on all drives.
Monitor WINS replication.
Monitor directory replication.
Maintain performance baseline data.
Monitor network traffic with sniffer or NETMON to keep performance up.
Keep Service Pack and Hotfixes current as per company policy.
Monitor Web traffic for indications of attacks.
Install software for users
Monitor user email for corporate policy violations.
Check Print Queues.
Keep a log of everything you have fixed or performed maintenance on.
Make sure all apps are shared.
Permissions and filesystem management.
Check for bad system and ini files on database server (Btrieve).
Make sure load on database server is acceptable and ghosted users
are cleared as well as multiple logons.


Nightly:
--------
Backups
(Next Applies to Terminal Server admins only)
Reboot each Citrix server.
Delete all autocreated printers stuck.
Clear out rogue local profiles.
Backups

Weekly:
-------
Clean Servers, check for .tmp files, jetdb files, etc.
Implement any new policy, permission, logon script, or scheduled
script modifications.
Research, Research, Research.
Change any active monitoring & alerting (third party tools) as needed.
Update Website, External and Intranet, send website log reports.
Check PerfMon, NetMon, (or 3rd party tools) for OK baselines.
Reboot Servers if needed.
Keep up-to-date on IT news regarding my networks.
Evaluate software for System Admin purposes.
Try to get some MCSE study time in.
Performance Monitoring/Capacity Planning- Budgeting for the future.
Uptime/Downtime reports.
Auditing network for unauthorized changes, ideally both from the
inside but also outside-in.
Plan for W2K migration.

Monthly:
---------
Rebuild Databases as needed.
Gather statistics on Webservers. Send to CEO/CIO/CTO/CFO (Whomever).
Clean exchange mailboxes.
Change Service Account Passwords (not doing this is russian roulette).
Convincing your boss that most of this stuff _needs_ to be done.
Extended testing backups with restores.
Maintaining applicable Service Level Agreements.
Set System and Application priorities: If more than one thing is
broken, what needs to be fixed first.
Managing off-site storage of backup tapes, whether you take them
home or a service picks them up.
IT System vulnerability analysis: like "This mail server uses this
mail router- what's the impact if one or both are down (if mail
server is down mail router will store inbound mail and may run out
of disk space).
Periodically reviewing all of the above, is documentation up to
date? Has the Disaster Recovery Plan been updated to reflect
changes in the environment?
Periodically reviewing workload. Are some things no longer done?
Periodically review company technical environment. How can it
be improved?


Initial or Occasionally.
------------------------
Disaster Recovery to alternate site, in case of emergency.
Configure and maintain DNS - Internal and External, DHCP, WINS,
TCP/IP, etc.
Document the full network.
Rebuild corrupt servers.
Test the Restore Procedure.
Reconfigure domain structure.. again.
Get a performance baseline for things like %Processor Time,
Pagefiling, Disk Queues.
Initial checklist should include status of administrative and
service passwords, status of the backups, check out DHCP scope(s),
WINS, DNS, remove unnecessary protocols.

Lastlly, dream to have a job without pagers or cell phone to contact you
24/7 (or winning the Super Lotto)!

Good Luck on your certification,
JayBeeOH

"Eyeofmars" <nobody@nowhere.com> wrote in message
news:kA9O8.156528$4i.14185140@bin2.nnrp.aus1.giganews.com...
> I will be wrapping up my W2k MCSE cert soon. I need 2 more exams. I have a
> question for those of you who are network admins already. I have a solid
> knowledge of all things microsoft sofar (DNS,DHCP,WINS,TCPIP etc.) I have
> limited network exp.( small NT4 peer to peer at work, home network w/4
> computers). My question is what are the most common things administrators
> and their assistants do on a day to day basis. I know this is a broad
> question but since I am so close to getting the MCSE I would like to make
> sure I am proficient on some of the everyday tasks. I know I won't be
> designing networks right away and will have to pay my dues but I want to
be
> prepared and ready to do the basics. Any comments would be appreciated.
> TIA....Dave
>
>

Report this post to a moderator

Hahaha outstanding... although I have passed some of that stuff off to help
desk personel. You did forget to mention answering stupid questions while
walking down hallways towards the data center.

Bob
"jaybee" <jaybeeoh@hotmail.com> wrote in message
news:CfcO8.3098$oC3.3373404@news2.news.adelphia.net...
> You asked for it! You're getting it....
>
> Daily:
> --------
> Check event log of every server, fix/try to fix as needed.
> Creating new directories, shares, and security groups, new accounts,
> disabling/deleting old accounts, managing account policies.
> Make sure backup runs and verify the files.
> Plugging Security holes.
> Exchange Management including DL's, users, etc.
> Train the training people, helpdesk people, and end users.
> Answer all important emails from CFO/CEO/IT-MIS Director.
> Glance over DSU/TSU, switches, hubs, make sure everything is green.
> Check router logs.
> Check firewall logs.
> Various calls to MS Support for things that really aren't your fault.
> Check for free space on all servers, for file pollution and quotas.
> Ensure that all server services are running.
> Ensure that antivirus definitions are up-to-date.
> Run defrag and chkdsk on all drives.
> Monitor WINS replication.
> Monitor directory replication.
> Maintain performance baseline data.
> Monitor network traffic with sniffer or NETMON to keep performance up.
> Keep Service Pack and Hotfixes current as per company policy.
> Monitor Web traffic for indications of attacks.
> Install software for users
> Monitor user email for corporate policy violations.
> Check Print Queues.
> Keep a log of everything you have fixed or performed maintenance on.
> Make sure all apps are shared.
> Permissions and filesystem management.
> Check for bad system and ini files on database server (Btrieve).
> Make sure load on database server is acceptable and ghosted users
> are cleared as well as multiple logons.
>
>
> Nightly:
> --------
> Backups
> (Next Applies to Terminal Server admins only)
> Reboot each Citrix server.
> Delete all autocreated printers stuck.
> Clear out rogue local profiles.
> Backups
>
> Weekly:
> -------
> Clean Servers, check for .tmp files, jetdb files, etc.
> Implement any new policy, permission, logon script, or scheduled
> script modifications.
> Research, Research, Research.
> Change any active monitoring & alerting (third party tools) as needed.
> Update Website, External and Intranet, send website log reports.
> Check PerfMon, NetMon, (or 3rd party tools) for OK baselines.
> Reboot Servers if needed.
> Keep up-to-date on IT news regarding my networks.
> Evaluate software for System Admin purposes.
> Try to get some MCSE study time in.
> Performance Monitoring/Capacity Planning- Budgeting for the future.
> Uptime/Downtime reports.
> Auditing network for unauthorized changes, ideally both from the
> inside but also outside-in.
> Plan for W2K migration.
>
> Monthly:
> ---------
> Rebuild Databases as needed.
> Gather statistics on Webservers. Send to CEO/CIO/CTO/CFO (Whomever).
> Clean exchange mailboxes.
> Change Service Account Passwords (not doing this is russian roulette).
> Convincing your boss that most of this stuff _needs_ to be done.
> Extended testing backups with restores.
> Maintaining applicable Service Level Agreements.
> Set System and Application priorities: If more than one thing is
> broken, what needs to be fixed first.
> Managing off-site storage of backup tapes, whether you take them
> home or a service picks them up.
> IT System vulnerability analysis: like "This mail server uses this
> mail router- what's the impact if one or both are down (if mail
> server is down mail router will store inbound mail and may run out
> of disk space).
> Periodically reviewing all of the above, is documentation up to
> date? Has the Disaster Recovery Plan been updated to reflect
> changes in the environment?
> Periodically reviewing workload. Are some things no longer done?
> Periodically review company technical environment. How can it
> be improved?
>
>
> Initial or Occasionally.
> ------------------------
> Disaster Recovery to alternate site, in case of emergency.
> Configure and maintain DNS - Internal and External, DHCP, WINS,
> TCP/IP, etc.
> Document the full network.
> Rebuild corrupt servers.
> Test the Restore Procedure.
> Reconfigure domain structure.. again.
> Get a performance baseline for things like %Processor Time,
> Pagefiling, Disk Queues.
> Initial checklist should include status of administrative and
> service passwords, status of the backups, check out DHCP scope(s),
> WINS, DNS, remove unnecessary protocols.
>
> Lastlly, dream to have a job without pagers or cell phone to contact you
> 24/7 (or winning the Super Lotto)!
>
> Good Luck on your certification,
> JayBeeOH
>
> "Eyeofmars" <nobody@nowhere.com> wrote in message
> news:kA9O8.156528$4i.14185140@bin2.nnrp.aus1.giganews.com...
> > I will be wrapping up my W2k MCSE cert soon. I need 2 more exams. I have
a
> > question for those of you who are network admins already. I have a solid
> > knowledge of all things microsoft sofar (DNS,DHCP,WINS,TCPIP etc.) I
have
> > limited network exp.( small NT4 peer to peer at work, home network w/4
> > computers). My question is what are the most common things
administrators[col
or=green]
> > and their assistants do on a day to day basis. I know this is a broad
> > question but since I am so close to getting the MCSE I would like to[/color]
make
> > sure I am proficient on some of the everyday tasks. I know I won't be
> > designing networks right away and will have to pay my dues but I want to
> be
> > prepared and ready to do the basics. Any comments would be appreciated.
> > TIA....Dave
> >
> >
>
>

Report this post to a moderator

I remember one contract I had as a young tech (just an A+ MCP, before
I got my MCSE), doing mostly workstation admin. Rule number one laid
down for me by the deputy IT mgr:

- If ever I logged in to a user's PC using an admin account (eg, local
admin), I _HAD_ to login to the normal user domain, using the account
of the PC's normal user, when I'd finished with the machine (and then
logout again) -- otherwise they wouldn't know how to login themselves,
since they didn't know how to read the details on the login dialogue,
or anything more complex than type the password; and they'd make a
help-desk call, which didn't look good in the stats.

At least if the user wasn't at his desk I didn't have far to go to
find his password -- it was invariably written on a post-it note stuck
to the side of the monitor....

I wondered why they bothered having passwords, let alone a policy that
required they be changed monthly.

--
rgds
DVD

(David Brownridge) <mailtoVD@melbpc.org.au>


"smackedass" <nospamkema@capecod.net> wrote in message
news:%lbO8.1528$Uz5.106925@newsread2.prod.itd.earthlink.net...

> Helping people log in to the network. Really. Either they've
forgotten
> their password, or someone else has logged on through their
computer, and
> they can't remember their username (by default the last username to
> successfully log in remains in the box), or the domain isn't
correct. I've
> been doing PC support at a company for about 3 years now, and this
is
> probably my #1 call.

Report this post to a moderator

I'll highlight a few of the big hot items- This is a really good list, I'm
impressed. I have to say this is what you'll be doing, but a couple things
are missing, or some things are much larger than others. I'm just trying to
help with some of the priorities. Some of this too, depends on your
environment, ie what you control, what types of servers you have, etc. I put
comments by some and s put a * next to ones that I think are high priorities
(do these first, they should all be done in this list, very impressive
list!)

Picture this: 5 people need rights, a web server is down, someones email is
gone, your boss is paging you, the backup tapes needed for today were not
delivered, the vps harddrive died - he walks up to you even though you don't
do desktops, and you feel sick, and it's only 8:30am. You're scheduled for
meetings for about 4-5 hours (if you're in a senoir position) and guess
what, you're the only one who has access to do some of the special project
stuff, directory creations, whatever. Of course, the meetings won't be
productive, and you'll probably hear people ramble on about things decided
the previous two months. You'll ask yourself, why am I here? Is this why I
got the MCSE? You'll be praised when it's convenient, but forgotten about
when raises come around. (joke)

Don't get me wrong, I love IT, but I want you to have a real idea of what
you're walking into. if you like fast-paced environments you'll love it. Not
all places are like that. Some are more laid back. Do what jaybee's done,
create a some checklists and go through them. Make yourself do it. Some
admins can't handle it, but others like jaybee here (from what it sounds
like) really have their stuff together. You should strive to be that sort of
admin. From what I've seen, all of the good admins have checklists (not just
server guys) and they go through them religiously.

LOGIN SCRIPTS will make your life easier, and the desktop teams
study up on this, this isn't stressed very much in the MCSE material (not to
my liking) but this will
help you more than you probably realize now - you'd be amazed at who can and
can't write a batch file
Also, don't do something dumb like put a pause in the login script, good
admins hate fixing other admins mistakes
Also, you'll make mistakes, but learn from them- that's really important

"jaybee" <jaybeeoh@hotmail.com> wrote in message
news:CfcO8.3098$oC3.3373404@news2.news.adelphia.net...
> You asked for it! You're getting it....
>
> Daily:
> --------
> Check event log of every server, fix/try to fix as needed.
> Creating new directories, shares, and security groups, new accounts,
*> disabling/deleting old accounts, managing account policies.
*> Make sure backup runs and verify the files.
*unless you like the idea of realoading all of your servers and restoring
from tape (worst case scenario and being fired once you're done) -> Plugging
Security holes.
*if this happens just leave hehe
*> Exchange Management including DL's, users, etc.
> Train the training people, helpdesk people, and end users.
*> Answer all important emails from CFO/CEO/IT-MIS Director.
*> Glance over DSU/TSU, switches, hubs, make sure everything is green.
*> Check router logs.
*> Check firewall logs.
AN IDS would help here - maybe, but first things first right
> Various calls to MS Support for things that really aren't your fault.
******(get the idea?)> Check for free space on all servers, for file
pollution and quotas.
*> Ensure that all server services are running.
*> Ensure that antivirus definitions are up-to-date.
> Run defrag and chkdsk on all drives.
> Monitor WINS replication.
> Monitor directory replication.
> Maintain performance baseline data.
> Monitor network traffic with sniffer or NETMON to keep performance up.
This really depends, if you're switched and segmented well you don't have to
worry
but it's good to keep tabs on it
******> Keep Service Pack and Hotfixes current as per company policy.
****** - again IDS - > Monitor Web traffic for indications of attacks.
> Install software for users
> Monitor user email for corporate policy violations.
*> Check Print Queues.
*> Keep a log of everything you have fixed or performed maintenance on.
> Make sure all apps are shared.
*> Permissions and filesystem management.
> Check for bad system and ini files on database server (Btrieve).
> Make sure load on database server is acceptable and ghosted users
> are cleared as well as multiple logons.
>
>
> Nightly:
> --------
> Backups
> (Next Applies to Terminal Server admins only)
> Reboot each Citrix server.
> Delete all autocreated printers stuck.
> Clear out rogue local profiles.
> Backups
>
> Weekly:
> -------
> Clean Servers, check for .tmp files, jetdb files, etc.
> Implement any new policy, permission, logon script, or scheduled
> script modifications.
> Research, Research, Research.
> Change any active monitoring & alerting (third party tools) as needed.
> Update Website, External and Intranet, send website log reports.
> Check PerfMon, NetMon, (or 3rd party tools) for OK baselines.
> Reboot Servers if needed.
This depends on your environment - not possible in a 24x7 shop
and yes NT can actually run stabilly for months - if yours isn't you've done
something wrong
or someone's causing a problem for you
> Keep up-to-date on IT news regarding my networks.
> Evaluate software for System Admin purposes.
> Try to get some MCSE study time in.
> Performance Monitoring/Capacity Planning- Budgeting for the future.
* - try to automate this if you can - lots of tools exist, good idea to look
at
to figure out where your problmes are
> Uptime/Downtime reports.
*> Auditing network for unauthorized changes, ideally both from the
> inside but also outside-in.
> Plan for W2K migration.
Ohhhh, hehe, this is not for newbies, if you're new put it off a few months
till
you're more confortable
>
> Monthly:
> ---------
> Rebuild Databases as needed.
*> Gather statistics on Webservers. Send to CEO/CIO/CTO/CFO (Whomever).
hehe, i guess everyone has to do this
> Clean exchange mailboxes.
> Change Service Account Passwords (not doing this is russian roulette).
** don't get me started> Convincing your boss that most of this stuff
_needs_ to be done.
> Extended testing backups with restores.
*this is actually a huge beast - i warned you > Maintaining applicable
Service Level Agreements.
> Set System and Application priorities: If more than one thing is
> broken, what needs to be fixed first.
* - this will save your butt > Managing off-site storage of backup tapes,
whether you take them
> home or a service picks them up.
> IT System vulnerability analysis: like "This mail server uses this
> mail router- what's the impact if one or both are down (if mail
> server is down mail router will store inbound mail and may run out
> of disk space).
> Periodically reviewing all of the above, is documentation up to
> date? Has the Disaster Recovery Plan been updated to reflect
> changes in the environment?
> Periodically reviewing workload. Are some things no longer done?
> Periodically review company technical environment. How can it
> be improved?
>
>
> Initial or Occasionally.
> ------------------------
> Disaster Recovery to alternate site, in case of emergency.
> Configure and maintain DNS - Internal and External, DHCP, WINS,
> TCP/IP, etc.
> Document the full network.
*> Rebuild corrupt servers.
* - do this before you do your first restore ! > Test the Restore Procedure.
> Reconfigure domain structure.. again.
> Get a performance baseline for things like %Processor Time,
> Pagefiling, Disk Queues.
> Initial checklist should include status of administrative and
> service passwords, status of the backups, check out DHCP scope(s),
> WINS, DNS, remove unnecessary protocols.
>
> Lastlly, dream to have a job without pagers or cell phone to contact you
* hehe - This is a must! > 24/7 (or winning the Super Lotto)!
>
> Good Luck on your certification,
> JayBeeOH
>
> "Eyeofmars" <nobody@nowhere.com> wrote in message
> news:kA9O8.156528$4i.14185140@bin2.nnrp.aus1.giganews.com...
> > I will be wrapping up my W2k MCSE cert soon. I need 2 more exams. I have
a
> > question for those of you who are network admins already. I have a solid
> > knowledge of all things microsoft sofar (DNS,DHCP,WINS,TCPIP etc.) I
have
> > limited network exp.( small NT4 peer to peer at work, home network w/4
> > computers). My question is what are the most common things
administrators[col
or=green]
> > and their assistants do on a day to day basis. I know this is a broad
> > question but since I am so close to getting the MCSE I would like to[/color]
make
> > sure I am proficient on some of the everyday tasks. I know I won't be
> > designing networks right away and will have to pay my dues but I want to
> be
> > prepared and ready to do the basics. Any comments would be appreciated.
> > TIA....Dave
> >
> >
>
>

Report this post to a moderator

"jaybee" <jaybeeoh@hotmail.com> wrote in
news:CfcO8.3098$oC3.3373404@news2.news.adelphia.net:

> Subject: Re: ? for the Admins
> From: "jaybee" <jaybeeoh@hotmail.com>
> Newsgroups: alt.certification.mcse
>
> You asked for it! You're getting it....

Thanks. I just saved that off to a text file.

William Korvine

Report this post to a moderator

Wow! Many thanks to "jaybee" for taking the time to reply to my question. As
I look over your list this information should comprise a networking course
in and of itself. As I move thru the MCSE path I have had the feeling there
is a lot of practical day to day activity that is not being discussed in the
materials.I am well aware that a lot of this comes with experience but I am
the type of person that likes to be prepared.Again thanks for this
information. I'm starting to see the big picture and I like the
challange.....Dave.

Report this post to a moderator

"jaybee" <jaybeeoh@hotmail.com> wrote in message
news:CfcO8.3098$oC3.3373404@news2.news.adelphia.net...
> You asked for it! You're getting it....
>
Wow! Many thanks to "jaybee" for taking the time to reply to my question. As
I look over your list this information should comprise a networking course
in and of itself. As I move thru the MCSE path I have had the feeling there
is a lot of practical day to day activity that is not being discussed in the
materials.I am well aware that a lot of this comes with experience but I am
the type of person that likes to be prepared.Again thanks for this
information. I'm starting to see the big picture and I like the
challange.....Dave.

Report this post to a moderator

Excellent list, jaybee.

smackedass

Report this post to a moderator