Toolbox VS CMPackager

I also read Adam Gross' blog about VDI & Co-management conflicts and am wondering if we could use something similar to the script he wrote to run DSREGCMD /LEAVE and clean up Intune enrollment info on the master image before sealing it up. Seems like it might work?

Toolbox/Intune/ADMXIngestion at master · AdamGrossTX/Toolbox · GitHub

Adam Gross also has some one his GitHub: https://github.com/AdamGrossTX/Toolbox/blob/master/Intune/Intune-UnHybridJoin.ps1 You shouldn't need to remove hybrid join (unless you want to ), but that script has it too.

I believe the basic user info and AD group/container membership should be retrievable through an admin service query to return filtered SMS_R_User records (ex around line 58 of this - https://github.com/AdamGrossTX/Toolbox/blob/master/ConfigMgr/AdminService/AdminServiceQuerySamples.PS1. I'm not affiliated, but that github repo has some useful stuff, along with this post from the author - https://www.asquaredozen.com/2019/02/12/the-system-center-configuration-manager-adminservice-guide/ ).

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.