deploying critical updates across the network?

[AntunB]

we are running windows 2000 server

with about 50 windows 2000 workstations



i can update the systems to SP4 using group policies



now is there a way to install critical updates on these workstations remotely? without giving local admin rights that are required to install this product?


and we cannot use SUS



thankyou

 

[mrdenny]

We use a program called HFNetChkPro. You can get it from

http://www.shavlik.com/.

It works fairly well. We use it to deploy to a couple of hundred servers. The person doing the patching will need admin rights on the machines which the patches are being installed on.

It will also allow you to reboot the machines at a later point in time, such as late that night to complete the install.

Denny

--Anything is possible. All it takes is a little research. (Me)

 

[AntunB]

thankyou for your help

i will look into it




thanks

 

[mrdenny]

no problem.

Denny

--Anything is possible. All it takes is a little research. (Me)

 

[JillofAllTrades]

Microsoft has SUS too that we use easily and successfully:

http://www.microsoft.com/windowsserversystem/sus/default.mspx

Christine

 

[OLDMO]

With the new SUS they did add domain support so if that was the problem it has been fixed. I just got it up and running on my network and it works great!


-Ryan

 

[AntunB]

the problem is no1 wants to cough up sum money for a server too use SUS

 

[Manwiz]

For a freebie solution, you can write a .cmd file that connects to your clients (using the FOR command) and executing the hotfix/patch using a remote execution tool, say for example, sysinternal's psexec (

http://www.sysinternals.com/ntw2k/freeware/psexec.shtml).

Your .cmd file may look something like,

FOR /F %%i in (Clients.txt) Do psexec.exe \\%%i -i -d -c whateverpatch.exe /quiet /norestart

or you could split this into two scripts (one for the FOR part which calls another script that executes the patch through psexec and may do other steps, say for example, writing to a log file, etc).

This should be quite straightforward and easy to implement. Best of all, it's F-R-freakin'-E-E! Hope this helps...

(=S.Manaois.3=)

 

[JillofAllTrades]

I don't think SUS uses a lot of resources, so you could probably put it on your existing server. I have about 50 clients and I have it running on a database server with no resource impact.

Christine

 

[AntunB]

ok we are going with sus


we are getting another server so we wil hav 3 servers




origionaly we couldnt put it on the current servers because 1 is NT

and the other has domino on it which runs on port 80, same as SUS




thankyou for all your ideas
it was much apreciated