Our enterprise also uses an authenticated proxy, so I've been banging my head to get this working!
I'm surprise to learn of this proxy oversight! This tool has "enterprise" all over the documentation (e.g. AAMEE?). There's good likelihood that other enterprises (still) have proxies in place. Makes me wonder if the CreativeCloud architects had this same proxy-ignorant oversite?
@Abhishek
Can you pass this request onto Jody Rogers or Karl Gibson (or whomever "owns" Adobe Enterprise Deployment products)?
I can pass the following curl switches and get out of our authenticated proxy; why can't you make AdobeUpdateServerSetupTool2.0 honor these curl options?
[Note: this example assumes Mac OS X or other Unix-y OSes]
curl --proxy myproxy.domain.com:port --proxy-user ADserviceAccount http://swupmf.adobe.com/webfeed/oobe/aam10/win/updaterfeed.xml
BTW: why does "mac" in xml feed return so much more info?
curl --proxy myproxy.domain.com:port --proxy-user ADserviceAccount http://swupmf.adobe.com/webfeed/oobe/aam10/mac/updaterfeed.xml