On 8/7/09, aki <
aki275@googlemail.com> wrote:
> Hi @Wes :-) . There are many gurus on the who will add more info but let me
> share what I know about Microsoft ( the last time I used one): For pricing :
>
http://chekelea.com/index.php?_a=viewCat&catId=9 . HTHs. ( corrections
> welcome )
>
>
> *Product *
> *Type*
> *
> Software Description*
>
> Standard Server 2003 R2
> *OEM
> 32-Bit OS, 1-4CPU, upto 4GB RAM, *A/D, *ICF, *RDA, *TS, *NLB, *VPN, *IAS,
> *NB, *ICS, *IPV6, *EFS, *FAX, * SFM, *IIS, *WMS, 5 CLT
> Small Business Server 2003 R2
> *OEM
> Includes all above, 1-2CPU, *SPS, *ES, *SUS,
> Small Business Server 2003 R2 Pre
> *OEM
> Includes all above, 1-2CPU, *SPS, *ES, *SUS, *SQL, *ISA2004, FP2003
> Standard Server 2008
> *OEM
> more details available
> *A/D : Active Directory
> *ICF : Internet Connection Firewall
> *RDA : Remote Desktop Administration
> *TS : Terminal Server
> *NLB : Network Load Balancing
> *VPN : Virtual Private Network Support
> *IAS : Internet Authentication Service
> *NB : Network Bridge
> *ICS : Internet Connection Sharing
> *IPV6 : Internet Protocol Version 6
> *EFS : Encryption File System
> *FAX : Fax Service
> *SFS : Services For Macintosh
> *IIS : Internet Informations Services
> *WMS : Windows Media Services
> *SPS : Share Point Services
> * ES : Exchange Server
> *SUS : Server Update Services
> *SQL : SQL server 2005 workgroup edition
> *ISA 2004: Internet and Security Acceleration Server
> * FP 2003 : FrontPage 2003
>
>
> License Schemes :
>
> Per User CAL
>
> With the Per User CAL model, a separate CAL is required for each unique user
> who accesses a server. If a user uses multiple computers, the user can
> access the server from each computer using only a single CAL. However, if a
> different user logs on to one of the computers, that user will need a
> separate Per User CAL to access the server.
>
> A typical example of the Per User CAL might be for a company that has two
> Exchange Servers used by 200 employees on 220 computers. This would require
> two server licenses (to install the product on the servers) and 200 Per User
> CALs. Because a CAL is assigned to each user, the number of computers
> accessing the servers is unimportant.
> Per Device CAL
>
> With the Per Device CAL model, a separate CAL is required for each unique
> device that accesses a server. If more than one person uses a specific
> computer, one CAL will allow all of them to access the server from that
> computer. However, if one of these users also uses another computer to
> access the server, the additional computer will need a Per Device CAL as
> well.
>
> A typical example of the Per Device CAL might be for a company that has two
> Exchange Servers used by 200 employees on 150 computers. This would require
> two server licenses (to install the product on the servers) and 150 Per
> Device CALs. Because a CAL is assigned to each device, the number of users
> accessing the servers is unimportant.
> Per Server CAL
>
> With the Per Server CAL model, a separate CAL is required for each unique
> device that accesses a server simultaneously. During setup, the server
> administrator enters the quantity of CALs purchased for the specific server.
> If this quantity were set to 30, only 30 computers would be allowed to
> connect to that server simultaneously. However, if that server served a pool
> of 100 computers, all the computers would have server access as long as no
> more than 30 were connected at the same time. After a computer disconnected
> from the server, a CAL would be freed so that another computer could connect
> to the server. If multiple servers are used to load balance, separate CALs
> are required for each server. For example, if you were using two exchange
> servers and purchased 200 Per Server CALs, you would likely assign 100 CALs
> to each server.
>
> *Per Seat Licensing* , *Per Server Licensing , *Per Processor Licensing, Per
> Mailbox Licensing
>