Module 15: Implementing Network Clients
Windows NT Server Client Access Licenses |
- Client Access Licenses (CAL):
- Provides legal right for a computer to be used to access a
computer running Windows NT Server.
- Are separate from the desktop operating system software
used to connect to Microsoft server products. A CAL is required.
Licensing is based on number of client connections to
computers running Windows NT Server.
Situation: server with two shared folders.
- Single connection; user connects to one or both shared
folders from one client.
- Multiple connection; user connects from two clients as same
user to one or both shared folders.
Licensing Modes: Selecting Per Seat vs. Per
Server Licensing |
- Per Server Licensing:
- Good for
- small networks
- Internet attached servers
- CALs are assigned to a specific server.
- Number of CALs determines how many simultaneous connections
can be made to a server.
- What if there are too many?: If limit of connections
is reached, additional clients will not be able to connect. Windows NT Server displays an
error message on client and logs the error in the system log.
During installation of Windows NT Server, if Per Server is
selected, enter the number of CAL purchased for that server. Must be at least the number
of clients connected simultaneously to the server. Additional clients will not
be able to access.
Per Server mode may be the economical choice if clients
meet following conditions:
- Ordinarily connect to only one occasional-use or
special-purpose server.
- Do not all need to connect to server at the same time.
- Per Seat licensing:
- CAL is purchased for each client
- Here, the focus in on the Client can access network
resources on any computer running Windows NT Server in the network.
- No limit on number of connected users to a server.
Licensing Selection Guidelines:
- If network contains only one server, select the Per Server
option and specify the maximum number of connections of simultaneously connections. If a
server is added so Per Seat is more economical, Windows NT Server allows a one time
conversion from Per Server to Per Seat. The other way around is not possible.
Windows NT Server will need to be reinstalled to go
from Per Server or start again at Per Server
- Select Per Seat mode if there are multiple servers and the
total number of CALs across all servers to support the Per Server mode is equal or greater
than the number of clients.
You can use this little worksheet to decide between the
two licensing modes:
Option |
Result |
Per Server Option |
|
Number of Servers
|
A |
Number of simultaneous workstation connections to each server
|
B |
In line C, enter (A*B)
|
C |
Per Seat Options |
|
Number of Seats (computers) that will access the server
|
D |
- If the result calculated for Line C is less than that
of Line D, then use Per Server licensing. Line C shows the number of Client Access
Licenses that will be needed.
- If the result calculated for Line D is less than that of
Line C, then use Per Seat Licensing. Line D shows the number of Client Access Licenses you
need.
- In either case, Line A shows the number of Server Licenses
that are needed.
Licensing Program in Control Panel |
- Licensing program in Control Panel is one of the
tools that can be used to track licensing data and to replicate the licensing data in a
centralized database. Double click and the Choose Licensing Mode dialog box
appears. Use it to view which licensing mode has been selected for each BackOffice
product, including Windows NT Server.
Option |
Use this option to |
Product |
Specify server product that
requires CALs |
Per Server for x concurrent
connections |
Add Per Server licensing mode
and add number of concurrent connections for that server |
Add Licenses |
Add CALs to increase the number
of concurrent client connections |
Remove Licenses |
Remove CALs to decrease the
number of concurrent client connections |
Replication |
Display Replication
Configuration dialog box; used to specify how a computer replicates licensing
information to a master server or enterprise server |
Per Seat |
View whether Per Seat licensing
mode has been selected. Options can be configured in License Manager in Administrative
Tools. |
Configuring License Replication |
- Maintains a centralized licensing database for an
organization. Use it to manage an organizations licensing agreements, and to ensure
legal compliance with software licensing requirements.
- A servers licensing information is routed to a
centralized database on a designated master server at specified intervals.
Licensing in a Single Domain Environment
PDC acts as master server; stand alone servers and BDCs
replicate licensing info to PDC.
Licensing Replication in an Enterprise Environment
Enterprise server acts as master server for two or more
domains. Each PDC acts as master server for its domain. Each PDC replicates licensing
information for master server for entire enterprise.
Replication Configuration dialog box contains the
following:
Option |
Use this option to |
Use this option when |
Domain Controller (PDC) |
Specify master server is the PDC |
-This computer is a stand alone
server or BDC. -This computer is stand alone server
or PDC and you dont want to replicate further. |
Enterprise Server |
Specify master server is an
enterprise server and enter its name |
-This computer is stand alone
server and you want to replicate directly to enterprise master. -This computer is a PDC, and you want to replicate to enterprise. |
Start At |
Set time each day when licensing
information is replicated to master server |
You want to manually set time to
start replication. |
Start Every |
Set frequency of license
replication |
You want Windows NT Server
computer to automatically stagger the replication of licensing information from each
server. |
- License Manager can be used to:
- View licensing for an organization.
- Administer license allocation and usage throughout
organization
- perform one way, one time change from Per Seat to Per
Server.
Tab |
Use this tab to |
Purchase History |
View product purchase date,
product quantity, and identify product administrator; can be used in both licensing modes |
Products View |
View number of Per Server and
Per Seat licenses by each BackOffice product |
Clients (Per Seat) |
Survey licensed and unlicensed
product usage. Click a user name to view the server usage history for the user, to upgrade
the user to a BackOffice license, or to revoke the users permission to access the
server. |
Server Browser |
View servers in a domain or
organization. Double click to expand the domain to display servers in that domain. |
- Adding or Removing CALs for Per Server Licensing:
On Server Browser tab in License Manager double
click the domain. Double click on a server to view installed BackOffice products. To add
or remove a product double click on it. The Choose Licensing Mode dialog box
appears.
Choose Licensing Mode Dialog Box
Option |
Use this option to |
Per Server for x
Concurrent connections |
View number of concurrent client
connections that are configured for a server |
Add licenses (Per Server) |
Add CALs to increase the number
of concurrent client connections |
Remove Licenses (Per Server) |
Remove CALs to decrease the
number of concurrent client connections |
Per Seat |
View whether Per Seat licensing
is selected |
Adding or Removing CALs for
Per Seat Licensing:
- To add CALs click New License on License menu
of the License Manager. Select the product, enter the number of CALs and click OK.
- To remove CALs, in License Manager, click Products
View tab and select the product. On the License menu click Delete. The Select
Certificate to Remove Licenses dialog box appears. Click the appropriate serial
number. In the Number of Licenses to Remove box, eneter the number of CALs to be
removed and click Remove.
Creating License Groups:
Windows NT Server Clients |
Client Software Included with Windows NT
Server
- Client software for Windows 95 or Windows NT Workstation is
automatically installed by installing OS.
- Computers running other OS such MS-DOS Microsoft provides
networking client software in Client folder on Windows NT Server 4.0 CD.
Client Software Provided by NTS
- Microsoft Network Client 3.0 for MS-DOS and Windows
- Microsoft LAN Manager 2.2c Client for MS-DOS
- Microsoft LAN Manager 2.2c Client for OS/2
- Microsoft Windows 95 Operating system
- Add-on Microsoft TCP/IP-32 for Windows for Workgroups 3.11
Microsoft Network
Client 3.0 for MS-DOS and Windows
|
- NetBEUI.
- IPX compatible transport (but not SPX).
- TCP/IP (supports DHCP but not DNS or WINS).
- Data link control (DLC).
- Full Redirector is used to log on to a network and
access services and resources.
- Default Microsoft Network Client 3.0 supports the full
redirector
- enables clients to take advantage of the following network
services:
- Domain logon capability and logon scripts.
- RAS version 1.1.
- Messaging.
- Interprocess communication (IPC) mechanisms as named pipes,
RPC and WinSock.
Note: |
Microsoft Network Client 3.0 has NO browsing
capabilities. To browse network there must be Windows for Workgroups or Windows NT in the
same workgroup. |
LAN Manager 2.2c for MS-DOS |
It includes:
- NetBEUI, DLC and TCP/IP (supports DHCP; not WINS and
DNS).
- Novell NetWare connectivity disk used to access NetWare
server
- Supports Remoteboot service; MS-DOS and Windows-based
computers can be remotely started
LAN Manager 2.2c for
OS/2
|
- Supports IBM OS/2 1.x and OS/2 2.x
- Includes NetBEUI and TCP/IP (supports DHCP; not WINS and
DNS).
Supported Protocols
- NetBEUI
- NWLink IPX/SPX compatible transport
- TCP/IP (DHCP, WINS and DNS supported)
- Support for 32-Bit Networking
- Windows 95 uses a 32-bit protected mode redirector for
network logon and to access resources. (Redir32.exe). The advantage of this redirector is
that it supports 32-bit WinNet32 programming interface and 32-bit protected mode drivers.
More robust than 16-bit.
Exactly the same as Win95
Network Client Administrator |
Windows NT Server CD includes installation
files for OS as Windows 95, Microsoft Network Client 3.0 for MS-DOS, LAN Manager 2.2c
Clients for MS-DOS or for OS/2 in the Clients folder.
What is Network Client Administrator?
- You can use Network Client Administrator to
- Install network client software by creating a network installation startup disk or an
installation disk set.
- Share the installation files contained in NTS CD.
- Copy the folders and files contained on the NTS CD to a network server and share them.
Using Network Client Administrator (Administrative
Tools) dialog box:
Option |
Use this option to |
Make Network Installation
Startup Disk |
- Create MS-DOS network installation startup disk
- can be used to automatically connect to server and install
Window 95, Microsoft Network Client 3.0 for MS-DOS and Windows
|
Make Installation Disk Set |
Create installation disk for
- Microsoft Network Client 3.0 for MS-DOS and Windows,
- LAN Manager 2.2c Clients for MS-DOS or for OS/2,
- Remote Access v1.1a for MS-DOS, or
- TCP/IP-32 for Windows for Workgroups
|
Copy Client-based Network
Administration Tools |
- Install client based Windows NT administration tools on
Windows 95 and Windows NT Workstation computers
- This option only copies the files to the share; you then go
to NTW or W95 to install the admin tools.
|
View Remoteboot Client Information |
- Remoteboot is a NT service that can be used to start DOS, Win3.1
and Win95-based computers over the network.
- The Remoteboot service is installed through the Network program in
Control Panel.
|
Note: Make sure
that you know when to use the first two options. There could well be a question about what
to create for the network installation of Win95. Of course, the answer is: Network
Installation Startup Disk. |
Creating a Network Installation Startup Disk |
- This disk is used to install software on the client
computer. The Network installation Startup Disk connects to a network share or shard CD,
usually on the server, but not necessarily.
- Used to connect to network share or shared CD computer
running Windows NT Server.
- Create this disk in Network Client Administrator
dialog box
- click Make Network Installation Startup Disk, click Continue.
The Share Network Client Installation Files dialog box appear
Option |
Use this option to |
Path |
Indicates the locatoin of the
target files |
Use Existing Path |
Specify existing path |
Share Files |
Share client folders and files
directly from CD |
Copy Files to a New Directory,
and then Share |
Specify whether files are copied
to new directory and then shared, or files are shared through existing server directory |
Use Existing Shared Directory |
Use files that have been
previously copied and shared |
- Target Client Configuration
- The next step is to specify the configuration
of the target clients.
- In Share Network Client Installation Files
dialog box click Share Files and click OK.
The Target Workstation Configuration
dialog box appears:
Option |
Use this option to |
Floppy Drive |
Select 3.5-inch or 5.25-inch for
floppy disk size |
Network Client |
Identify client software that
will be installed Microsoft Network Client 3.0 for MS-DOS and Windows or Windows 95 |
Network Adapter Card |
Select network adapter card for
client |
Configuring a Network
Startup Disk
|
After specifying target client configuration click OK. The
Network Startup Disk Configuration dialog box appears. Use it to configure the
following information for the client:
|
- Enable Automatic DHCP Configuration
|
|
|
|
|
|
|
|
|
After information is provided, a prompt requests insertion
of a formatted, HD MS-DOS system disk in destination drive. Network Client Administrator
copies files to the disk.
Creating an Installation Disk Set |
Use Installation Disk Set to manually install following
client software or service on each client as opposed to downloading it from a network
server.
Installation disk sets can be created for the following NT
clients:
- Microsoft Network Client 3.0 for MS-DOS and Windows
- LAN Manager 2.2c Clients for MS-DOS or for OS/2
- Remote Access v1.1a for MS-DOS
- TCP/IP-32 for Windows for Workgroups 3.11
To create one in Network Client Administrator,
select Make Installation Disk Set and click Continue. Share Network
Client Installation Files dialog box appears; configure the options and click OK.
Make Installation Disk Set dialog box appears. Configuration options:
Option |
Use this option to |
Network Client or Service |
Specify type of installation
disks to create |
Destination Drive |
Specify destination drive for
the disk (A or B) |
Format Disks |
Format disks to be used |
Client-based Network Administration Tools |
System Requirements for Windows 95 |
Minimum requirements to install Win NT Server Administration tools for Win 95:
- Need Win 95 (well duh)
- 486 DX /33
- 8 MB RAM
- 3 MB free disk space in the system partition. This is important because the Windows NT
Server Tools are installed in the \srvtools folder on the computer's system partition.
- Client for Microsoft Networks must be installed
Heres how you install the Server Tools
- Insert Windows NT Server 4.0 CD
- Go to Control Panel; Add/Remove Programs
- Select Windows Setup tab and click Have Disk
- In Copy Manufacturers files from box type
CD:\Clients\Srvtools\Win95 and click OK.
- Click Windows NT Server Tools and click Install;
installed in Srvtools root folder.
- Edit path in Autoexec.bat to the folder (C:\Srvtools) and
restart computer.
System Requirements for Windows NT
Workstation |
Tool |
File name |
DHCP Manager |
Dhcpadmn.exe |
Remote Access Administrator |
Rasadmin.exe |
Remoteboot Manager |
Rplmgr.exe |
Server Manager |
Srvmgr.exe |
System Policy Editor |
Poledit.exe |
User Manager for Domains |
Usrmgr.exe |
WINS Manager |
Winsadmn.exe |
DNS Manager |
N/A |
Services for Macintosh included with Windows
NT |
- Services for Macintosh enables clients running Microsoft OS
and Macintosh clients to share file, print administrative and other network resources.
- It supports LocalTalk, Ethernet, Token Ring and FDDI.
Benefits:
Function |
Remark |
File sharing |
Clients can work on the same
documents, even if some work with the Macintosh version of the application and others with
the Windows or MS-DOS version. |
Printer sharing |
PC printer or Macintosh based
printers can be used |
Simplified administration |
Network with Macintosh, DOS and
Windows client can be managed from NT Server computer |
AppleTalk routing support |
Macintosh networks can be
connected to create AppleTalk internetwork |
Requirements for Windows NT Server:
- Minimal 2 MB available disk space on NTFS volume.
- Requirements for Macintosh Clients
- Macintosh OS 6.0.7 or later.
- AppleShare (the Apple networking software for Macintosh).
Installing Services for Macintosh |
This is done through Services tab of the Network
program.
Creating a Macintosh-Accessible Volume |
Example exam question: how to share files between Macs and Windows/MS-DOS? : Create a
Macintosh accessible volume.
After installing the service a MacFile menu is
added to the Server Manager; use this to create Macintosh accessible volumes. To
make folders stored on a Macintosh-accessible volume also available to Windows- and MS-DOS
based clients, it is necessary to share the folder from which the volume was created.
Note: Macintosh
computers have maximum partition size of 2 GB. If a Macintosh client accesses a NTFS
partition larger than 2 GB, users may get the message that there are 0 bytes available. |
Features That Install Automatically with
Services for Macintosh |
AppleTalk protocol |
- delivers data to its destination; can be installed and
configured through Protocols program in Control Panel.
|
File Service for Macintosh |
- used to manage Macintosh volumes, folders and files
|
Print Service for Macintosh |
- eanbles Windows, MS-DOS or Macintosh clients to print to
either AppleTalk or non-AppleTalk printing device.
|
|