The storage point may be in the main data centre, but the application is required at another centre many miles away, so the WAN is carrying data that it should not have to. Under this new system, where they expect us to just call the BAT file that has been downloaded with the deployment image, SCCM/EPCM will download the application to the client, then completely ignore what it has downloaded and start pulling the software in from the storage point. ![]() In a multi-site, multi-distribution point setup (very common with SCCM) this system allowed the application to be downloaded from the local distribution point, then run on the client, thus reducing network load, particularly in a WAN environment. Detection MethodsĪll Autodesk deployments generated by the users up to and including version 2021 generated SCCM/EPCM scripts that were totally server agnostic, so when SCCM downloaded the application to a folder in C:\Windows\ccmcache everything ran from there, we also had the option for a much more granular build than we do under this new regime. Packaging for MEMCM - More info please, e.g.Installer.exe where can I can find ALL possible command line switches.News flash Packages are an ARCHAIC deployment option in SCCM (for probably a decade at this point and technically it's not SCCM its MEMCM for those of us who actually keep our environment up to date) This should be an Application period.Īll that frustrated vitriol might be lessened if I could find an actual documented list of Installer.exe's valid command switches, maybe there's a -wait or a -sccm I'd even take an antiquated -sms! Something ANYTHING to make this not like shooting off a shotgun in a dark room and hoping it doesn't kill someone. I don't like to rant but it seriously like the people designing these bundling logic have NEVER touched a modern version of SCCM. and failed." meanwhile the install is still rolling along. Running either the Bat file OR the Installer.exe command line from the batch file promptly spawn entirely new installation processes and then promptly DIES! Which causes the SCCM client to go "guess we're done here. The second bigger issues is in order for An Application in SCCM to properly work it needs to WAIT to return until it's ALL done installing. A simple list even a rem block under each item with its MSI GUID would go a LONG way to making this easier to package. The problem is the bundle kind of obfuscates that all you get is a reference to the same installer.exe with uninstall and a xml manifest file for each piece you bundled. I'd be fine if it was just layering in ALL the MSI GUID's for the major software installs. What about a detection method? Applications in SCCM need to have a detection method to tell when they are installed. bat file generated when you run the Custom Install bundle you create from your management site. difficult.įirst the only information I could find was two pages one that just says to install silently comment out and uncomment these lines in the. Trying to get it into SCCM as an application has proved. ![]() Though it seems to still be severely lacking or rage inducing to try and find more information about it. Been really stoked about the new ability to bundle most of the 2022 AutoDesk products back into a single package.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |