jorlando

I am using Secunia as well... We are using 6.0. Secunia 6.0 has SCCM Database integration so you don't have to put the Secunia Client on every machine when SCCM already has all the information it needs. What version of Secunia are you running?

I have been struggling with slow software inventories. The client settings are pretty basic, with only one item set to search subfolders (*.exe in Program Files (x86) or Program Files). The inventory time has gone from 20 minutes to 3-8 hours and I really cannot find any reason why. We have about 20,000 workstations and this is impacting the vast majority of them. In the inventoryagent.log there are no errors... just LONG delays between each namespace. On some machines we may see a timeout after 2 hours: CThrottler::Throttle()[{C0ED66AD-8194-49FD-9826-D0DD38AB7DAA}] - soft timeout exceeded. Throttling is now disabled for the current iteration of this task. The other thing I see is a lot of errors in the inventoryprovider.log. First of all a search of books and the web does not provide me with a description of what this log is tracking, so if anyone can explain I am all ears. But there does seem to be a lot of errors here... keep in mind this is happening on thousands of machines: Here is a snippet: Failed in discovering instance. Invalid object (Error: 8004100F; Source: WMI) InventoryProvider 9/10/2013 1:05:02 AM 25516 (0x63AC) Failed to do HandleGetObjectAsync(). Invalid object (Error: 8004100F; Source: WMI) InventoryProvider 9/10/2013 1:05:02 AM 25516 (0x63AC) GetObjectAsync - Error handling request, 8004100f InventoryProvider 9/10/2013 1:05:02 AM 25516 (0x63AC) PopulateInstance - Requested instance not found. InventoryProvider 9/10/2013 1:05:02 AM 25516 (0x63AC) Failed in discovering instance. Invalid object (Error: 8004100F; Source: WMI) InventoryProvider 9/10/2013 1:05:02 AM 25516 (0x63AC) Failed to do HandleGetObjectAsync(). Invalid object (Error: 8004100F; Source: WMI) InventoryProvider 9/10/2013 1:05:02 AM 25516 (0x63AC) GetObjectAsync - Error handling request, 8004100f InventoryProvider 9/10/2013 1:05:02 AM 25516 (0x63AC) PopulateInstance - Requested instance not found. InventoryProvider 9/10/2013 1:05:02 AM 25516 (0x63AC) Failed in discovering instance. Invalid object (Error: 8004100F; Source: WMI) InventoryProvider 9/10/2013 1:05:02 AM 25516 (0x63AC) Failed to do HandleGetObjectAsync(). Invalid object (Error: 8004100F; Source: WMI) InventoryProvider 9/10/2013 1:05:02 AM 25516 (0x63AC) GetObjectAsync - Error handling request, 8004100f InventoryProvider 9/10/2013 1:05:02 AM 25516 (0x63AC) PopulateInstance - Requested instance not found. InventoryProvider 9/10/2013 1:05:02 AM 25516 (0x63AC) Failed in discovering instance. Invalid object (Error: 8004100F; Source: WMI) InventoryProvider 9/10/2013 1:05:02 AM 25516 (0x63AC) Failed to do HandleGetObjectAsync(). Invalid object (Error: 8004100F; Source: WMI) InventoryProvider 9/10/2013 1:05:02 AM 25516 (0x63AC) GetObjectAsync - Error handling request, 8004100f InventoryProvider 9/10/2013 1:05:02 AM 25516 (0x63AC) PopulateInstance - Requested instance not found. InventoryProvider 9/10/2013 1:05:02 AM 25516 (0x63AC) Failed in discovering instance. Invalid object (Error: 8004100F; Source: WMI) InventoryProvider 9/10/2013 1:05:02 AM 25516 (0x63AC) Failed to do HandleGetObjectAsync(). Invalid object (Error: 8004100F; Source: WMI) InventoryProvider 9/10/2013 1:05:02 AM 25516 (0x63AC) GetObjectAsync - Error handling request, 8004100f InventoryProvider 9/10/2013 1:05:02 AM 25516 (0x63AC) PopulateInstance - Requested instance not found. InventoryProvider 9/10/2013 1:05:02 AM 25516 (0x63AC) Anyone have thoughts as to why the Software Inventory is so slow? Thanks.

I wanted to share a problem I had recently that was difficult to diagnose, but simple to resolve. My secondary site was having database replication issues. The symptoms were clients assigned to the secondary site were unable to download and run packages. Looking at the client logs the issue was there was no reply from the MP with content location. So the clients could not get a location to download content from. Under Monitoring and Database Replication the link showed Link Failed and Link has Failed. On the Primary Site the rcmctrl.log showed no errors, but on the secondary site the rcmctrl.log had the following error: Launching 2 sprocs on queue ConfigMgrDRSQueue and 0 sprocs on queue ConfigMgrDRSSiteQueue. SMS_REPLICATION_CONFIGURATION_MONITOR The asynchronous command finished with return message: [A .NET Framework error occurred during execution of user-defined routine or aggregate "spDRSActivation": ~~System.TypeInitializationException: The type initializer for 'System.Data.SqlClient.SqlConnection' threw an exception. ---> System.TypeInitializationException: The type initializer for 'System.Data.SqlClient.SqlConnectionFactory' threw an exception. ---> System.TypeInitializationException: The type initializer for 'System.Data.SqlClient.SqlPerformanceCounters' threw an exception. ---> System.MethodAccessException: Attempt by method 'System.Configuration.TypeUtil.CreateInstanceRestricted(System.Type, System.Type)' to access method 'System.Diagnostics.SwitchElementsCollection..ctor()' failed. ---> System.Security.SecurityException: Request failed… [truncated for readability] This issue is caused by MS13-052 (KB2840628) and Microsoft has released a hotfix, KB2872041, for the issue. Here is a link: http://blogs.technet.com/b/configmgrteam/archive/2013/07/17/issues-reported-with-ms13-052-kb2840628-and-configmgr.aspx

Sounds like you dont have any products or classifications selected. Launch the SCCM 2012 Console. Check Administration > Site Configuration > Sites and Right Click the Primary Site. Choose Configure Site Componenets > Software Update Point and check settings here. Upload the WCM.log and Wysncmgr.log if this is not the resolution.

Console > Monitoring > Reporting > Reports > Software Updates - A Compliance > Compliance 2 - SPecific Software Update

Might have been KB2720211

Those two KB's are if your cab file is coming out at 0k. Does not sound like the problem. Also an FYI you can have the wsutil create a log for you here is what I use: "c:\program files\update services\tools\wsusutil.exe" export d:\WSUSBackups\backup.cab d:\WSUSBackups\backup.log I have honestly not found the log very useful but it may help shed some light on your issue. James

I also have two SCCM enviroments. One that has internet access and a 2nd that is completely offline. Couple of questions. How big is the cab file that is created with the export of the metadata? If its 0k this is a known issue and you need to export less content to resolve or try this: http://support.microsoft.com/kb/2828185 or http://support.microsoft.com/kb/2819484 I would also recommend installing kb2720211 on both WSUS servers. One more thing... not only do you need to import/export the metadata but you need to copy all the content too!! Copy over the entire WSUS\WsusContent folder first!!!

You will want to create an application instead of a package. When you create the deployement type you have the option to create a dependency.

If your WSUS server OS is not 2012 I would also make sure the following two updates are applied to it: http://support.microsoft.com/kb/2720211 http://support.microsoft.com/kb/2734608

After working with both Secunia and Microsoft we finally found the problem. One of my secondary sites had severe issues. The MP on this site was preventing new info from being written to the sql database. Had to completely blow away the secondary site and set it up again. Even though the machines we were looking at were part of the primary site, the secondary site was holding the database hostage.

I have had to run the /noservice syntax on machines that are not in a trusted AD or cannot access the client source files. So it may be worth looking at AD discovery, Client Share Permissions, and Boundaries.

SCCM 2012 SP1 CU1 I could use some assistance on an issue. I am attempting to deploy updates that were created using Secunia. I can deploy the Secunia CSI Client to my target collection without any problem. The problem is when I attempt to add additional Secunia Packaged updates. From what I can tell the evaluation never completes. My reports show missing updates, however the SCCM Client never completes the evaluation of the deployment and therefore never downloads and applies the updates. Here is what I have done so far. I have tried deploying one updated at a time and the only one that works successfully is the CSI Agent. This makes me very confident it is not a certificate problem, or an administrative problem with the deployment package, distribution point, update group or deployment. UpdateDeployemnt.log: Message received: '<?xml version='1.0' ?><SoftwareUpdatesMessage MessageType='EvaluateAssignments'><UseCachedResults>True</UseCachedResults></SoftwareUpdatesMessage>' UpdatesDeploymentAgent 6/30/2013 12:37:07 PM 5932 (0x172C) Assignment {C2A7802C-68F9-4253-A074-AE558139F5EF} has total CI = 635 UpdatesDeploymentAgent 6/30/2013 12:37:07 PM 5932 (0x172C) Detection job ({E70D8F9A-DDCB-465E-9E51-7E30097612C3}) started for assignment ({C2A7802C-68F9-4253-A074-AE558139F5EF}) UpdatesDeploymentAgent 6/30/2013 12:37:07 PM 5932 (0x172C) Started evaluation for assignment ({C2A7802C-68F9-4253-A074-AE558139F5EF}) UpdatesDeploymentAgent 6/30/2013 12:37:07 PM 5932 (0x172C) Assignment({6C96BA91-B521-4852-BFBE-E6067A77A1C0}) already in progress state (AssignmentStateDetecting). No need to evaluate UpdatesDeploymentAgent 6/30/2013 12:37:07 PM 5932 (0x172C) Evaluation initiated for (1) assignments. UpdatesDeploymentAgent 6/30/2013 12:37:07 PM 5932 (0x172C) DetectJob completion received for assignment ({C2A7802C-68F9-4253-A074-AE558139F5EF}) UpdatesDeploymentAgent 6/30/2013 12:38:05 PM 260 (0x0104) This machine belongs to two update groups. The first group (Assignment ending in F5EF) has 635 updates and is working properly. Teh evaluation runs, the 2nd group (Assignement edning in A1C0) has been "In Progress" for almost a week. It only contains 9 third party updates... The real catch it the reports show that the update is missing, required and the deadline has passed. Attached some files if anyone has any idea's were to look next. Thanks in advance WindowsUpdate.log UpdatesStore.log UpdateDiscoveryProvider.log UpdatesDeployment.log UpdatesDeployment-20130630-062518.log UpdatesHandler.log UpdatesStore-20130630-123758.log WUAHandler.log