the point is not access to a computer and/or internet (use a laptop!)
I think what the poster mentions is the need to use
1) software inventory with links to the relevant software and updates
(eg. windows update and macromedia update)
2) a step-by-step installtion instructions that can be displayed
With my "developer" hat on, I would say you need something that adds
items to a database in the order you do the steps, with a url/upload
field of the software used in that step and settings screenshots
Sorry I cannot help with the actual solution but I am sure there are a
lot of MIS departments out there that would use/need something like
this
regards
MD
On Tue, 21 Sep 2004 12:16:39 +0200, Jochem van Dieten
<[EMAIL PROTECTED]> wrote:
> Brook Davies wrote:
> > Does anyone out there use a specific software package for documenting the
> > steps involved in rebuilding a server?
>
> Notepad.
>
>
> > I find I try to do this in MSWORD,
> > but the service packs, patches and configuration items change so much that
> > it is difficult to keep this data up-to-date.
>
> I think there is another problem. When you actually need to
> rebuild your server, who says you are going to have MS Word at
> hand? Though you most definitely shouldn't depend on just an
> electronic version of the document, having one next to the paper
> version can be very convenient to copy-paste serials,
> configuration lines etc.
> The added advantage of plain text is that you can feed it to the
> command line. Firewall configuration, network configuration,
> non-default registry keys, user accounts for services etc. are
> all set from the command line and it is just a matter of
> rerunning the scripts.
>
> Jochem
>
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
