I always thought that part of Adobes dominance in this market was to allow some piracy of their product because that's how teenagers learned how to use it.
Adobe then made their money from actual business users who MAKE money from the tools and therefor must have legit licenses. And those businesses use Adobe because their workforce learned it already, and it became the defacto-standard because of that.
Using Adobe’s IT tools to deploy Creative Cloud for teams
Let’s say you are rolling out 50 seats of Creative Cloud for teams in your office. You may be involved with the actual administration of sending out invites. This is done through the admin portion of the Creative Cloud site. From the Invite Multiple option you can either copy and paste user’s email addresses (ouch! carpal tunnel) or import a .txt or .csv file of the user’s email address. Then you can send them an invite and they’ll login with or create an Adobe ID.
Then they’ll download and install the Creative Cloud version of the Adobe Application Manager and begin downloading and installing the full offering of Adobe’s Creative Cloud applications and updates. All of them. All of the apps. All at once. All 50 of the users. What? This is in your Portland office? The only office that hasn’t had the network upgrade yet. Better turn off your mobile stat and hide.
Now that scenario of course could be avoided if you used your existing deployment infrastructure by pushing out packages of the apps rather than using your office’s internet connection for all 50 users. But how do you package up a set of apps that come from the cloud? Ah, you need a work-a-round, a hack. Well my friend, as a former IT admin I am all about the hack. Here’s how you do it: The bulk of the applications they are downloading from the Creative Cloud are the CS6 installers and to be frank, are not exactly what I’d call svelte in the MB/GB department. So you could download them yourself from our FTP site as the CS6 Master Collection and then use AAMEE 3.1, our CS6 packager, to package them out and distribute them.
But wait, AAMEE requires a volume serial number, right? Well remember we also have a Trial workflow in AAMEE 3.1. And the Trial workflow is really an unlicensed version of the CS6 app, just waiting for licensing via a serial number or an Adobe ID login associated with a subscription or Creative Cloud membership. Get it? So once it is packaged up you can distribute using your deployment infrastructure and then have them log in after you send the invites. This turns the unlicensed CS6 app into a Creative Cloud app. Magic. More like magic hack.
A few caveats about this plan/hack are:
1) apps such as the Edge tools, Muse and Lightroom aren’t part of CS6 so the end-users will have to download those apps on their own. The Edge tools and Muse are quite lightweight in size though.
2) the updates that you package with AAMEE 3.1 will not fully get the applications up to date. Why? Because the Creative Cloud have their own special feature updates that are not part of CS6. Therefore they can’t be seen in the Updates screen with the CS6-based AAMEE 3.1. You could execute the Remote Update Manager (RUM) once the end user has signed into the application with a valid Creative Cloud account. Then when you run RUM it will recognize the install as a Creative Cloud app and then pull that Creative Cloud-specific update down and install it.
They may end up losing a bit of business from working pros from this, but the name Adobe still has huuuuuuge name recognition value for millions of corporate and other customers.
Your proof of eligibility must be a document issued by the institution with your name, institution name, and current date.** Types of proof of enrollment include:
• School ID card
• Report card
• Tuition bill or statement
You computer does have to connect to the internet once a month to verify that your membership is still current, but that’s it. Once that check has happened you can disconnect and run all of your Creative Cloud apps OFF-line.
The real true inner-sanctum FOSS attitude about features users want is "You want feature X in package Y? Learn to code. Learn to code real good. Offer yourself as a dev on the package Y team. Code feature X yo'self. If the other more senior devs like it (and you) maybe it'll get picked for inclusion, in version = (current + 6.5)."
Legible. Application icons should be distinguishable from one another at small icon sizes, on file icons, and in the OS. Icons must be differentiable beyond color and should be legible for color blind persons via shape, letter-forms, tone, or other method.
Application icons should be distinguishable from one another at small icon sizes, on file icons, and in the OS. Icons must be differentiable beyond color and should be legible for color blind persons via shape, letter-forms, tone, or other method."
« Older In his retirement speech, Donald Kagan, eminent hi... | With the Terrafugia Transition... Newer »
This thread has been archived and is closed to new comments
Buy a Shirt