Licensing Options for 2 Servers and 20 Workstations
Scenerio:
2 Servers and 20 Workstations.
I've only setup/configured single server networks in the past.
This job will have two servers splitting the roles of DC, AD, DHCP, DNS, Exchange, SQL, FS, etc...
The way I understand it:
I will install Windows Server 2003 on each box.
(these come with 5 CAL's each)
I will install Exchange on 1 box (This also comes with 5 CAL's ?)
I will have 20 workstations.
Do I just buy an additional 20 CAL's and install them on the primary server?
Will this allow all workstations to access BOTH servers?
Do I have to buy Exchange CAL's as well?
Please suggest to me how the licenses should be purchased.
Thanks,
Brent
2 Servers and 20 Workstations.
I've only setup/configured single server networks in the past.
This job will have two servers splitting the roles of DC, AD, DHCP, DNS, Exchange, SQL, FS, etc...
The way I understand it:
I will install Windows Server 2003 on each box.
(these come with 5 CAL's each)
I will install Exchange on 1 box (This also comes with 5 CAL's ?)
I will have 20 workstations.
Do I just buy an additional 20 CAL's and install them on the primary server?
Will this allow all workstations to access BOTH servers?
Do I have to buy Exchange CAL's as well?
Please suggest to me how the licenses should be purchased.
Thanks,
Brent
What are you saying Red, havnt you had your morning coffee yet?
the way i understand this is that both servers are on the same domain and both came with 5 cals (10 cals in total) and you wish to connect 20 clients, therefore you will only need to purchase 10 cals and install them all on the server that is going to have the licencing service.
As for exchange cals
http://www.microsoft.com/resources/sam/lic_cal_exchange_server.mspx
the way i understand this is that both servers are on the same domain and both came with 5 cals (10 cals in total) and you wish to connect 20 clients, therefore you will only need to purchase 10 cals and install them all on the server that is going to have the licencing service.
As for exchange cals
http://www.microsoft.com/resources/sam/lic_cal_exchange_server.mspx
I thought that was SBS only - although I have been known to be horribly horribly wrong ;)
This is the main reason you get so many opinions on it!
This is the main reason you get so many opinions on it!
Ok now Im not sure...........
all my networks that i can think of have been with an SBS running FSMO
we need Sembee or maybe jay to clarify ;)
all my networks that i can think of have been with an SBS running FSMO
we need Sembee or maybe jay to clarify ;)
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Sembee,
Just to clarify
"then you don't install CALs anywhere, they are done on an honour system."
That only relates to the exchange cals the user cals still must be licenced.
Thats my understanding.
Just to clarify
"then you don't install CALs anywhere, they are done on an honour system."
That only relates to the exchange cals the user cals still must be licenced.
Thats my understanding.
sorry "Licenced" should have been "loaded"
There is nothing to load.
Only SBS and Terminal Services come with items to load - as they are hard enforced. The Enterprise products (ie full product of Exchange, Windows etc) are not hard enforced. The only thing that enforces them is the awful license logging service, which causes more problems than it is worth and should be globally disabled using group policy.
Simon.
Only SBS and Terminal Services come with items to load - as they are hard enforced. The Enterprise products (ie full product of Exchange, Windows etc) are not hard enforced. The only thing that enforces them is the awful license logging service, which causes more problems than it is worth and should be globally disabled using group policy.
Simon.
ASKER
Hey guys, thanks for the discussion back and forth among yourselves... it doesn't make me feel so bad that I didn't know the answer.... lol
To clarify at this point:
Servers. I will be purchasing 2 Dell Servers with Server 2003 Std R2 preinstalled.
Each state they come with 5 CALs. So I should purchase 10 more CAL's (Total now 20: 5+5+10). Turn off licensing globally and use the Honor System
Exchange: I will be purchasing Exchange 2003 Std Seperately and installing myself on one of the boxes.
I will have to purchase additional Exchange CAL's (Either 20 or 15 if it comes with 5). This will have to be loaded into Exchange and Activated.
Terminal Services: Server 2003 has (i think) 2 Sessions as freebies, If I need more, I will have to buy additional TS CAL's and load them as needed (including configuring the TS Licensing Server)
Am I on track?
To clarify at this point:
Servers. I will be purchasing 2 Dell Servers with Server 2003 Std R2 preinstalled.
Each state they come with 5 CALs. So I should purchase 10 more CAL's (Total now 20: 5+5+10). Turn off licensing globally and use the Honor System
Exchange: I will be purchasing Exchange 2003 Std Seperately and installing myself on one of the boxes.
I will have to purchase additional Exchange CAL's (Either 20 or 15 if it comes with 5). This will have to be loaded into Exchange and Activated.
Terminal Services: Server 2003 has (i think) 2 Sessions as freebies, If I need more, I will have to buy additional TS CAL's and load them as needed (including configuring the TS Licensing Server)
Am I on track?
There is nothing to be loaded in to Exchange. You simply buy the application and the CALs. You don't get any kind of license key.
For Windows - as you said.
For terminal services, you get two connections free as part of remote desktop. If you want to have more connections then you need to install Terminal Services from Add/Remove Programs, Windows Components and have a Terminal Server licensing server somewhere.
I don't recommend that is installed on either Exchange or a domain controller, for obvious security reasons.
Simon.
For Windows - as you said.
For terminal services, you get two connections free as part of remote desktop. If you want to have more connections then you need to install Terminal Services from Add/Remove Programs, Windows Components and have a Terminal Server licensing server somewhere.
I don't recommend that is installed on either Exchange or a domain controller, for obvious security reasons.
Simon.
Ok now that we have resolved the licencing issue.
You didnt originally mention that you were going to run one of the servers as a term server. This being the case i would completly rethingk the setup. If you havnt yet bought the servers or software, then with only 20 workstations you would be a whole lot better of buying one server with SBS OEM + 20 cals (or 15 if you get sbs with 5 cals), and then the second server with 2003 enterprise, and install this one as a member server and run Term services on it.
The reasoning behind this is ..
1. Amount of users, SBS has a limitation of 75 and you only have 20 so plenty of room for growth.
2. Ease of managment, SBS comes with wizards for just about everything. This will save you a lot of greif if you do not have extensive knowledge of enterprise and excdhange.
3. Server roles. As you can read above, you should not have exchange on the DC, you should not have Exchange on the Termserver machine (this is very important), the termserver should not be a DC. That said you are one server short. Exchange can run on a DC and this is what SBS does very well.
4. Price, The cost of SBS is a lot cheaper than Server and exchange seperatley and SBS has more featurs added that will give you a better ROI. if you get SBS enterprise this will give you ISA wich will also be great.
and as sembee said (regardless of server or SBS) "license logging service, which causes more problems than it is worth and should be globally disabled using group policy"
You didnt originally mention that you were going to run one of the servers as a term server. This being the case i would completly rethingk the setup. If you havnt yet bought the servers or software, then with only 20 workstations you would be a whole lot better of buying one server with SBS OEM + 20 cals (or 15 if you get sbs with 5 cals), and then the second server with 2003 enterprise, and install this one as a member server and run Term services on it.
The reasoning behind this is ..
1. Amount of users, SBS has a limitation of 75 and you only have 20 so plenty of room for growth.
2. Ease of managment, SBS comes with wizards for just about everything. This will save you a lot of greif if you do not have extensive knowledge of enterprise and excdhange.
3. Server roles. As you can read above, you should not have exchange on the DC, you should not have Exchange on the Termserver machine (this is very important), the termserver should not be a DC. That said you are one server short. Exchange can run on a DC and this is what SBS does very well.
4. Price, The cost of SBS is a lot cheaper than Server and exchange seperatley and SBS has more featurs added that will give you a better ROI. if you get SBS enterprise this will give you ISA wich will also be great.
and as sembee said (regardless of server or SBS) "license logging service, which causes more problems than it is worth and should be globally disabled using group policy"
SBS has its own licensing application that has to be left running, because SBS is hard enforced. It can make things confusing.
I was surprised that SBS wasn't being mentioned...
Simon.
I was surprised that SBS wasn't being mentioned...
Simon.
ASKER
I've always setup my one server clients with SBS in the past.
Setting up two servers (client insists... who am I to argue) I was skittish about using SBS on one as I've read lots of places about incompatibilites and specifics on how to configure it.
Hmmmmm.... maybe rethinking this projects configuration now.
Setting up two servers (client insists... who am I to argue) I was skittish about using SBS on one as I've read lots of places about incompatibilites and specifics on how to configure it.
Hmmmmm.... maybe rethinking this projects configuration now.
On the SBS machine you can disable the licence logging service. Licencing will still be enforced but not monitored.
as long as you leave the terminal server machine as a member ser there will be no issue.
You can make the second server a DC but the SBS must remain as the fsmo server, and you CANNOT have two SBS machines on the same domain.
But other than that i have setup lots of SBS + Termserver networks, Both for production and for workshop testing and training (to see how bad a new tech can get it, and then how hard it is to fix ;)
You can make the second server a DC but the SBS must remain as the fsmo server, and you CANNOT have two SBS machines on the same domain.
But other than that i have setup lots of SBS + Termserver networks, Both for production and for workshop testing and training (to see how bad a new tech can get it, and then how hard it is to fix ;)
sorry forgot to add. I am not sugesting that you make the term server a DC. While itis possible it is not a good practice.
ASKER
I'm posting a seperate question asking for recommendations for dividing up the roles between the two server boxes.
Input from you guys on this one would be appreciated :)
https://www.experts-exchange.com/questions/22405238/Server-Roles-between-two-Servers-Recommendations.html
Brent
Input from you guys on this one would be appreciated :)
https://www.experts-exchange.com/questions/22405238/Server-Roles-between-two-Servers-Recommendations.html
Brent
i dont mind putting in the time. But a bit of a points split would have been nice
You will also need to buy Exchange cals (and I believe it comes with 5)
Also, when doing this, get 3 opinions, one of which should be from Microsoft, and the most expensive is going to be the correct one.
-red