Licensing query...
-
@Joel said in Licensing query...:
@Breffni-Potter It's a valid point and one we explored but the database is ridiculous in size and we need a beast of a box for it to process all the calculations. In testing we played around with different options but found a server with enough processing power, ram and cores worked a treat.
RE: Office. We have Office 365 so I was just planning on installing using those licenses.
O365 works now. I published a licensing guide for it like a week ago.
https://mangolassi.it/topic/10077/installing-ms-office-pro-plus-from-office-365-on-windows-rds
-
@hobbit666 said in Licensing query...:
@Joel said in Licensing query...:
RE: Office. We have Office 365 so I was just planning on installing using those licenses.
You will need to check what you got as only a few plans allow RDS access, can't remember off top of my head.
But you will still need RDS Cals and Server CalsYes, normal CALs are already needed because there is a Windows Server in the mix, and RDS for the remote access. You will likely want to share apps only, not the full desktop.
-
@scottalanmiller
No, without RDS zero can log in that are not admins doing admin tasks. You can have a single user use it as a desktop. The two limit is license restricted to administration. Any shared desktop use whatsoever requires RDS licenses.That's what I meant 2 Admins by default
O365 works now. I published a licensing guide for it like a week ago.
https://mangolassi.it/topic/10077/installing-ms-office-pro-plus-from-office-365-on-windows-rdsWill need to read that and catch up, might help us here
-
@hobbit666 guys im trying to use the Office 2013 deployment tool as per the link above but cant get Office suite installed. Can someone help with my configuration.xml?
note: i have created a share \database01\share and have put my Office2013 (64bit).exe (downloaded from office365) into this share and named the file 'Setup64'
see code from my config file below:
<Configuration>
<!-- <Add SourcePath="\data01\Share\Setup64.exe" OfficeClientEdition="64" >
<Product ID="O365ProPlusRetail">
<Language ID="en-us" />
</Product>
<Product ID="VisioProRetail">
<Language ID="en-us" />
</Product>
</Add> --><!-- <Updates Enabled="TRUE" UpdatePath="\data01\share" /> -->
<!-- <Display Level="None" AcceptEULA="TRUE" /> -->
<!-- <Logging Path="%temp%" /> -->
<!-- <Property Name="AUTOACTIVATE" Value="1" /> -->
</Configuration>
I then run: \data01\share\setup64 /configure \data01\share\configuration.xml - and nothing happens when i click run!
anyideas?
-
Hi Guys
Following my convo above about the terminal/rds server setup. I now have this working well so thankyou for helping with that.
As a recap, I have a virtual DC (DC01) to manage our users/groups and a virtual App server (APP01) running with Excel installed which is published as a remote app. Our end users use Pertino to access and run the remote Excel and are authenticated via the DC. I think this works well and keeps the setup more 'internal' and not published over the web which is better for security.
I am currently using the 100 day free licenses for RDS, however my question is when that runs out, should I purchase Device CALS or User CALS?
We have so far 15 users logging in and they pretty much use their own laptops to access the APP01. -
Device CALS are cheaper
Think last quote I had (before all the price hike due to brexit)£100 User cal, £77 device cal
-
@hobbit666 stupid question (my licensing knowledge is of a newb), should i choose device CAL, would i just need to license the 1 app01 server for 15users to access it? As opposed to licensing 15user CALs to use the app01 server?
-
If I remember your database server is a RDS server too?
In that case you are going to need Server CAL's (Device or User) and RDS CAL's.Which one to choose depends on future plans. If at the moment you have 1 : 1 ration of computers and users then I would go cheaper device CALs BUT! if you think people will start accessing from different devices like tablets/laptops/phones etc then User CAL's make more sense.
-
Device call are cheaper but I thought they were assigned to specific devices.
Where as user CALS were transferable...
Am I wrong?
-
@DustinB3403 said in Licensing query...:
Device call are cheaper but I thought they were assigned to specific devices.
Where as user CALS were transferable...
Am I wrong?
Device Cal's are transferable also every 90 days
-
Only if the same devices will realisticly be used would I consider device CALs.
User CALs are a lot more flexible.
Device CALs also make sense for shift workers. You only have 30 devices bit they are shared by 90 people.
-
@hobbit666 said in Licensing query...:
If I remember your database server is a RDS server too?
In that case you are going to need Server CAL's (Device or User) and RDS CAL's.Which one to choose depends on future plans. If at the moment you have 1 : 1 ration of computers and users then I would go cheaper device CALs BUT! if you think people will start accessing from different devices like tablets/laptops/phones etc then User CAL's make more sense.
Yes, the database is a RDS server so we will indeed need RDS Cals. I assume also this is 1x RDS CAL per user?
User cals probably makes sense as some have two laptops and an office computer. -
@Dashrender said in Licensing query...:
Only if the same devices will realisticly be used would I consider device CALs.
User CALs are a lot more flexible.
Device CALs also make sense for shift workers. You only have 30 devices bit they are shared by 90 people.
If all users are logging into the same RDS server than do I simply need RDS CALs (for each user) and a single Device CALS for the server?
-
@Joel said in Licensing query...:
@Dashrender said in Licensing query...:
Only if the same devices will realisticly be used would I consider device CALs.
User CALs are a lot more flexible.
Device CALs also make sense for shift workers. You only have 30 devices bit they are shared by 90 people.
If all users are logging into the same RDS server than do I simply need RDS CALs (for each user) and a single Device CALS for the server?
There are two types of CALs. Windows server CALs, which come in two flavors (user or device). And RDS CALs which also has user or device.
In your situation you would need to buy one of each kind per user.
-
@Joel said in Licensing query...:
@Dashrender said in Licensing query...:
Only if the same devices will realisticly be used would I consider device CALs.
User CALs are a lot more flexible.
Device CALs also make sense for shift workers. You only have 30 devices bit they are shared by 90 people.
If all users are logging into the same RDS server than do I simply need RDS CALs (for each user) and a single Device CALS for the server?
Servers don't use device CALs.
-
@Joel said in Licensing query...:
@Dashrender said in Licensing query...:
Only if the same devices will realisticly be used would I consider device CALs.
User CALs are a lot more flexible.
Device CALs also make sense for shift workers. You only have 30 devices bit they are shared by 90 people.
If all users are logging into the same RDS server than do I simply need RDS CALs (for each user) and a single Device CALS for the server?
It's a one time either-or deciscion. Either User CALs or Device CALs. Call centers will probably use Dev CALs (Many users, few devices) while most other companies with more devices than users will use User CALs. You can't mix them whatsoever.
You not only need CALs for the servers (-> operating system), but also for many MS products. For example MS Project Server or SharePoint. You need to buy these CALs too.
-
You may want to talk to someone at a reseller like Misco or Softcat that's a specialist as Microsoft licensing can be tricky.