SUP and WSUS

I everyone,
I have an issue with SCCM 2012 R2 and the windows updates.
In SCCM, I created several software update groups (and packages) to manage the deployment of the updates on Windows 7 OS.
I have not deployed any of them yet to any collection but if I "Check the updates" from the Control Panel, Windows Updates, I get a list of updates to install.
Is that a normal behavior ?
I thought I shouldn't see any updates since they are not deployed.
Moreover if I try to install them, they are directly downloaded from my SUP and not from the Distribution Point so.
Have you already had the same issue ?
Shoud I reinstall the software update point and WSUS ?
Thank you.

I sounds like the WSUS server might have been used to deploy updates outside of ConfigMgr.
Can you verify the following:
The client is configured to use the right WSUS Server (might be a GPO that points to an old WSUS Server)
There is no released updated on the WSUS Server (it should all be managed from ConfigMgr and not WSUS)
If you're using an old WSUS Server that was previous used to deploy patches outside of ConfigMgr, I'd recommend that you install (or re-install) a new WSUS Server and use that.
Ronni Pedersen | Microsoft MVP - ConfigMgr | Blogs:
www.ronnipedersen.com/ and www.SCUG.dk/ | Twitter
@ronnipedersen

Similar Messages

Best Practice for SUP and WSUS Installation on Same Server

Hi Folks,
I have a question, I am in process of deploying SCCM 2012 R2... I was in process of deploying Software Update Point on SCCM with one of the existing WSUS server installed on a separate server from SCCM.
A debate has started with of the colleague who says that the using remote WSUS server is recommended by Microsoft because of the scalability security that WSUS will be downloading the updates from Microsoft and SCCM should be working as downstream
server to fetch updates from WSUS server.
but according to my consideration it is recommended to install WSUS server on the same server where SCCM is installed... actually it is recommended to install WSUS on a site system and you can used the same SCCM server to deploy WSUS.
please advice me the best practices for deploying SCCM and WSUS ... what Microsoft says about WSUS to be installed on same SCCM server OR WSUS should be on a separate server then the SCCM server ???
awaiting your advices ASAP :)
Regards, Owais

Hi Don,
thanks for the information, another quick one...
the above mentioned configuration I did is correct in terms of planning and best practices?
I agree with Jorgen, it's ok to have WSUS/SUP on the same server as your site server, or you can have WSUS/SUP on a dedicated server if you wish.
The "best practice" is whatever suits your environment, and is a supported-by-MS way of doing it.
One thing to note, is that if WSUS ever becomes "corrupt" it can be difficult to repair and sometimes it's simplest to rebuild the WSUS Windows OS. If this is on your site server, that's a big deal.
Sometimes, WSUS goes wrong (not because of ConfigMgr)..
Note that if you have a very large estate, or multiple primary site servers, you might have a CAS, and you would need a SUP on the CAS. (this is not a recommendation for a CAS, just to be aware)
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!)

SUP and WSUS on the same server.

Hi,
My SCCM environment as follows:
Windows Server 2012 R2 Standard, Configuration Manager 2012 R2, SQL 2012 SP1 CU7
WSUS 6.3.9600.163.84 . All these running on the same server.
SCCM SUP role is enabled, WSUS using SQL Express database. This is Central and Primary site server as well.
Issue is:
1. SUP does not get updates. SUP is configured to get updates from Internet and WSUS console Sync options pointing to its own server name. I tried to change WSUS console sync option to internet couple of times but it looks WSUS changes this back.
2. I want to use WSUS/SUP for SCCM Endpoint definitions update and also for patch installation for clients (Clients Windows update pointing to this server)

What do you mean that this is a Central and Primary site server? Those two roles can not be installed on the same site server.
When it comes to SUP in ConfigMgr, the installation process on WS 2012 is basically this:
1. Install the Windows Server Update Services role, run the initial configuration wizard.
2. Install a SUP site system role on the server and let ConfigMgr configure everything.
Additionally I'd not run a SQL Express for the WSUS since you already have SQL installed. Instead I'd create the SUSDB on the same SQL server that you're running the ConfigMgr DB on.
In my preprequisites installation tool, all you need to do is to open a PowerShell console, run the tool and click on the Install WSUS button, specify the SQL Server and the tool will automatically configure everything. When the tool has completed, you can
go ahead and add the SUP from ConfigMgr and configure it from the ConfigMgr console.
You'll find the tool here:
http://gallery.technet.microsoft.com/ConfigMgr-2012-R2-e52919cd
Regards,
Nickolaj Andersen | www.scconfigmgr.com | @Nickolaja

SCCM 2012 on Server 2012 and WSUS 3.0 SP2 on Server 2008

We are installing SCCM 2012 SP1 fresh into our development environment - the primary site server and the database (SQL 2012) are both being installed on Server 2012.
We have an existing WSUS box on a Windows 2008 (not R2) server - the WSUS server version is 3.2.7600.256. We have set this up as the software update point.
For the purposes of this discussion, these are the server names (obviously obfuscated):
Primary site server: sccm.domain.local
Database server: sccmdb.domain.local
WSUS server: wsus.domain.local
On the primary SCCM server, I've installed the WSUS user interface (Install-WindowsFeature -Name UpdateServices-UI), in order to work with the remote WSUS server.
Updates synchronization appears to be working fine, but when I try to setup client distribution via SUP, I'm getting the following error in the Application event log:
Log Name:      Application
Source:        SMS Server
Date:          8/6/2013 11:03:11 AM
Event ID:      6613
Task Category: SMS_WSUS_CONFIGURATION_MANAGER
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      sccm.domain.local
Description:
On 8/6/2013 11:03:11 AM, component SMS_WSUS_CONFIGURATION_MANAGER on computer sccm.domain.local reported: WSUS Configuration Manager failed to publish client boot-strapper package "9D5353E5-DA80-48C3-97DE-C9C528F73A2D" with version "5.00.7804.1000"
to the Software Updates Point.
As well as this in the WMC.log:
PublishApplication(9D5353E5-DA80-48C3-97DE-C9C528F73A2D) failed with error System.InvalidOperationException: Publishing operation failed because the console and remote server versions do not match.~~   at Microsoft.UpdateServices.Internal.BaseApi.Publisher.LoadPackageMetadata(String
sdpFile)~~   at Microsoft.UpdateServices.Internal.BaseApi.UpdateServer.GetPublisher(String sdpFile)~~   at Microsoft.SystemsManagementServer.WSUS.WSUSServer.PublishApplication(String sPackageId, String sSDPFile, String sCabFile) $$<SMS_WSUS_CONFIGURATION_MANAGER><08-06-2013
11:03:11.787+240><thread=3704 (0xE78)>
ERROR: Failed to publish sms client to WSUS, error = 0x80131509 $$<SMS_WSUS_CONFIGURATION_MANAGER><08-06-2013 11:03:11.803+240><thread=3704 (0xE78)>
It would seem obvious that this is because of a mismatch in versions between the WSUS server version on wsus.domain.local, compared to the UpdateServices UI on sccm.domain.local.
Is there a way around this, without having to upgrade the WSUS server to Server 2012?
Thanks for any thoughts you may have!

Not really. As mentioned though, even the separate WSUS server is probably overkill. In ConfigMgr, WSUS is used to handle the update catalog and that's it. Clients do *not* report status to the WSUS instance and do *not* download updates from the WSUS instance.
No management is ever done in WSUS.
So, in reality, once a month, clients connect to WSUS to download the delta update catalog (delta compared to what they currently have) which usually comes out to about a few hundred KB (yes KB, not MB) -- this download is done via BITS. The server also
syncs the catalog from the WSUS instance, via the SUP, in a similar fashion. If you are using SCEP, the frequency will be greater, but the deltas will be much smaller.
EULAs, as needed, are also stored in WSUS and accessed by clients -- these are also quite small only a select few updates requires them.
That's it. Standing up a dedicated WSUS instance means having a server sitting there doing almost nothing else.
If you are concerned about load on the site server, then you should create a separate site system that contains the MP, SUP (and WSUS instance), and DP. Then, for HA purposes, you can simply build a second site system with these three roles also and HA will
essentially be automatic (from a client functionality perspective).
Jason | http://blog.configmgrftw.com

SCCM 2012 and WSUS

I know this horse has been beat, and is probably just dust now but I am still having a problem. I am not sure what to do next. I see others have had this problem but their resolutions have not worked.
Site Config:
OS - Windows Server 2012 Datacenter
SQL - SQL Server 2012 Enterprise SP1
SCCM - SCCM 2012 SP1
WSUS : Database and WSUS Services
I have done the setup in the Server Manager window and can open the console. Below are the errors I am getting.
From SMS_WSUS_SYNC_MANAGER
WSUS Synchronization failed.
Message: WSUS update source not found on site CM1. Please refer to WCM.log for configuration error details..
From SMS_WSUS_CONFIGURATION_MANAGER
WSUS Configuration Manager failed to subscribe to update categories and classifications on WSUS Server "SERVER".
Error in WCM.log
Failed to set Subscriptions on the WSUS Server. Error:(-2147467259)Unspecified error
Error in wsyncmgr.log
Sync failed: WSUS update source not found on site CM1. Please refer to WCM.log for configuration error details.. Source: getSiteUpdateSource
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=SERVER SITE=CM1 PID=1548 TID=1740 GMTDATE=Fri Sep 13 19:08:50.063 2013 ISTR0="getSiteUpdateSource" ISTR1="WSUS update source not found on
site CM1. Please refer to WCM.log for configuration error details." ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
Sync failed. Will retry in 60 minutes

Re-set the WSUS and SUP roles according to your doco, which is nice by the way, but I am still getting errors in WCM.
Assembly WSUSMSP loaded in .NET runtime v4.0.30319.17929 SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:12 PM 5108 (0x13F4)
Attempting connection to WSUS server: <SERVER.DOMAIN>, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:12 PM 5108 (0x13F4)
Successfully connected to server: <SERVER.DOMAIN>, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:14 PM 5108 (0x13F4)
Verify Upstream Server settings on the Active WSUS Server SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:14 PM 5108 (0x13F4)
Successfully configured WSUS Server settings and Upstream Server to Microsoft Update SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:16 PM 5108 (0x13F4)
WSUS Server configuration has been updated. Updating Group Info. SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:16 PM 5108 (0x13F4)
Updating Group Info for WSUS. SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:16 PM 5108 (0x13F4)
Set DBServerName property in SCF to 'VRC1SCCMPRIP01' on this site for <SERVER.DOMAIN>. SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:16 PM 5108 (0x13F4)
user(NT AUTHORITY\SYSTEM) runing application(SMS_WSUS_CONFIGURATION_MANAGER) from machine (<SERVER.DOMAIN>) is submitting SDK changes from site(CM1) SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:16 PM 5108 (0x13F4)
Attempting connection to WSUS server: <SERVER.DOMAIN>, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
Successfully connected to server: <SERVER.DOMAIN>, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
Category Product:041e4f9f-3a3d-4f58-8b2f-5e6fe95c4591 (Office 2007) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
Category Product:18e5ea77-e3d1-43b6-a0a8-fa3dbcd42e93 (Windows 8.1 Dynamic Update) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
Category Product:2ee2ad83-828c-4405-9479-544d767993fc (Windows 8) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
Category Product:3e5cc385-f312-4fff-bd5e-b88dcf29b476 (Windows 8 Language Interface Packs) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
Category Product:5312e4f1-6372-442d-aeb2-15f2132c9bd7 (Windows Internet Explorer 8 Dynamic Installer) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
Category Product:6407468e-edc7-4ecd-8c32-521f64cee65e (Windows 8.1) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
Category Product:6d76a2a5-81fe-4829-b268-6eb307e40ef3 (Windows 7 Language Packs) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
Category Product:704a0a4a-518f-4d69-9e03-10ba44198bd5 (Office 2013) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
Category Product:84f5f325-30d7-41c4-81d1-87a0e6535b66 (Office 2010) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
Category Product:97c4cee8-b2ae-4c43-a5ee-08367dab8796 (Windows 8 Language Packs) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
Category Product:a38c835c-2950-4e87-86cc-6911a52c34a3 (Forefront Endpoint Protection 2010) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
Category Product:bfe5b177-a086-47a0-b102-097e4fa1f807 (Windows 7) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
Category Product:f4b9c883-f4db-4fb5-b204-3343c11fa021 (Windows Embedded Standard 7) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
Category ProductFamily:fe729f7e-3945-11dc-8e0c-cd1356d89593 (Silverlight) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
Starting WSUS category sync from upstream... SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
WSUS sync running SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:37:22 PM 5108 (0x13F4)
WSUS sync running SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:38:22 PM 5108 (0x13F4)
WSUS sync running SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:39:22 PM 5108 (0x13F4)
WSUS sync running SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:40:22 PM 5108 (0x13F4)
Refreshing categories from WSUS server SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:40:37 PM 5108 (0x13F4)
Attempting connection to WSUS server: <SERVER.DOMAIN>, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:40:37 PM 5108 (0x13F4)
Successfully connected to server: <SERVER.DOMAIN>, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:40:37 PM 5108 (0x13F4)
Successfully refreshed categories from WSUS server SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:40:45 PM 5108 (0x13F4)
Attempting connection to WSUS server: <SERVER.DOMAIN>, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:40:45 PM 5108 (0x13F4)
Successfully connected to server: <SERVER.DOMAIN>, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:40:45 PM 5108 (0x13F4)
Category Product:6d76a2a5-81fe-4829-b268-6eb307e40ef3 (Windows 7 Language Packs) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:40:45 PM 5108 (0x13F4)
Subscription contains categories unknown to WSUS. SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:40:45 PM 5108 (0x13F4)
Failed to set Subscriptions on the WSUS Server. Error:(-2147467259)Unspecified error SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:40:45 PM 5108 (0x13F4)
From SUPSetup.log
<09/17/13 13:36:13> ====================================================================
<09/17/13 13:36:13> SMSWSUS Setup Started....
<09/17/13 13:36:13> Parameters: I:\Program Files\Microsoft Configuration Manager\bin\x64\rolesetup.exe /install /siteserver:<SERVER.DOMAIN> SMSWSUS 0
<09/17/13 13:36:13> Installing Pre Reqs for SMSWSUS
<09/17/13 13:36:13> ======== Installing Pre Reqs for Role SMSWSUS ========
<09/17/13 13:36:13> Found 1 Pre Reqs for Role SMSWSUS
<09/17/13 13:36:13> Pre Req SqlNativeClient found.
<09/17/13 13:36:13> SqlNativeClient already installed (Product Code: {D411E9C9-CE62-4DBF-9D92-4CB22B750ED5}). Would not install again.
<09/17/13 13:36:13> Pre Req SqlNativeClient is already installed. Skipping it.
<09/17/13 13:36:13> ======== Completed Installation of Pre Reqs for Role SMSWSUS ========
<09/17/13 13:36:13> Installing the SMSWSUS
<09/17/13 13:36:13> Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)
<09/17/13 13:36:13> Checking runtime v2.0.50727...
<09/17/13 13:36:13> Did not find supported version of assembly Microsoft.UpdateServices.Administration.
<09/17/13 13:36:13> Checking runtime v4.0.30319...
<09/17/13 13:36:13> Found supported assembly Microsoft.UpdateServices.Administration version 4.0.0.0, file version 6.2.9200.16384
<09/17/13 13:36:13> Found supported assembly Microsoft.UpdateServices.BaseApi version 4.0.0.0, file version 6.2.9200.16384
<09/17/13 13:36:13> Supported WSUS version found
<09/17/13 13:36:13> Supported WSUS Server version (6.2.9200.16384) is installed.
<09/17/13 13:36:13> CTool::RegisterManagedBinary: run command line: "C:\Windows\Microsoft.NET\Framework64\v2.0.50727\RegAsm.exe" "I:\Program Files\Microsoft Configuration Manager\bin\x64\wsusmsp.dll"
<09/17/13 13:36:13> CTool::RegisterManagedBinary: Registered I:\Program Files\Microsoft Configuration Manager\bin\x64\wsusmsp.dll successfully
<09/17/13 13:36:13> Registered DLL I:\Program Files\Microsoft Configuration Manager\bin\x64\wsusmsp.dll
<09/17/13 13:36:13> Installation was successful.
<09/17/13 13:36:13> ~RoleSetup().
Second to last line shows completion.

SCCM and WSUS, where does it go?

Hi everyone, we are deploying SCCM to about 30 sites. We have a central server, primary, secondary servers, and distribution points. The question is where do I install WSUS? Do I need it on all the servers? I cant seem to find a good
answer.
And when I do deploy WSUS how should I hook it up? Should the secondary look at the primary as a distribution point? What about the distribution point servers? Do they need WSUS?
Thank you!

No, not really.
First, 1,000's of clients does not in any way mean you need a CAS. You only need a CAS if you have multiple primary sites and multiple primary sites are only called for (in 99% of the cases) if you have 100,000+ managed clients; i.e., way more
than 1,000's. Primary sites are about scale-out in terms of client count only, not location. Many (even 100's) of remote locations is not a valid technical reason to have a CAS and primary sites have nothing to do with remote locations either.
With a CAS in the picture, you must have a WSUS instance and SUP in your CAS and on each primary site. You can optionally have a WSUS instance and SUP on any secondary sites.
Without a CAS in the picture, the primary site must have a WSUS instance and SUP and any secondary sites can optionally have one also.
As mentioned, the WSUS instance and SUP at secondary sites are optional depending upon the bandwidth limitations and client count at the location being served by the secondary site. WSUS instance at secondary sites are downstream (in WSUS terms)
from the WSUS instance at the primary site they are a child of for catalog sync purposes only.
Clients assigned to a primary site will use the WSUS instance for that primary site unless they are within the scope of a secondary site that also has a WSUS instance and SUP. WSUS instances at a CAS are never used by clients -- they simply are upstream
(in WSUS terms) from the WSUS instances at the primary sites for catalog sync purposes.
In general, you should not use a domain GPO to configure the WSUS instance for the clients to use. This is set automatically on the clients using a local GPO by the ConfigMgr agent. Depending upon your scenario, you can set this, but it must match what
the ConfigMgr agent wants or Software Updates will be disabled on the client.
WSUS instances integrated in ConfigMgr only handle the update metadata/catalog (and EULAs) -- they do not handle the update binaries (as mentioned above those are handled by the DPs in ConfigMgr). Thus, clients must still be able to communicate with the
proper WSUS instance (per the paragraph above) to download/access the update catalog (and EULAs).
Jason | http://blog.configmgrftw.com | @jasonsandys

SUP separate WSUS

Hello everyone
Just one question.
WSUS is mandatory to install SUP in SCCM 2012 R2. My question is: We already have a WSUS server, can I install the SUP and the WSUS in different servers? or the WSUS
Administration Console is enough?

Hi,
Here is a similar post for your reference.
SCCM 2012 Remote WSUS Server, SUP Not Working
http://social.technet.microsoft.com/Forums/en-US/69f6b512-7337-42b5-8bcc-d1683e349893/sccm-2012-remote-wsus-server-sup-not-working?forum=configmanagergeneral
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.

[SOLVED] Wrong scancodes for Ctrl, Super and Alt on keyboard

I have bought this keyboard and I'm having an issue with it that I can't figure out. Under Archlinux, the Control, Super and Alt key are interpreted as the Shift key. I have tested it on a tablet running Android and its behavior is identical however when testing it under a laptop running Windows 8 it behaved correctly.
I've checked the scancodes and keycodes using showkey and all of the 3 problem keys match the Shift key's scancode / keycode.
When pluging in the keyboard, this is what dmesg outputs:
[ 3151.870872] usb 1-2: new low-speed USB device number 13 using xhci_hcd
[ 3152.040418] usb 1-2: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes
[ 3152.040428] usb 1-2: ep 0x82 - rounding interval to 64 microframes, ep desc says 80 microframes
[ 3152.043548] input: SONiX USB Keyboard as /devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/0003:0C45:7603.0011/input/input33
[ 3152.094113] hid-generic 0003:0C45:7603.0011: input,hidraw0: USB HID v1.11 Keyboard [SONiX USB Keyboard] on usb-0000:00:14.0-2/input0
[ 3152.107227] input: SONiX USB Keyboard as /devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.1/0003:0C45:7603.0012/input/input34
[ 3152.158239] hid-generic 0003:0C45:7603.0012: input,hiddev0,hidraw1: USB HID v1.11 Keyboard [SONiX USB Keyboard] on usb-0000:00:14.0-2/input1
Any help in figuring out the issue is highly appreciated.
Last edited by stormhaden (2015-05-04 13:51:29)

Turns out I wasn't searching for my problem using the right keywords. After some variation in the search terms I have found this driver: https://bitbucket.org/Swoogan/aziokbd. I gave it a try and it seems to fix the problem.

Difference between Wsus 3.0 and Wsus 4.0

Hi all,
I would like to know what are differences between Wsus 3.0 and Wsus 4.0.
I have already notice that for Local Publishing, the method IPublisher.PublishPackage(sourcePath,
additionalSourcePath, packageDirectoryName), totally ignore the "additionalSourcePath" parameter.
Are there any documentation or web site where I can find differences between Wsus 3.0 and 4.0 ?
Thanks.
David COURTEL
IT Technician
Wsus Third-Party Softwares Publishing :
http://wsuspackagepublisher.codeplex.com

I would like to know what are differences between Wsus 3.0 and Wsus 4.0.
The differences between WSUS v3 and WSUS v6 (please note the correct version number) are documented ... somewhere ... but at the moment I can't find them. (Presumably it would be in the Release Notes for Win2012, but that idea is a bust.)
In short, these are the notable distinctions:
WSUS v6 is compiled with the .NET Framework v4
WSUS v6 provides an extended interface for management via PowerShell
WSUS v6 supports SHA256 hashes (which were implemented by the WUAgent v7.8 and rolled back to the WUAgent v7.6 in KB2720211 and WSUS v3.2 in KB2734608)
I have already notice that for Local Publishing, the method IPublisher.PublishPackage(sourcePath, additionalSourcePath, packageDirectoryName), totally ignore the "additionalSourcePath" parameter.
Changes to the API should be reflected in the
SDK.
Also worth of note.. publishing TO a WSUS v6 server must be performed from a Windows Server 2012 system or a Windows 8 system with RSAT. Publishing to a WSUS v6 server from a WSUS v3.2 console cannot be done due to internal dependencies in the Local
Publishing API on the build number of the console and server involved in the publishing process.
Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
SolarWinds Head Geek
Microsoft MVP - Software Distribution (2005-2013)
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

NAC and WSUS

Hi to all,
I'm new at NAC, does anyone know the steps on how to configure the remediation on a client machine using NAC and WSUS?? Is there a rule that match it??, etc, etc...
Thanks in advance for your help!

Click clean access under device mgmt.
Click the clean access agent tab.
Click requirements.
Add one for MS update check if you don't already have one made by clicking new requirement. Choose windows update service for the requirement type drop down box. If you already have a rule for the windows update service check you can click edit instead (next to the move up down arrow buttons).
About half way down you can choose MS servers or WSUS servers.

Any idea why super() and this() needs to be first statement

Java recommends super() and this() to be the first statement to be used.why this design constraint is imposed?
This imposes one more restriction
where super() and this() cannot be used at the same time?
how this constraint is useful.
for eg:
class A
     A(int a)
     System.out.println("A(int)");
     A(int a,int b)
     System.out.println("A(int,int)");
class B extends A
     B()
          super(1);
          System.out.println("B()");
     B(int i)
          this();
          super(1,1);//compile-error :must be first statement
the above eg may be a bad design,but are the constraints imposed for this purpose?or anything else?

To make sure that the constructor is the first thing that runs, and to make sure >the super instance is completely constructed before we do anything with the >child instance.
Both these go toward having the object be in a consistent, valid state.I accept the point,but considering the code part
B()
   //super(1);
System.out.println("B()");
B(int i)
super(1,1);
this();
}in above super instance will be constructed first followed by this().
but this() cannot be used as second statement???
I feel ,this is because this() in turn calls the super constructor again?to restrict this constraint made?is it something like that?

Database instance for SCCM 2012 and WSUS on a single primary site server

I am going to install SCCM 2012 and its SQL database on a single physical server. This is going to be a single primary site server. The default SQL instance will be dedicated to SCCM 2012 with no other named instances to be added on the SQL server down
the road.
During the WSUS server role installation, there is the Database Options page asking for using (1) Windows Internal Database, (2) existing db server on this computer, or (3) an external db server.
Since SCCM 2012 doesn't share db instance with others, how should I handle the WSUS db that's going to be hosted on the same SCCM/SQL physical server? Do I really need to create a separate SQL instance just for the WSUS db?
Thanks and regards.

Even though you can do it, it is the best practice to have SCCM 2012 and WSUS installed on separate instances.
http://technet.microsoft.com/en-us/library/hh692394
When the Configuration Manager and WSUS databases use the same SQL Server and share the same instance of SQL Server, you cannot easily determine the resource usage between the two applications. When you use a different SQL Server instance
for Configuration Manager and WSUS, it is easier to troubleshoot and diagnose resource usage issues that might occur for each application.

Super and sub classes

Using an Super class and couple of subclasses of this super.
Super{
m1(){
subclass1, subclass2, subclass3...etc.
these subclasses call super class method m1().
In super class m1() want to know which subclass called this method m1(). how to find this?
Ofcourse can use a variable and in super and set it in subclass but is there a smart way in java to find this. I would appreciate your help.
Thanks.

if (this instanceof SuperClass)
if (this instanceof SubClass1)
etc.
But this is very poor design. You should override m1() in each subclass to have it do whatever is necessary in each case.

Huge Sized download taking place at port 8530 between clients and WSUS\SUP of secondary site

Hi Guy's
Need a solution to the issue, the SCCM 2012 clients under a secondary site { Secondary site with SUP\WSUS } are downloading 200Mb + data at port 8530. This seems quite abnormal.
Need to know answer of below
1- Actual size of catalog what clients should download or path where on WSUS is stored
2- How to restrict a huge sized download between WSUS and CM 2012 client
This is not the case where clients are directly reporting to Primary size.
Regards
Sushain Kapoor
Regards Sushain KApoor

Hi Jason
Just a little clarity, will the client download information for a particular product or all the products selected in wsus.
Eg: Windows 7 systems will download the catalog information of Windows 7 only against selections made in WSUS. Or it will download the windows XP and windows vista and other product information also. This particular question i am asking as i see only 300
updates as found in windowsupdate.log and not the thousands synced in WSUS
Is the update metadata exported using the wsusutil.exe the actual catalog size what clients are downloading
Regards Sushain KApoor

SUP and SQL login failed

Hi,
Been racking my brain about this one, searched online (including here) but haven't found a solution yet. My scenario is: SCCM 2012 R2 and SQL 2012 (with databases CM_SCM and SUSDB, instance name is MSSQLSERVER) installed on the same server. SCCM will only
be used to build servers using TS. I'm using SCCM as a SUP to do offline servicing of the wim files. This setup was working up to several weeks ago (don't know exactly when it stopped) and since, whenever I do a software update sync, I get
'Sync failed: WSUS server not configured. Please refer to WCM.log for configuration error details.. Source: CWSyncMgr::DoSync'.
Checking the WCM.log I get the following error:
System.Data.SqlClient.SqlException (0x80131904): Login failed for user 'DOMAIN\MACHINENAME$'.~~ at Microsoft.UpdateServices.Internal.BaseApi.SoapExceptionProcessor.DeserializeAndThrow(SoapException soapException)~~ at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccessProxy.ExecuteSPGetConfiguration()~~
at Microsoft.UpdateServices.Internal.BaseApi.UpdateServerConfiguration.Load()~~ at Microsoft.UpdateServices.Internal.ClassFactory.CreateWellKnownType(Type type, Object[] args)~~ at Microsoft.UpdateServices.Internal.ClassFactory.CreateInstance(Type
type, Object[] args)~~ at Microsoft.UpdateServices.Internal.BaseApi.UpdateServer.GetConfiguration()~~ at Microsoft.SystemsManagementServer.WSUS.WSUSServer.SetUpstreamServerSettings(Boolean SyncFromMicrosoftUpdate, Boolean ReplicaServer, String
UpstreamWSUSServerName, Int32 UpstreamWSUSServerPortNumber, Boolean UseSSL, Boolean HostBinariesOnMU, Int32 ReportingLevel, Int32 MaximumAllowedComputers)~~ClientConnectionId:00000000-0000-0000-0000-000000000000
If I then check the SQL Server log, I have (over and over again) the error:
Login failed for user "DOMAIN\MACHINENAME$". Reason: Could not find a login matching the name provided. [CLIENT: <local machine>] - Error 18456, Severity: 14, State: 5
According to http://sqlblog.com/blogs/aaron_bertrand/archive/2011/01/14/sql-server-v-next-denali-additional-states-for-error-18456.aspx , state 5 indicates (as the error msg mentions) that the login doesn't exist, however in the SQL server it does exist
and is also present under both DBs\Security\Users.
There was no SPN set for the service account I created when setting the server up (in this case sccmsql), I've now set it manually to MSSQLSvc/FQDN:1433, as mentioned in http://technet.microsoft.com/en-us/library/hh427336.aspx#BKMK_ManageSPNforDBSrv
, but without any luck.
Thanks in advance for reading this.
Dan

Dan,
Remove the SUP role. Remove WSUS and delete the SUSDB. Reboot the site server and reinstall WSUS and SUP. It'll recreate all the required permissions as part of the install.
Cheers
Paul | sccmentor.wordpress.com

SUP and WSUS

Similar Messages

Maybe you are looking for