Ninite Alternative
-
I'm a complete scripting NOOB... so a little help in what is needed would be cool.
-
-
@Dashrender said:
I'm a complete scripting NOOB... so a little help in what is needed would be cool.
What do you want to accomplish? I provided install and update examples above.
-
@scottalanmiller said:
@Dashrender said:
I'm a complete scripting NOOB... so a little help in what is needed would be cool.
What do you want to accomplish? I provided install and update examples above.
for a single workstation, what do you do with that for the entire network?
-
@Dashrender said:
@scottalanmiller said:
@Dashrender said:
I'm a complete scripting NOOB... so a little help in what is needed would be cool.
What do you want to accomplish? I provided install and update examples above.
for a single workstation, what do you do with that for the entire network?
The most likely thing that you would do is put in a scheduled job for updates so that each machine updates itself weekly or so. That's the super easy way. Takes no special skills.
-
A really simple script approach would be like this:
for %i in (desktop1 desktop2 desktop3) do PsExec.exe \%i cup all
That one line is all that you need. Just fill in the list of machines that you want to update in the paranthesis and you are good to go. You can make it more advanced by filling in that portion from a text file or whatever. But the basics are very simple. It's not really scripting, just a single statement that does everything. This command is the "cup all" which is the universal update command. All packages would be updated on every system.
-
Similarly if you wanted to install the Java Runtime (JRE) on every machine you would do this command:
for %i in (desktop1 desktop2 desktop3) do PsExec.exe \%i cinst javaruntime
-
I presume you have to provide credentials assuming your user is not a local admin.?
Ive never used psexecute before.
-
@Dashrender said:
I presume you have to provide credentials assuming your user is not a local admin.?
Ive never used psexecute before.
psexec is awesome. If you are on a domain it, just works.
-
I made an article about Chocolatey too: http://www.scottalanmiller.com/windows/2014/03/15/open-source-command-line-package-management-tool/
-
And I wrote a guide to automating Chocolatey with PsExec: http://www.scottalanmiller.com/windows/2014/03/15/automating-chocolatey-with-psexec/
-
Can you use chocolaty in a workgroup environment where there is a standard local user & common password?
-
Can you set the chocolatey program to use a specific network share for the repository, instead of connecting to the same website on every machine? This would be really useful on networks behind firewalls with no internet access or really poor internet connectivity.
-
Would it be possible to get Chocolatey to output it's results to a log file or somehow report on the progress / result of the update / install? It would be good to know for sure what programs got updated, or more importantly if any of the updates failed.
-
@JustRob said:
Can you use chocolaty in a workgroup environment where there is a standard local user & common password?
Chocolatey doesn't use AD. It just needs local admin privileges. Any admin account can be used.
-
@JustRob said:
Can you set the chocolatey program to use a specific network share for the repository, instead of connecting to the same website on every machine? This would be really useful on networks behind firewalls with no internet access or really poor internet connectivity.
That's something that I would have to research. But I would be surprised if you can't. Although you can definitely use a proxy to do that.
-
@scottalanmiller said:
@JustRob said:
Can you use chocolaty in a workgroup environment where there is a standard local user & common password?
Chocolatey doesn't use AD. It just needs local admin privileges. Any admin account can be used.
So do you have to be logged in with the same account on the machine you are pushing the updates from / running the remote command from (source) as is used on the machine you are updating (target)? Or can you specify in the update command on your source machine what credentials to use on the target machine(s)?
-
@scottalanmiller said:
@JustRob said:
Can you set the chocolatey program to use a specific network share for the repository, instead of connecting to the same website on every machine? This would be really useful on networks behind firewalls with no internet access or really poor internet connectivity.
That's something that I would have to research. But I would be surprised if you can't. Although you can definitely use a proxy to do that.
You can set up a proxy to take requests for files from a website and pull them from a file share instead?
-
@JustRob said:
@scottalanmiller said:
@JustRob said:
Can you set the chocolatey program to use a specific network share for the repository, instead of connecting to the same website on every machine? This would be really useful on networks behind firewalls with no internet access or really poor internet connectivity.
That's something that I would have to research. But I would be surprised if you can't. Although you can definitely use a proxy to do that.
You can set up a proxy to take requests for files from a website and pull them from a file share instead?
The proxy itself would be the file share in that case. A proxy like squid would allow that, yes.
-
@scottalanmiller @dashrender @justrob Russinovich pushed out an update to psexec last week—
As usual, he doesn't say much about it (or even announce it). Assumption is it smooths interoperability up to Win8.1
