.BAT file

[Guest]

Hi, I am currently working in a workgroup network. The
network has various versions of windows and it is running
pretty good. When the computers start up, they have a
message saying that 'cannot find startup.BAT'. (because
it is called somehting else.BAT on the server). This
startup.BAT file was created by a person who worked
previously. My understanding is that it has been created
so that all the computers have the same background
amongst other things.

can that .BAT file also be editing all the computers
registry so that it is the same as the servers registry??

My question is how can i find out what this startup.BAT
file is doing? I want to learn how to create one myself.
i have located it on the server. and also how do i make
the other computers read that particular .BAT file?

 

[Lanwench [MVP - Exchange]]

Hi, I am currently working in a workgroup network. The
network has various versions of windows and it is running
pretty good. When the computers start up, they have a
message saying that 'cannot find startup.BAT'. (because
it is called somehting else.BAT on the server). This
startup.BAT file was created by a person who worked
previously. My understanding is that it has been created
so that all the computers have the same background
amongst other things.

can that .BAT file also be editing all the computers
registry so that it is the same as the servers registry??

My question is how can i find out what this startup.BAT
file is doing? I want to learn how to create one myself.
i have located it on the server. and also how do i make
the other computers read that particular .BAT file?

If you're in a workgroup, not a domain, this file must be local on each
computer, as you can't use login scripts in a workgroup. Try checking out
the startup properties of all the PCs - msconfig, startup folder, etc., to
find out where/what the file is and edit it on one to correct it if need
be - then copy it to the others.

How many computers? With more than a small handful, a domain is a much
better option, as workgroups don't scale well. Also, domain login scripts
are the way to go.