GarthMJ

I always enabled Names Pipes. However, if you have an open ticket with MS, I strongly recommend that you don't continue with troubleshooting in the forums. Items I guess might conflict with item CSS suggest. This will increase the time it takes to solve the problem and may cause new problems.

You didn't answer the question about SQL names pipes. if you have opened a case with CSS, I never recommend that you continue with forum posts. Thye ideas can conflict and cause more problems, as such keep with the CSS ticket.

Are NamedPipes enabled for SQL?

Just to be clean NT AUTHORITY\SYSTEM MUST be SA within SQL.

This WMI class is not enabled by default within hardware inventory. You would enable it as you would any other class.

Since you are on CMCB 1606, You missed the obvious things like. - Are you running a supported version of CMCB? - Is SQL running the latest SP/CU? - Is the OS uptodate? etc.

Since a SU is limited to 1000 SU, this doesn't make sense to do. Instead, create or purchase that can report set the will report on all SUG.

This blog might help. https://www.enhansoft.com/blog/why-wont-collections-update-on-the-cas

Have you enabled software inventory Is software inventory Inventoring .lnk files? Is there a reason you aren't just using a configuration baseline? it is easier to do this.

I wouldn't bother with a collection for this. instead, I would just deploy these SU just as you would any other SU. I would use this to determine what SU to deploy. https://www.enhansoft.com/blog/how-to-determine-what-software-updates-are-required-within-configuration-manager

ok, So what have you tried? what is not working for you?

You have the automatic push enabled or you have a GPO to force the install. In either case, you need to figure out which and turn it off.

Unless you say within package (not application) the deploy run from DP, all content will be cached.

I'm not following you, can you provide more details as to what exactly you are trying to do.

yes but depending on what version you are using now. That recommend might have changed. Are you using CM12 or CMCB?

Again CM uses the local computer account, you can't change its password. So exactly what account did you change its password?

CM12 doesn't have a service account, it uses the local computer account. So exactly what account did you change?

Since that is not the expected results. You will need to open a support case with CSS (Microsoft Support) directly to get support for this issues.

Are you seeing the new policies being download? For example, if the computer is off the network, the computer will re-run with the old version, why because as far as it is concerned those policies are still current.

I know that you don't like the answer but in a nutshell, it is right. Think about it. How does a CM client know that there are new source files? At a high level, the processes is a follows. Source Files are updated. CM is told to update source files CM creates the package for replication. CM update the source version within db. CM create a policy stating there is a new version for package x. DP are told to update source files DP actually get new source files. CM update the source version within db. Client contact MP and for all policies All policies are evaluated Client run package x, notices that it's version does not match package x Client downloads new source files Client run package x. If client do not see the latest version of the package then something is wrong in step 1-4. Once step 5 happens, all clients will wait for the newest source files to be on their DP once the policies are evaluated.

That would only happen if the DPs are not updated with the newest source files.

It can cause problems if you delete the source SU.

And exactly what happened when you ran the Psexec command? Did you try trying the cmd using the 32bit cmd too? It is easy to prove the timeout as it will show within the logs that the install timed out.

And what happens when you run it with the local system account? Have you contacted IBM about this yet?

Timeout issue is generally a network issue.