![]() ![]() You might recall from last month that basically all you need to do to stay on the side of the angels (or at least on the side of Microsoft's lawyers) is to buy a $40 Client Access License (CAL) for every machine that accesses your domain's servers. Terminal Server's licensing is a bit more complex than file and print services licensing. They wonder how many and what kind of licenses they need to keep from running afoul of Microsoft's software licensing policies. The subject of setting up a home network clearly intrigues people, but they invariably wonder how much a setup such as the one I've described costs-especially for the software. When speaking to groups about Terminal Server, I often tell the previous story or one like it. One of these days, I'll get around to setting up a CE-based machine with a wireless modem then, I'll be able to work in the backyard. The 533MHz Digital Alpha chip on one of my servers makes a superlative engine for Terminal Server if I can ever get rid of the network cables, it will be perfect. If cable modems ever make it out here to the hinterland, my terminal server will be an excellent Internet sharing device. Dumb terminals start up quickly because they have no OS to load. Using PCs takes too much space and presents too many maintenance hassles. I'd like to put several dumb terminals around the house to let me conveniently write articles, surf the Web, or check my email. Terminal Server is a great product, at least for my purposes. ![]() ![]() This month, I look into another licensing morass-this time for NT Server 4.0, Terminal Server Edition. Last month, I tried to make sense of Windows NT 4.0 file and print services licensing. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |