WINDOWS NT

Defensive Computing

Prevent server crashes by enabling administrative alerts on critical parameters such as swap file size. Run Windows NT Performance Monitor and select View/Alert, Edit/Add to Alert and % Usage Peak from the Paging File object. Set it to alert you if usage goes over 90 percent. This gives you a warning before NT starts expanding the page file automatically--which can degrade performance. You can use the same approach to avoid critical conditions such as running out of disk space.

Hiding a server from the browser

To hide a server from the browser, edit:
HKEY_LOCAL_MACHINE\\SYSTEM\CurrentControlSet\Services\LanmanServer \Parameters
Add value Hidden (REG_DWORD). Set it to 1.
Reboot the server. It may take up to ½ hour for the server to disappear from the browse lists.

Want to move or recreate your mail PostOffice?

The PostOffice is in a directory called WGPO.
To move it: Move it (and all the subdirectories) to a new location which is shared with "Full Control".
Edit:HKEY_CURRENT_USER\Software\Microsoft\Mail \Microsoft Mail
Double click ServerPath and change it to the new WGPO location.
If you have WFWG or W95 users, change the ServerPath= in their MSMAIL.INI.
To start over(delete it):
Delete the WGPO directory
Edit: HKEY_CURRENT_USER\Software\Microsoft\Mail
and delete the Microsoft Mail Sub Key.

Enable your DOS apps to print to a network printer

At a command prompt (or in a batch file), type: NET USE LPTx \\computername\sharename /PERSISTENT:YES .

Carry Lotsa Cache

Maximize server throughput with a large client-side cache. Microsoft's Windows NT Advanced Server Reviewer's Guide indicates Windows for Workgroups 3.11 clients run against an NT server can double their performance with 4MB dedicated to VCACHE. This is the configuration Microsoft recommends for client-side systems with 12MB or more of RAM.

Make Your Presence Known

If you're adding Windows NT workstations or servers to LAN Manager 2.x domains, enable LM-compatible broadcasts in the NT systems. Broadcasting is a technique LAN Manager servers use to announce their presence on the net to other LAN Manager systems. By default, Windows NT doesn't provide these broadcasts. Instead, it relies on the BrowseMaster technology developed for WFWG. As a result, Windows NT systems are invisible on the network. To turn broadcasts on, choose the Control Panel/Network icon, select the Server object and click on the Configure button. When the Server Configuration dialog box appears, check the Make Browser Broadcasts to LAN Manager 2.x Clients box. When you restart, NT systems will be visible to LAN Manager users.

Setting and mapping shares from the command line

You can create shares from the command line or a batch file using NET SHARE (type net share /? for syntax) and you can map any share using NET USE. There is no native way to establish share permissions from the command line. The NT Server Resource Kit contains PERMCOPY.EXE that allows you to copy permissions from one share to another. You can either use an existing share as the source or create some hidden models (hidden shares end with a $ as in \\MachineName\Model1$). The syntax for PERMCOPY.EXE is: permcopy \\SourceMachine SourceShareName \\DestinationMachine DestinationShareName (Source and Destination MachineName can be the same).
You may also use RMTSHARE.EXE from the Resource Kit to set up shares with permissions.

Convert LAN Servers

The Windows NT Advanced Server Upgrade for LAN Manager lets you upgrade LAN Manager servers to Windows NT. It includes special programs for automatically migrating the user database, shared resources, server configuration, access control lists (permissions) and so on. It costs significantly less than the regular Windows NT Advanced Server package. You'll need to convert LAN Manager servers to Windows NT Advanced Servers, rather than to the basic Windows NT package, in order to retain their centralized domain administration features. You can mix Windows NT Advanced Servers and LAN Manager servers in a single network, but the primary domain controller must be a Windows NT Advanced Server. Plus, LAN Manager servers won't be able to validate log-on requests from users attempting to connect with global accounts from a trusted Windows NT Advanced Server domain.

Want to move tons of shares to another WinNT server?

If the prospect of moving all those shares to your new server has you down, here is a simple method that will only take a few minutes. Navigate to the following registry key: HKEY_LOCAL_MACHE\SYSTEM\CurrentControlSet \Services\LanmanServer\Shares Save the Key to a filename on a floppy. On the new server, navigate to the same key and save its' empty Shares key to a floppy before restoring it from the 1st server. This will destroy any existing shares on the new server. Now, restore the empty Shares key that you saved from the new server to the 1st server or delete the values manually (also from the Security sub-key). Create at least one new share on each server. This is required so explorer can refresh its' shares. In Control Panel / Services, stop and restart the Server Service. If you don't want that new share, unshare it normally.

Want an inexpensive groupware solution?

By placing a shortcut to the desktop folders of your team members on your desktop, you can drag documents from explorer to that icon and a copy of the document will appear in their desktop folder and its' icon will be displayed on their desktop. For Windows NT, the desktop folder is located at %windir%\profiles\UserName\Desktop and for W95 it is Windows\Desktop.

Can't get NT to recognize the 256 processors on your MOBO?

If you have more processors than NT will recognize, try editing:
HKEY_LOCAL_MACHINE/System/CurrentControlSet/Control /Session Manager/ Environment/NUMBER_OF_PROCESSORS
and
HKEY_LOCAL_MACHINE/System /CurrentControlSet/Control/Session Manager/Environment /LicensedProcessors
Now, when you do an update install (re-install into the same directory), NT will recognize those extra processors. As with any system modification requiring use of the NT CDROM, re-apply your latest SP. Don't forget to generate a current ERD (RDISK.EXE /S).
Be sure that you are not violating any license agreements if you do this. You will require a custom HAL if your MOBO has more than 4 processors.

Want to map a drive letter to a sub-directory without creating a share?

Type SUBST /? at a command prompt for syntax. Here are some examples:
subst h: \\ServerName\User$\%username% where User$ is a hidden share of the main users directory and %username% represents the users sub-directory and is not shared.
subst x: c:\temp where temp is a local directory on local drive c:.
subs x: \\ServerName\C$\DirectoryName\SubDirectoryNamewhere C$ is a hidden administrative share and DirectoryName and SubDirectoryName are not shared.

Call the Exterminator

When a Windows NT system has trouble accessing the network, you can debug it with the net send command. Normally, you'd use this command to send alert-type text messages to users, such as "Server going down in 10 seconds, please log off!'' But the /BROADCAST command-line switch makes it useful for debugging as well. In this mode, net send uses a low-level datagram broadcast that all users receive on the local segment, regardless of whether the sending machine is logged onto the net.

To use it, type the following at a Windows NT command prompt: net send /BROADCAST Tommy can you hear me? If the system is working properly, the text message will pop up on the screens of all LAN Manager and Windows NT systems on the local network segment. If it doesn't, even low-level data packets aren't being transmitted. This indicates the network card is misconfigured or the wrong driver is installed.

Join the Group

Windows NT's built-in networking can participate in two very different kinds of administrative groups: workgroups, as used in WFWG; and domains, as used by the Windows NT Advanced Server. Workgroups are ad hoc groupings of workstations and peer servers for administrative convenience. Each system maintains its own user account database and is administratively separate from all the others. Domains have a single account database, maintained by the Primary Domain Controller, which must be a Windows NT Advanced Server. Systems participate in the domain log-on through the Primary Domain Controller, or one of its backups that replicate the Primary Domain Controller's user database. Windows NT workstations can participate as members of an Advanced Server domain or can be outside of it, but only domain members can be centrally administered. This means if you use Windows NT workstations with Windows NT Advanced Servers, you should set them up as domain members. Otherwise, they must be set up as standalone workgroup members. Although you can mix the two, the result is difficult to administer.

Give 'em the Boot

If you're running Windows NT servers from a locked closet or server room, you can make them fully bootable. This means they won't require human intervention to carry out initial log-ins and run startup batch files. Run the Windows NT Registry Editor (REGEDT32.EXE), select the server's HKEY_LOCAL_MACHINE key and then SOFTWARE/Microsoft/Windows NT/CurrentVersion/WinLogon. Select Edit/Add Value, then enter value name AutoAdminLogon of type REG_SZ and set it to 1. Set the DefaultUserName and DefaultPassword variables to suit the server's log-in and script execution. Because this procedure stores the clear-text user name and password in the Registry, I suggest you create a special account for this purpose that doesn't have administrative permissions.

Long-Distance Server Control

Control servers remotely--even over slow links--with REMOTE.EXE from the Windows NT Resource Kit. Copy REMOTE.EXE on both the server and client system. Start the server's copy from a command prompt by typing REMOTE /S cmd.exe server1. You can then connect from the client by typing REMOTE /C server name server1. This gives you a command session on the client that's executed on the server, allowing you to control nearly all aspects of system operation. This approach even works across telephone lines using Windows NT Remote Access Service (RAS).

Managing the Mapped Network Drive dropdown list

If you want to remove some the connections in the list, edit: HKEY_CURRENT_USER\Software\Microsoft \WindowsNT\CurrentVersion\Network \PersistentConnections
Highlight and delete unwanted entires. Then double click Order and remove the letters that have been deleted. You may rearrange the letters to change the display order.

Ghosted connections

If you want to Ghost/Un-Ghost persistent connections, edit:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet \Control\NetworkProvider Value: RestoreConnection REG_DWORD
0 = ghost connection
1 = persistant (not ghosted)

Freeware Messager - Send WinPopUp messages in WinNT

Tired of using "NET SEND" or Server Manager to send network PopUp messages? Download Messager, expand the archive, and place the files in \system32. Create a shortcut to messager.exe and place it on your DeskTop or in the Start Menu.

Alert the Administrator

Schedule server batch jobs and other processes using the AT.EXE command-line scheduler. Start the Scheduler service, using Control Panel's Services applet or the Server Manager. Then type AT at any command prompt for a list of active jobs, AT /? for on-line help, AT server name for a list of active jobs on any server on the net, or (for example) AT 10 AM EVERY MONDAY NET SEND ADMINISTRATOR HI THERE to send a weekly greeting to the administrator. You can start any valid Windows NT command or batch file using this method--including backups, and service starts and stops.

It's Okay to Be Insecure

If security's not a primary concern, eliminate the Press Ctrl+Alt+Del to Log In, and the need to enter a user name and password each time the system starts by modifying your system configuration. Run REGEDT32, and add two new REG_SZ variables to the HKEY_LOCAL_MACHINE\Software\Microsoft \Windows NT\CurrentVersion\Winlogon key. The new variables should be named DefaultPassword (which should be set to the password used by the user name specified by the DefaultUserName variable) and AutoAdminLogon (which should be set to 1). Also check to see that the DefaultDomain variable has a legal value (this should be the local Windows NT Advanced Server domain on Advanced Server networks, or the Machine Name on standalone Windows NT systems). Then exit the Registry and log off. The system will automatically log you on using the specified default user name and password. Note: Because this step stores a clear-text password in the Windows NT registry, it violates C2 security guidelines and should not be used on secure systems.

Give our machine a Netbios alias in Windows NT

If you have an machine name that is invalid for SQL Server, Exchange, or just want to be cute, you can change it in Control Panel / Networks, but that could be a lot of work. Create an alias instead, by editing:
HKEY_Local_Machine\System\CurrentControlSet \Services\LanmanServer\Parameters
Add Value: OptionalNames REG_SZ String: "Alias"

Guest Welcome

To make Windows NT shared resources (files and printers) accessible to WFWG machines (and Windows NT systems that aren't members of the same Windows NT Advanced Server Domain), enable the built-in Guest account. Log on as the administrator, run User Manager (or User Manager for Domains on a Windows NT Advanced Server) and double-click on the account named Guest. By default, the Account Disabled check box is checked. Remove the check to make shared resources available to those without accounts on your system. Now, any shared resource you gave the group "everyone" access to in File Manager is visible and accessible to guests. To keep guests out of certain shares, give everyone the No Access permission and override this by giving Full Access or other permissions to specified user groups.

At Your Service

Use the NWLink protocol shipped with Windows NT to provide application services to NetWare clients. Install it by going to Control Panel/Network and clicking on the Add Software button. Select NWLink IPX/SPX Compatible Transport from the list, and click on the Continue button. This copies NWLink files. Click on Continue. After bindings are run, you'll see the NWLink Configuration dialog box. The defaults should work for most systems. Click on OK. You'll need to shut down and restart Windows NT to use NWLink. Applications that use NetBIOS commands to provide low-level I/O will work with NetWare client software when run on an NT server using NWLink. In other respects, NWLink functions like the NetBEUI protocol and can even replace it for communications between NT systems.

WINDOWS 95

Use Novell's Client

You should use Novell NetWare client software instead of Microsoft's Client for NetWare Networks, when your LAN uses NetWare IP, NDS (NetWare Directory Services), 3270 emulators in DOS sessions; if it relies on DOS TSRs; or if you want to use NetWare's NCP Packet Signature feature. Then, you should use the appropriate NETX or VLM redirectors.

Use Microsoft's Client

Use the Microsoft Client for NetWare Networks to use a 32-bit driver with Plug-and-Play support, Windows 95 unified logon and management tools, long filenames, peer-to-peer resource sharing via IPX and client-side caching to increase performance.

Enable Long Filenames

NetWare 3.x and 4.x servers can be configured to support long filenames. The OS/2 namespace emulates an HPFS volume, allowing Windows 95 machines to store long filenames on NetWare volumes. Enable this on your file server by typing the following lines at your NetWare server console:

load os2

add name space os2 to

volume sys

Next, add the following line to your STARTUP.CNF file:

load os2

Then shut down your NetWare server and copy the latest version of the OS2.NAM file from NetWare's disks or CD-ROM into the same directory that contains the SERVER.EXE file. Finally, reboot your server so that the changes will take effect.

Set Your Options

To customize your NetWare options using Microsoft's supplied Client for NetWare Networks, choose the Network option in Control Panel (or follow our tip for displaying the Network Control Panel). Click the Configuration tab and double-click on the option for Client for NetWare Networks. In the Properties box, choose a preferred server from the drop-down combo box, pick a network drive to be the first NetWare drive letter or select the checkbox to enable logon script processing.

Map the Public Folder

Map a drive to the PUBLIC directory of the NetWare server's SYS volume in order to use Novell utilities such as SYSCON. To do this, highlight the server you want in the Network Neighborhood dialog box, double-click to log on, and enter your name and password if necessary. Double-click on the SYS volume and then right-click on the PUBLIC directory folder and choose the Map Network Drive option.

Create a Network Shortcut

Create a shortcut to frequently accessed network directories by right-dragging the desired network directory folder to your desktop. Choose Create Shortcuts Here.

Circumvent Printing Snafus

Using both the Microsoft Network Client and Novell Client software in Windows 95 simultaneously can cause printing problems when jobs are sent to NetWare print queues. If this happens, you can remove the Microsoft File and Printing Services by right-clicking the Network Neighborhood, deleting the Microsoft File and Printing Services and then adding Novell's File and Printing Client. You may not use both. Printing through NetWare usually resumes unaided.

Restore Network Ties Automatically

If you use the Client for Microsoft Networks in Windows 95, be sure to check off the Logon and Restore Network Connections option. The alternate choice, Quick Logon, is useful for programs that use network resources by their network name (example: \\winnt\msoffice\winword\winword.exe). Applications that use DOS drive letters must have them restored via the Network Logon Options/Logon and /Restore Network Connections.

Enable Network Backups

Windows 95 includes a network backup agent from Cheyenne Software and one from Arcada. Either can be added into the Network Neighborhood properties, but the programs must be enabled before they'll work. Highlight the agent in the Network Neighborhood Property sheet and click on Properties. Either software option requires additional software on your network server.

Keep Your Win95 CD at Hand

Don't shelve your Windows 95 CD-ROM or diskettes once you've installed the operating system. They contain a database, called a .CAB file, of Windows printer drivers that you may need when you are changing printers or installing a new printer. If you can't find your .CAB file, check your hard disk. Many OEM installations of Windows (also known as pre-installs) have additional drivers in the \windows\driver directory and you will find the needed .CAB file in the \windows directory.

Legal Disclaimer
THE INFORMATION IN THIS PUBLICATION IS PROVIDED "AS IS". WE EXPRESSLY DISCLAIMS ALL REPRESENTATIONS AND WARRANTIES OF ANY KIND REGARDING THE CONTENTS OR USE OF THE INFORMATION INCLUDING, BUT NOT LIMITED TO, EXPRESS AND IMPLIED WARRANTIES OF ACCURACY, COMPLETENESS, MERCHANTABILITY, FITNESS FOR A PARTICULAR USE, OR NON-INFRINGEMENT. IN NO EVENT SHALL WE BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES, INCLUDING LOST PROFITS, LOST BUSINESS OR LOST DATA, RESULTING FROM THE USE OR RELIANCE UPON THE INFORMATION, EVEN IF WE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OF IMPLIED WARRANTIES, SO THE ABOVE EXCLUSION MAY NOT APPLY TO YOU.