-
Posts
1949 -
Joined
-
Last visited
-
Days Won
93
Posts posted by GarthMJ
-
-
You will not lose you custom reports. However if you have any doubts, you can always backup your report first. (Which you should be doing anyways.)
-
Then you need to review the IIS logs to determine why you are getting 401 errors from you DP. it is mostly like that you have locked down the DP server with some extra security.
-
To be clear you did this on your WG PC, right?
-
Any share, particularly on your DP. You are just trying to prove that the account works, nothing more.
-
Have you tested the network access account (NAA) on you WG PC to confirm that the account does work? You do this by mapping a drive with the NAA account .
-
-
if you look at the RDL you will see that it is a Null to get the (All) for the prompt.
-
Start by looking at the built-in report. Which one get you the closest to what you need.
-
Each Month Enhansoft gives away a free SCCM dashboard / report.
November's Free Report is...
Total Usage Trend Analysis for Collections! This software metering dashboard gives you results for all applications and will display these details for up to four collections. The results are grouped by month and will go back as far as what is stored in your SCCM environment (usually 9-months to a year).
Get your free report today! The Total Usage Trend Analysis for Collections report is only available in November.
-
-
Here is a list of all of the log file and what they do.
https://docs.microsoft.com/en-us/sccm/core/plan-design/hierarchy/log-files -
You need to review the log files to determine why, it is not installing.
-
8 hours ago, Sokoban said:
Hi
What log file ? in Event Viewer ?
It will depend on how you are deploying reader. Here is the list of log files. https://docs.microsoft.com/en-us/sccm/core/plan-design/hierarchy/log-files
-
What exactly doesn't work? What do the log file say is happening?
-
On you r site server, unselect the Win32_PhysicalMemory under hardware inventory. Does this fix your issue?
-
6 hours ago, kaiserclaw said:
This is what I got so far:
select SMS_R_System.ResourceId, SMS_R_System.ResourceType, SMS_R_System.Name, SMS_R_System.SMSUniqueIdentifier, SMS_R_System.ResourceDomainORWorkgroup, SMS_R_System.Client from SMS_R_System inner join SMS_G_System_ADD_REMOVE_PROGRAMS on SMS_G_System_ADD_REMOVE_PROGRAMS.ResourceID = SMS_R_System.ResourceId where SMS_G_System_ADD_REMOVE_PROGRAMS.ProdID like "{34624CAC-1434-468E-56DC-2A7D44D5F49F}" and SMS_R_System.SecurityGroupName != "MGT\\App-install-Adapt"
You will need to use a sub-select query to do the not in stuff.
Here is an example. https://www.enhansoft.com/blog/subselect-wql-query-to-find-pcs-that-do-not-have-either-x86-or-x64-versions-of-software-installed
-
1
-
-
You need to export it from the console (client settings) . However I would try Sherry's stuff first, as it is harder to "kill" the sms_def.mof in CMCB.
-
That take care of the one file what about the client setting (sms_def.mof)?
-
Have you reviewed your Client setting (sms_def.mof) and Configuration.mof files
-
There is no directly link between those two SQL views. You will need to dig deeper to find a indirect link between them.
-
What do you have for you query already? What is not working with it?
Here are a few reporting tips. Seven Tips for Writing SCCM dashboards
-
Did you create a SWM rule for spotify? When did you create this rule? Is the Software listed in Installed Programs in resource explorer? Is the SW installed under the user content? if it is installed under the user context then you will need a 3rd party tool to collected this information with SCCM.
-
Have you looked at the built-in reports for this info?
-
I would start by looking at the builtin report to see if ARP reports give you what you want? until that is confirmed there is no point trying to join a user name to a computer.


Suppress faulty KB after patching cumulative updates and also on the next cumulative updates
in Troubleshooting, Tools, Hints and Tips
Posted
Assuming that this is a cumulative KB, you don't directly. You contact MS to so that the KB can be fixed or you fixed your software that it works with the KB.