Beefy Boxes and Bandwidth Generously Provided by pair Networks
"be consistent"
 
PerlMonks  

Re: McAfee Dat Check

by Marza (Vicar)
on Mar 22, 2002 at 19:12 UTC ( [id://153632]=note: print w/replies, xml ) Need Help??


in reply to McAfee Dat Check

This node falls below the community's threshold of quality. You may see it by logging in.

Replies are listed 'Best First'.
Re: Re: McAfee Dat Check
by OzzyOsbourne (Chaplain) on Mar 28, 2002 at 13:49 UTC

    Not bad! For what it does; it is fine.

    What a glowing recommendation. Take something that I worked hard on, thought was good, use a lot, and knock it down. Thanks for your input.

    The reason I use an input file for my 500+ servers is that I can update my server list for the 30+ scripts that I run against them in one place.

    Sorry, you caught me on a bad day, and I'm a little insulted (although I'm not sure if I should be).

    I would probably feel better if you had made code corrections and said, "See, stupid? Like this." rather than just knocking down the code with offhand remarks. But that's the way it goes I suppose...

    -OzzyOsbourne

      Well I guess I should not post when I am tired. Does that sound better then posting without a license? ;-)

      In your case that does make sense! 500 Servers ick. I was going to say why not automate but if you have 500 servers then you have a few thousand workstations. Right?

      I only have about 350 machines total. The script I wrote checks all machines. I used the Roth NetAdmin mod to get a list of all NT/2000 workstations and servers. The only problem is that you have to build exclusion routines for stuff like Samba servers. But again in my case, people here would not always update the input file.

      Why not build a ping into the routine. That way if a machine is down, you avoid the registry error when it tried to connect. I needed this because a few of our junior admins would go looking for the down machine and try and figure out why it did not have McAfee or Netshield installed! *SIGH*

        Using the connect method does have one advantage over your approach.

        If I can't connect to a server be it from the remote registry service is down, the server is down, or there was an uninstall of netshield and *shock* the uninstaller left junk in the registry, the code I gave you will only make one attempt to connect with the server.

        Your code will try three times and get three errors.

        Okay, this is the last time I promise. ;-)

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://153632]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others drinking their drinks and smoking their pipes about the Monastery: (5)
As of 2024-03-28 21:34 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found