Jump to content

Recommended Posts

Posted (edited)
Adobe are moving away from SDL, you can still buy them but next year you will have to go to user based, minimum 500 (but a lot cheaper per licence).

Note that SDL won't give you Adobe 2019 - you need user based licences for that and if you move over next year it will require a complete reinstall.

Happy to have a chat if you like.

I'm confused, that doesn't seem to be true at all? SDL works fine with Adobe 2019 - indeed that's why they built the new system - as the old device based licenses didn't work with 2019. SDL has only been out a couple of months, superceding the old device licenses.

 

I've just built an SDL package to install, so will see what it installs now.

Edited by localzuk
  • Thanks 1
Posted

Sorry, added an S.

 

You can still buy Device licences but they won't run 2019 and at the end of the year you will have to migrate to SDL/user licences.

 

John

Posted

On a slightly related note: Asked adobe for Spark, got it, but it's not "Spark with Premium Features", should that be free too?

 

Should we use the user sync tool, or Enterprise ID federated with GSuite/O365? With Enterprise ID looks like I have to import all the users.

Posted

Yes. You really need to be importing every night to keep up with changes. You really want it automated,

The SSO is more of a one time setup. Until certificates expire. A certificate is also required for the sync tool.

This is how I did it.

 

https://broadsystemadmin.wordpress.com/2018/12/10/adobe-user-sync/

 

The worst part was the Certificate creation using openssl.

https://helpx.adobe.com/marketing-cloud-core/kb/adobe-io-authentication-step-by-step.html

 

 

 

Each environment is different however so test test test.

  • Thanks 1
Posted

thanks

 

It's weird they have login with google, but won't just allow everyone/everyone in a group to login/assign licences.

Posted
Thanks, did mean Federated ID, not Enterprise ID. Let's install a 3rd AD sync client! At least it's not wanting to sync passwords too
Posted
At least it's not wanting to sync passwords too

Once thing I wish the User Sync Tool would sync is DoBs since users are prompted to enter this when they first login with their federated ID.

 

That said, I found out this week some year 7s were unable to use Photoshop because they were born in 2007 rather than 2006 (like the rest of the class). The only way to avoid the "Access Denied" screen seems to be to lie about when they were born.

Posted
Wait, what? I thought the whole point of federated IDs was that you as an enterprise were confirming that people under the age of 13 had permission - it even says something about people under 13 having to be federated IDs on their site!
Posted (edited)
I thought the whole point of federated IDs was that you as an enterprise were confirming that people under the age of 13 had permission - it even says something about people under 13 having to be federated IDs on their site!

That's exactly what I thought too! I might query this with Adobe since it's extremely annoying.

 

https://helpx.adobe.com/enterprise/using/sdl-deployment-guide.html

 

Enterprise or Federated IDs are owned by the organization or school and all data is legally owned by the organization. You must use Enterprise or Federated IDs if your students are under 13 years old or above, for example K-12 schools. You can also use these IDs if you want to exercise tighter control on who can access the apps. To use Enterprise or Federated IDs, if you haven’t already, you’ll need to set up identity.

 

Adobe IDs are owned by the users and any data associated with the Adobe ID is legally owned by the users. Users need to be 13 or older to create Adobe IDs. IT admins don’t have any way to monitor or control data and content associated with an Adobe ID account. You can use Adobe IDs if your users are above 13 years of age and you do not want to monitor or control data access.

 

A couple of other annoyances are the confirmation prompt that appears if you leave an app open for 90 minutes (which also steals focus from whatever other app you are in) and the fact that admins can't customise the initial sign-in dialog box e.g. disable (or deemphasize) all sign in options other than the Google button.

 

nTUveZ.png

 

baUmgx.png

Edited by Arthur
Posted

Definitely look into the Chest agreement.

Have just set up the sync tool with federated IDs using Azure for our college ready to roll out 2019 apps during the summer reimaging works. Was a bit daunting at first but lots of reading and a couple of questions to Adobe support (who were surprisingly helpful) and it's all done.

My issue now is that any apps you package install the Creative Cloud desktop app which auto logs in at boot time which is really slowing down older machines which just have Acrobat DC installed....

Posted
My issue now is that any apps you package install the Creative Cloud desktop app which auto logs in at boot time which is really slowing down older machines which just have Acrobat DC installed....

Deleting the autorun entry should fix that issue. That's what I do with PSADT during deployment, but you could use GPP to do the same thing.

 

Remove-RegistryKey -Key "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run" -Name 'AdobeAAMUpdater-1.0' -ContinueOnError $True
Remove-RegistryKey -Key "[color="#FF0000"]HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Run[/color]" -Name '[color="#FF0000"]Adobe Creative Cloud[/color]' -ContinueOnError $True

Remove-File -Path "$envCommonDesktop\Adobe Creative Cloud.lnk"

  • Thanks 1
Posted
We have 1500 students but only 200 SDL on 200 pcs and that is fine. As when all the 200 devices are logged in you can’t run it any more

 

If I've read that right, then the SDL is smart concurrent licensing? e.g. you could install on 500 PC's so that it was 'available' but you'd only have 200 users at any one time able to use?

Posted
Under the chest scheme its based on your staff FTE. As ling as you don't go over that figure for the home use rights. SDL should cover students and staff on organisation owned devices.
Posted

New SDL features...

 

Shared Device Licensing | What's new

 

  • Deploy licenses to multiple labs
  • Delegate administrative tasks to other admins
  • Recover unused licenses

How to upgrade your shared device licenses

To use the latest features of Shared Device Licensing on end-user machines, you can either choose to:

 

 

Shared Device Licensing | Deployment guide

 

Create product profiles

If you plan to deploy shared device licenses in multiple labs to your institution, you can map each lab to a different product profile on the Admin Console.

 

For example, you can create a product profile for labs to be unrestricted, so that anyone can use Adobe apps, even users without a school account. Additionally, you can create product profiles for other labs where access to the installed applications needs to be restricted to users with a school account. Also, you can restrict access to the applications installed in these labs based on the access policies defined on the corresponding product profiles.

 

For details, see how to create and manage product profiles.

Posted (edited)
Wait, what? I thought the whole point of federated IDs was that you as an enterprise were confirming that people under the age of 13 had permission - it even says something about people under 13 having to be federated IDs on their site!

I think I have found the cause...

 

KALFGg.png

 

Our User Access Policy wasn't set to "Enterprise/Federated ID User Only".

 

sd4zWz.png

 

Edit. With "Enterprise/Federated ID User Only" or "Organization User Only" I now see the following message when trying to sign into an Adobe CC 2019 app with my federated ID. :(

 

Edit 2. After talking with Adobe, the error message is displayed because I clicked the Google sign in button rather than the "Sign in with an Enterprise ID" link. :doh:

 

tnjzL5.png

 

thanks for that Arthur, works great :-)

Excellent! :)

Edited by Arthur
  • 2 weeks later...
Posted

I've just had a quote for "Creative Cloud for enterprise All Apps"

 

A/

VIPE Creative Cloud for enterprise All Apps ALL Multiple Platforms EU English Enterprise Licensing Subscription New Monthly K-12 SCHOOL SITE LICENSE (500+) - Named (Minimum order 500)

 

@£4.16 x 500 = £2,080

 

 

&

 

B/

VIPE Creative Cloud for enterprise All Apps ALL Multiple Platforms EU English Enterprise Licensing Subscription New Monthly Shared Device Education License Lab and Classroom - Device

 

@£165.71 x 100 = £16,571

 

 

 

This is for a new build school which will only have 120 students in year 7 initially - but over the course of 5 years will rise to 900 students as each new year of 180 fills the school.

 

 

My forecast for the number of computers on site year on year is around:

 

Year 1 : 300

Year 2 : 340

Year 3 : 380

Year 4 : 430

Year 5 : 480

 

 

Just trying to get my head around the pricing!

 

 

In year 1 are my options either

A/ @ £2,080 or B/ @ £49,713

 

And in year 5

A/ @ £3,744 or B/ @ £79,540.80

 

 

I think I must be reading the quote wrong :confused:

Posted (edited)

You know what's weird - I signed up for "Adobe Incentive Plan (VIP)" 25 x Shared Device Licenses, 12 months @ £34 each last year. Just sent in my request for renewal pricing, so we'll see what it comes out at for me.

 

EDIT: Had the pricing back already... Still £34 per device.

Edited by localzuk
Posted

I think I must be reading the quote wrong :confused:

 

Not really, they reduce the single user school price a lot recently. And the lab price assumes you're just putting it in 1 room, not every computer in the school

 

1:40 ratio, so 1 in 40 are using it at once, everyone has 1 lesson a week, or 1 in 5 pupils are doing that level of work, and use it 8 times a week, seems about right. Min 500 users is what's killing me though, totally do it without that.

  • 2 weeks later...
Posted
We have 1500 students but only 200 SDL on 200 pcs and that is fine. As when all the 200 devices are logged in you can’t run it any more

 

I assume you are therefore using 200 x generic logins for SDL's?

  • 1 month later...
Posted

Has anyone done this, we've currently got device licenses what is the difference?

 

120 user licenses is that just we can only use it with 120 logins/users?

 

A lot of the adobe stuff is convoluted

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...