Suffice it to say that in any big organization that licensing is complex enough to require a dedicated person to handle all license agreements (inventory). It also requires a special section of training in the MCSE tracks.
<br><br><div><span class="gmail_quote">On 5/16/07, <b class="gmail_sendername">Bradley Hook</b> <> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Last I checked, there are two CAL models used by MS: per-server and<br>per-seat. Per-server means you buy a set number of licenses for that<br>server, and that server will never permit more than that many<br>connections. This is really the only way to legally connect non-MS
<br>clients to a CAL restricted service. With per-seat, the server allows<br>unlimited connections from machines that each have their own individual<br>Microsoft CAL.<br><br>Note, though, that last I checked the MS software did not actually have
<br>any mechanism for verifying the per-seat licensing model. It was<br>primarily used in situations where the organization purchased<br>site-licenses that granted per-seat CALs for every machine they owned.<br>MS has been beefing up their licensing enforcement since then, so I
<br>wouldn't be surprised if they actually verify them now.<br><br>~Bradley<br><br>Jon Pruente wrote:<br>> On 5/16/07, RtX <> wrote:<br>>> Exchange Server comes with a client license for up to 5 clients only. This
<br>>> means that only 5 connections are available, any more would be refused. The<br>>> company (or owner) may choose to purchase more client licenses in 5 - 10 -<br>>> 25 license packs from MS for more connections.
<br>><br>> I've read about the MS license model before, and I've even helped a<br>> friend buy a server and a copy of Win2k3 for a Win only<br>> client/server/master program the payroll/accountants used. From my
<br>> understanding, you have to buy a copy of Windows, er, buy a license of<br>> Windows which also comes with a copy of the software you just<br>> licensed... Plus any additional client access licenses (CAL) you need
<br>> if you need more than the default for your copy of Windows. THEN you<br>> have to buy a client license to connect to each of the CALs you are<br>> dealing with, which also most likely means a desktop license for the
<br>> Windows running on the client, or is the client license a part of a<br>> desktop Windows license, and thus is the MS stink mentioned earlier in<br>> the thread?<br>><br>> I guess that's like saying only IBM reps can come change the paper in
<br>> your feed tray because you only licensed the right to print from it<br>> and not to self service it. If you do it yourself you're gonna owe<br>> them the money you would have payed to have them come out and do it
<br>> for you. Or something.<br>><br>> Jon.<br></blockquote></div><br>