询问者
部署wsus前置条件

问题
全部回复
-
你好,
您不需要一个域来实现这一点,但是通过GPO配置客户端在域中要容易得多。
您可以使用本地组策略或直接在registry中配置对WSUS的客户端访问。
根据官网的安装需求描述,确认您计划用于安装WSUS的帐户是Local Administrators组的成员。
如果回答是有帮助的, 请将其标记为答案, 可以帮助其他有相同问题的社区成员, 并快速找到有用的答复。
针对Windows 2008/2008R2的扩展支持将于2020年结束,之后微软将不再为其提供安全更新。点击此处或扫描二维码获取《在 Azure 上运行 Windows Server 的终极指南》,把握良机完成云迁移并实现业务现代化。
- 已编辑 Carl FanMicrosoft contingent staff 2020年1月17日 9:22
-
我的就是用有local administrators组权限的域账号安装wsus角色的时候提示“windows更新服务配置失败”,产生日志如下:
2019-12-24 17:21:35 Postinstall started
2019-12-24 17:21:35 Detected role services: Api, UI, WidDatabase, Services
2019-12-24 17:21:35 Start: LoadSettingsFromXml
2019-12-24 17:21:35 Start: GetConfigValue with filename=UpdateServices-Services.xml item=ContentLocal
2019-12-24 17:21:35 Value is true
2019-12-24 17:21:35 End: GetConfigValue
2019-12-24 17:21:35 Start: GetConfigValue with filename=UpdateServices-Services.xml item=ContentDirectory
2019-12-24 17:21:35 Value is E:\hotfix
2019-12-24 17:21:35 End: GetConfigValue
2019-12-24 17:21:35 Content directory is E:\hotfix
2019-12-24 17:21:35 Database roleservice is not installed
2019-12-24 17:21:35 End: LoadSettingsFromXml
正在启动安装后步骤
2019-12-24 17:21:35 Start: Run
2019-12-24 17:21:35 Fetching WsusAdministratorsSid from registry store
2019-12-24 17:21:35 Value is S-1-5-21-3664393768-2240217363-45894770-1000
2019-12-24 17:21:35 Fetching WsusReportersSid from registry store
2019-12-24 17:21:35 Value is S-1-5-21-3664393768-2240217363-45894770-1001
2019-12-24 17:21:36 Configuring content directory...
2019-12-24 17:21:36 Configuring groups...
2019-12-24 17:21:36 Starting group configuration for WSUS Administrators...
2019-12-24 17:21:36 Found group in regsitry, attempting to use it...
2019-12-24 17:21:38 Writing group to registry...
2019-12-24 17:21:38 Finished group creation
2019-12-24 17:21:38 Starting group configuration for WSUS Reporters...
2019-12-24 17:21:38 Found group in regsitry, attempting to use it...
2019-12-24 17:21:38 Writing group to registry...
2019-12-24 17:21:38 Finished group creation
2019-12-24 17:21:38 Configuring permissions...
2019-12-24 17:21:38 Fetching content directory...
2019-12-24 17:21:38 Fetching ContentDir from registry store
2019-12-24 17:21:38 Value is E:\hotfix
2019-12-24 17:21:38 Fetching group SIDs...
2019-12-24 17:21:38 Fetching WsusAdministratorsSid from registry store
2019-12-24 17:21:38 Value is S-1-5-21-3664393768-2240217363-45894770-1000
2019-12-24 17:21:38 Fetching WsusReportersSid from registry store
2019-12-24 17:21:38 Value is S-1-5-21-3664393768-2240217363-45894770-1001
2019-12-24 17:21:38 Creating group principals...
2019-12-24 17:21:38 Granting directory permissions...
2019-12-24 17:21:39 Granting permissions on content directory...
2019-12-24 17:21:39 Granting registry permissions...
2019-12-24 17:21:39 Granting registry permissions...
2019-12-24 17:21:39 Granting registry permissions...
2019-12-24 17:21:39 Configuring shares...
2019-12-24 17:21:39 Configuring network shares...
2019-12-24 17:21:39 Fetching content directory...
2019-12-24 17:21:39 Fetching ContentDir from registry store
2019-12-24 17:21:39 Value is E:\hotfix
2019-12-24 17:21:39 Fetching WSUS admin SID...
2019-12-24 17:21:39 Fetching WsusAdministratorsSid from registry store
2019-12-24 17:21:39 Value is S-1-5-21-3664393768-2240217363-45894770-1000
2019-12-24 17:21:39 Content directory is local, creating content shares...
2019-12-24 17:21:39 Creating share "UpdateServicesPackages" with path "E:\hotfix\UpdateServicesPackages" and description "A network share to be used by client systems for collecting all software packages (usually applications) published on this WSUS system."
2019-12-24 17:21:39 Deleting existing share...
2019-12-24 17:21:39 Creating share...
2019-12-24 17:21:39 Share successfully created
2019-12-24 17:21:39 Creating share "WsusContent" with path "E:\hotfix\WsusContent" and description "A network share to be used by Local Publishing to place published content on this WSUS system."
2019-12-24 17:21:39 Deleting existing share...
2019-12-24 17:21:39 Creating share...
2019-12-24 17:21:39 Share successfully created
2019-12-24 17:21:39 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."
2019-12-24 17:21:39 Deleting existing share...
2019-12-24 17:21:39 Creating share...
2019-12-24 17:21:39 Share successfully created
2019-12-24 17:21:39 Finished creating content shares
2019-12-24 17:21:39 Stopping service WSUSService
2019-12-24 17:21:39 Stopping service W3SVC
2019-12-24 17:21:41 Configuring WID database...
2019-12-24 17:21:41 Configuring the database...
2019-12-24 17:21:41 Establishing DB connection...
2019-12-24 17:21:41 Checking to see if database exists...
2019-12-24 17:21:41 Database exists
2019-12-24 17:21:41 Switching database to single user mode...
2019-12-24 17:21:41 Loading install type query...
2019-12-24 17:21:41 DECLARE @currentDBVersion int
DECLARE @scriptMajorVersion int = (14393)
DECLARE @scriptMinorVersion int = (0)
DECLARE @databaseMajorVersion int
DECLARE @databaseMinorVersion int
DECLARE @databaseBuildNumber nvarchar(10)
IF NOT EXISTS(SELECT * FROM sys.databases WHERE name='SUSDB')
BEGIN
SELECT 1
END
ELSE
BEGIN
SET @currentDBVersion = (SELECT SchemaVersion FROM SUSDB.dbo.tbSchemaVersion WHERE ComponentName = 'CoreDB')
SET @databaseBuildNumber = (SELECT BuildNumber FROM SUSDB.dbo.tbSchemaVersion WHERE ComponentName = 'CoreDB')
DECLARE @delimiterPosition INT = CHARINDEX('.', @databaseBuildNumber)
IF (@delimiterPosition = 0)
BEGIN
RAISERROR('Invalid schema version number', 16, 1) with nowait
return
END
SET @databaseMajorVersion = SUBSTRING(@databaseBuildNumber, 1, @delimiterPosition - 1)
SET @databaseMinorVersion = SUBSTRING(@databaseBuildNumber, (@delimiterPosition + 1), (10 - @delimiterPosition))
IF @currentDBVersion < 926
BEGIN
SELECT 3
END
ELSE
BEGIN
IF (@scriptMajorVersion > @databaseMajorVersion OR
(@scriptMajorVersion = @databaseMajorVersion AND @scriptMinorVersion > @databaseMinorVersion))
BEGIN
SELECT 2
END
ELSE IF (@scriptMajorVersion = @databaseMajorVersion AND
@scriptMinorVersion = @databaseMinorVersion)
BEGIN
SELECT 0
END
ELSE
BEGIN
SELECT 4
END
END
END2019-12-24 17:21:41 Install type is: Reinstall
2019-12-24 17:21:41 Creating logins...
2019-12-24 17:21:41 Fetching account info for S-1-5-20
2019-12-24 17:21:41 Found principal
2019-12-24 17:21:41 Found account
2019-12-24 17:21:41 Got binary SID
2019-12-24 17:21:41 Fetching WsusAdministratorsSid from registry store
2019-12-24 17:21:41 Value is S-1-5-21-3664393768-2240217363-45894770-1000
2019-12-24 17:21:41 Fetching account info for S-1-5-21-3664393768-2240217363-45894770-1000
2019-12-24 17:21:42 Found principal
2019-12-24 17:21:42 Found account
2019-12-24 17:21:42 Got binary SID
2019-12-24 17:21:42 Setting content location...
2019-12-24 17:21:42 Fetching ContentDir from registry store
2019-12-24 17:21:42 Value is E:\hotfix
2019-12-24 17:21:42 Swtching DB to multi-user mode......
2019-12-24 17:21:42 System.Data.SqlClient.SqlException (0x80131904):
在 Microsoft.UpdateServices.DatabaseAccess.DBConnection.DrainObsoleteConnections(SqlException e)
在 Microsoft.UpdateServices.DatabaseAccess.DBConnection.ExecuteCommandNoResult()
在 Microsoft.UpdateServices.Administration.ConfigureDB.ExecuteQueryNoResults(String query)
在 Microsoft.UpdateServices.Administration.ConfigureDB.SetMultiUser(Boolean noFail)
ClientConnectionId:8800f7e2-6f59-46ae-a72c-dae36fc5c5d0
Error Number:3605,State:1,Class:16
2019-12-24 17:21:42 Disposing Connection
2019-12-24 17:21:42 Clearing Connection Pools
2019-12-24 17:21:42 System.Data.SqlClient.SqlException (0x80131904):
在 Microsoft.UpdateServices.DatabaseAccess.DBConnection.DrainObsoleteConnections(SqlException e)
在 Microsoft.UpdateServices.DatabaseAccess.DBConnection.ExecuteCommandNoResult()
在 Microsoft.UpdateServices.Administration.ConfigureDB.ExecuteQueryNoResults(String query)
在 Microsoft.UpdateServices.Administration.ConfigureDB.SetMultiUser(Boolean noFail)
在 Microsoft.UpdateServices.Administration.ConfigureDB.Configure()
在 Microsoft.UpdateServices.Administration.ConfigureDB.Run(String instanceName, Action`1 logWriter, Boolean contentLocal)
在 Microsoft.UpdateServices.Administration.PostInstall.Run()
在 Microsoft.UpdateServices.Administration.PostInstall.Execute(String[] arguments)
ClientConnectionId:8800f7e2-6f59-46ae-a72c-dae36fc5c5d0
Error Number:3605,State:1,Class:16
严重错误:
-
你好,
看到您得到信息,似乎是在安装数据库这步有问题,就是这个WID.
如果您正在使用WID,请卸载WSUS & Windows内部数据库(WID)。重新启动以进行清理。
一旦启动,删除C:\WINDOWS\WID目录和所有的文件,重新安装WSUS.
如果回答是有帮助的, 请将其标记为答案, 可以帮助其他有相同问题的社区成员, 并快速找到有用的答复。
针对Windows 2008/2008R2的扩展支持将于2020年结束,之后微软将不再为其提供安全更新。点击此处或扫描二维码获取《在 Azure 上运行 Windows Server 的终极指南》,把握良机完成云迁移并实现业务现代化。
- 已编辑 Carl FanMicrosoft contingent staff 2020年1月17日 9:22
-
1。我已经卸载了wid并清理wid目录及所有文件后重新安装还是报这个错误,是否跟我的操作系统为Windows2016 标准板有关?
2。首台wsus是否需要联网?
- 已编辑 small-fish 2019年12月29日 8:44