Multiple Installs on Several machines



reader@newsguy.com
07-10-2005, 12:23 AM
I'm sure this subject has been discussed here before but not sure how
to start digging into this.

I run 5 machines on a home network, all running win xp pro or home
edition, and have been spending more and more time just installing sw
or organizing each one. An example may be a recent update for nero:
New update pkgs released => I use nero on all machines so => ended up
installing the update on all five. Very time consuming.

How do system admins handle this kind of thing? Can one machine be
made to serve all the others needs for nero? Or can the update be
packaged somehow so that only one click is required to start a program
that handles the whole install (on each mach). (Nero update is in 6
pkgs).

In brief, how do administrators handle multiple installs to keep 5
machines up to date with current software or to install a new pkg on
all of them?

andy smart
07-10-2005, 12:24 AM
reader@newsguy.com wrote:
> I'm sure this subject has been discussed here before but not sure how
> to start digging into this.
>
> I run 5 machines on a home network, all running win xp pro or home
> edition, and have been spending more and more time just installing sw
> or organizing each one. An example may be a recent update for nero:
> New update pkgs released => I use nero on all machines so => ended up
> installing the update on all five. Very time consuming.
>
> How do system admins handle this kind of thing? Can one machine be
> made to serve all the others needs for nero? Or can the update be
> packaged somehow so that only one click is required to start a program
> that handles the whole install (on each mach). (Nero update is in 6
> pkgs).
>
> In brief, how do administrators handle multiple installs to keep 5
> machines up to date with current software or to install a new pkg on
> all of them?

System admins use a server (we have 2003), create a domain and then use
group policies to push the software out to the machines. You can't do
this with XP Home even if you were to have a server as it can't join a
domain. Some admins with small networks prefer to use something like
Symantec ghost and re-image the machines with new software, however you
need a volume licence copy of XP as it does not need activation - you
also have to store your 'work' on a different machine.

Sorry not to offer a solution for your case though :-(

ByTor
07-10-2005, 12:25 AM
In article <uekcc2t1q.fsf@newsguy.com>, reader@newsguy.com, says...

> I'm sure this subject has been discussed here before but not sure how
> to start digging into this.
>
> I run 5 machines on a home network, all running win xp pro or home
> edition, and have been spending more and more time just installing sw
> or organizing each one. An example may be a recent update for nero:
> New update pkgs released => I use nero on all machines so => ended up
> installing the update on all five. Very time consuming.
>
> How do system admins handle this kind of thing? Can one machine be
> made to serve all the others needs for nero? Or can the update be
> packaged somehow so that only one click is required to start a program
> that handles the whole install (on each mach). (Nero update is in 6
> pkgs).
>
> In brief, how do administrators handle multiple installs to keep 5
> machines up to date with current software or to install a new pkg on
> all of them?
>

Basically Andy's suggestion is right on the money
though..........Myself, I have 7 running in my home & basically I feel
more comfortable running them independently........so I just grin & bear
it when it's time to update.
If positioning is a problem (I have 2 machines in my basement apt) I use
PC Anywhere from my master machine to connect to all machines and do
whatever installing & updating I need to. Each machine has 2 seperate
HD's on them, 1 for storage of Images/Data the other just for the
OS's..........Most all installs can be run from my Master HD's on my
machine across the network, some have to be run independently from the
machine you're working on...........I'd say imaging is the most
important part as eventually a machine will get screwed (6yr old, the
wife, & 65yr old mother) and all I do is take a master image with all
the latest and restore it.....no big deal. I've tried the server bit but
it did not serve my purposes as each person uses their computer
differently. I do not worry about licensing issues but there are some
limits......My experience with XP Home is limited as I use professional
editions in all my testing grounds.....Win2K being by far the less
problematic for me so far and is used on all my systems..........

Hope this all helps............. ;0)

Steve N.
07-10-2005, 12:25 AM
reader@newsguy.com wrote:

> I'm sure this subject has been discussed here before but not sure how
> to start digging into this.
>
> I run 5 machines on a home network, all running win xp pro or home
> edition, and have been spending more and more time just installing sw
> or organizing each one. An example may be a recent update for nero:
> New update pkgs released => I use nero on all machines so => ended up
> installing the update on all five. Very time consuming.
>
> How do system admins handle this kind of thing? Can one machine be
> made to serve all the others needs for nero? Or can the update be
> packaged somehow so that only one click is required to start a program
> that handles the whole install (on each mach). (Nero update is in 6
> pkgs).
>
> In brief, how do administrators handle multiple installs to keep 5
> machines up to date with current software or to install a new pkg on
> all of them?

NetAdmins use real servers, tools and policies to do this. There is no
way to accomplish this natively with Windows deskto OSes.

Steve


Multiple Installs on Several machines