Do you remember the DCO licensing compared with external user licensing? And all frustrations and misconceptions there were involved? And that there was no device-license available? Yes, we have web services now, but if you want to license it, it's just way too expensive (in many cases) ...
Well, there is some good news. Microsoft listened .. and changed the licensing options. In fact, effective from September 1st 2010, Microsoft is introducing three lighter access license rights to help the customers more affordably extend their Dynamics ERP to more people within their organization (obviously not my words ;°) ).
What is changed?
The previous name "DCO" or "Dynamics Client for Office" was not really "self explaining". So they introduced a new (confusing) name: Microsoft Dynamics Light User. Don't be mistaken, this is not a user! No functionality! It's just the same as DCO, just rebranded. What can you do with this license? Well, look at NAV data or execute NAV business logic from outside of NAV... . And you need one for each named user.
Now, problem was: if 200 internal people had to click only one button on one machine once or twice a day (time clock, for example), you had to buy 200 of these babies.. . It could become really expensive.
Therefore, Microsoft also introduces two new Licensing Options:
With one remark: "not involving project / job codes". What they mean with that, I don't know (yet) I'll try to find out.
Competitive an convenient licensing for scenarios accessing the Dynamics Solution through a single purpose device (e.g. Bar code data capture, time clock, ..). Finally, I would say. Obviously, the price is more expensive then a light user, but it happens a lot that users share one machine ... so things could get very very interesting..
Furthermore, Microsoft introduces Volume Discounts in this matter. I'm not going to reveal any prices here (as they might differ country by country .. and I'm not sure I am allowed to), but see below the links to the price lists.
And that's not all. They also separate the SharePoint server licensing from the dynamics user access licensing, which is a good thing, in my opinion. It only made things more complicated. You want SharePoint: get SP licenses. You want to integrate with NAV? Get Light user or something else.. . Clear, no?
To finish, they completed a "revised" how-to-license-guide with a customer ready version to be able to frame a consistent message to all the customers... . too bad I didn't find this guide on partnersource (yet).
Here are the links to the price lists..
Well, all material is available at your PAM.
Implementing Light user with sharepoint is just: named user! everyone who is using sharepoint, should have a light user.
please, any idead about implementing light user license with sharepoint? any material will be useful if available. thanks in advance.
If I'm not mistaken, C/FRONT uses the license file to log into NAV .. and therefore it logs in with a normal user .. it's how the framework works.. .
To be honest, I wouldn't use C/FRONT but web services to cover what you need (and shoud be able to cover..).
is there any reason why web services can't be used in your scenerio?
Regarding third party application invoking NAV via the C/FRONT API, what's the less expensive licencing option beside the VERY pricey full blown NAV user when you reach 200+ users ...
It's about right .. but I would like to rephrase a little bit: "they are allowed to do anything (create & posting SO) from outside NAV ... like web, office, .. "
this is of course my understanding, without any guarantee .. ;°)
With NAV Light User License, the users cannot do anything in Classic Client & RTC, but they can do anything (create & posting SO) in web, office, sharepoint, or third party application. Am I correct ? Thanks.
thanks for your comment..
I already informed/asked Microsoft but no answer yet. I think they don't know themselves.. ;°)
Great one, Waldo! Couple of months ago I was looking for the best price model for a scenario I had at hand, and DCO just wasn't there. Now with these three things, it's exactly what the customer needs.
And about project/job codes... I would say they actually refer to dimensions. It's just that somebody in the marketing department doesn't know that.
It reminds me of a situation when on printed NAV marketing materials it said that NAV 5.0 contains something custom KPIs. A customer hang on to this, and we were chasing Microsoft people for months trying to find *ANYONE* who knew what this "feature" was. The solution was to take it away from the next brochure :)