A community dedicated to the profession of IT Systems Administration
No generic Lemmy issue posts please! Posts about Lemmy belong in one of these communities:
[email protected]
[email protected]
[email protected]
[email protected]
Microsoft wants you to buy 1 PC and license per user. They pretend to support multi-user systems but in reality most of their admin tools suppose a machine is dedicated to a user, or that users are at least generally always using the same machine.
If you can programatically fix the issues causing the calls, put the fix in a login script using traditional mechanisms.
We were expecting the same and wishes MS just admitted this to us so we can go on.
We have no good mechanisms to deploy startup scripts and try to rely as much as possible on the best-practises Microsoft has. If we ever get those anyway..
This may be what you’re looking for. Treat the system like a VDI install when you’re installing things and look for “machine-wide” installers. Also consider getting FSLogix (free from Microsoft) to put user profiles in portable containers.
Interesting article but not really what we're looking for:
This option is especially useful for computers with multiple users and for when you don't want executable files running from a user profile.
Other than where the sync app is installed, the behavior is the same.
It's not the installation but the configuration that is causing trouble. FSLogix would require on-prem hardware.
You should be using machine wide installers not user appdata installers. Are you not?
So aside from using machine wide installers and ensuring that users are licensed for those products, you also need to setup enterprise roaming.
By the way, intune policies if they aren't changing don't take 8 hours to propogate to the machine, they take hours to propogate world wide like group policy takes hours to propogate in international sized ad forests.
So if you've got your intune policy set to auto sign in one drive and teams and whatever apps, assuming all your devices are intune registered, that setting doesn't take hours to get to the machine. It's immediate on first login. If you change that setting, it's some hours to get it across every single machine. By the way in my experience, generally 80% of the time with a forced sync from the company portal app you should deploy with intune, it's practically as fast as gpupdate. There's a few times where you need to patiently wait 15 minutes but you can see that if you name your configuration profile like (v12) and you'll see it's either still (v11) or immediately (v12) and you stuffed a setting and it's still not working.