Licensing for Great Plains and RDS
Hi -
I'm presently working on a project to help our group implement Great Plains accounting software for our finance team. We're having some issue with the correct licensing required for operating the Great Plains software using RDS for the accounting team.
If you had to start from scratch - no licensing purchased or MSFT server infrastructure - and built an environment with the end result of allowing 15 Great Plains users that were sharing 10 desktops among the 15 users how would you construct the environment.
I know this is a broad ranging question but the licensing for Office, Server 2012, SQL Server, SQL Server CAL, Great Plains Users, RDS Client CALS (user/device), Server CALs (user/device) gets to be quite complicated and I'm having a hard time assessing what of our existing infrastructure needs to be changed to be compliant.
The Requirements for End Users Would Be:
Great Plains Access
RDS Server Access
Domain Access
Office Access
Desktop Access (OEM PRO OS included)
Clients and Users:
15 Users
10 Desktops
Infrastructure Needed (that I know of):
MSFT Server (DC, etc etc)
SQL Server (Great Plains)
MSFT Server (RDS)
I know some of the more complex items revolve around how Great Plains is licensed per user and what relationship that interaction would require for SQL Server licensing CALs. As they'll be accessing office via the Remote Desktops and locally on the desktops, how will this affect Office licensing. RDS CALs in my estimate would make sense to license by device as we're only running 10 desktops with 15 users sharing those machines. Is there anything else I'm overlooking?
I'm presently working on a project to help our group implement Great Plains accounting software for our finance team. We're having some issue with the correct licensing required for operating the Great Plains software using RDS for the accounting team.
If you had to start from scratch - no licensing purchased or MSFT server infrastructure - and built an environment with the end result of allowing 15 Great Plains users that were sharing 10 desktops among the 15 users how would you construct the environment.
I know this is a broad ranging question but the licensing for Office, Server 2012, SQL Server, SQL Server CAL, Great Plains Users, RDS Client CALS (user/device), Server CALs (user/device) gets to be quite complicated and I'm having a hard time assessing what of our existing infrastructure needs to be changed to be compliant.
The Requirements for End Users Would Be:
Great Plains Access
RDS Server Access
Domain Access
Office Access
Desktop Access (OEM PRO OS included)
Clients and Users:
15 Users
10 Desktops
Infrastructure Needed (that I know of):
MSFT Server (DC, etc etc)
SQL Server (Great Plains)
MSFT Server (RDS)
I know some of the more complex items revolve around how Great Plains is licensed per user and what relationship that interaction would require for SQL Server licensing CALs. As they'll be accessing office via the Remote Desktops and locally on the desktops, how will this affect Office licensing. RDS CALs in my estimate would make sense to license by device as we're only running 10 desktops with 15 users sharing those machines. Is there anything else I'm overlooking?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thank you for your help!
ASKER
Each of the servers require their own CAL as well? To connect to the domain even though they have a server OS license?
SQL Server CALS can be purchased per user and per device?
For some reason I thought, if you had a full copy of the software for the desktops - anyone using RDS from that desktop -would be allowed to access the RDS version of the software as well?
Thanks for your help.