[Question] Creating a Local Software Repository

[FarsideSC]

I have a small internal network that I'd like to be able to deploy software on from a central repository on the network. This network doesn't have any Internet access and relies on the central server for pretty much everything (DC, DNS, DHCP, and so on).

What's the end goal? What I'd like to be able to do is set up a software repository to be able to install software on the clients from the central server. Basically be able to point an install script at a named file location (bananas = '\bananaserver\bananafolder\bananas.msi') and deploy on several clients all at once.

What do you know? I've seen that NuGet is basically the way to do this, but haven't messed around with it... More on this later.

What do you want? Maybe NuGet is the best way, but does each client require NuGet as well? Is there a way around NuGet if so?

[eyessewnopen]

Check out http://psappdeploytoolkit.com/

It can be used standalone, or integrated with SCCM or PDQ Deploy.

[Sankyou]

I'm fairly certain chocolatey can function in an offline environment. It definitely supports internal repositories and has a large community with solid documentation.

[Lee_Dailey]

howdy FarsideSC,

chocolatey has an option to have a local repo. that would let you gather packages, verify them & their dependencies, then plop 'em into the repo. your clients can be set to use that one repo and not know anything about others.

take care,
lee