Office 365
-
E3 for me. That screen you posted is after you click manage. Nothing on the manage screen shows counts allowed.
Here is what I see on mine after I cleaned up old systems.
-
No clue how Pro Plus licensing works.
Frankly - I still don't know how you deploy O365 to 100 units and attache the main user of the computer to the account instead of person doing the install.
I assume with the automated tools, there must be some type of first attempt launch process that kicks off when the user launches it the first time, they then log in with their O365 account and it attaches to their account.
But I don't know for sure. -
Interesting note, my desktop is not showing up in that list.
-
@JaredBusch I saw that same screen but didn't post the whole thing.
-
@Dashrender You deploy using the Click to Run tool. Which sounds easier than it is to setup.
-
@wrx7m said:
@Dashrender You deploy using the Click to Run tool. Which sounds easier than it is to setup.
I'm assuming there is a way to grant local admin rights to only that tool then? My users don't have local admin rights.
-
The way it works is that it uses a script and an xml file with settings to download the file. You can run it as a startup script via GPO so they don't need to be admins. None of my users are either.
-
@wrx7m said:
The way it works is that it uses a script and an xml file with settings to download the file. You can run it as a startup script via GPO so they don't need to be admins. None of my users are either.
Good tip. Thanks.
-
Can it be that I have some 2016 and some 2013 installs as to why it allows me 10 standard (non mobile) devices?
-
@wirestyle22 Hit me up if you need more info. Also, I think only certain plans let you use click to run. I can't think of how they would prevent you from using it, as I don't think you put any identifying info in until after everything has been installed and the user logs in to activate the license.
-
-
@wrx7m said:
@wirestyle22 Hit me up if you need more info. Also, I think only certain plans let you use click to run. I can't think of how they would prevent you from using it, as I don't think you put any identifying info in until after everything has been installed and the user logs in to activate the license.
Probably the plans that allow for on-premises installs
