-
Posts
1949 -
Joined
-
Last visited
-
Days Won
93
Posts posted by GarthMJ
-
-
There is going to be no wrong answer to this, each person will do it differently. I would do it so that ti makes sense to you.
-
Did you know that Enhansoft is giving away a free report set on Software Update Health? Check out the blog about it. https://www.enhansoft.com/blog/software-update-health-dashboard-set-special-microsoft-ignite-giveaway
They give away something every month too! https://giveaway.enhansoft.com/
Keep in mind that I do work for them too.
-
You you have reviewed the logs files on the client and MP right?
-
great. so everything is good now then. right?
-
Review the inventory.log to see if it has run.
-
Review he inventory.log on the client, is it preforming a heartbeat discovery? -
Since this tool only comes with PFE Consulting services and this tool is updated regularly, only PFE consulting services can answer this question for you.
-
I would check to see if your client are running the most current version of the client.
-
There is no simple answer. The biggest issue is that you had BadMIFs and didn't know it, that is the most common reason that I see. But there are millions of other reasons too.
-
Are you sure??? you will likely find that was not the case and the full inventory has "fixed" it.
-
I would force a full hardware inventory on one fo the PC to confirm that it has the correct data. if that works then force full hardware inventory on the whole collection. These blogs will help you with these tasks.
-
1
-
-
you have looked within Resource explorer and confirm what build number they are showing right?
-
I see nothing wrong with that query and I tested it within my environment and it only shows 16299 build computers. I would update your query again and force the collection to update.
-
Can you please post the full query to be reviewed.
-
I see nothing in there but if the error is a red herring, I would expect to either.
I would make sure that the MSI isn't blocked.
I will manually install it as the local system account https://verbalprocessor.com/2007/12/05/running-a-cmd-prompt-as-local-system/ if it fails, send this to q-pulse and get them to tell you why it is failing. if this works then it is an interactive setup or x64 issues.
-
Have you talked to Q-Pulse about this? I have a hard time believing that the local system account which has more rights than the administrator account doesn't have the right rights. IMO the error is more likely a red herring and there is another true error.
-
Did you create and review the MSI log file? This will tell you why it is failing.
-
the script will work as you because you have access to the share. The script will not work from CM as the computer account generally don't have access to network shares.
-
That is because you are trying to copy the shortcut from a UNC. Since you are using PowerShell, create the shortcut or copy the shortcut from the local folder.
-
I’m sure that you can use PowerShell to do this. With a bit of googling and cutting & pasting this should work.
-
You don't need a product code to uninstall an application. use your PowerShell script.
-
You will need to provide more details.
Yes, you can uninstall the software but only if there is a way to uninstall that software. That is your first step, is to determine if you can uninstall the software. No one can help you with that you need to review the software or talk to the vendor.
-
4 hours ago, amit paul said:
issue got resolved after solving SQL server configuration manager issues.
Open a command prompt as administrator
Navigate to your SQL version’s shared directory (cd <version path>):
SQL 2008: C:\Program Files (x86)\Microsoft SQL Server\90\Shared\
SQL 2008 R2: C:\Program Files (x86)\Microsoft SQL Server\100\Shared\
SQL 2012: C:\Program Files (x86)\Microsoft SQL Server\110\Shared\
SQL 2014: C:\Program Files (x86)\Microsoft SQL Server\120\Shared\Then run the following command:
mofcomp sqlmgmproviderxpsp2up.mof
1802 Upgrade successfully completed.
The funning is I have a rough draft blog post mostly written on how to install the SQL WMI providers. The WMI providers seem to be removed when you applied some of the SQL SU. It wasn't something I thought of when you posted here.
-
26 minutes ago, amit paul said:
Unfortunately I tried all troubleshooting however CSS failed to provide any possible solution after two days troubleshooting.
Make sure that CSS credits your account for the failed case.

CN 1806 Failing Prereq check
in System Center Configuration Manager (Current Branch)
Posted
The screenshots show that you AI update point is running on Windows 2008. So what server is that on?