I noticed you asked on Twitter as well. Gary's answer is good, I would add that if you want to see where the exe files are downloading to, you can use the -dv
switches to get quite a bit more information and/or inspect the Chocolatey log files.
For more detail about what you want to do, I'm understanding that you want to be able to not use Chocolatey.org or the internet at all for internal machines. Almost every business I talks to has this requirement, and we totally agree that you should not ever give away trust/control to the internet as a business: http://www.slideshare.net/ferventcoder/chocolatey-and-puppet-managing-your-windows-software-since-2011/9. I'll restate it here though. If you are a business, you should not use Chocolatey.org for packages because you are giving up control over when pkgs are updated, and whether packages break due to the changing internet. You are also placing trust in the internet. Both of those are pretty much no no's for any business worth their salt using something like Chocolatey in a production scenario. We also mention this on the About page of Chocolatey.org.
Instead, when businesses use Chocolatey, they usually download the package and the files that the package usually reaches out to the internet for. Then they edit the package itself to point to those internal files. They then take those edited packages and place them on an internal repository. All of the computers in their network point to that internal repository and the default chocolatey.org source is disabled.
That process does take some time, which is why we are working on Chocolatey for business with something that would help that become a simple command and eventually a button click for businesses.