Unfortunately, I will now find I am signed-out of that account in Outlook AND signed-in to Excel with the next account I used for Outlook!!!!!Īctually, you're right. However, if I sign-out of that Excel still works fine obviously and that is how I want them to work. So, once all signed-in to the email accounts in Outlook everything is fine, but then I open Excel and find I have been signed into those as well (with the first account I sign-in to Outlook with). I have also tried turning off Modern Auth on these accounts (O365 tenancy), but found I couldn't even sign-in then and it got too complicated to mess with a 'live' prod system. This is where it gets complicated as I think the 'grey box' account one must be some sort of Exchange set-up and the portal one goes to O365.
1 of which I sign in with an 80s-style grey box (no problem), but 3 of which require some sort of sign-in to a portal (Modern Auth.?). It seems to be the 'Office' way, but a bit like you I wanted machine installs (although it's doubtful that our users will go into 5 device territory anyway as we have 1-1 teacher and admin devices). via group policy ?I have a similar but slightly different issue with it that I posted about a while ago, but didn't really get any answers for, so it's stopped my plans for a roll-out' for the time being. Is not used / relevant for an LTSC/perpetual install? I also tried with DeviceBasedLicensing set to 1 just to see what would happen and install worked so maybe that setting My auto-generated xml has 0 (these options were greyed out in the wizard)
Just wary of getting caught out by the "5 device logins limit" I thought we could use SharedComputerLicensing but not DeviceBasedLicensing as you need EES license for What is the difference anyway as they sound quite similar? I also signed in to the standalone one drive client (was already installed on PC but not signed in).īoth of these sign ins gave me an error :īut word does seem to be working and can open files from one drive.Īlso not sure about values for DeviceBasedLicensing and SharedComputerLicensing
Only solution I've found is to sign out and then sign in with the users office 365 account We have on-premise AD only at the moment. word it auto "signs in" with the users domain account. That isn't supported on windLTSC, and Office LTSC 2021 is (until Oct 2026)Ĭouple of things: on starting e.g. Was thinking about going with latest i.e. We are still on windLTSC with Office pro plus 2016. Bit late to the party as usual but did my first test install / upgrade today toĪctually went better than expected Included my xml config below.
0 kommentar(er)
