|
hassana -> RE: Help with choosing between PER-SEAT / PER-SERVER (19.May2006 12:30:12 PM)
|
Hi Helen, Check following websites ------------------------------- http://www.microsoft.com/resources/sam/lic_cal.mspx http://www.samspublishing.com/articles/article.asp?p=98829&seqNum=4 In per server mode, you are licensed for a certain number of concurrent connections to the server. If you have 50 licenses, 50 clients can connect to the server. Per server mode is the best choice when you have a small network consisting of only one domain (and one domain controller). It also works best for networks when only part of your client base is connected to the server at any one time. For example, if you run different shifts at your company, you need only a per server license that covers the number of users connected to the server at any one time (not your entire employee population). In per seat mode, you purchase a license for each network user on the network. Each of these users can connect to any and all the servers on the network. As far as large networks go, per seat mode is probably the best licensing strategy, especially if network resources are spread across a number of Windows Server 2003 servers. You must select your licensing mode during Windows Server 2003 installation. So, it is important to consider licensing in terms of network growth and usage. However, if you select to use the per server licensing and then determine that it would make more sense to change to per seat licensing, you have one opportunity to switch licensing modes. This switch is done using the Licensing snap-in. ------------------------------ We have one SBS 2003 Dell PowerEdge server and is running on Per Server mode. You can alway change to Per Seat later...but I don't think you can change from Per Seat to Per Server. Good Luck Hassan
|
|
|
|