Another interesting part would be the Zero-Configuration MSI Deployment. Insert MSI into Dirfiles and get started. No parameters are required. Thank you for the video!
Thank you for the video! I have a conceptual problem with the overall app assignment options in Intune and also Im working on a strategy to have all our provisioned apps through Intune constantly updated. As an Administrator you want that your apps which you provide are being constantly updated. So the move would be that you package the apps that you want to provide constantly and set them on required. I standardized the app packaging with powershell app deployment toolkit lately. The problem with that is, that in the ESP phase, all required apps get installed if you enroll new autopilot devices and that slows down your ESP installation phase. How do you guys work with that? What is your general strategy to update and maintain provisioned apps? Do you use something like evergreen / PSPackageFactory in combination with PSADT?
Hi paradox Thank you for the comment! You are absolutely right about keeping your apps updated. We have a couple of videos showing more automation on that part and Nickolaj is working on a more automated assignment approach also: ua-cam.com/video/BdtWTDIFzp0/v-deo.html ua-cam.com/video/OI12ZTa3Qrw/v-deo.html To keep 3rd party apps updated I use winget for that. This tool works really well github.com/Romanitho/Winget-AutoUpdate And then Microsoft announced that they will deliver patching of 3rd party patches using MDE+Intune in the near future, so stay tuned for that.
The thing is multiple profiles will be used on the computer. So let's say user 1 logs in he/she has access to those programs set with the specific settings within the application. User 2 logs in, and those same application programs should apply to user 2, user 3, user 4, etc. Is this possible through MDT? an example of this would be the "command prompt" or "Textpad" the text size, fonts, and color are set as specific settings it should apply to all newly logged-in users. I heard this is possible through PSADT but im new to the program any help would be great
Hi Carrealuu This scenario is pretty common when it comes to applications and their method to write configurations. They are normally "Per user" based also to follow Microsoft best practises on how to make program code. PSADT have a possibility to add registry keys to all users even if it is in the HKCU space. I am about to plan 2 new videos on how to work with registry in PSADT. Stay tuned for the next 2 sessions, they will be for you.
![PowerShell App Deployment Toolkit - [Chapter 4 Mastering Registry Keys]](http://i.ytimg.com/vi/qOtVwcxGNSI/mqdefault.jpg)
![PowerShell App Deployment Toolkit - [Chapter 4 Mastering Registry Keys]](/img/tr.png)
Another interesting part would be the Zero-Configuration MSI Deployment. Insert MSI into Dirfiles and get started. No parameters are required.
Thank you for the video!
Hi Christian
Yes that is correct. Very easy and nice way to fast deploy your basic MSI packages. 👌🏻
your videos are so valueable! Any chance you could do a troubleshooting series about MDM policies in intune?
Hi Michael. Thanks for that!
Yes I am planning to make some deep troubleshooting next year. Time is my issue 😁
Thank you for the video!
I have a conceptual problem with the overall app assignment options in Intune and also Im working on a strategy to have all our provisioned apps through Intune constantly updated.
As an Administrator you want that your apps which you provide are being constantly updated. So the move would be that you package the apps that you want to provide constantly and set them on required. I standardized the app packaging with powershell app deployment toolkit lately.
The problem with that is, that in the ESP phase, all required apps get installed if you enroll new autopilot devices and that slows down your ESP installation phase.
How do you guys work with that? What is your general strategy to update and maintain provisioned apps? Do you use something like evergreen / PSPackageFactory in combination with PSADT?
Hi paradox
Thank you for the comment!
You are absolutely right about keeping your apps updated. We have a couple of videos showing more automation on that part and Nickolaj is working on a more automated assignment approach also:
ua-cam.com/video/BdtWTDIFzp0/v-deo.html
ua-cam.com/video/OI12ZTa3Qrw/v-deo.html
To keep 3rd party apps updated I use winget for that. This tool works really well
github.com/Romanitho/Winget-AutoUpdate
And then Microsoft announced that they will deliver patching of 3rd party patches using MDE+Intune in the near future, so stay tuned for that.
The thing is multiple profiles will be used on the computer. So let's say user 1 logs in he/she has access to those programs set with the specific settings within the application. User 2 logs in, and those same application programs should apply to user 2, user 3, user 4, etc. Is this possible through MDT? an example of this would be the "command prompt" or "Textpad" the text size, fonts, and color are set as specific settings it should apply to all newly logged-in users.
I heard this is possible through PSADT but im new to the program any help would be great
Hi Carrealuu
This scenario is pretty common when it comes to applications and their method to write configurations. They are normally "Per user" based also to follow Microsoft best practises on how to make program code.
PSADT have a possibility to add registry keys to all users even if it is in the HKCU space. I am about to plan 2 new videos on how to work with registry in PSADT. Stay tuned for the next 2 sessions, they will be for you.
@@MSEndpointMgr wow thank you so much and happy new year!
Happy new year!
Is there a way to Uninstall an older version of an app and then install the new version all in the same script?
Yessir.
If you use the remove-msi first you remove the app, and then straight after add the install command for the program you want to install.
Check out this video about 4min in I am doing it
ua-cam.com/video/2rKVq482nz0/v-deo.html
I edit the XML file so the default install option is /QN instead of /QB!
Great tip!
The problem is all the software you cant get in msi format and no silent install parameters for the exe
Luckily only very few left of that kind. For that task we need to repackage using a MSI packaging tool