Server 2012 R2 WSUS - Product's Missing / Different to SUP 2012 R2

Hi @all,
is there any Hotfix or Settings-Set exist, where i can add, missing Products in WSUS
My problem is, that some Product f.e. Windows 7 Language Pack's are missing in WSUS von Server 2012 R
THX for information about.
Greetz Berni

Hi,
Windows 7 language packs are available for computers that are running Windows 7 Ultimate or Windows 7 Enterprise. The Windows 7 language packs can be installed only from the Optional Updates section in Windows Update. However, these language packs are not
available on the Microsoft Windows Server Update Services (WSUS) server or through the Microsoft Download Center.
The following technet articles might be of more help:
Use the lpksetup.exe command.
http://technet.microsoft.com/en-us/library/cc748922(v=ws.10).aspx
This example shows how to install multiple language packs.
http://technet.microsoft.com/en-us/library/cc766010(v=ws.10).aspx
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Similar Messages

Windows Server 2012 Foundation, in a Workgroup - "The server did not finish checking the license compliance. If the server is joined to a domain, make sure that the server can connect to a domain controller"...

Every few days we see two dialogs with the following messages:
Dialog 1, title: Check for Licensing Compliance is Incomplete
The server did not finish checking the license compliance. If the server is joined to a domain, make sure that the server can connect to a domain controller.
Dialog 2, title: Check for Licensing Compliance is Incomplete
The server did not finish checking the license compliance. If the server is joined to a domain, make sure that the server can connect to a domain controller. If the license compliance check cannot be completed, the server will automatically shut
down in 8 day(s) 23 hour(s) 0 minute(s).
The server is not (and never has been) joined to a domain or had any DC roles installed. In fact its still connected to the default Workgroup.
The server was configured in our office and never showed this message until it was installed on site. The main difference from what I can see is that when installed on site it was given a static IP address and does not have any DNS settings in the network
adapter properties.
I have scoured a number of forums on this error but in almost every other instance of this error message the servers are connected to a Domain Controller and the solutions generally are linked to dis-joining and rejoining the domain. Unfortunately this is
not an option for this scenario.
I initially thought that adding some relevant DNS server IP address may resolve the issue, however, we have the exact same model server configured exactly the same running at a different site that does not experience this problem. This server also has no
DNS server configured.
I have seen a post that suggests turning off the servers "Foundation Checking", but I'm unsure how to do this.

Thanks for your response Vivian.
I can confirm that this server is not (and never has been) a member of any active directory, it is configured as a Workgroup server. It was initially configured on a network that does have an active directory, but was never joined to it. During that time it
never displayed these messages.
The server was moved into production on a different site and network and setup with a static IP address.The site network does have its own active directory but the server was not joined to it. It is whilst on this new network that these messages began.
Since my original post DNS servers have been added and the Microsoft activation has been verified, however, the messages are still appearing.
There are only 2 user accounts configured on this server. The local admin account and another local admin user.
The remote desktop services roles have been installed but not yet configured. I don't think that has any bearing on this scenario though.
The description of this error in the above "Introduction to Windows Server 2012 Foundation" link states:
This error occurs when the server cannot finish checking the requirements for the root domain, forest trust configuration, or both. It usually happens when the server cannot connect to a domain controller. If the situation persists, the server will
shut down 10 days after the first time the compliance check failed. Each time this error message occurs, it will state the actual time remaining before the server will shut down. If you restart the server after it has shut down because of non-compliance, the
server will shut itself down again in 3 days.
The above description leads me to the following question - In a Workgroup environment, does the server still try to contact a domain controller to establish a level of trust? If this is the case could it be that the server can no longer see the initial DC
on its new network and this is what is triggering the messages?
Am I clutching at straws here?

SQL Server 2012 BI Features (Standart Edition)

Hello everyone
I've a question about licensing in SharePoint and SQL Server. Firstly, we are using SharePoint 2013 Enterprise edition and SQL Server 2012 Standart edition. Which of tools below are possible use integrated with SharePoint 2013 with our current
SQL Server Edition?
-PowerView
-PowerPivot
-SSRS
Also, is it possible to Analysis services intensively with our SQL server Standtart edition? For instance, creating cubes,data mining, forecasting, etc.. ?
Thanks in advance..

Hi Omnipotent06,
Reporting Services in SharePoint mode is a collection of server components that provide report generation and delivery, based on Microsoft SQL Server and Microsoft SharePoint products. But different features are supported by the different
editions of SQL Server 2012. If we are using SQL Server 2012 Standard edition, there are many limitations. For example, Power View and PowerPivot are not supported in SQL Server 2012 Standard edition.
It supports most features of Reporting Services, except Data driven report subscription, Scale out deployment(Web farms) and Alerting. As to Analysis Services, it supports Backup/Restore, Attach/Detach databases, High Availability and
Programmability (AMO, ADOMD.Net, OLEDB, XML/A, ASSL) features. For more details, please see the following document:
http://technet.microsoft.com/en-us/library/cc645993.aspx
The following excellent article is for your reference:
Installing Reporting Services SharePoint Mode Report Server for Power View and Data Alerting
Hope this helps.
Thanks,
Katherine Xiong
If you have any feedback on our support, please click
here.
Katherine Xiong
TechNet Community Support

New WSUS on Server 2012 - problem with win8 clients

Hi,
Two weeks ago we created a new Server 2012 and installed the WSUS role from scratch on it. Its version number is: 6.2.9200.16384. It replaced a Server 2008 WSUS server. After some time all the win7 clients updated and reported as
they did on the old and replaced server.
However all our win8 clients refuse to update against this server. They show correctly up in WSUS server console each with 107 needed updates day after day. We have rebooted them and done numerous wuauclt /resetauthorization /detectnow and wuauclt
/detectnow /reportnow, but to no avail.
I paste in some lines from a win8 client winupdate log at the end of this message if someone can figure out what I have to do to get these clients update as they did against the old wsus server. Thanks for help on this issue.
regards Tor
2014-02-03   08:33:38:008   920   153c   Agent   *************
2014-02-03   08:33:38:008   920   153c   Agent   ** START ** Agent: Finding updates [CallerId = Windows Update Command Line]
2014-02-03   08:33:38:008   920   153c   Agent   *********
2014-02-03   08:33:38:008   920   153c   Agent      * Online = Yes; Ignore download priority = No
2014-02-03   08:33:38:008   920   153c   Agent      * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation'
or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2014-02-03   08:33:38:008   920   153c   Agent      * ServiceID = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} Third party service
2014-02-03   08:33:38:008   920   153c   Agent      * Search Scope = {Machine & All Users}
2014-02-03   08:33:38:008   920   153c   Agent      * Caller SID for Applicability: S-1-5-18
2014-02-03   08:33:38:008   920   153c   Misc   Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\wuredir.cab:
2014-02-03   08:33:38:008   920   1990   AU   >>## RESUMED ## AU: Search for updates [CallId = {ABC7E77F-635F-4192-9B92-CBF9B1CB8AB0} ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}]
2014-02-03   08:33:38:008   920   1990   AU      # 0 updates detected
2014-02-03   08:33:38:008   920   1990   AU   #########
2014-02-03   08:33:38:008   920   1990   AU   ## END ## AU: Search for updates [CallId = {ABC7E77F-635F-4192-9B92-CBF9B1CB8AB0} ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}]
2014-02-03   08:33:38:008   920   1990   AU   #############
2014-02-03   08:33:38:023   920   153c   Misc   Microsoft signed: Yes
2014-02-03   08:33:38:023   920   153c   Misc   Infrastructure signed: Yes
2014-02-03   08:33:38:023   920   153c   EP   Got 9482F4B4-E343-43B6-B170-9A65BC822C77 redir SecondaryServiceAuth URL: "http://fe1.ws.microsoft.com/w8/2/redir/storeauth.cab"
2014-02-03   08:33:38:023   920   153c   Misc   Validating signature for C:\Windows\SoftwareDistribution\WuRedir\117CAB2D-82B1-4B5A-A08C-4D62DBEE7782\wuredir.cab:
2014-02-03   08:33:38:039   920   153c   Misc   Microsoft signed: Yes
2014-02-03   08:33:38:039   920   153c   Misc   Infrastructure signed: Yes
2014-02-03   08:33:38:039   920   153c   EP   Got 117CAB2D-82B1-4B5A-A08C-4D62DBEE7782 redir Client/Server URL: "https://fe2.ws.microsoft.com/v6/ClientWebService/client.asmx"
2014-02-03   08:33:38:055   920   153c   PT   +++++++++++ PT: Synchronizing server updates +++++++++++
2014-02-03   08:33:38:055   920   153c   PT      + ServiceId = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}, Server URL = https://fe2.ws.microsoft.com/v6/ClientWebService/client.asmx
2014-02-03   08:33:38:055   920   153c   Agent   Reading cached app categories using lifetime 604800 seconds
2014-02-03   08:33:38:055   920   153c   Agent   Read 0 cached app categories
2014-02-03   08:33:39:211   920   153c   Agent      * Added update {E7FF661C-6A03-4387-A1EE-1D723B52EF60}.3 to search result
2014-02-03   08:33:39:211   920   153c   Agent      * Added update {E8B477DF-479E-4BCA-B8F8-2D987A509009}.2 to search result
2014-02-03   08:33:39:211   920   153c   Agent      * Added update {BB85CCA0-88DC-4DA7-8E81-B7F7E5E73B81}.100 to search result
2014-02-03   08:33:39:211   920   153c   Agent      * Added update {18DEF1D9-4513-467E-9D7E-E1772855BB9E}.100 to search result
2014-02-03   08:33:39:211   920   153c   Agent      * Added update {971D9BE4-5145-4DB5-962C-CEE2EE3A2842}.3 to search result
2014-02-03   08:33:39:211   920   153c   Agent      * Added update {CCB380C9-29F5-4305-96DD-86DE2D00438B}.2 to search result
2014-02-03   08:33:39:211   920   153c   Agent      * Added update {455BDD67-9ED0-4DE7-94F1-3480EA942414}.12 to search result
2014-02-03   08:33:39:211   920   153c   Agent      * Added update {ADFBFCE0-FFD4-4826-B9CF-50AE8182E3C5}.2 to search result
2014-02-03   08:33:39:211   920   153c   Agent      * Added update {BFA8C8B8-EEF7-4A82-A36C-8F760F792430}.3 to search result
2014-02-03   08:33:39:211   920   153c   Agent      * Added update {3F05DE38-92BC-44B6-B06B-5217E5CF12CA}.1 to search result
2014-02-03   08:33:39:211   920   153c   Agent      * Added update {A9A0E183-0667-46D6-84E4-17CEBCEE5A22}.1 to search result
2014-02-03   08:33:39:211   920   153c   Agent      * Added update {36BEF0D5-80ED-4942-8457-6F9C88546E06}.1 to search result
2014-02-03   08:33:39:211   920   153c   Agent      * Added update {A292CD86-AB4E-4388-8C7B-CFB392EDE6AC}.1 to search result
2014-02-03   08:33:39:211   920   153c   Agent      * Found 13 updates and 31 categories in search; evaluated appl. rules of 69 out of 94 deployed entities
2014-02-03   08:33:39:211   920   153c   Agent   *********
2014-02-03   08:33:39:211   920   153c   Agent   ** END ** Agent: Finding updates [CallerId = Windows Update Command Line]
2014-02-03   08:33:39:211   920   153c   Agent   *************
2014-02-03   08:33:39:211   920   1a64   Report   REPORT EVENT: {0786C161-F6DC-4842-85D6-9506124654AD}   2014-02-03 08:33:38:008+0100   1
147 [AGENT_DETECTION_FINISHED]   101   {00000000-0000-0000-0000-000000000000}   0   0   Windows Update Command Line   Success   Software Synchronization
Windows Update Client successfully detected 0 updates.
2014-02-03   08:33:39:211   920   1a64   Report   REPORT EVENT: {1E5D9728-220F-44A3-8BCC-ADE69687531D}   2014-02-03 08:33:38:008+0100   1
156 [AGENT_STATUS_30]   101   {00000000-0000-0000-0000-000000000000}   0   0   Windows Update Command Line   Success   Pre-Deployment Check
Reporting client status.
2014-02-03   08:33:39:211   920   1a64   Report   REPORT EVENT: {57BAB7D0-685B-4D73-BDF7-82AFCE8675B0}   2014-02-03 08:33:39:211+0100   1
147 [AGENT_DETECTION_FINISHED]   101   {00000000-0000-0000-0000-000000000000}   0   0   Windows Update Command Line   Success   Software Synchronization
Windows Update Client successfully detected 13 updates.
2014-02-03   08:33:39:211   920   1a64   Report   CWERReporter finishing event handling. (00000000)
2014-02-03   08:33:39:227   920   153c   Agent   *************
2014-02-03   08:33:39:227   920   153c   Agent   ** START ** Agent: Finding updates [CallerId = Windows Update Command Line]
2014-02-03   08:33:39:227   920   153c   Agent   *********
2014-02-03   08:33:39:227   920   153c   Agent      * Online = No; Ignore download priority = No
2014-02-03   08:33:39:227   920   153c   Agent      * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation'
or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2014-02-03   08:33:39:227   920   153c   Agent      * ServiceID = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} Third party service
2014-02-03   08:33:39:227   920   153c   Agent      * Search Scope = {Current User}
2014-02-03   08:33:39:227   920   153c   Agent      * Caller SID for Applicability: S-1-5-21-4260610346-2664610402-3334891387-1155
2014-02-03   08:33:39:258   920   153c   Agent      * Added update {E8B477DF-479E-4BCA-B8F8-2D987A509009}.2 to search result
2014-02-03   08:33:39:258   920   153c   Agent      * Added update {BB85CCA0-88DC-4DA7-8E81-B7F7E5E73B81}.100 to search result
2014-02-03   08:33:39:258   920   153c   Agent      * Added update {18DEF1D9-4513-467E-9D7E-E1772855BB9E}.100 to search result
2014-02-03   08:33:39:258   920   153c   Agent      * Added update {971D9BE4-5145-4DB5-962C-CEE2EE3A2842}.3 to search result
2014-02-03   08:33:39:258   920   153c   Agent      * Added update {CCB380C9-29F5-4305-96DD-86DE2D00438B}.2 to search result
2014-02-03   08:33:39:258   920   153c   Agent      * Added update {455BDD67-9ED0-4DE7-94F1-3480EA942414}.12 to search result
2014-02-03   08:33:39:258   920   153c   Agent      * Added update {ADFBFCE0-FFD4-4826-B9CF-50AE8182E3C5}.2 to search result
2014-02-03   08:33:39:258   920   153c   Agent      * Added update {3F05DE38-92BC-44B6-B06B-5217E5CF12CA}.1 to search result
2014-02-03   08:33:39:258   920   153c   Agent      * Added update {A9A0E183-0667-46D6-84E4-17CEBCEE5A22}.1 to search result
2014-02-03   08:33:39:258   920   153c   Agent      * Added update {36BEF0D5-80ED-4942-8457-6F9C88546E06}.1 to search result
2014-02-03   08:33:39:258   920   153c   Agent      * Added update {A292CD86-AB4E-4388-8C7B-CFB392EDE6AC}.1 to search result
2014-02-03   08:33:39:258   920   153c   Agent      * Found 11 updates and 29 categories in search; evaluated appl. rules of 58 out of 94 deployed entities
2014-02-03   08:33:39:258   920   153c   Agent   *********
2014-02-03   08:33:39:258   920   153c   Agent   ** END ** Agent: Finding updates [CallerId = Windows Update Command Line]
2014-02-03   08:33:39:258   920   153c   Agent   *************
2014-02-03   08:33:39:258   920   153c   Agent   *************
2014-02-03   08:33:39:258   920   153c   Agent   ** START ** Agent: Finding updates [CallerId = Windows Update Command Line]
2014-02-03   08:33:39:258   920   153c   Agent   *********
2014-02-03   08:33:39:258   920   153c   Agent      * Online = No; Ignore download priority = No
2014-02-03   08:33:39:258   920   153c   Agent      * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation'
or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2014-02-03   08:33:39:258   920   153c   Agent      * ServiceID = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} Third party service
2014-02-03   08:33:39:258   920   153c   Agent      * Search Scope = {Current User}
2014-02-03   08:33:39:258   920   153c   Agent      * Caller SID for Applicability: S-1-5-21-2212025170-3189117132-1219651784-500
2014-02-03   08:33:39:305   920   153c   Agent      * Added update {E8B477DF-479E-4BCA-B8F8-2D987A509009}.2 to search result
2014-02-03   08:33:39:305   920   153c   Agent      * Added update {BB85CCA0-88DC-4DA7-8E81-B7F7E5E73B81}.100 to search result
2014-02-03   08:33:39:305   920   153c   Agent      * Added update {18DEF1D9-4513-467E-9D7E-E1772855BB9E}.100 to search result
2014-02-03   08:33:39:305   920   153c   Agent      * Added update {971D9BE4-5145-4DB5-962C-CEE2EE3A2842}.3 to search result
2014-02-03   08:33:39:305   920   153c   Agent      * Added update {CCB380C9-29F5-4305-96DD-86DE2D00438B}.2 to search result
2014-02-03   08:33:39:305   920   153c   Agent      * Added update {455BDD67-9ED0-4DE7-94F1-3480EA942414}.12 to search result
2014-02-03   08:33:39:305   920   153c   Agent      * Added update {ADFBFCE0-FFD4-4826-B9CF-50AE8182E3C5}.2 to search result
2014-02-03   08:33:39:305   920   153c   Agent      * Added update {BFA8C8B8-EEF7-4A82-A36C-8F760F792430}.3 to search result
2014-02-03   08:33:39:305   920   153c   Agent      * Added update {3F05DE38-92BC-44B6-B06B-5217E5CF12CA}.1 to search result
2014-02-03   08:33:39:305   920   153c   Agent      * Added update {36BEF0D5-80ED-4942-8457-6F9C88546E06}.1 to search result
2014-02-03   08:33:39:305   920   153c   Agent      * Added update {A292CD86-AB4E-4388-8C7B-CFB392EDE6AC}.1 to search result
2014-02-03   08:33:39:305   920   153c   Agent      * Found 11 updates and 30 categories in search; evaluated appl. rules of 60 out of 94 deployed entities
2014-02-03   08:33:39:305   920   153c   Agent   *********
2014-02-03   08:33:39:305   920   153c   Agent   ** END ** Agent: Finding updates [CallerId = Windows Update Command Line]
2014-02-03   08:33:39:305   920   153c   Agent   *************
2014-02-03   08:33:39:305   920   153c   Agent   *************
2014-02-03   08:33:39:305   920   153c   Agent   ** START ** Agent: Finding updates [CallerId = Windows Update Command Line]
2014-02-03   08:33:39:305   920   153c   Agent   *********
2014-02-03   08:33:39:305   920   153c   Agent      * Online = No; Ignore download priority = No
2014-02-03   08:33:39:305   920   153c   Agent      * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation'
or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2014-02-03   08:33:39:305   920   153c   Agent      * ServiceID = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} Third party service
2014-02-03   08:33:39:305   920   153c   Agent      * Search Scope = {Current User}
2014-02-03   08:33:39:305   920   153c   Agent      * Caller SID for Applicability: S-1-5-21-4260610346-2664610402-3334891387-1323
2014-02-03   08:33:39:352   920   153c   Agent      * Added update {E8B477DF-479E-4BCA-B8F8-2D987A509009}.2 to search result
2014-02-03   08:33:39:352   920   153c   Agent      * Added update {BB85CCA0-88DC-4DA7-8E81-B7F7E5E73B81}.100 to search result
2014-02-03   08:33:39:352   920   153c   Agent      * Added update {18DEF1D9-4513-467E-9D7E-E1772855BB9E}.100 to search result
2014-02-03   08:33:39:352   920   153c   Agent      * Added update {971D9BE4-5145-4DB5-962C-CEE2EE3A2842}.3 to search result
2014-02-03   08:33:39:352   920   153c   Agent      * Added update {CCB380C9-29F5-4305-96DD-86DE2D00438B}.2 to search result
2014-02-03   08:33:39:352   920   153c   Agent      * Added update {455BDD67-9ED0-4DE7-94F1-3480EA942414}.12 to search result
2014-02-03   08:33:39:352   920   153c   Agent      * Added update {ADFBFCE0-FFD4-4826-B9CF-50AE8182E3C5}.2 to search result
2014-02-03   08:33:39:352   920   153c   Agent      * Added update {BFA8C8B8-EEF7-4A82-A36C-8F760F792430}.3 to search result
2014-02-03   08:33:39:352   920   153c   Agent      * Added update {3F05DE38-92BC-44B6-B06B-5217E5CF12CA}.1 to search result
2014-02-03   08:33:39:352   920   153c   Agent      * Added update {36BEF0D5-80ED-4942-8457-6F9C88546E06}.1 to search result
2014-02-03   08:33:39:352   920   153c   Agent      * Added update {A292CD86-AB4E-4388-8C7B-CFB392EDE6AC}.1 to search result
2014-02-03   08:33:39:352   920   153c   Agent      * Found 11 updates and 30 categories in search; evaluated appl. rules of 60 out of 94 deployed entities
2014-02-03   08:33:39:352   920   153c   Agent   *********
2014-02-03   08:33:39:352   920   153c   Agent   ** END ** Agent: Finding updates [CallerId = Windows Update Command Line]
2014-02-03   08:33:39:352   920   153c   Agent   *************
2014-02-03   08:33:39:352   920   153c   Agent   *************
2014-02-03   08:33:39:352   920   153c   Agent   ** START ** Agent: Finding updates [CallerId = Windows Update Command Line]
2014-02-03   08:33:39:352   920   153c   Agent   *********
2014-02-03   08:33:39:352   920   153c   Agent      * Online = No; Ignore download priority = No
2014-02-03   08:33:39:352   920   153c   Agent      * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation'
or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2014-02-03   08:33:39:352   920   153c   Agent      * ServiceID = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} Third party service
2014-02-03   08:33:39:352   920   153c   Agent      * Search Scope = {Current User}
2014-02-03   08:33:39:352   920   153c   Agent      * Caller SID for Applicability: S-1-5-21-4260610346-2664610402-3334891387-1282
2014-02-03   08:33:39:383   920   153c   Agent      * Added update {E8B477DF-479E-4BCA-B8F8-2D987A509009}.2 to search result
2014-02-03   08:33:39:383   920   153c   Agent      * Added update {BB85CCA0-88DC-4DA7-8E81-B7F7E5E73B81}.100 to search result
2014-02-03   08:33:39:383   920   153c   Agent      * Added update {18DEF1D9-4513-467E-9D7E-E1772855BB9E}.100 to search result
2014-02-03   08:33:39:383   920   153c   Agent      * Added update {971D9BE4-5145-4DB5-962C-CEE2EE3A2842}.3 to search result
2014-02-03   08:33:39:383   920   153c   Agent      * Added update {CCB380C9-29F5-4305-96DD-86DE2D00438B}.2 to search result
2014-02-03   08:33:39:383   920   153c   Agent      * Added update {455BDD67-9ED0-4DE7-94F1-3480EA942414}.12 to search result
2014-02-03   08:33:39:383   920   153c   Agent      * Added update {ADFBFCE0-FFD4-4826-B9CF-50AE8182E3C5}.2 to search result
2014-02-03   08:33:39:383   920   153c   Agent      * Added update {BFA8C8B8-EEF7-4A82-A36C-8F760F792430}.3 to search result
2014-02-03   08:33:39:383   920   153c   Agent      * Added update {3F05DE38-92BC-44B6-B06B-5217E5CF12CA}.1 to search result
2014-02-03   08:33:39:383   920   153c   Agent      * Added update {36BEF0D5-80ED-4942-8457-6F9C88546E06}.1 to search result
2014-02-03   08:33:39:383   920   153c   Agent      * Added update {A292CD86-AB4E-4388-8C7B-CFB392EDE6AC}.1 to search result
2014-02-03   08:33:39:383   920   153c   Agent      * Found 11 updates and 30 categories in search; evaluated appl. rules of 60 out of 94 deployed entities
2014-02-03   08:33:39:383   920   153c   Agent   *********
2014-02-03   08:33:39:383   920   153c   Agent   ** END ** Agent: Finding updates [CallerId = Windows Update Command Line]
2014-02-03   08:33:39:383   920   153c   Agent   *************
2014-02-03   08:33:39:383   920   1990   AU   >>## RESUMED ## AU: Search for updates [CallId = {66AF0139-896D-4607-8660-B66D2B58EA26} ServiceId = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}]
2014-02-03   08:33:39:383   920   1990   AU      # 12 updates detected
2014-02-03   08:33:39:383   920   1990   AU   #########
2014-02-03   08:33:39:383   920   1990   AU   ## END ## AU: Search for updates [CallId = {66AF0139-896D-4607-8660-B66D2B58EA26} ServiceId = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}]
2014-02-03   08:33:39:383   920   1990   AU   #############
2014-02-03   08:33:39:383   920   1990   AU   All AU searches complete.
2014-02-03   08:33:39:383   920   1990   AU   AU setting next detection timeout to 2014-02-03 10:18:51
2014-02-03   08:33:44:211   920   1a64   Report   CWERReporter finishing event handling. (00000000)
2014-02-03   08:41:39:472   920   1a64   EP   Got WSUS Client/Server URL: "http://elias:8530/ClientWebService/client.asmx"
2014-02-03   08:41:39:472   920   1a64   PT   WARNING: Cached cookie has expired or new PID is available
2014-02-03   08:41:39:472   920   1a64   EP   Got WSUS SimpleTargeting URL: "http://elias:8530"
2014-02-03   08:41:39:472   920   1a64   PT   Initializing simple targeting cookie, clientId = c5e26849-287b-4b96-ba5d-1489d6fad2f2, target group = , DNS name = dt-ikt-tor.framnes.lan
2014-02-03   08:41:39:472   920   1a64   PT      Server URL = http://elias:8530/SimpleAuthWebService/SimpleAuth.asmx
2014-02-03   08:41:39:519   920   1a64   EP   Got WSUS Reporting URL: "http://elias:8530/ReportingWebService/ReportingWebService.asmx"
2014-02-03   08:41:39:519   920   1a64   Report   Uploading 2 events using cached cookie, reporting URL = http://elias:8530/ReportingWebService/ReportingWebService.asmx
2014-02-03   08:41:39:566   920   1a64   Report   Reporter successfully uploaded 2 events.
2014-02-03   08:42:13:212   920   178c   Report   WARNING: CSerializationHelper:: InitSerialize failed : 0x80070002
2014-02-03   08:43:40:450   920   178c   AU   ########### AU: Uninitializing Automatic Updates ###########
2014-02-03   08:43:40:450   920   178c   WuTask   Uninit WU Task Manager
2014-02-03   08:43:40:513   920   178c   Service   *********
2014-02-03   08:43:40:513   920   178c   Service   ** END ** Service: Service exit [Exit code = 0x240001]
2014-02-03   08:43:40:513   920   178c   Service   *************

Today I opened Control Panel / Windows Updates and first did a check for new updates (from the WSUS server). Nothing was found and it reported Windows is Updated.   Then I clicked the link Check for updates from Microsoft via internet, and
it found around 24 updates.
This is confirmation of the point that I made in the previous post. The updates are *NEEDED* by this system, but the updates were not *AVAILABLE* from the assigned WSUS Server. You were able to get them from Windows Update, but that does not fix your continuing
issue with the WSUS Server.
but it still reported the original 108 Needed updates.
Exactly. As previously noted, the client is functioning perfectly. The problem is NOT with the client; the problem is with the WSUS Server. The updates that this client needed were not AVAILABLE to be downloaded from the WSUS server.
Why this is the case requires further investigation on your part, but is either because the updates are not properly approved, or the update FILES are not yet downloaded from Microsoft to the WSUS server.
It appears that the wsus server doesn't get any information back from the client despite that it displays new Last contact and Last Status report timestamps.
This conclusion is incorrect. The WSUS Server got every bit of information available from the client -- you've confirmed this by the number of updates reported as "Needed" by the Windows Update Agent to the WSUS Server.
I assumed that the log would display if the updates were downloaded or not.
It will log when the updates are actually downloaded. If there's no log entries for updates being downloaded, then they're not being downloaded. If the logfile says "Found 0 updates", then that means exactly what it says: It couldn't find any approved/available
updates to download.
In your case it "Found 11 updates", but now it will be impossible to diagnose that fault, because you went and got them from Windows Update.
All Win8 versions are checked in the WSUS server's Product list so the updates should at least have been downloaded to the server.
This is why understanding the infrastructure is so critical. Your conclusion is invalid based on the premise given, and you may be using improper terminology which only confuses the rest of us as well.
First, selecting updates for synchronization only gets the update metadata (i.e. the detection logic) downloaded to the WSUS database.
The Second Step in this process is to Approve those updates for one or more WSUS Target Groups that contain the appropriate client systems. Following the approval of an update, the WSUS Server downloads the INSTALLATION FILE for that update.
Once the WUAgent sees an approved update and the installation file is available, then the WUAgent will download the file and schedule the update for installation.
Most of the post I read about my problem is about upgrading a 2008 WSUS server to support Win8 / Server 12 clients. When I try to run this update on my Server 12 WSUS it refuses to run (probably because it is for Server 2008).
Yeah.. totally different issue in those posts than what you're describing here.
What should I do to try to track down the problem?
Well.... now that it's 11 days since the logfile was posted, and you've already updated that system, we'll first need to find another system exhibiting the same issue.
Then I'll need to ask a number of questions to properly understand the environment, as well as what you have or have not done.
Then, from there, we can attempt to figure out why your Windows 8 client apparently sees some updates as approved/available but is still not downloading them. We do not yet have sufficient information to even speculate on a possible cause -- there are several.
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

No sccm 2012 r2 in wsus product list

SCCM 2012 R2 standalone site server setup on a server 2012 r2 with local wsus server installed.
When configure SUP, in the product list I can see sms2003 and sccm2007 up to sccm 2012 sp1, but can't find sccm 2012 r2 nor other system center 2012 r2 components. Is this correct or I missed something?
thanks in advance

Hi,
You are correct, in addtion:
To update system center configurtation manager site, before instaling it is always reomended to read the associated KB article and process of updating the envionrment, the options are:
A cumulative update , which provides a set of multiple updates for the current product version. When yinstalling a cumulative update for Configuration Manager on a site server, it installs and runs an update bundle. Update bundles can run on a central
administration site server, a primary site server, a secondary site server, or a computer that runs an instance of the SMS Provider
Or A Service pack, which is a new version of the product
This article provides an
http://technet.microsoft.com/en-us/library/jj553405.aspx provides one with an understanding of the ways and options available when updating a configuration manager environment.

WSUS - Server 2012 R2 - Export and Import

Greetings,
I have a Server 2012 R2 system with the WSUS role installed. This server resides on a disconnected network so we must bring updates from an online WSUS server. I have experience performing successful exports and imports in the past with Server 2008
R2 and WSUS 3.0 SP2 (with KB2828185). However, I have yet to get a successful import on Server 2012 R2. The issue I am experiencing comes after what appears to be a successful import. All of the updates show up in the catalog, but none of
the approvals are there. I approve the relevant updates and the number of updates needing files on the status screen increase, but they never verify the content. The individual updates are stuck indefinitely waiting for content with no errors to
be found anywhere. Both servers have identical OS and WSUS configuration. Here is my procedure.
Source Server
- Approve/Decline relevant updates
- Wait for download to finish
- Run Server Cleanup Wizard
- Backup WSUSContent directory using 7-Zip to break into DVD size files
- wsusutil.exe export export.xml.gz export.log (I've tried export.cab and export.gz, neither produces a different result)
- Copy and extract all content to disconnected server.
- Import metadata with "wsusutil.exe import export.xml.gz import.log"
As I said, I get no related error messages in any event log, SoftwareDistribution.log, WindowsUpdate.log, Change.log.
When I've done this in the past with WSUS 3.2, the status dashboard would show all the approved updates that require content and that number would quickly decrease as the system would validate the files in the WSUSContent directory. This is occurring
on both my test server and my live server. I'm confident that I have missed something, but I need help. Anything that anyone can offer would be appreciated.

Hi Wayne,
Before we export and import updates, we should confirm that the settings for express installation files and update languages on the WSUS export server match the settings on the WSUS import server. If these settings do not match, updates will not
be correctly applied.
>> I approve the relevant updates and the number of updates needing files on the status screen increase, but they never verify the content.
Please try to run wsusutil reset.
If issue persists, please check if the WSUS content folder has the proper configuration.
Besides, could you please restart the export WSUS server and export/import again?
Best Regards.
Steven Lee Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Server 2012 R2 cannot update from 2008 R2 WSUS server

Our WSUS server is on a 2008 R2 VM. Updates for all 2008 R2 and lower servers, and Windows 7 clients work fine. I have one Server 2012 R2 in production and it cannot check for updates. It gets 800b0001 as the error code. I can
click on check for updates from Microsoft, then it does reach out to the Internet, download and install updates.
I also tried from my Win 8.1 laptop and I get error 8024402C. Any idea's?

I found in another thread the fix.
In regedit go to HKLM\Software\Microsoft\Update Services\Server\Setup and change "wYukonInstalled"
from a 1 to a 0.
Installer succeeds.
However now the Update Services console does not work. I get a connection error.
It's one thing after another with these things. I don't understand why Microsoft can't ever make something simple. IISReset did not cure this either.
The WSUS administration console was unable to connect to the WSUS Server via the remote API.
Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service.
The WSUS administration console has encountered an unexpected error. This may be a transient error; try restarting the administration console. If this error persists,
Try removing the persisted preferences for the console by deleting the wsus file under %appdata%\Microsoft\MMC\.
System.IO.IOException -- The handshake failed due to an unexpected packet format.
Source
System
Stack Trace:
at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
at System.Threading.ExecutionContext.runTryCode(Object userData)
at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)
at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)
at System.Net.PooledStream.Write(Byte[] buffer, Int32 offset, Int32 size)
at System.Net.ConnectStream.WriteHeaders(Boolean async)
** this exception was nested inside of the following exception **
System.Net.WebException -- The underlying connection was closed: An unexpected error occurred on a send.
Source
Microsoft.UpdateServices.Administration
Stack Trace:
at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)
at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer(String serverName, Boolean useSecureConnection, Int32 portNumber)
at Microsoft.UpdateServices.UI.AdminApiAccess.AdminApiTools.GetUpdateServer(String serverName, Boolean useSecureConnection, Int32 portNumber)
at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.GetUpdateServer(PersistedServerSettings settings)
at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.ConnectToServer()
at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.get_ServerTools()

Windows Server 2012 R2 Essentials Trial Key - Did I miss it, too?

I tried both "Windows Server 2012 Essentials" and "Windows Server 2012 R2 Essentials". Here is the link to the page I downloaded the images:
http://www.microsoft.com/en-us/evalcenter/evaluate-windows-server-2012-essentials
The following are the respective links to the images I used which were provided by the above webpage:
http://care.dlservice.microsoft.com/dl/download/1/2/9/129AEC4F-1C6C-44B2-9B61-77935E8AB1F4/WindowsServer2012Essentials-English-Install.iso
http://care.dlservice.microsoft.com/dl/download/8/F/7/8F7024D2-AB2A-4BE2-8406-1E3AC49C5C1F/9600.16384.WINBLUE_RTM.130821-1623_X64FRE_SERVER_SOLUTION_EN-US-IRM_SSSO_X64FRE_EN-US_DV5.ISO
I tried burning these images to DVD and booting my Intel NUC with resulting disc. Setup goes fine but it asks me for a product key. I have not received any mail nor was there any pointers to a product key. This is why I tried both R1 and R2.
I found a similar post here regarding this issue (in fact I found a couple):
http://social.technet.microsoft.com/forums/windowsserver/en-US/db7fd5b9-f58d-4456-86cf-816ec91ded14/windows-server-2012-trial-key-did-i-miss-it
But the answers were unsatisfactory, so please do not give me the same response.
Just in case the question/directive comes up, I redownloaded and re-burned the images using sector verification. There are no checksums posted on the site so who knows if something got broken while downloading it, but I find it extremely unlikely that
a few bad sector would cause the intaller to forget its evaluation key rather than borking the whole installer.
Further note that I tried "Windows Server 2012 R2" (standard / non-essentials) and that image correctly had the trial versions baked in. So, I would bet dollars to donuts the problem lies in the images not in a download / burn failure.
I want to use the new NUC as a central content/backup server for all the home computers which are unfortunately growing at bunny reproduction rates. Since Windows Home Server was discontinued, I was pointed to Server 2012 R2 as the alternative / upsell.
Let me know if this is the case or if a better-fit product exists.
Also, is the "Essentials" install a simply a licensing matter (e.g., 25 user cap) or is it more fundamentally crippled than the standard version? I am only a home enthusiast and so not really interested in using the product in a production environment.
I only want some ensurance that if I download "standard", I can put in an "essentials" key at the end of evaluation. If not, then please point me to a correct "Windows Server 2012 R2 Essentials" trial image.
Thanks,
Ryan

Hi Ryan,
à
http://www.microsoft.com/en-us/evalcenter/evaluate-windows-server-2012-essentials
We can find following description from this TechNet Evaluation Center website. Then please check if you can
find product key.
In addition, for Windows Server 2012 Essentials, please check if you can use
HHRHF-YMNJW-RPGCC-VV68W-BWMVY. For Windows Server 2012 R2 Essentials, please check if you can use
R9N79-23MWD-MBP9B-KHF8Q-C36WX.
If any update, please feel free to let me know.
Hope this helps.
Best regards,
Justin Gu

WSUS server role on Windows Server 2012 R2 - Supported SQL Configurations

According to
this page the supported SQL configurations for WSUS on Windows Server 2012/2012 R2 stop at SQL Server 2012 SP1, but there is no mention of SQL Server 2012 SP2 being supported.
However, both the SCCM 2012 R2
supported configuration page and this announcement state that SQL Server 2012 SP2 is fully supported on SCCM 2012 R2 with no
known limitations. Bearing in mind a big part of SCCM is to perform software updates which in turn requires WSUS to be installed...
... Is SQL Server 2012 SP2 supported on WSUS 4.0 (aka WSUS server role on Windows Server 2012 R2)?

The only thing that mattered for the versions mentioned on TechNet probably is the date the articles are published. I'm no Microsoft employee so I cannot guarantee you support even if I trace back some Microsoft article that explains the lifecycle of MS
products and support.
Fact is that MDT uses a database, SQL is a database server. SQL server has all kinds of compatibility modes to support databases dating multiple versions back.
Another fact is that a Service pack is an
update to the software (be it a large one) Microsoft will not break compatibility with their own products (and may others that relay on SQL server) by an update.
And a last fact is that in general, updates are required when you need support. After all, updates fix issues, and engineers generally don't like ghosthunting a bug that has already been patched.
MCP/MCSA/MCTS/MCITP

WSUS issue on server 2012 - Failing to update and have to set WinHTTP set

Very new to 2012 with little knowledge on the product
We have been seeing an issue for a while where we need to set the WinHTTP proxy in order for servers to correctly check in for WSUS and download patches. This has been set in the Windows 2008 R2 build so hasn't been an issue before. e.g.
However with Windows Server 2012 R2, setting the WinHTTP proxy causes some issues. With Exchange 2013 the PowerShell console does not connect with this set so we need a way around this.
It seems as if the we use the FQDN in the GPO it then tries to go out to the internet thinking that the FQDN is an internet address and then blocked by the proxy so hence we had to create the proxy set on the server. We don't want to have to set WinHTTP
on every 2012 servers as this would be very time consuming and will become un-manageable. Any help is greatly appreciated.

Hello,
What is the version of your WSUS? I suppose windows server 2012 is newly added in your network and the WSUS server is not patched.
An update for Windows Server Update Services 3.0 Service Pack 2 is available (KB2734608)
http://support.microsoft.com/kb/2734608
Hope this helps.

Install WSUS on Server 2012 R2 in an environment that only has Server 2008 & Server 2008 R2 servers?

I want to use WSUS on Windows Server 2012 R2 in an environment that has only Server 2008 and Server 2008 R2 servers in production. I currently have one WSUS server setup on 2008 R2 that will serve in one geographic location and the WSUS Server 2012 R2 that
I looking to setup will be at a separate geographic location.
Has anyone tried this? Are there any problems one can expect? Is this a bad idea?

Has anyone tried this?
Thousands!!! :-)
Are there any problems one can expect? Is this a bad idea?
No. Why would you think it might be?
Have you read the product documentation and familiarized yourself with the system requirements and support capabilities of the product?
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

Using Windows Server 2012 VL Product key with Windows Server 2012 R2

Hi all,
Trying to use a Server 2012 vl product key to active a Server 2012 R2, but running into issues, namely it is not accepting the key. I have read many threads pointing out that different keys are required, but no mention of the process that one needs
to take in order to obtain/swap product keys? Any ideas appreciated? :)

The product key I have is for Windows Server 2012 Standard VL, (It's not a DC).
I have downloaded the evaluation iso for Windows Server 2012 R2 and want to licence it (with a VL), but it is failing with the Windows Server Standard 2012 VL product key.
My question is - am I doing something wrong, or do I need to ask Microsoft to change the product key / buy a new one? - What steps do I need to take?
The product key for WS2012 will not work for WS2012R2. (so, yeah, you're doing that wrong)
WS2012R2 is not a "free" upgrade from WS2012 (it's different to Win8.0 -> Win8.1)
Your WS2012 pkey will work with WS2012. To use WS2012R2 you need a WS2012R2 pkey.
If you want to "convert" an evaluation license install, into a full licensed install, you must match the version (2012 vs. 2012R2) and the edition, and must use DISM as well as the correct pkey.
http://technet.microsoft.com/en-us/library/jj574204.aspx
If you don't have the correct pkey for WS2012R2 already, and you don't have one waiting for you in the Volume Licensing Service Center website, you'll need to purchase a new license for WS2012R2.
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

Server 2012 R2 WSUS not synchronizing

So I am testing out a new WSUS server on Server 2012 R2.
This has been working fine for a few weeks and downloading updates from MS with no problems.
However from the 8th December on-wards it now fails.
I checked to see if any updates had been installed on the 7th and there was one so I uninstalled it but still the same problem.
The error is as follows:
WebException: The request was aborted: Could not create SSL/TLS secure channel.
at System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request)
at System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebRequest request)
at Microsoft.UpdateServices.ServerSync.ServerSyncCompressionProxy.GetWebResponse(WebRequest webRequest)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at Microsoft.UpdateServices.ServerSyncWebServices.ServerSync.ServerSyncProxy.GetAuthConfig()
at Microsoft.UpdateServices.ServerSync.ServerSyncLib.InternetGetServerAuthConfig(ServerSyncProxy proxy, WebServiceCommunicationHelper webServiceHelper)
at Microsoft.UpdateServices.ServerSync.ServerSyncLib.Authenticate(AuthorizationManager authorizationManager, Boolean checkExpiration, ServerSyncProxy proxy, Cookie cookie, WebServiceCommunicationHelper webServiceHelper)
at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.SyncConfigUpdatesFromUSS()
at Microsoft.UpdateServices.Serve
Anyone any ideas what this is and why it has suddenly stopped working?
Regards,
Rob

The update removed was KB3011780.
There were some issues with the original release of this update. A revision was published on Nov 18, 2014. You might check to be sure that the latest revision is approved. Possibly the server had installed the earlier revision?
As for the SSL part... no idea. This is not something we have setup or changed.
My apologies. I confused the issue here. This is the logfile attempting to synchronize with Microsoft, and it does use SSL for that task.
There are only a few reasons why this SSL connection would fail:
Something is now interfering with the connection. (Is the WSUS server configured to use a proxy server?)
The WSUS Server is missing a required certificate to authenticate the Microsoft certificate chain.
Note also that the installation of MS14-066 changed the priority order of the ciphers used for SSL/TLS connections, so if there are intermediary devices, make sure they also support the use of those ciphers.
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

Wsus synching but now updating server 2012

Hi
I recently installed WSUS on server 2012 64bit. Everything installed fine I configured it right as well (I guess)
Update directly from MS
No Proxy server
Created Group policy for client
Created computer group
Now in console I can do the synchronize fine but my download status still says - 0
I tried to approve few critical updates but still nothing
I can browse all the sites and I can manually update Windows server so thinking I am connected to internet ok and sync is 100% succeeded
What am I missing here --- Please help
Regards
Manoj Nain

Hello,
Updates will be downloaded when you approve it, but it will take some time to download the files.
And you may get a message like this:
If so, what you should do is to wait. Once the downloading is finished, it can be applied to clients.
Hope this helps.

Cannot publish Flash Updates Verification of file signature failed for file SCUP 2011, SCCM 2012 R2 and WSUS all on same Windows Server 2012 machine

I am attempting to distribute Adobe Flash updates using SCUP 2011, SCCM 2012 R2, WSUS ver4 and Windows Server 2012. Everything installs without error. I have acquired a certificate for SCUP signing from the internal Enterprise CA. I have
verified the signing certificate has a 1024 bit key. I have imported the certificate into the server's Trusted Publishers and Trusted Root CA stores for the computer. When I attempt to publish a Flash update with Full content I receive the following
error:
2015-02-13 23:00:48.724 UTC Error Scup2011.21 Publisher.PublishPackage PublishPackage(): Operation Failed with Error: Verification of file signature failed for file:
\\SCCM\UpdateServicesPackages\a2aa8ca4-3b96-4ad2-a508-67a6acbd78a4\3f82680a-9028-4048-ba53-85a4b4acfa12_1.cab
I have redone the certificates three times with no luck. I can import metadata, but any attempt to download content results in the verification error.
TIA

Hi Joyce,
This is embarrassing, I used that very post as my guide when deploying my certificate templates, but failed to change the bit length to 2048. Thank you for being my second set of eyes.
I changed my certificate key bit length to 2048, deleted the old cert from all certificate stores, acquired the a new signing cert, verified the key length was 2048, exported the new cert to pfx and cer files, imported into my Trusted publishers
and Trusted Root Authorities stores, reconfigured SCUP to use the new pfx file, rebooted the server and attempted to re-publish the updates with the following results:
2015-02-16 13:35:44.006 UTC Error Scup2011.4 Publisher.PublishPackage PublishPackage(): Operation Failed with Error: Verification of file signature failed for file:
\\SCCM\UpdateServicesPackages\a2aa8ca4-3b96-4ad2-a508-67a6acbd78a4\3f82680a-9028-4048-ba53-85a4b4acfa12_1.cab.
Is there a chance this content was already created and signed with the old cert, so installing the new cert has no effect? In ConfigMgr software updates I see 4 Flash updates, all marked Metadata Only (because they were originally published as "Automatic."
No Flash updates in the ConfigMgr console are marked as downloaded. I can't find any documentation on how the process of using SCUP for downloading content for an update marked Metadata Only actually works.
Comments and suggestions welcome.

Server 2012 R2 WSUS - Product's Missing / Different to SUP 2012 R2

Similar Messages

Maybe you are looking for