Server 2016 / O365 licenses

[RoadRunner]

Hi,

Having a client that has maybe 40 E3 licenses for staff with computers and I was thinking of getting 90 K1 licenses for staff on the road with phones to get emails.
When integrating with server 2016 does that need a CAL for each user ?
I would think so as the users will be setup on the server even though they are not using local logons or server resources they will still show up in active directory and things like password sync will be used.
Would be nice if I don't need to get 90 Cals ;-)

EDIT: Just seen it's not K1 it's F1 now. After 2 hours on the phone it looks like 130 server Cals it is.

 

[freedomit]

Why not just create them in O365 and not sync them to the local AD? If your using AD Connect it’s a one way sync (on premise to cloud) anyway I think

 

[YeOldeStonecat]

If they're just remote O365 mailbox users, why invest in local user cals on the server for them?

 

[trevm999]

I don't see why you would need CALs for those users if they are not communicating with the server.

My understanding is that user CALs are not at tied to active directory user objects.

And for arguments sake, what if you went with device CALs? If their devices aren't communicating with the server then they don't need CALs.

 

[YeOldeStonecat]

I recall the wording "any user or device that accesses server software directly or indirectly...requires a CAL". The word "indirectly" leaves it a bit gray.

Although a device such as a workstation is not communicating with the server, the user account is using a server service...the Azure AD Sync...which is installed on the server to sync with the clients O365 tenant.

The hybrid of cloud service and on-prem being so new, not a lot of documentation out there I guess. I lean towards they need a CAL..but Trev may be right in that just an AD object doesn't need to be covered, since it's used for management purposes. Interested in what the outcome for this is. While I have a few deployments out there similar to this, those clients are non-profits so we cover the licensing above and beyond..being so cheap through TechSoup. I always have the client purchase way more than they'll possibly need.

 

[HCHTech]

My world doesn't intersect with clients that would need that many CALs, but at the 5-CAL pak price, that's a little bit north of $4,000. I would want to know for sure whether that expense was necessary.

 

[seedubya]

EDIT: Just seen it's not K1 it's F1 now. After 2 hours on the phone it looks like 130 server Cals it is.

Just wondering why they need to be listed in the on premises directory at all? Nice to have n'all but necessary?

 

[RoadRunner]

Once you have 130 users we want them all synced to the server with AD sync. Might stick the essentials role on the server as well.
I want all users and passwords in one place. Otherwise if someone needs a password change it's like hhhhmmmm is he O365 email only or on premise ?
Also if one of the email only users gets a computer at some stage he is good to go.
I was put through to some senior licensing guy at Ingram and he said nothing changed with the licensing. Every user on the server needs a CAL like it always was...... So my understanding is that if the user is synced to the server he needs a license. But really hard to figure out for sure.

We are talking $15K in licenses as we need Server/some RDP/User Cals.
Anyone any input on OEM vs VLK. Just checking on that as well and trying to figure out if VLK with software assurance only gives you an additional 2 years of upgrade rights. Would be a pain if in 3-5 years you have to fork out $15K again when you need a new server.
You kind of want to make the right decision with those numbers

 

[RoadRunner]

Another 3 hours later Microsoft China support tells me I don't need the license. That's after talking to Microsoft Tech support first as we are a Silver Cloud Partner as well and pay $2.5K a year for that. They told me for F1/K1 I have to call the other guys.......:
There’re three sign-in models for Office 365:
https://blogs.office.com/en-us/2014/05/13/choosing-a-sign-in-model-for-office-365/?eu=true
So use synchronized identity as you describes doesn’t require a Windows server cal. To use AD FS service ,however, does require a Windows server cal.

And Ingram Micro tells me these Chinese call centres don't know anything and according to this we need licenses:
https://technet.microsoft.com/en-us/library/exchange-online-service-description.aspx
16 Office 365 Business Essentials, Office 365 Business Premium, and Office 365 Enterprise F1 do not provide access rights for utilization with on-premises servers. To be compliant, customer must purchase or have previously purchased the appropriate CALs or upgrade to an Enterprise SKU that provides these access rights.

I think this is a very GREY zone and it depends how much time you want to waste on it and how many different answers you want. To be on the safe side you just pay or you might be covered but not for sure. This client got audited from Microsoft before. If they get done again and they tell them we need another $5K in licenses that we did not tell them about I guess it would have to come out of my pocket.

Microsoft licensing is great. I always feel like I'm the only one that ever asked those questions when you call them. Does everyone else either not license correctly or just over license, just in case.

 

[RoadRunner]

So it looks like everyone thinks as soon as you enable Essentials Role (which I wanted to do) every device has to be licensed no matter if mobile phone or not. If you don't enable the Essentials Role and the device never gets ANYTHING off the on site server you are good. This means they can't even connect to the office wifi as the server would do DHCP for those devices.
I'll stick to that. Won't enable essentials role and tell them the users with email only accounts can't connect to the local network.

Does anyone know if all the anytime connect/vpn stuff works without Essentials Role and no fancy gui for user accounts and stuff .
Still waiting for the client to sign off on the quote. Not a good time of the year to get anything done.