The best source of usage rights are defined in the Sitecore MVP Program Agreement:
Sitecore hereby grants MVP a non-exclusive, non-transferable,
non-assignable, non-sublicensable, revocable, limited license to use
the Pre-Release Software and Released Software, in compliance with all
applicable laws, in object code form only, solely for evaluation,
Open the license file (license.xml) and search for: '<Object Id="SiteCore.EditorUser"', inside this element you should find a <name>SiteCore.EditorUser</name><count>3</count>.
The count should be the number of allowed users.
I think the purpose section only shows for client licenses and not development licenses. It appears to be ...
The best answer is "ask your Sitecore Sales rep". With that said, I did ask the sales team while at Sitecore Symposium and they said it wouldn't require any additional licences outside of what Sitecore 8 xDB support required.
Again, I would ask your sales rep as they may give you a different answer as it will very by each customer.
Since you mentioned upgrading, the way the coveolicense.xml is generated is a bit different in the newer Coveo/Sitecore versions. The new versions authenticate with the cloud in order to get your org and then write both the Coveolicense.xml in the data folder along with Coveo\ConfigurationEncryptionKeys\IndexingEncryptionKeys file.
The newer version no ...
Yes. You can only run as many instances of Sitecore as your license permits. What that is exactly, differs from case to case.
Instance means "Application" really. As in one IIS Application / AppPool.
If you need licenses for QA, Test, Dev and so on - these need to be purchased separately. Usually these go at a slightly lower rate (Dev ones, at least) - but ...
The license required for using xConnect is called Sitecore.xDB.Base.
If you have access to a Sitecore instance using that license, open the Launchpad, go to Control Panel and open Installed Licenses. You should see this license in the list.
Or you can just open the license.xml and look for the part that looks like this:
You mention that you've got a partner license to develop the application. I believe from a legal standpoint the partner can use the partner license for development, but when client can access (for instance to test) the client's license should be used.
Obviously if the partner is the client you would use the same partner license - just be mindful that you ...
If you are a partner, you can find details about the partner license outlined on SPN here:
The partner license statement on SPN qualifies your scenario with a usage clause. Essentially, are they 'internal developmen/test' environments or is it being used by the customer/client.
Always ask this question to your Sitecore Sales rep
If you are working at a customer, your sales rep is the only person who can definitively look at your license agreement and validate if it covers the scenario you are attempting. Nobody on this site can definitively answer license questions but them. All that can be provided is a guess at some 'normal' ...
Sitecore licensing is a separate cost from Azure usage costs. At its most basic, one bill pays Sitecore and one bill pays Microsoft.
Consumption-based licensing (also known as subscription licensing) is just another model for buying your license, but there are many different possible costs that could be involved here. For example, you might license only the ...
Maybe. Whatever I suggest here, you are going to have to verify with your Sitecore Sales Representative.
If the DR environment is "cold", then I have experienced Sitecore will allow this without extra license purchase. "Cold" meaning, the DR environment spins up and takes over, when disaster strikes.
Reasoning being, you actually do not "overuse" your ...
You don't need a JSS license to use the Sitecore.Services.GraphQL package, which is essentially the "core" part of using GraphQL with Sitecore. So you are free to create your own schemas, extenders, etc... or use the built-in options.
As I recall, a client from a while back wanted to have more content authors than they wanted to pay for content authoring licenses. (We're talking like 200+ authors). So, they contracted the company I was working for to bulid a completely custom authoring app that allowed this to happen without having to login as Sitecore users.
So, as it stands to reason, ...
You can use a FTPS or Web Deploy client to connect directly to the filesystem on the deployed App Service instance. Open up your .publishsettings file with a text editor, and you can see the endpoints to use and the username/passwords.
Ensure you use an FTP client that supports explicit TLS encryption (like WinSCP).
I'll preface this with stating I am in no ways a lawyer nor an expert in Sitecore licensing, but I believe from my experience the answer to the question (as stated) is "No".
Based on a license supporting X CM and Y CD servers, typically you should be able to install Sitecore between X and X+Y times. Also, your installations may not equal your number of ...
Just to add onto what @MarkCassidy said, if you have a Partner license for development that is separate from your client's license, the limits imposed by the clients license do not prohibit the developer from installing as many development instances as are necessary up to the limit imposed by their Partner license. In this case, a "development instance" is ...
Here's another way to check if your license does have the XDB enabled or not.
Steps are login to your content editor and then click on the RED top left side hamburger menu as shown in below image.
Then click on license
on opening model window scroll down all the way below where you will see entry named like sitecore.xdb.base and date. as show below in ...
It is actually as straight-forward as you might have guessed: all you need to do is open up your license file and search for the text Sitecore.xDB.Base (case-insensitive). If you get a hit, then your license has an xDB Base key.
The path to your license file is set incorrectly. The default value of the license file setting in config is:
<setting name="LicenseFile" value="$(dataFolder)/license.xml" />
If you have not change this, then most likely the issue is the dataFolder variable is not set correctly. Use a patch config set to update it to match the folder path your ...
This couldn’t the final answer to your queries but some analysis from my end, worth reading :)
Update in License File:
Whenever Sitecore official module is installed into an instance, below changes are included/appended in license file. (/data/license.xml)
Name,Expiration,count,version & license agreement are appended under <signature&...
So the KB article hasn't been updated in a while and isn't correct for the 9.x series. The keys you require are as follows:
There is currently no license check for the 9.x series engine functionality just for ...
I disabled the Coveo config files in the Coveo folder in App_Config\Includes, by appending .example to the end of each of them. I restarted the website and was able to access the content editor just fine.
I may have been able to download and install the Coveo Sitecore package, but I have not tried that. Will update this if I do.
For me looks like you didn't register on Sitecore Developer Trial Program.
After you register on Sitecore Developer Trial Program, your request would be processed by Sitecore Developer Trial Team. For me it takes one week to receive the trial license.
You will receive next email where it explain the steps you need to follow, and the license.
You should be able to download the packages from the site https://dev.sitecore.net when you are logged in.
Alternative to download the packages:
Another trick is, you can use the Sitecore Instance Manager (SIM 1.5)
Install it with your ...