[Additional 2014-01-10: the same issue occurs with Adobe Creative Cloud and the CCP. In this case the outbound attempts are on both port 80 and port 443, so you’ll need two rules.]
Here’s the scenario: when using AAMEE (the “Adobe Application Manager Enterprise Edition”) to install Adobe Creative Suite 6 on a machine  on an isolated LAN (i.e., a machine with no direct connection to the internet) it takes a very long time to install. A very, very long time. During most of this time CPU and disk activity are minimal.
It turns out that the installer is trying to contact various web sites on the internet, including crl.verisign.net, presumably in order to see whether any of the digital certificates on files in the install media have been revoked. When the attempt times out, the installer continues, but it makes many such attempts.
The workaround I recommend is to install an outbound Windows Firewall rule blocking web traffic. Windows then instantly fails any attempt to contact a web site. You can do this from an administrative command line like this (split for readability):
netsh advfirewall firewall add rule name="block www" dir=out action=block protocol=tcp remoteport=80
To remove the rule later, this is the command:
netsh advfirewall firewall delete rule name="block www"
So how much time does this save? Well, on one of our new machines, the installer takes 30 minutes if the firewall rule is in place. Without it, it takes five hours.
I’ll be raising this with Adobe and perhaps, if we’re lucky, the next version won’t be quite so vigorous in its efforts to check the digital signatures. In the meantime, you may find this approach useful.
 The same problem may exist when using the regular installer; I haven’t checked.