jskfan
asked on
deploying DST package
Our network is not Active Directory domain Network, we still use SUS for windows updates.
our clients are W2000 professional and are setup through registery to pull the updates from our SUS server.
Now we have a DST(Daily Saving Time) package that we need to deploy to our clients.
Is there any way to set up the DST so that w2k pro machine can pull the packag????
thanks
our clients are W2000 professional and are setup through registery to pull the updates from our SUS server.
Now we have a DST(Daily Saving Time) package that we need to deploy to our clients.
Is there any way to set up the DST so that w2k pro machine can pull the packag????
thanks
ASKER
but we don't have Active Directory domain.
is there any way to make this patch run on all workstations without going around each workstations???
is there any way to make this patch run on all workstations without going around each workstations???
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
We have around 100 computers.
Can we store the patch in the network and use psexec to install the patch in workstations??
we have admin account in all workstations, so if I understand I need to logon to my machine with that same admin account and run psexec.
is there any script that helps us use psexec for all workstations at one time??
example: creating a text file with all workstations in rows then run a script that picks the name of the workstation from the textfile???
thanks
Can we store the patch in the network and use psexec to install the patch in workstations??
we have admin account in all workstations, so if I understand I need to logon to my machine with that same admin account and run psexec.
is there any script that helps us use psexec for all workstations at one time??
example: creating a text file with all workstations in rows then run a script that picks the name of the workstation from the textfile???
thanks
Where the Heck is that no-good sirbounty when you need him?
He is a script king.
The short answer is yes, but I'm a scripting zero.
I can get you the psexec command line and I'll try to find the script that runs it using a text file list of all computers.
Back soon.
Vic
He is a script king.
The short answer is yes, but I'm a scripting zero.
I can get you the psexec command line and I'll try to find the script that runs it using a text file list of all computers.
Back soon.
Vic
The psexec command string is pretty simple:
psexec \\computername PatchName.exe
There is something about use a file with all the computer names in it; using something like @filename.txt
But I'm not sure of the exact syntax.
Vic
psexec \\computername PatchName.exe
There is something about use a file with all the computer names in it; using something like @filename.txt
But I'm not sure of the exact syntax.
Vic
no-good? Now Vic, you've gone and hurt my feelings... : P
Try this:
If you have a list of computers, then use:
for /f %a in (C:\Computers.txt) do psexec \\%a c:\pathtofile\file.exe
That's just a command-line command.
If you need to add it to a batch file, change %a to %%a (both instances).
Try this:
If you have a list of computers, then use:
for /f %a in (C:\Computers.txt) do psexec \\%a c:\pathtofile\file.exe
That's just a command-line command.
If you need to add it to a batch file, change %a to %%a (both instances).
True Vic, psexec has it's own method:
psexec @Computers.txt c:\pathtofile\file.exe
psexec @Computers.txt c:\pathtofile\file.exe
oops - better clear up the path for that too.
psexec @C:\computers.txt c:\pathtofile\file.exe
psexec @C:\computers.txt c:\pathtofile\file.exe
sirbounty,
That is what I was looking for.
I am going to test the "add to knowledgebase" trick here.
BTW - I finally found a forum where I have more points than you.
Something about 'Military Trivia' - LOL.
Thanks for jumping in here.
Vic
That is what I was looking for.
I am going to test the "add to knowledgebase" trick here.
BTW - I finally found a forum where I have more points than you.
Something about 'Military Trivia' - LOL.
Thanks for jumping in here.
Vic
No kiddin? We've got a Military Trivia Zone? Neat!
jskfan,
When running psexec, it automatically assumes the permissions of the account typing the command.
If you are logged on as an administrator for all of those boxes, it will run without any problem.
If needed, you can also insert a username and password within the command string.
sirbounty - no we don't (I lied).
Vic
When running psexec, it automatically assumes the permissions of the account typing the command.
If you are logged on as an administrator for all of those boxes, it will run without any problem.
If needed, you can also insert a username and password within the command string.
sirbounty - no we don't (I lied).
Vic
ASKER
sirbounty:
Can you give me the final script?? I saw you changing it in your above comments.
Can I have the final script to run??
Thanks
Can you give me the final script?? I saw you changing it in your above comments.
Can I have the final script to run??
Thanks
ASKER
So how does the remote computer needs to be logged on.
is it with the same username and password that I am logged on to the computer from which I am running Psexec??
thanks
is it with the same username and password that I am logged on to the computer from which I am running Psexec??
thanks
Two seperate routes posted actually...
If you have a list of computers, then use:
for /f %a in (C:\Computers.txt) do psexec \\%a c:\pathtofile\file.exe
That's just a command-line command.
If you need to add it to a batch file, change %a to %%a (both instances).
Otherwise, just using psexec's builtin 'loop' method:
psexec @C:\computers.txt c:\pathtofile\file.exe
and both will use your current logged in credentials.
-u 'username' -p 'password'
(added to psexec parameters) allows you to change the user credentials)
If you have a list of computers, then use:
for /f %a in (C:\Computers.txt) do psexec \\%a c:\pathtofile\file.exe
That's just a command-line command.
If you need to add it to a batch file, change %a to %%a (both instances).
Otherwise, just using psexec's builtin 'loop' method:
psexec @C:\computers.txt c:\pathtofile\file.exe
and both will use your current logged in credentials.
-u 'username' -p 'password'
(added to psexec parameters) allows you to change the user credentials)
jskfan,
See my previous comment at accounts and permissions.
When you are logged into 'computer1' and psexec is sitting on computer1, the commands you are running on all the remote computers automatically run with the permissions of your account.
Make sense?
Vic
See my previous comment at accounts and permissions.
When you are logged into 'computer1' and psexec is sitting on computer1, the commands you are running on all the remote computers automatically run with the permissions of your account.
Make sense?
Vic
jskfan,
I just enjoy the heck out of getting an email with the title "Good Answer"!
Thank you for the points.
(But), if you wouldn't mind, please request in the "Support" Forum (FREE questions there) to have a moderator re-open this question and split some points off with sirbounty.
My PSEXEC trick is not nearly so neat without his script to automate things.
Thanks again for the points and I'm looking forward to your next question.
Regards,
Vic
I just enjoy the heck out of getting an email with the title "Good Answer"!
Thank you for the points.
(But), if you wouldn't mind, please request in the "Support" Forum (FREE questions there) to have a moderator re-open this question and split some points off with sirbounty.
My PSEXEC trick is not nearly so neat without his script to automate things.
Thanks again for the points and I'm looking forward to your next question.
Regards,
Vic
Vic - While I do appreciate the sentiment...it's not at all necessary.
Just happy to help. :^ )
~sirbounty
Just happy to help. :^ )
~sirbounty
But if you're going to run it, it is just another patch that has to be run like any other.
Vic