NetMan07

After the responses received here and my own tests, I can confirm that my problem was caused by the VLC .MSI installer as the .EXE version installed the software properly for all users.

Hi, I’m trying to deploy 'VLC Media Player' as an application with the OS when imaging computers using ‘Microsoft Deployment Toolkit’. The install command I’m using is: msiexec.exe /i "vlc-3.0.16-win64.msi" /quiet /norestart /qn If I log into the imaged PC as the local administrator, VLC is there and opens straight away. However, as soon as I log in as a new/different user and open the desktop shortcut, VLC runs through its Windows installer automatically and then opens. Is there something I need to do/tweak to get VLC to install for all users of the computer during deployment? Thanks.

Thanks for the advice. I couldn't decide if by "distribution" they meant organisations putting the full installer (MSI/EXE) file on the "intranet site or local network" for pupils/staff to grab and take away to install anywhere. That is a very different situation to IT simply pre-installing the software on their fixed LAN computers for day-to-day use.

Hi, I want to install 'Adobe Acrobat Reader' on each of our LAN computers so that pupils/staff can view PDFs. Do I need to apply for Adobe's 'Distribution License Agreement' to do this? I've read conflicting views on the internet and their own webpage (linked below) isn't particularly clear because they don't actually define what "distribute" means. https://acrobat.adobe.com/us/en/acrobat/pdf-reader/volume-distribution.html Thanks.

Thanks for the quick responses Steve and Jcx500. Can the modern apps be removed by script after an image has been deployed to a computer? If the modern apps have been removed, is there still a need to create default profiles? I'm trying to move away from the profiles model and use GPO more to control our users.

Hi, Windows 10 Enterprise (1909), Windows 2016 Domain The last problem I’m struggling with before being able to deploy ‘Windows 10’ is the very long first logon time that occurs whenever a user logs onto a computer they’ve not used before (i.e. no existing local profile). It’s well griped about on the web as being caused by the modern apps provisioning. In open access/shared areas this long first logon time would be every time a user logged on in the majority of cases. How did you overcome this for your deployment? Thanks.