search

microsoft / shell-intune-samples

Sample shell scripts for Intune admins.
MIT License
670 stars 222 forks source link

Teams Update #13

Closed mcainiom closed 3 years ago

mcainiom commented 3 years ago

We are having issues with Teams being out of date and no longer working without an update. The script aborts if the Application is already present, can the autoupdate variable be overridden so the modified date is checked and a version is installed anyway if the meta file is not present?

theneiljohnson commented 3 years ago

Yes, set autoUpdate="false" and it will overwrite the current install.

mcainiom commented 3 years ago

Thanks, ended up forking the script and making modifications. Couldn't work out how to pass properties/variables using the quick run command in Intune

theneiljohnson commented 3 years ago

We can’t pass variables to scripts yet. It’s on our roadmap, hopefully before the end of the year.

Feel free to let me have any recommendations, I’d love to see what you had to change.

From: mcainiom @.> Date: Monday, 19 April 2021 at 16:20 To: microsoft/shell-intune-samples @.> Cc: Neil Johnson @.>, Comment @.> Subject: Re: [microsoft/shell-intune-samples] Teams Update (#13)

Thanks, ended up forking the script and making modifications. Couldn't work out how to pass properties/variables using the quick run command in Intune

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fshell-intune-samples%2Fissues%2F13%23issuecomment-822553221&data=04%7C01%7Cneiljohn%40microsoft.com%7C41d5b24afad6478e089308d9034698f2%7C72f988bf86f141af91ab2d7cd011db47%7C0%7C0%7C637544424051311209%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=%2BXThAt4quXnpkL%2Fi9WZB0n356yd%2BALAC6aoYsOL5VSs%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAGOC2JNI2WBFAOV5GQJHT73TJRCZ5ANCNFSM425JYHLA&data=04%7C01%7Cneiljohn%40microsoft.com%7C41d5b24afad6478e089308d9034698f2%7C72f988bf86f141af91ab2d7cd011db47%7C0%7C0%7C637544424051321163%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Epi90yPta4zDduI5WTdFSTbfdtCP09YVmgFrP68%2BV7U%3D&reserved=0.

mcainiom commented 3 years ago

It was only the autoupdate I changed. I also added a check so when an internal server returned a 200 it would download from our internal web server to save the pipe, a simplified version of what you've done on the office install script. A small cosmetic change I made was adding the ':' to the last-modified date just to cleanup the guff that's returned.

Some really nice, useful scripts though, definitely changed my attitude/mindset towards packaging software. Where possible I just script the download from the source and install and don't touch the package. Office I have a script to write out our install customisation xml and let the downloaded package pick that up. Life changing :D