This article uses the same core steps to install WSUS Role on Windows Server 2012 as the article Step 2: Install the WSUS server role. The only change in this article is related to which database WSUS will use, in this case it will be Microsoft SQL Server.
1. Log on to the server on which you plan to install the WSUS server role by using an account that is a member of the Local Administrators group.
2. In Server Manager, click Dashboard, and then click Add roles and features.
3. On the Before you begin page, click Next.
4. In the Select installation type page, confirm that Role-based or feature-based installation option is selected and click Next.
5. On the Select destination server page, choose where the server is located (from a server pool or from a virtual hard disk). After you select the location, choose the server that you want to install the WSUS server role, and then click Next.
6. On the Select server roles page, select Windows Server Update Services. 7. In the Add Roles and Features Wizard dialog box, click Add Features, and then click Next.
8. On the Select features page, leave the default selections, and then click Next. Note: WSUS only requires the default Web Server role configuration. If you are prompted for additional Web Server role configuration while setting up WSUS you can safely accept the default values and continue setting up WSUS.
9. On the Windows Server Update Services page, click Next.
10. On the Select Role Services page, select Database, uncheck WID (both can't be used at the same time), and then click Next. 11. On the Database Instance Selection page type the name of the SQL Server (MachineName\Instance) and click Check Connection. If the connection between WSUS and SQL Server is working properly you can click Next to proceed. 12. On the Content location selection page, type a valid location to store the updates, and then click Next.
13. On the Confirm installation selections page, review the selected options, and then click Install.
14. On the Installation progress page, make sure that the installation succeeded, and then click Close.
15. In Server Manager, verify if a notification appears to inform you that a restart is required. This can vary according to the installed server role. If it requires a restart make sure to restart the server to complete the installation.
At this point you can follow Step 3, which is Configure WSUS Server.
Yagmoth555 edited Revision 5. Comment: good articles ! linked from windows 2012 portal & added minor tag
FZB edited Revision 3. Comment: formating
Microsoft WSUS Team edited Revision 2. Comment: adding last paragraph
Microsoft WSUS Team edited Revision 1. Comment: Fixing step 11 again
Microsoft WSUS Team edited Original. Comment: Fixing step 11
That would be powershell-wise
I thought this was even easier and without the errors I had trying this method:
Install-WindowsFeature -Name UpdateServices-Services,UpdateServices-DB –IncludeManagementTools
&
wsusutil.exe postinstall SQL_INSTANCE_NAME="SERVER-DC1" CONTENT_DIR=D:\WSUS
NOTE: SQL on same server as WSUS so server instance is same.
This is awesome. But Freddy is correct.
Nice post
For the author : There is a missing step after the step 12; about the IIS Web Service Role installation
Good evening,
at point 13, it recognise correctly sql server (2008) and then will stop.
log report this:
2012-10-25 16:29:33 Postinstall started
2012-10-25 16:29:33 Detected role services: Api, Database, Services
2012-10-25 16:29:33 Start: LoadSettingsFromXml
2012-10-25 16:29:33 Start: GetConfigValue with filename=UpdateServices-Services.xml item=ContentLocal
2012-10-25 16:29:33 Value is true
2012-10-25 16:29:33 End: GetConfigValue
2012-10-25 16:29:33 Start: GetConfigValue with filename=UpdateServices-Services.xml item=ContentDirectory
2012-10-25 16:29:33 Value is e:\
2012-10-25 16:29:33 Content directory is e:\
2012-10-25 16:29:33 Start: GetConfigValue with filename=UpdateServices-DB.xml item=InstanceName
2012-10-25 16:29:33 Value is argosqlotto
2012-10-25 16:29:33 SQL instance name is argosqlotto
2012-10-25 16:29:33 End: LoadSettingsFromXml
Post install is starting
2012-10-25 16:29:33 Start: Run
2012-10-25 16:29:33 Configuring content directory...
2012-10-25 16:29:33 Configuring groups...
2012-10-25 16:29:33 Starting group configuration for WSUS Administrators...
2012-10-25 16:29:33 Found group in regsitry, attempting to use it...
2012-10-25 16:29:35 Writing group to registry...
2012-10-25 16:29:35 Finished group creation
2012-10-25 16:29:35 Starting group configuration for WSUS Reporters...
2012-10-25 16:29:35 Found group in regsitry, attempting to use it...
2012-10-25 16:29:35 Configuring permissions...
2012-10-25 16:29:35 Fetching content directory...
2012-10-25 16:29:35 Fetching ContentDir from registry store
2012-10-25 16:29:35 Value is e:\
2012-10-25 16:29:35 Fetching group SIDs...
2012-10-25 16:29:35 Fetching WsusAdministratorsSid from registry store
2012-10-25 16:29:35 Value is S-1-5-21-4239855068-164700391-3746156017-1001
2012-10-25 16:29:35 Fetching WsusReportersSid from registry store
2012-10-25 16:29:35 Value is S-1-5-21-4239855068-164700391-3746156017-1002
2012-10-25 16:29:35 Creating group principals...
2012-10-25 16:29:35 Granting directory permissions...
2012-10-25 16:29:35 Granting permissions on content directory...
2012-10-25 16:29:35 Granting registry permissions...
2012-10-25 16:29:35 Configuring shares...
2012-10-25 16:29:35 Configuring network shares...
2012-10-25 16:29:35 Fetching WSUS admin SID...
2012-10-25 16:29:35 Content directory is local, creating content shares...
2012-10-25 16:29:35 Creating share "UpdateServicesPackages" with path "e:\UpdateServicesPackages" and description "A network share to be used by client systems for collecting all software packages (usually applications) published on this WSUS system."
2012-10-25 16:29:35 Deleting existing share...
2012-10-25 16:29:35 Creating share...
2012-10-25 16:29:35 Share successfully created
2012-10-25 16:29:35 Creating share "WsusContent" with path "e:\WsusContent" and description "A network share to be used by Local Publishing to place published content on this WSUS system."
2012-10-25 16:29:35 Creating share "WSUSTemp" with path "C:\Program Files\Update Services\LogFiles\WSUSTemp" and description "A network share used by Local Publishing from a Remote WSUS Console Instance."
2012-10-25 16:29:35 Finished creating content shares
2012-10-25 16:29:35 Configuring database...
2012-10-25 16:29:35 Configuring the database...
2012-10-25 16:29:35 Establishing DB connection...
2012-10-25 16:29:35 System.Data.SqlClient.SqlException (0x80131904): Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK)
at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean ignoreSniOpenTimeout, TimeoutTimer timeout, Boolean withFailover)
at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString connectionOptions, SqlCredential credential, TimeoutTimer timeout)
at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(TimeoutTimer timeout, SqlConnectionString connectionOptions, SqlCredential credential, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString userConnectionOptions)
at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions)
at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnectionPool pool, DbConnectionOptions options, DbConnectionPoolKey poolKey, DbConnectionOptions userOptions)
at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnectionOptions userOptions)
at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnectionOptions userOptions)
at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection)
at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection)
at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection)
at System.Data.ProviderBase.DbConnectionClosed.TryOpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry)
at System.Data.SqlClient.SqlConnection.Open()
at Microsoft.UpdateServices.DatabaseAccess.DBConnection.Connect(String connectionString)
at Microsoft.UpdateServices.DatabaseAccess.DBConnection.Connect()
at Microsoft.UpdateServices.Administration.ConfigureDB.CreateDBConnection()
at Microsoft.UpdateServices.Administration.ConfigureDB.ConnectToDB()
at Microsoft.UpdateServices.Administration.ConfigureDB.Configure()
at Microsoft.UpdateServices.Administration.PostInstall.Run()
at Microsoft.UpdateServices.Administration.PostInstall.Execute(String[] arguments)
ClientConnectionId:279bf9bd-c9e5-4fc2-a38c-e8c3d377e256
Fatal Error: Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.