Re: Maintenance on SBS2003 Server

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

You can delete old log files from C:\Windows\system32\LogFiles or elsewhere.
They don't take up much room - I usually get around to them once or twice a
year. Never delete any logs that are created by Exchange, though - those
should go away when you back up Exchange, then the server will recreate new
ones throughout the day until the next backup. If you have Exchange logs
accumulating past the time of a full backup, that indicates a problem you'll
need to address.

You can get great how-to info for the SP from
http://www.smallbizserver.net/Default.aspx. I wouldn't worry too much about
it - remember you're only hearing from the few with problems, not the many
with successful SP installs. Just do a good backup first and allow enough
time for all the updates.


"Mike Lambert" <mikel@xxxxxxxxxxxxx> wrote in message
news:11ormpnliobu9da@xxxxxxxxxxxxxxxxxxxxx
> Thanks a lot for all your suggestions! I haven't installed SP1 for
> SBS2003 or the service pack for Exchange yet. With all the posts about
> problems installing these I have been a little afraid to even start. But,
> I guess I need to make that a priority. With all the log files that are
> created do I need to delete them from somewhere, or is this automatic?
>
> We have a tape drive that use to do a full backup every night, and yes we
> do take them offsite.
>
> Thanks again for your help!
>
> Mike
>
>
> "Dave Nickason [SBS MVP]" <gwdibble@xxxxxxxxxxxxxxxxxxxxxx> wrote in
> message news:eAwGTlc9FHA.1420@xxxxxxxxxxxxxxxxxxxxxxx
>> FWIW, this is what I do:
>>
>> - check all logs daily for errors or possible problems (or as close to
>> daily as I can)
>> - make sure the backup ran successfully, and that the designated person
>> changed the tapes, also daily
>> - monitor the AV software to make sure it's updating the servers and
>> workstations as it should be
>> - frequently check the server monitoring program to make sure no hardware
>> is failed or failing. I try to do this in the server room rather than
>> remotely so I can make sure that there's not a vacuum cleaner plugged
>> into the UPS or someone's coat hanging on a server
>> - occasionally monitor the drives for free space
>> - occasionally check the UPS status
>> - keep track of patch releases and install all necessary patches shortly
>> after their release (you can subscribe to security alerts, etc. from
>> Microsoft or watch for Susan Bradley to post something when they're
>> released)
>>
>> For Exchange, I do nothing except monitor the server logs daily and the
>> database size occasionally. Rightly or wrongly, I almost never defrag.
>>
>> Two comments: If you frequently monitor the server logs, you may spot
>> something at the warning stage and avert a problem before it becomes
>> critical (and thereby makes it into the e-mail report). And, it's a good
>> idea to do some monitoring so that you're familiar with how things run
>> normally - this can help a lot in troubleshooting when something goes
>> wrong.
>>
>> "Mike Lambert" <mikel@xxxxxxxxxxxxx> wrote in message
>> news:11ori68rnpctpd7@xxxxxxxxxxxxxxxxxxxxx
>>> We are a small business that decided to get a server with Small Business
>>> Server 2003 because we do not have a dedicated IT department or person.
>>> I have been assigned with the responsiblity of keeping it running and
>>> upgraded. Since I am new to servers in general I was wondering what I
>>> need to do on a weekly or yearly basis. I have the normal server report
>>> and backup report e-mailed to me every morning. Is this enough to try
>>> and stop any problems that might come up? Do I need to defrag the hard
>>> drives, clear old logs, review other information on some kind of
>>> schedule? Is there anything I need to do with Exchange as far as
>>> maintenance is concerned? What do other people do with this kind of
>>> maintenance? Any suggestions would be greatly appreciated.
>>>
>>> Mike
>>>
>>
>>
>
>


.

Relevant Pages

  • Re: Outlook client fails to connect to Exchange Server 2000 but OW
    ... there were errors in the logs even before this. ... Now I tried to get help from 1 guy workin with MS Exchange, ... We have a single MS Exchange Server 2000 which works as a member ... I can access exchange thru OWA but not thru Outlook client. ...
    (microsoft.public.exchange.clients)
  • RE: CEICW-OMA errors
    ... After the exchange server has been reinstalled, ... then reproduce the issue by running CEICW again to capture logs. ... calling CEmailCommit::ValidatePropertyBag. ...
    (microsoft.public.windows.server.sbs)
  • Re: Outlook client fails to connect to Exchange Server 2000 but OW
    ... there were errors in the logs even before this. ... Now I tried to get help from 1 guy workin with MS Exchange, ... We have a single MS Exchange Server 2000 which works as a member ... I can access exchange thru OWA but not thru Outlook ...
    (microsoft.public.exchange.clients)
  • Direct Push only working sporadicly.
    ... Stand-alone Exchange 2003 server w/SP2. ... sometimes a handset will receive e-mail almost instantly ... huge number of 401 response codes in the IIS logs and in the handset ...
    (microsoft.public.pocketpc.activesync)
  • Re: 4.4.7 email delays
    ... If message passes Exchange then it should show up in logs. ... If you set your e-mail client to use ISP's server for outbound mail, then outgoing message will not be recorded in logs. ...
    (microsoft.public.exchange.admin)