DNS is the foundation the house of Active Directory is built upon. If DNS doesn’t work, neither will your Windows network. Here are the 10 most common DNS errors—and how you can avoid them.
- By Bill Boswell
- May 01, 2004
You can give ordinary users NT and WMI administrative rights for routine tasks—to a degree.
- By Chris Brooke
- May 01, 2004
In an entirely new approach to product reviews, 13 loyal MCP Magazine readers detail their experiences running Exchange 2003 in production environments.
- By Doug Barney
- May 01, 2004
These networks aren’t well known by many, yet they’re responsible for controlling much in our lives. And they’re not very secure.
- By Roberta Bragg
- May 01, 2004
How Exchange 2000 is like your two-year-old.
- By Bill Boswell
- April 27, 2004
Run legacy apps without hitting the security barrier.
- By Don Jones
- April 23, 2004
Who gave this reader the silly idea that Windows 2000 and Windows 2003 can't live within the same domain?
- By Bill Boswell
- April 20, 2004
Reader has trouble with DCs looking within when doing DNS lookups.
- By Bill Boswell
- April 13, 2004
- By Joe McKendrick
- April 12, 2004
Ports are a good way in, and often remain unchecked.
- By Don Jones
- April 09, 2004
You can use a script to compile log info into a file for closer examination.
- By Chris Brooke
- April 01, 2004
Software Restriction Policies is a terrific new security tool—if you know what it can’t do, as well as what it can.
- By Roberta Bragg
- April 01, 2004
You'll never truly see the beauty of Exchange 2003 unless you migrate. Here are five tools to make that move quicker and easier.
- By Danielle Ruest and Nelson Ruest
- April 01, 2004
Using the Active Directory Connector is an effective way to move your legacy Exchange environment to a new Exchange 2003 setup.
- By Bill Boswell
- April 01, 2004
Knowing what’s in your Event Logs is a key to knowing what your servers are doing. Here’s how to make sense of them.
- By Derek Melber
- April 01, 2004