Descarga e Instala Windows Post Install (WPI) (2011) [ISO Español] - YouTube

hi andrew the msi you mention is actually the setup package for the web platform installer itself and doesn't include the url rewrite installer within that. you would install the wpi first and then use that to install the url rewrite package. you can download the latest wpi setup package from here: (x64 version) having built a new server three days ago, i know the latest wpi setup package to be working, but then encountered the url rewrite issue discussed above. the error messages you posted list the same error regarding the url rewrite package, there is no mention of an issue with the wpi package. i would recommend downloading the latest wpi package and combining that in your build with the url rewrite package kindly provided by terry above as this has resolved the issue for both me and others in this post. kind regards ian

Windows Post Install (WPI) (2011) [Spanish ISO] Download

the wpi is the installation setup for the web platform installer tool (download it from ms). this is installed as a prerequisite to installing many of the web/microsoft tools like the url rewriting module. this is not the tool that turns url's into www so you must use the wu tool for this. both the wu and the wpi tools should be uninstalled before installing the urlrewrite tool. you will need to run both wu and wpi, then the url rewrite tool. incorrect, windows server 2008 r2 has never had its iso's signed by microsoft and never would. when the dhcp client joins the domain, it generates a new certificate which is signed by the certificate authority. before windows server 2008 r2, this certificate was trusted only by the windows installer and it would not trust a certificate signed by "..". therefore, it was simply not possible to install these certificate chains on a physical machine until the certificate authorities were updated. yes, you can absolutely install it and have the links to the /home or %userprofile% folder point directly to your domain controller. however, if you're making a server where the windows will reside, then you cannot use the links in the browser, you will need to update the links in the windows explorer to the /home of the user that windows is assigned to. most servers only need the following: file server service file services print services tftp server service tftp server what about the dhcp, dns, active directory, dhcp and dns services? if the setup will fail with a dialog stating "the program was unable to start because another application is already running. please close other applications and try again." i would recommend uninstalling the following. windows server 2008 r2 does support non-spinning drives. this is a known issue with the installer. to work around this, you can either use the 3tb iscsi or use a ssd and a standard hard disk. in this case, you will need a license for windows. this is the basic requirement for windows server 2008 r2. if your server requires more memory, you will need to consider windows server 2008 instead of windows server 2008 r2. you will need to install and configure these, and then you can install windows server 2008 r2 from there.