| A few colleagues are running into a problem where during the SharePoint 2013 prerequisites install (or product preparation tool), on their Windows 2012 server, the tool continually fails creating the application/web server role and causes the system to go into an endless reboot/restart. The workaround has been published in a Microsoft Support KB Article (KB2765260) - http://support.microsoft.com/kb/2765260. When this problem occurs, the Products Preparation Tool does not progress past the "Configuring Application Server Role, Web Server (IIS) Role" stage. Workaround - Make sure that the server meets the minimum hardware requirements for SharePoint Server 2013. For more information about the minimum hardware requirements for SharePoint Server 2013, go to the following Microsoft TechNet website:
Hardware and software requirements for SharePoint 2013 - Install Windows Features for SharePoint manually. To do this, run the following commands in an elevated Windows PowerShell Command Prompt window:
Import-Module Servermanager Add-WindowsFeature NET-WCF-HTTP-Activation45,NET-WCF-TCP-Activation45,NET-WCF-Pipe-Activation45 Add-WindowsFeature Net-Framework-Features,Web-Server,Web-WebServer,Web-Common-Http,Web-Static-Content,Web-Default-Doc,Web-Dir-Browsing,Web-Http-Errors,Web-App-Dev,Web-Asp-Net,Web-Net-Ext,Web-ISAPI-Ext,Web-ISAPI-Filter,Web-Health,Web-Http-Logging,Web-Log-Libraries,Web-Request-Monitor,Web-Http-Tracing,Web-Security,Web-Basic-Auth,Web-Windows-Auth,Web-Filtering,Web-Digest-Auth,Web-Performance,Web-Stat-Compression,Web-Dyn-Compression,Web-Mgmt-Tools,Web-Mgmt-Console,Web-Mgmt-Compat,Web-Metabase,Application-Server,AS-Web-Support,AS-TCP-Port-Sharing,AS-WAS-Support, AS-HTTP-Activation,AS-TCP-Activation,AS-Named-Pipes,AS-Net-Framework,WAS,WAS-Process-Model,WAS-NET-Environment,WAS-Config-APIs,Web-Lgcy-Scripting,Windows-Identity-Foundation,Server-Media-Foundation,Xps-Viewer - Run the Products Preparation Tool again.
[1] http://support.microsoft.com/kb/2765260 |