[Editor's Note: Share your NT discoveries, comments, problems, solutions, and experiences with products and reach out to other Windows NT Magazine readers (including Microsoft). Email your contributions (400 words or less) to r2r@winntmag.com. Please include your phone number. We edit submissions for style, grammar, and length. If we print your submission, you'll get $100.]
DNS Migration
I read Mark Minasi's "DNS Disaster Recovery" (April 1999) with interest, and I'd like to share my experience of migrating DNS information from one Windows NT server to another. My company recently needed to replace the PDC because of a system partition failure. The PDC acted as both a WINS and DNS server; we didn't expect problems with WINS after the migration, but we were worried about having to rebuild the DNS data.
To prevent problems, I copied all the .dns files in the \%systemroot%\system32\dns directory, and I exported the old machine's Registry entries from HKEY_LOCAL_MACHINE\SYSTEM\ CurrentControlSet\Services\DNS. On the new PDC, I stopped the DNS service and I copied the .dns files to \%systemroot%\system32\dns. I decided to use Microsoft's native method of loading entries from the Registry. Two alternatives exist for this method. One alternative is to use a Registry editor. The other alternative is to use DNS Manager to create a dummy zone on the server (you can use any name for the zone), then delete the zone. The default value for the Registry entry HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\ Services\DNS\Parameters\EnableBootFromRegistry is 1. After I restarted DNS services, the DNS server loaded the correct zone information.
—Alex Wun
wun.alex@hit.com.hk
MCSE Paths
I recently obtained my MCSE at Royal Roads University in Victoria, British Columbia. The program I completed has more lab time than formal instruction, and it includes a period of work experience following the coursework portion. Even after that much practical experience, I'd rather not be pitchforked into a senior IT position without shadowing a more experienced network administrator for a couple of years. Therefore, I agree with David Chernicoff's opinion regarding practical experience for MCSEs (Forefront, "The Problem with Certification Programs," January 1999).
From what I've seen, the amount of hands-on experience someone with an MCSE has depends on which path the person uses to pursue certification. The three most common paths seem to be the paper MCSE, goal-oriented MCSE, and slow-and-steady MCSE.
In a paper MCSE program, candidates purchase their texts at a local bookstore, study the texts in the bathroom, memorize output from braindump Web sites, and pass the MCSE exams. Many of these MCSEs have never worked on a real (i.e., nonsimulated) network.
In a goal-oriented MCSE program, candidates complete an instructor-led program but spend most of the classroom time studying Transcender and Personal Exam Prep (PEP) tests. These candidates take any exam that they can pass quickly because they really want those letters after their name.
In a slow-and-steady MCSE program, candidates regard certification as a useful start in the IT field but recognize that they must supplement the degree with a continuing practical and theoretical commitment. These candidates would rather do a job well than finish it quickly.
Candidates who fall into the first two groups are preventing MCSE certification from becoming the IT equivalent of a Certified Management Accountant (CMA), Certified General Accountant (CGA), or Certified Accountant (CA) designation in accounting. I've worked in the accounting field for 6 years and understand the depth and extent of training that goes into these certifications. As IT professionals, we should seek to emulate this commitment to training.
—Robert Ian Clark
westbus@islandnet.com
Use WSH to Automate User Management
My company is in the process of making all user environments consistent. I use a Microsoft Excel spreadsheet to generate a batch file that creates user home directories, sets permissions, and creates network shares. All I need to do is enter the usernames in one column. Other columns use the usernames as variables and create commands according to a formula. Then, I copy the commands to a batch file that does the final work.
I decided to complete this project on a group basis because some groups have hundreds of users, and entering usernames individually in User Manager for Domains is painfully slow. I wanted to extract the username for each group and dump the usernames into the spreadsheet. I could have used the Microsoft Windows NT Server 4.0 Resource Kit's showmbrs.exe utility to direct the output to a file, but I found a better solution. I discovered that I could use the VBScript file in Listing 1, page X, with Microsoft Active Directory Service Interfaces (ADSI) and Windows Scripting Host (WSH) to put usernames directly into the spreadsheet. I also discovered that I could use this method to accomplish other tasks. For example, I used the code in Listing 2 to change the logon script for all the users. If you know the name of the group, you can use the code in Listing 3 to directly change the group members' logon script.
—Larry Lai
llai@ats.com