![]() ![]() ![]() I’ve logged into the software manually with some test accounts. ![]() I’ve created and downloaded packages for OSX and Windows environments and done good few mac deployments using ARD (Apple Remote Desktop). I’ve looked at the profile and general settings – pretty easy. I’ve configured and synchronised our Azure Active Directory users as Federated IDs which now exist in our Adobe Cloud agreement – pretty easy. I’m giving my full perspective here and not meaning or intending to teach anyone to suck eggs as there are a lot of respectful technical minds here on edugeek. The idea of SSO (Single Sign On) is that you login once and that any relevant sub systems/software are aware of that and won’t bother you for credentials. What this means is that whilst the software is licensed to a device, End users are still required to manually authenticate with an ID whereas before under the Device License model, all end users had to do is open the software and use it which is how it should be in a teaching and learning environment. Support dept of secondary school with 800+ students.Īdobe have made using their product more difficult to access for schools and establishments by introducing SDL (Shared Device Licensing) and this has been out for alittle while now. ![]()
0 Comments
Leave a Reply. |