Hello,

I was wondering what (if any) written documentation should be kept in terms
of "Server Configuration Settings"?

What sort of things do you all "write down" when it comes to documenting
your systems?

At the moment, my directors have a record of Administrator Passwords and
some information covering the Backup / Restore procedure.

This information would be useful for a "third party" in case work had to be
carried out on the system and I was un-available for some reason.

TIA
Stephen

Re: Documenting SBS Server Settings? by Kevin

Kevin
Wed Jul 13 21:47:40 CDT 2005

First, kudos for addressing this need.

Somethings, off the top of my head ... to start the ball rolling ...

Keep a log book of when and what patches, hotfixes and service packs have
been installed on your server, what mods you have made (group policy
changes, reg fixes, etc.)

A network diagram is always helpful.

Be sure to record admin id and password of ither devices (network print
servers, routers, wireless access points, etc.)

A list of phone numbers and account numbers for things like you ISP, your
telephone vendor, your web provider, etc.


--
Kevin Weilbacher [SBS-MVP]
"The days pass by so quickly now, the nights are seldom long"


"StudioTwo" <studio_two@hotmail.com> wrote in message
news:%237RiZd5hFHA.3912@tk2msftngp13.phx.gbl...
> Hello,
>
> I was wondering what (if any) written documentation should be kept in
> terms of "Server Configuration Settings"?
>
> What sort of things do you all "write down" when it comes to documenting
> your systems?
>
> At the moment, my directors have a record of Administrator Passwords and
> some information covering the Backup / Restore procedure.
>
> This information would be useful for a "third party" in case work had to
> be carried out on the system and I was un-available for some reason.
>
> TIA
> Stephen
>



Re: Documenting SBS Server Settings? by StudioTwo

StudioTwo
Wed Jul 20 02:52:35 CDT 2005

Thanks for the Advice.

"Kevin Weilbacher [SBS-MVP]" <kweilbacMVP@gte.net> wrote in message
news:uQXbo5BiFHA.3608@TK2MSFTNGP12.phx.gbl...
> First, kudos for addressing this need.
>
> Somethings, off the top of my head ... to start the ball rolling ...
>
> Keep a log book of when and what patches, hotfixes and service packs have
> been installed on your server, what mods you have made (group policy
> changes, reg fixes, etc.)
>
> A network diagram is always helpful.
>
> Be sure to record admin id and password of ither devices (network print
> servers, routers, wireless access points, etc.)
>
> A list of phone numbers and account numbers for things like you ISP, your
> telephone vendor, your web provider, etc.
>
>
> --
> Kevin Weilbacher [SBS-MVP]
> "The days pass by so quickly now, the nights are seldom long"
>
>
> "StudioTwo" <studio_two@hotmail.com> wrote in message
> news:%237RiZd5hFHA.3912@tk2msftngp13.phx.gbl...
>> Hello,
>>
>> I was wondering what (if any) written documentation should be kept in
>> terms of "Server Configuration Settings"?
>>
>> What sort of things do you all "write down" when it comes to documenting
>> your systems?
>>
>> At the moment, my directors have a record of Administrator Passwords and
>> some information covering the Backup / Restore procedure.
>>
>> This information would be useful for a "third party" in case work had to
>> be carried out on the system and I was un-available for some reason.
>>
>> TIA
>> Stephen
>>
>
>