Here are links and excerpts from articles I've written.
Installing Lotus Domino Server on Windows NT - Windows NT Magazine, Published by Duke Communications, Inc. in September, 1998.
Imagine that you're cruising along happily in your Microsoft universe, when a customer asks you to install Lotus Domino Server for a groupware system. You try in vain to convince the customer to use Microsoft Exchange Server but must finally give in. Then you set out to research installing and administering Domino. You head to the computer store, which has every book imaginable about Microsoft products, but little about Domino. When you do find something, it's about Domino development--not installation and administration. Not having the time or money for official training, you simply install Domino several times until you think you have it right.
Windows NT Login Scripting - Windows NT Administrator’s Report, Published by TechRepublic, in March, 1999.
Windows NT Server has several limitations compared to other Network Operating Systems. Other systems such as Novell NetWare and Banyan Vines had the luxury of being created from the ground up to be full featured in network utilities. Since Windows NT came from a workstation background, some compromises had to be made.
Login scripts and effectively mapping home directories are two things that are weak with Windows NT. Many solutions to this problem have been suggested, but none I have seen have ever worked correctly as advertised. The solution that I propose has been tested and works in several different installations in many different companies, and the results have been excellent.
Novell and Banyan allow the use of special commands for their logon scripts. Windows NT only allows normal programs, usually contained within batch files. A “Typical” logon script is one such as below called LOGON.BAT:
TCPIP and Windows - Exploring Windows NT Magazine, Published by the Cobb Group in May, 1998.
The goal of this article is to present a quick, tried and true method for installing a Windows NT network utilizing TCP/IP as the protocol. We are going to assume that this is a simple installation. No installation is ever quite this simple. However, providing for every situation is something you can only get from your own experience, and is not something you can get from a magazine article.
What we are going to cover is DHCP, WINS, and DNS installations. The network configuration is as follows. Two Windows NT 4.0 Servers are installed on the network along with forty workstations along with an IBM AS/400. For the IP address range we are going to use in this example network, we are going to use the reserved Class C address range. If the network is going to have an Internet connection, most smaller networks use address translation behind a firewall. In the case of having a direct connection, simply use the address range that your ISP gives you.
Our primary server name is going to be BART. HOMER is the name of the server used to host the Intranet, and the AS/400’s name is MARGE. The TCP/IP domain name is vf.net and the Windows NT domain name is VFNET. These servers all will have assigned static IP addresses.