Virusguard and Winguard on an SUN NFS network
2007-12-25 10:23:00
I would like to thank all those who replied to my quey.
Original mail:
Currently we have 25 virusguard/winguard licenses
for DOS/WFW311. When the updates come every quarter,
I have to go around to each one of the PC's and install them.
This now has become very time comsuming and as we going to
be getting more PC's in the future I see becoming more of a
problem.
All the PC's are connected on SUN network, that is each PC runs
SUN's PCNFSpro Client Network software for Windows and avails of
SUN Fileserver resources.
I would like to be able to keep all the DR. Solomons software in
one place ( ie on a SUN shared partition ) and then have the PC
access it on bootup.
The problem is when the PC is booted, the network is NOT available
until windows loads meaning that virusguard never gets loaded and
as a result the windows equivalent never gets loaded either.
Do anyone have any ideas how to overcome this problem.
PS : Does anyone know the exact functionality of the command "netbind.exe"
and a summary will be forthcomming.
------------------------------------------------------
Replies :
1.
You need to write a simple batch file that gets run from windows
startup group in a dos session that checks to see if two files
are different; One on the PC someplace safe, one on the network.
If they ARE, then it should transfer the new files down from the
network, and then tell the user how to do a safe reboot.
You could also write a Delphi or Visual Basic app for this fairly
easily, I believe.
You can use the DOS port of GNU diff, or I believe there is some
MSDOS command that does the same thing.
Martin Espinoza <drink@sei.com>
--------------------------------------------------------
2.
You might want to look putting PC-Admin on the server and then booting
the pcs using dhcp. This will allow the ini files to be edited before
windows is completely up. You could also use the login script
capabilities to perform after boot activities.
Most people think dhcp is only for dynamic ip address allocation but it
can be used for much more.
greg.kranz@amp.com (Greg Kranz)
---------------------------------------------------------
3.
What we did to over come this problem, was add a script that would
copy the files to the DOS box, if they were newer on the server. I am not
exactly sure how to do this under the PCNFSpro, as we are currently only
running PCAdmin, which is dos based. But if it is like PCadmin, there is
a script that is run at "boot" time on the pc, just add a call to another
dos batch file that copies it off if the one on the server is newer. It
won't take effect until the next reboot, but I guess you can't have everything.
medar!rmsun!rmorse@uunet.uu.net (Robert Morse)
----------------------------------------------------------
4.
use NFS as a distribution mechanism, rather than running it from NFS. In the
users' profiles, get them to periodically suck down the latest copy to the PC,
so all will be cool for the next boot.
Alternatively, can you arrange for a 'nobody' login to execute the software,
then for the user to login afterwards?
Anderson McCammont <and@morgan.com>
---------------------------------------------------------
5.
One possibility is to create a network logon procedure. We have included in
each PC c:\autoexec.bat a call to a logon.bat file that is in one of the
central servers (we use PC-NFS 5.x, but the final result will be the same).
After initializing the network (net init in autoexec.bat) and mounting some
standard drives (\nfs\drives.bat) we do a call to drive:\path\logon.bat.
In logon.bat you can do anything you like ;).
Extract from PC-NFS 5.1 documentation:
"netbind" - The command line to run netbind only applies when you configure
an NDIS driver. It comes before prt and net init. The netbind program
initiates the final binding of the NDIS drivers and protocols. ... _
Victor Dias Fernandes ( victor.dias-fernandes@dg12.cec.be)
---------------------------------------------------------
Many Thanks to all of you.
regards,
James.
PS : Sorry about the delay on the summary.
Comments
Got something to say?
You must be logged in to post a comment.
