sccmclictr VS CMPackager

To any future comers, it seems /u/chfuchs comment about using https://github.com/rzander/sccmclictr is the solution. However, there are a few caveats. You must enable WinRM (even on localhost), which can be done via cmd prompt using winrm quickconfig. The other thing is, it must run as admin. So I can see the TS advertisement, and when I hit "re-run" advertisement, it immediately pops up in Software Center. I'm not sure what the issue is, but this works 100% of the time (tried it in a VM and two desktops, and a laptop all within different boundaries).

I like to use this tool to see which updates are missing on a computer on the fly: https://github.com/rzander/sccmclictr

Client Center for Configuration Manager is a ConfigMgr Agent troubleshooting tool that provides a user-friendly interface for a quick overview of client settings, running services and agent settings. vawlk uses it to "remotely troubleshoot SCCM client issues … This is just a gui for SCCM/Windows powershell commands, and it shows you a window for those commands as they run. Pretty sweet for an SCCM environment."

Use something like Client Center https://github.com/rzander/sccmclictr if you really want a gui to do it manually without locking the device.

I’d grab this tool if I were you, Client Center for config manager https://github.com/rzander/sccmclictr

Well, not Collection Commander, nor the "old" SCCM Client Center; but this one, sure... I still use it occasionally: https://github.com/rzander/sccmclictr

CMPackager if you want a single file that does everything

Current package used. https://github.com/asjimene/CMPackager/blob/main/Disabled/AdobeReader.xml

Cmpackager can assist automated application deployment. https://github.com/asjimene/CMPackager

It's not that I didn't like the answer, I just made the post on other platforms to expand it further, since sometimes the community can't be here. The script using -ComObject for internet explorer works very well, it captures the link and if I want I can download it, but the only dissatisfaction is that this command doesn't seem to work on Windows Server. But for you who still don't know why I'm looking to do this via powershell, it's for SCCM using a utility that automates software downloading and publishing for SCCM which is CMPackager

This is the way https://github.com/asjimene/CMPackager

The CMPackager script is really amazing, and if implemented well it can really reduce the number of manual interventions in terms of SCCM applications. But I saw some details about CMPackager. It basically puts the name of the application along with its version, and this is a problem because if there is more than one version (Chrome for example) you will see several entries in the Applications field in SCCM, such as Chrome 97.04692.70, Chrome 97.04692 .71, Chrome 97.04692.72, Chrome 97.04692.73 and this is really annoying. So opening the CMPackager.ps1 I removed the variable "$ApplicationSWVersion" that is related to the display name of the application in SCCM, and so far everything is ok, the script continues to download and create the package and distribute normally the problem is that it cannot just update the content within that same name, as if it depended on always creating a new name in SCCM and that really is a problem. As this log shows, I had a Google Chrome entry in the Applications list in SCCM and its version is 68.127.32839 and the latest version CMPackager found is 97.0.4692.71 but instead of it just changing the version and update the content, it simply skipped that part and ended the script.