Re: Script: Run a command for each computer on network

[Ben Scott]

On Fri, Mar 26, 2010 at 8:26 AM, James Rankin  wrote:
> Sometimes when the browser is getting it's electrons
> in a twist, I'll find machines in the server subnet not appearing when the
> script is run from the workstations subnet, and vice versa.

  While the NetBIOS browser is certainly not the most reliable thing
in the universe, I find the following helps:

A1. Use WINS
A2. Configure all computers as NetBIOS P-nodes (peer-to-peer) (no broadcasts)
A3. On each subnet, designate a small number of reliable computers be
preferred master browsers

-- Ben

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

RE: Script: Run a command for each computer on network

[John Cook]

Nice, I feel violated after stepping into Bens dumping ground!

John W. Cook
Systems Administrator
Partnership For Strong Families
315 SE 2nd Ave
Gainesville, Fl 32601
Office (352) 393-2741 x320
Cell (352) 215-6944
Fax (352) 393-2746
MCSE, MCTS, MCP+I, A+, N+, VSP4, VTSP4

From: Andrew S. Baker [mailto:asbz...@gmail.com]
Sent: Thursday, March 25, 2010 9:50 PM
To: NT System Admin Issues
Subject: Re: Script: Run a command for each computer on network

Nice, Ben

Thanks.  It's always good to see different approaches.

-ASB: http://XeeSM.com/AndrewBaker

On Thu, Mar 25, 2010 at 8:36 PM, Ben Scott 
mailto:mailvor...@gmail.com>> wrote:
Here's another batch script I realized others might find useful.  It
runs a command for every computer it finds on the network (via "NET
VIEW").  Useful when you want to do something on every computer
currently running on the LAN.  You can specify patterns to match and
patterns to exclude.

The command runs on the local computer, but you could combine it with
PSEXEC to run the commands on the remote computer.

It includes an example that will concisely list the version of two
different OCX control files for each matching computer.

http://sites.google.com/site/mailvortex/windows/for-each-computer

-- Ben

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~







CONFIDENTIALITY STATEMENT: The information transmitted, or contained or 
attached to or with this Notice is intended only for the person or entity to 
which it is addressed and may contain Protected Health Information (PHI), 
confidential and/or privileged material. Any review, transmission, 
dissemination, or other use of, and taking any action in reliance upon this 
information by persons or entities other than the intended recipient without 
the express written consent of the sender are prohibited. This information may 
be protected by the Health Insurance Portability and Accountability Act of 1996 
(HIPAA), and other Federal and Florida laws. Improper or unauthorized use or 
disclosure of this information could result in civil and/or criminal penalties.
Consider the environment. Please don't print this e-mail unless you really need 
to.

This email and any attached files are confidential and intended solely for the 
intended recipient(s). If you are not the named recipient you should not read, 
distribute, copy or alter this email. Any views or opinions expressed in this 
email are those of the author and do not represent those of the company. 
Warning: Although precautions have been taken to make sure no viruses are 
present in this email, the company cannot accept responsibility for any loss or 
damage that arise from the use of this email or attachments.

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

Re: Script: Run a command for each computer on network

[James Rankin]

I use net view combined with psexec in a few of my command scripts (most
notably the ones that do *gpupdate* and *wuauclt /detectnow*), however I
find that you've got to have your browser service in good working order for
it to function as expected. Sometimes when the browser is getting it's
electrons in a twist, I'll find machines in the server subnet not appearing
when the script is run from the workstations subnet, and vice versa. If you
find this issue, maybe it's time to break out the dark mysteries of *browstat
*and find out how your browsing is doing.

On 26 March 2010 00:36, Ben Scott  wrote:

> Here's another batch script I realized others might find useful.  It
> runs a command for every computer it finds on the network (via "NET
> VIEW").  Useful when you want to do something on every computer
> currently running on the LAN.  You can specify patterns to match and
> patterns to exclude.
>
> The command runs on the local computer, but you could combine it with
> PSEXEC to run the commands on the remote computer.
>
> It includes an example that will concisely list the version of two
> different OCX control files for each matching computer.
>
> http://sites.google.com/site/mailvortex/windows/for-each-computer
>
> -- Ben
>
> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~
> ~   ~
>



-- 
"On two occasions...I have been asked, 'Pray, Mr Babbage, if you put into
the machine wrong figures, will the right answers come out?' I am not able
rightly to apprehend the kind of confusion of ideas that could provoke such
a question."

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

Re: Script: Run a command for each computer on network

[Ben Scott]

On Thu, Mar 25, 2010 at 9:50 PM, Andrew S. Baker  wrote:
>> ... runs a command for every computer it finds on the network ...
>
> Nice, Ben

  Thanks!

> Thanks.  It's always good to see different approaches.

  That was my thinking.  :)

-- Ben

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

Re: Script: Run a command for each computer on network

[Andrew S. Baker]

Nice, Ben

Thanks.  It's always good to see different approaches.

-ASB: http://XeeSM.com/AndrewBaker


On Thu, Mar 25, 2010 at 8:36 PM, Ben Scott  wrote:

> Here's another batch script I realized others might find useful.  It
> runs a command for every computer it finds on the network (via "NET
> VIEW").  Useful when you want to do something on every computer
> currently running on the LAN.  You can specify patterns to match and
> patterns to exclude.
>
> The command runs on the local computer, but you could combine it with
> PSEXEC to run the commands on the remote computer.
>
> It includes an example that will concisely list the version of two
> different OCX control files for each matching computer.
>
> http://sites.google.com/site/mailvortex/windows/for-each-computer
>
> -- Ben
>
> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~
> ~   ~
>

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

Script: Run a command for each computer on network

[Ben Scott]

Here's another batch script I realized others might find useful.  It
runs a command for every computer it finds on the network (via "NET
VIEW").  Useful when you want to do something on every computer
currently running on the LAN.  You can specify patterns to match and
patterns to exclude.

The command runs on the local computer, but you could combine it with
PSEXEC to run the commands on the remote computer.

It includes an example that will concisely list the version of two
different OCX control files for each matching computer.

http://sites.google.com/site/mailvortex/windows/for-each-computer

-- Ben

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~