Jul 14, 2018 The next course of action to troubleshooting hardware inventory in SCCM is to look at the client log files, specifically the InventoryAgent.log. The full path for the log file is C:WindowsCCMLogs. Another thing you have to note, is that SCCM will never actually show that the “hardware inventory”.
- Sccm Client Settings Software Inventory
- Sccm Client Software Inventory
- Sccm Software Inventory Configuration
- Kerosakan Perisian Aplikasi
- Sccm Client Policy Software Inventory
Applies to: System Center Configuration Manager (Current Branch)
This procedure configures the default client settings for software inventory and applies to all the computers in your hierarchy. If you want to apply these settings to only some computers, create a custom device client setting and assign it to a collection. For more information about how to create custom device settings, see How to configure client settings in System Center Configuration Manager.
To configure software inventory
- In the Configuration Manager console, choose Administration > Client SettingsDefault Client Settings.
- On the Home tab, in the Properties group, choose Properties.
- In the Default Settings dialog box, choose Software Inventory.
- In the Device Settings list, configure the following values:
- Enable software inventory on clients - From the drop-down list, select True.
- Schedule software inventory and file collection schedule - Configures the interval at which clients collect software inventory and files.
- Configure the client settings that you require. The Software inventory section of the About client settings in System Center Configuration Manager article has a list of the client settings.Client computers will be configured with these settings when they next download client policy. To initiate policy retrieval for a single client, see How to manage clients in System Center Configuration Manager.TipError code 80041006 in inventoryprovider.log means the WMI provider is out of memory. That is, the memory quota limit for a provider has been hit and inventory provider cannot continue.In this case, the inventory agent creates a report with 0 entries so no inventory items are reported.
A possible solution for this error would be to reduce the scope of the software inventory collection. In circumstances when the error occurs after limiting the inventory scope, increasing the MemoryPerHost property defined in the _ProviderHostQuotaConfiguration class can provide a solution.
To exclude folders from software inventory
- Using Notepad.exe, create an empty file named Skpswi.dat.
- Right-click the Skpswi.dat file and click Properties. In the file properties for the Skpswi.dat file, select the Hidden attribute.
- Place the Skpswi.dat file at the root of each client hard drive or folder structure that you want to exclude from software inventory.
Sccm Client Settings Software Inventory
Note
Software inventory will not inventory the client drive again unless this file is deleted from the drive on the client computer.
Posted by2 months ago
I make this post after many hours of scouring the Google. In my searching 90% of the posts and resolutions ended at updating the MIF file to 50MB.. I did not see one contiguous post that went past updating the MIF. The solution (for me) from diving into the scattered logs of SCCM and IIS and a client.
In efforts of having as many solutions in one place. the Max MIF file size is located in the registry:
HKLK:SoftwareMicrosoftSMSComponentsSMS_Inventory_Data_Loader
DWORD Max MIF Size: <Maximum value is 50000000>
Issue: Hardware inventory Scan Date - Not current event after running the client actions
You may say, I HAVE ALREADY UPDATED THE MIF MAX FILE SIZE!! What next?!?!
Step 1: Review the Client side log C:WindowsCCMLogsCcmMessaging.log (this is the one and only time ill mention the full path of a client log)
CcmMessaging.log loops
Several of these events
Raising event:
instance of CCM_CcmHttp_Status
{
ClientID = 'GUID:a9a762bb-7f34-4faf-a2a6-68ffcf5fa69e';
DateTime = '20190723191405.875000+000';
HostName = 'server.domain.com';
HRESULT = '0x00000000';
ProcessID = 5804;
StatusCode = 0;
ThreadID = 15940;
};
instance of CCM_CcmHttp_Status
{
ClientID = 'GUID:a9a762bb-7f34-4faf-a2a6-68ffcf5fa69e';
DateTime = '20190723191405.875000+000';
HostName = 'server.domain.com';
HRESULT = '0x00000000';
ProcessID = 5804;
StatusCode = 0;
ThreadID = 15940;
};
Followed by this event
Supplied sender token is null. Using GetUserTokenFromSid to find sender's token.
Well this lead me down the BITS path. The BITS path actually started at a server log but in order to stay focused on the client first ill continue there.
Running the powershell command (as admin)
Get-BitsTransfer -allusers
you may see a few entries. one probably google. So now you get further information on the bits message
Get-BitsTransfer -Jobid {GUID} | select -property *
then something like below pops up. with a server name (crossed off in orange) and trailing path. CCM_Incoming is tied to IIS.
Not much more we can do on the client side at this point. But notice the Access denied portion.
Now we go server side.
![Client Client](/uploads/1/2/4/8/124897009/413463104.png)
Some logs I found helpful on the server side were the following:
Sccm Client Software Inventory
<installDIR>SMS_CCMLogsMP.Hinv.log - in here you will probably see some errors about delta changes and that the MIF file got sent to a BADMIFs folder.
<installDIR>MS Config MgrCCMIncomingBITS-Sessions - These folders will most likely be empty
<installDIR>MS Config MgrLogsdataldr.log - more specific errors about MIF files
Sccm Software Inventory Configuration
NOW HERES THE KICKER!
c:inetpublogslogfilesW3SVC1 - IF YOUR CASE IS ANY LIKE MINE YOU'LL SEE LOG FILES between 100 and 250 MB EACH!! OF PURE TEXT!!! WHAT?! Open one of those suckers up, do not use CMTRACE it will crash.. I found notepad++ works well or you can use powershell to open a small portion.
launch PS as admin from the explorer window navigated to the folder above.
get-content latestlog.log | select -last 100 | out-gridview still takes a bit to open but significantly less time.
![Missing Missing](/uploads/1/2/4/8/124897009/946484133.png)
The log was loaded with these errors:
BITS errors..
So I open up IIS and go to Sites --> Default --CCM_Incoming and at the bottom you'll see BITS Uploads. I clicked on that got this error:
BITS server was unable to read from the IIS Meta-base as it is corrupt. The settings for this virtual directory have been reset to the BITS defaults. Parameter count mismatch.
Of course we also count common sense, because a little respect for the product is the minimum. For the installation and use of the software you have to follow some hints and rules, which we would like to put in front of our manual and the download.The MorePowerTool for the AMD Radeon RX 5700 (XT) and Radeon VII (New!)We are happy that our community member hellm has finished the software MorePowerTool (MPT for short) for the release and that we can offer this software here on our RTG page exclusively for download as well as the direct support in the forum. A permanent operation of the components with values not intended by the manufacturer can lead to irreparable damage! Amd overclocking software. For the installation and use of the software you have to follow some hints and rules, which we would like to put in front of our manual and the download.Important preliminary remark- DisclaimerFirst of all it should be explicitly mentioned that this represents a massive interference in the regulation of the graphics card and may only be used by experienced overclockers and only for test purposes. The protective functions (switch-off limits) are all still activated, which minimizes the risk somewhat, but of course components such as the SOC, the memory or the voltage regulators can also suffer damage!
Now i never like to see the word corrupt. After hitting OK, IIS Crashed..
Now researching this back when i saw the access denied errors the suggestion to modify the IUSR permissions to the following folder was suggested:
<installDIR>MS Config MgrCCMIncoming (Keep this in the back of your mind)
BEAR WITH ME ALMOST DONE!
Well, i had to REMOVE the BITS feature from Server manager Remove Feature. (in case someone doesnt know BITS is Background Intelligent Transfer Services)
After removing, restart your server, then Re-Install BITS.
I do another restart
After all of that, go back into IIS --> Sites --> Default --CCM_Incoming BITS Uploads and WOOT it should open no problem. I selected Allow Clients to Upload Files --- selected default
Kerosakan Perisian Aplikasi
Sccm Client Policy Software Inventory
IT SHOULD WORK NOW!!!!! Wrong.. Now before you cry, the last step that i had to take was to go back to the IUSR account and modify the permissions of the Incoming folder to full control. Everything worked then.
I hope this helps someone out! Sorry for the long post
2 comments