features of window 95

Using a 32-bit, Protected-Mode Network Client
For best performance, select a network client that uses a 32-bit redirector for accessing servers. Windows 95 includes the 32-bit Microsoft Client for NetWare Networks and the Client for Microsoft Networks; each of these has a 32-bit redirector. The benefits of using a 32-bit, protected-mode client include the following:
Provides for easy installation and configuration using built-in Windows 95 tools
Uses no real-mode memory
Provides faster data I/O across the network
Offers greater stability than real-mode redirectors
Allows more than one redirector to be run at one time, and thereby enables access to servers for multiple networks without having to reload the operating system for a new network client
Makes networking seamless in the Windows 95 user interface; users can browse the server for multiple networks in Network Neighborhood, all within the same namespace — users don't need to know which type of network they are browsing
If you are using another type of network, contact your network vendor regarding the availability of a 32-bit, protected-mode network client. If a protected-mode client is unavailable, you can run a protected-mode Windows 95 client such as Client for Microsoft Networks in conjunction with a real-mode network client.
Using a 32-bit, Protected-Mode Protocol
If you select a 32-bit, protected-mode network client, then by default Windows 95 also sets up a 32-bit, protected-mode protocol. Even if you are running a real-mode client such as the Novell® 3.x workstation shell (NETX) with a real-mode implementation of IPX/SPX to access NetWare® servers, you can still load the 32-bit version of the Microsoft IPX/SPX-compatible protocol. The benefits of adding the protected-mode protocol are better performance and better stability for network communications to servers that are not running NetWare (for example, computers running Windows 95 or Windows NT).
In addition, for protocols such as TCP/IP, the Microsoft 32-bit version enables additional functionality such as the ability to use DHCP and WINS servers that dynamically set the IP addresses and resolve computer names for client computers on the network. Each protocol has a number of benefits, as discussed in Chapter 12, "Network Technical Discussion."
Using the Latest Network Adapter Drivers
For best performance, use the latest network adapter drivers available. These should be NDIS 3.1-compatible drivers which provide Plug and Play capabilities. Such drivers take up no real-mode memory and can be loaded or unloaded dynamically as required.
The only instances in which you wouldn't use the latest drivers are:
The newest driver isn't available for your network adapter.
Your site requires ODI cards and drivers.
Recommended Features for Network Clients (Optional)
The following optional features are recommended for your preferred configuration. These features define how Windows 95 will be installed and administered in your organization.
Using System Policies
For centralized administration of client computers, you must enable system policies. System policies allow you to centrally edit and control individual user and computer configurations. For example, if you want to place a custom Start menu on user desktops or to limit access to Control Panel options, system policies make it easy to do this from a central location for a large number of users.
Enabling policies creates a single file that resides on the server, and thus does not involve physically touching the client computer. In general, the policy file can be modified on the server after Windows 95 is installed; however, some types of changes, such as adding group support or a nonstandard server path for product updates, require configuration on the client computer. For information on the types of restrictions available and for details on how to implement system policies, see Chapter 15, "User Profiles and System Policies."
Using User Profiles
With user profiles, users can use personalized desktop settings each time they log on to a computer. This is especially useful for multiple users sharing a single computer who want to customize their desktops and have those custom settings loaded at logon. Conversely, a single user can move between computers using the same profile if the administrator stores that profile on the server. An administrator can also take advantage of profiles to require that a mandatory desktop configuration be loaded each time a user logs on. The ability to change profile settings can be controlled by the administrator. For information on how to use user profiles, see Chapter 15, "User Profiles and System Policies."
User profiles are not needed when only one person uses the computer or when a custom desktop adds no value. By not enabling user profiles, the logon process is shortened slightly, because the system does not need to locate and load the profile.
Enabling Remote Administration
To remotely administer a computer's Registry, you must first enable this capability. This is done on the client computer by installing the network service called Microsoft Remote Registry service, enabling user-level security, and enabling the Remote Administration feature. Remote administration capabilities allow you to conduct a variety of tasks remotely over the network such as administering the file system, sharing or restricting directories, or querying and making changes to the Registry. If you plan to do any of these tasks, be sure to enable this feature during Windows 95 installation.
You should not enable remote administration if you don't need these services, because doing so causes unnecessary, extra processes to run on the client computer and on the network. These extra remote services could then theoretically be used by individuals on the network— provided they knew the appropriate password — to access information on your client computers. However, Windows 95 comes with security capabilities to protect against unauthorized use of the Remote Registry service. For more information, see Chapter 16, "Remote Administration."
Using Setup Scripts for Windows 95 Setup
Setup scripts (which are batch files) allow you to predefine responses to prompts that appear during Windows 95 Setup. Setup scripts go hand-in-hand with push installations to completely automate the installation process. The choice to use a setup script is very straightforward. If you need to conduct a similar installation more than five times, you should use a setup script. Begin planning for setup scripts and push installations during this phase, as you are specifying the preferred client configuration. Make sure that you document each feature needed, so that you can automate the selection of these features. For more information, see Chapter 5, "Custom, Automated, and Push Installations."
Using Push Installations for Windows 95 Setup
You need to understand and plan in advance how the push installation process will work for a given computer. There are several alternatives for remotely initiating the installation, ranging from editing the client's login script, to sending by electronic mail a link that contains a setup script. You will want to consider how to push the installation for each computer and make sure that the client computers are configured to support this process.
For organizations with 50 or more computers, being physically present to install each client computer is not a viable option because of the cost. In that case, you may need to turn to an administrative software solution such as Microsoft Systems Management Server. When using administrative software tools, additional client-side software may be needed. Be sure to include this software in the installation plan.
For more information about using push installations, see Chapter 5, "Custom, Automated, and Push Installations."
Using Peer Resource Sharing Services
The peer resource sharing capability in Windows 95 allows your client computers to share files and printers directly from a local personal computer, instead of on a central server. Peer resource sharing may reduce the traffic and disk space required on central servers, because you are leveraging the power of individual computers.
Security for peer resource sharing services may take the form of user-level security based on the user accounts on a Windows NT or NetWare network. Notice that a Microsoft Windows NT Client Access License is required if the computer will be connecting to servers running Windows NT Server. For information, see Chapter 8, "Windows 95 on Microsoft Networks," or contact your Microsoft reseller.
If you don't have servers to provide security validation or don't want to use user-level security, you can use share-level security, with each individual implementing security and a password scheme on the local computer. Share-level security is set on a directory-by-directory basis.
If you do not want to use peer resource sharing services and want to disable the capability on each client computer, you can do so by selecting the appropriate option in system policies.
Using User-Level Security
User-level security is based on user account lists stored on Windows NT or Novell NetWare servers. The user accounts specify which users have access rights on the network. Windows 95 passes on a user's request for access to the servers for validation. Pass-through user-level security protects shared network resources by requiring that a security provider authenticate a user's request to access resources.
User-level security is required for remote administration of the Registry and for network access to full user profiles. For information on implementing security in Windows 95, see Chapter 14, "Security."
Other Optional Features
The following features may be useful in your organization. Review the related discussion before making a decision.
Using Microsoft Exchange Mail
The new Microsoft Exchange feature in Windows 95 manages all messaging information in one place, with a single inbox for electronic mail, faxes, and other messages. In addition, Windows 95 comes with a complete small-business mail system — that is, a mail client and a postoffice — that allows users to exchange electronic mail through a single postoffice. This mail client integrates well into Microsoft Mail servers, and the postoffice can be upgraded to provide an enterprise mail system.
You can also use a variety of other mail or messaging systems through Microsoft Exchange as long as they use a MAPI 1.0 driver. If you have an existing mail system that doesn't use a MAPI 1.0 driver, you can continue to use that mail system without running the Microsoft Exchange Mail capability. In this case, you would install Microsoft Exchange only if you wanted to use the Microsoft Fax capability so that incoming faxes are collected by Microsoft Exchange. For more information, see Chapter 26, "Electronic Mail and Microsoft Exchange," and Chapter 27, "Microsoft Fax."
Using Microsoft Fax
Microsoft Fax provides a built-in fax capability that allows a computer running Windows 95 to send and receive faxes as bitmap and binary files without any additional software. It also allows users within a Windows 95 workgroup to share a fax modem, but if you have an existing fax server in your organization, you should probably to continue to use that server for computers on the network. In that case, Microsoft Fax features would still be useful for portable computer users who travel. For more information, see Chapter 27, "Microsoft Fax."
Using Dial-Up Networking
This built-in client software allows the computer to use popular, server-based dial-in packages such as Windows NT RAS, Novell Netware Connect, and Shiva NetModem. Dial-Up Networking provides additional security for remote dial-up connections and requires some additional configuration of procotols and software. For more information, see Chapter 28, "Dial-Up Networking and Mobile Computing."
Using The Microsoft Network
The Microsoft Network is an online service that offers chat capability, information bulletin boards, and electronic mail. It is the best place to obtain Microsoft product information and technical support. For more information, see Chapter 29, "The Microsoft Network."
Using Disk Management Tools
Windows 95 ships with useful disk tools such as disk compression and defragmenting utilities that run from within Windows 95. The disk compression utility upgrades DoubleSpace® and DriveSpace™ programs from MS-DOS 6.2x. For details, see Chapter 20, "Disks and File Systems."
Top Of Page
Performing the Lab Test: The Details
This phase in the deployment process involves four significant efforts: preparing the site, conducting the installation, testing the installation, and restoring the system.
Preparing the Test Site and Equipment
Preparing the site involves ensuring that the location of each computer, the computer itself, and the hard disk in particular are all ready for Windows 95 to be installed. In terms of the physical site, make sure that you have the appropriate jacks for connecting to the network.
In terms of the computer itself, make sure that it has the appropriate hard disk space, RAM (at least 4 MB, but 8 MB is recommended), and processor (386DX or better is recommended) to run Windows 95. To review the requirements for running a shared copy of Windows 95 from a server, see Chapter 4, "Server-Based Setup for Windows 95."
In addition, run virus detection, disk scanning, and defragmentation programs on the computer to correct any problems prior to installation. Although the computer may appear to be operating properly, software upgrades often uncover hardware or software problems, because of the way they read and write data to the hard disk. Correct any such problems before installing Windows 95.
Lastly, when preparing the site, be sure to back up critical data and configuration files for the system, in case the installation fails or you need to revert to the previous operating system for some reason. This includes backing up INI files (such as WIN.INI and SYSTEM.INI), GRP files, AUTOEXEC.BAT, CONFIG.SYS, and all key data files. As an added precaution, create a system startup disk and back up the Windows and DOS directories and all the files in the root directory.
If you need to automate the restoration, consider using a commercial backup program, instead of copying the files by hand.