Quantcast
Channel: All Forums
Viewing all articles
Browse latest Browse all 28504

Web Proxy Workaround

$
0
0

We recently had to install extensions only available on the Web Platform Installer.  The problem we ran into was that Web Platform Installer didn't work as intended (i.e. using IE proxy setting), so it was failing with the "cannot connect to network / download product list" error.  For other extensions, the MSI file still required the use of Web Platform Installer.  So below is what we had to do to get these extensions installed going around the proxy.  I hope this helps, or at the very least, supplements the instructions already available.

To install extensions through Web Platform Installer around a proxy:

1.) Download WebPICMD.exe utility (http://www.iis.net/learn/install/web-platform-installer/web-platform-installer-v4-command-line-webpicmdexe-preview-release_1072)

2.) Use it with the Offline flag to download the items you need (this step has to be done on a machine outside of the proxy)

- The list for v4 is available at http://www.microsoft.com/web/webpi/4.0/WebProductList.xml (Use the productId)

- Example of a batch file to download the Web Farm Framework 2.2 (Product ID = WebFarmFrameworkv2) and SQL Server Data Tools for VS2010 (Product Id = SSDTVS2010) to the C-drive.

WebPICMD.exe /Offline /Products:SSDTVS2010,WebFarmFrameworkv2 /Path:C:\

pause

3.) Copy contents onto machine inside proxy. Note the directory.

4.) Create a batch file in the <ProductId>\feeds directory called "Install.bat"

5.) Paste the following:

WebPICMD.exe /Install /Products:<ProductId> /XML:"<Copy Location>\<ProductId>\feeds\shadow-webproductlist.xml" /Log:Install.log

6,) Run the batch file

7.) Review log file for errors (Install.log)

Troubleshooting:

1.) Some extensions are dependent on certain versions of the Web Platform Installer (believe it or not). For example, the Web Farm Framework v2.2 is dependent on WPI v3

2.) Sometimes the installation file needs to be run directly due to failure from running in batch file (for example, SSDT). You should be able to determine the location of the installationfile from the log file.

Links to WPI versions

v3

x64 -

http://download.microsoft.com/download/B/0/0/B00FEF21-79DE-48B0-8731-F9CFE70CE613/WebPlatformInstaller_3_10_amd64_en-US.msi

x86 -

http://download.microsoft.com/download/B/0/0/B00FEF21-79DE-48B0-8731-F9CFE70CE613/WebPlatformInstaller_3_10_x86_en-US.msi

v4

 http://www.microsoft.com/web/downloads/platform.aspx

Feel free to correct / propose suggestions!  Thanks!


Viewing all articles
Browse latest Browse all 28504

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>