On-Site or Public?
We primarily offer this class as a two-day on-site class in other words,
your company hires Mark to come teach it on-site. However, we
are also offering Mastering Windows 2000 Server: A Guide to
Planning, Installing, and Running Windows 2000/.NET Server in Your Network as a
public class in a number of U.S. and Canadian cities. If you're interested, signup info and
other details are at www.minasi.com/pubsems.htm.
We will schedule future
public seminars based on interest. If you don't have enough people in your company to justify bringing Mark on-site
but would like to attend the class then you can help us decide which cities (if
any) could produce enough sales to make a public class worthwhile. We plan
to cover this material in two fact-packed days using lecture and
demonstration. Attendees receive both a copy of Mastering Windows
2000 Server, 4th Edition and printouts of preliminary new sections intended
for the next edition.
Course Objectives
To introduce your current NT administrators and technical IT managers to the
benefits (and, inevitably, sometimes the negative aspects) of Windows
2000. As Windows 2000 includes nearly forty million lines of program code,
there are so many new features and gotchas that current NT experts could spend
months trying to figure out which of the new 2000 functionality is useful and
only then could they start planning!
This course saves you time and money in two basic ways. First, I
designed it to be as brief as possible, saving money in terms of instructor time
and lost employee productivity hours. Second, the course reduces the
amount of time that your admins need to get up to speed on Windows 2000 by
pointing out the parts of 2000 that offer the greatest potential gains, helping
you to "cherry-pick" the best new technologies. Third, the more I work
with 2000 and 2002 the more I'm convinced that most books and courses take the wrong
tack: for example, Active Directory should not be your first task
DNS should!
Course Duration
In the perfect world, I'd like to spend five days with your NT/2000
technicians but I know how understaffed most IT shops are nowadays, so I've
tried to whittle the information down to the absolute basics, the things that I
feel that current NT techies need to know in order to get started making 2000
work in your enterprise. Two very information-packed days will show them
what to expect on the road ahead, where the smooth pavement ends and the
potholes begin.
What About a Shorter Class?
Only have one day? Hey, look, the customer's always right give us a
buzz and I'll remove enough content to make a day's worth of material.
I've even got specific 90-minute short pieces if you'd prefer that. (See www.minasi.com/talks.htm
for a list.)
Prerequisites
To save time, I've designed this course to build upon existing NT 4.0
administrator knowledge, so you should have a good working knowledge of NT
administration and infrastructure. On the other hand, if you don't yet
have NT experience then it's easy for me to add that material I've been
teaching NT classes since 1993 but of course then I'll need more time with
the students.
Course Outline
- Overview
- Main goals of Windows 2000
- For Server
- For Professional
- How Microsoft did in achieving those goals
- Major effects to expect both new benefits and new requirements
- How to roll out Professional first, Server first? (Or wait for
Service Pack 38?)
- Creating a Sturdy Infrastructure:
DHCP, WINS and DNS under 2000 ...
But Mostly DNS
When discussing Windows 2000 preparation, many people start from Active
Directory. But that's putting the cart before the horse because
anyone who's done it can tell you that if you do an AD without first building
a sturdy DNS infrastructure, you're doomed to fail.
For the past five years, most NT networks have relied upon three important
bits of "plumbing:" the Dynamic Host Configuration Protocol (which
simplifies putting unique Internet addresses on every computer), the Domain
Naming System (which keeps track of every computer's Internet name), and the
Windows Internet Naming Service (which keeps track of every computer's
Microsoft networking name yes, every NT PC has two names). Windows
2000 brings some important changes to both DHCP and WINS, and this talk tells
you what those changes are and how to get the most out of them. But the
really big story is DNS. DNS was once a sort of afterthought in NT
networks. But in 2000-based networks, DNS is now a central repository of
essential network information, so the majority of the talk focuses on DNS.
So this section is a complete tutorial on the inner workings of DNS:
how DNS works, how it manages and replicates its data, how to design a DNS
structure that works best for your company, and how to secure it and make it
ready for Active Directory.
In this section, you'll first learn how DNS works: how its hierarchy of
names functions, how it stores and replicates its data, and how to design an
effective architecture of DNS servers. Then you'll learn about how
Microsoft's Windows 2000 DNS servers go beyond the basics and extend DNS's
power. Finally, you'll learn how to build a Windows 2000-based DNS
architecture that can coexist with an existing non-Windows 2000 DNS
structure.
- DHCP, WINS and DNS overview
- DHCP under 2000: everything gets better
- DHCP servers must be authorized by AD
- Effects of a mixed AD/non-AD environment
- Authorizing a DNS server
- DHCP servers now have a command-line interface
- DHCP servers will now register DNS
- WINS under 2000: yes, it's still around, and probably will be for
a while but it works better now
- What's in a name: WINS versus DNS names
- Understanding the DNS hierarchy
- Zones versus domains: what's a "zone," anyway?
- Private or public root?
- How DNS resolutions work, and how 2000 improves them
- Where DNS stores and replicates its databases
- Primary and secondary zones
- RFC-compliant replication strategies
- Incremental versus full zone replication
- "AD integrated" replication
- DNS designs: delegation, forwarders and slaves
- Internal and external names: how to build different DNS names on
your internal network that are not exposed externally
- DNS and Active Directory
- AD needs
- Must you use a Microsoft DNS?
- Problems with Microsoft DNS and a "standard" primary zone
- One solution: AD integrated zones
- Using an alternative: building a Linux-based Dynamic DNS server
- Living with BIND: using a
Win2K-based child domain
- Active Directory Concepts and Planning
Windows 2000's "big show" is Active Directory. This section explains
its pieces and basic concepts, then illustrates how to use it to exploit its
delegation abilities and how to plan and use an AD structure.
- Domains in AD: how they're different from and similar to NT 4.0
domains
- Groups in AD: how they're different from and similar to NT
4.0 groups
- Fine-grained administrative control I: understanding
organizational units
- Fine-grained administrative control II: understanding and using
delegation
- Replication I: how AD replicates in a one-site world
- Multiple domains in a tree
- Multiple domains in a forest
- Who holds the power: understanding the types of administrators in
W2K
- Design issues: empty forest roots, enterprise administrators
- Migration issues
- Types: In-Place versus "Clean and
Pristine"
- Tools
- Understanding SID histories
- What they are
- How they work
- Potential problems with SID histories
- "Re-ACLing" instead of SID histories
- Re-working domain structures
- Consolidating NT 4.0 domains into AD domains with Active Directory
Migration Tool (ADMT)
- Finding ADMT
- Installing ADMT
- ADMT capabilities
- ADMT limitations
- Using ADMT
- How the Global Catalog works to accomplish logons and speed
authentication and what you need to do to keep it running
- Employing sites to control bandwidth problems
- Replication II: how AD replicates in a multi-site world
creating sites, site links, and site link bridges
- Overall design summary and advice
- Remote Support Tools in 2000
It's 3 AM and there's trouble at the office ... but the office is 20 miles
away. Isn't there some way to administer the network from home while
you're still in your pajamas? Third parties have always offered good
remote support tools, but Windows 2000 now includes a wealth of remote control
power. This section explains how to use Windows 2000's built-in tools to
produce "action at a distance," so you can fix that problem and get back to
bed in record time.
- Windows Terminal Server and Services
- How Terminal Services work
- Where it's useful
- Protocol issues: RDP versus ICA
- Licensing: the confusing part
- Using TSAC (Terminal Server Advanced Client)
- Web-based Terminal Services
- Windows Management Instrumentation-based remote tools, including Manage
Computer
- 2000 and Telnet
- Telnet authentication
- What can you do with Telnet?
- What good is the command line, anyway? A summary of Resource Kit
command-line tools
- Telnet on Windows 2000 Professional
- Built-in remote control with NetMeeting 3.0: replacing PCAnywhere
- Platforms that support NetMeeting 3.0
- Setting up NetMeeting
- Activating Net Meeting Remote Desktop Sharing
- Intellimirror: Finally, Tools for Support Staff!
Over the years, Microsoft operating systems have made life easier for
developers with a protected 32-bit programming environment, and easier for
users with a simple-to-use graphical user interface. But there hasn't
been much to make our lives easier as support people until now. This
section explains the strengths and weaknesses of the built-in support tools
included with Windows 2000. (Note: this section does not cover one
Intellimirror technology, the Remote Installation Service, as we cover that in
the later "rollout" section.)
- The support problems that Microsoft sought to solve
- What you'll need to exploit these technologies (W2K Pro, Server, Active
Directory)
- Restricting disk quotas
- How offline files work and how they can make your network faster and
more reliable
- Introducing group policies: GP mechanics
- How policies work: DLL-based versus Registry-based
- Local policies
- Numbers of policies versus numbers of effects (policy planning)
- Policy precedence: sites, domains, OUs
- Policy order within a container: which policy applies first in a
domain?
- Fine-tuning policies: policy filtering
- Altering precedence -- no override and block policy inheritance
- Where policies live: the Group Policy Template and the Group
Policy Container
- Using group policies to protect user data, simplify rollouts and support
roaming users with folder redirection
- Using group policies to distribute software
- Group policy design issues
- Group policy troubleshooting
- Great resource kit tools for policy troubleshooting
- Centralized software deployment
- The problem: you must be an admin to install much software
- The cause: why you've got to be an admin
- The solution: two technologies
- The MSI package format
- The Windows Installer Service
- Controlling the Installer Service with policies
- Publishing versus assigning and the Class Store
- Lower-tech answers: the ZAP file
- Creating MSI packages of your own
- Why some apps won't work under 2000: how Windows File
Protection (WFP) works, and how it sometimes keeps older apps from
functioning
- Working around WFP's limitations the undocumented way with DLL
redirection
- So is SMS dead?
- Windows 2000 Storage
It doesn't get as much play as Active Directory, but Windows 2000's new
storage tools are pretty neat. This section shows you how to use them to
their fullest.
- Basics: FAT32 support, NTFS is now safe for boot drives (with
Recovery Console)
- Distributed File System
(Dfs)
- How it works
- Setting it up
- What you need AD for
- What clients need to access Dfs shares
- Fault tolerant Dfs
- Reparse points get rid of those drive letters (or most of
them, anyway)
- Remote Storage Manager
- Encrypting File System
- How it works
- Setting up recovery agents
- How secure is
EFS?
- Rollout Tools: From Empty Hard Disk To Working Computer in Twenty
Minutes or Less
Machine upgrades and new staffing mean that support people spend a lot of
time putting an operating system and a suite of applications on a
computer. Furthermore, it's unfortunately true that one of the most
effective troubleshooting techniques in the Windows and NT world is "wipe the
hard disk and re-install," which means even more installation time.
Tools like Ghost and Drive Image Pro simplify a rollout task but suffer from
the "every machine needs a unique SID" problem, as well as Microsoft's
reluctance to support any system rolled out with Ghost or Drive Image
Pro. Windows 2000 offers three different technologies intended to
simplify rollouts.
- Scripting Windows 2000 installation: overview
- Scripting installs: building scripts with Setup Manager, then
adding the necessary tweaks
- Doing winnt.sif installs
- Expanding scripts: exploiting the OEMPREINSTALL features to
customize and extend an installation
- Rolling out new applications automatically with WinInstall LE
- Using the script to install extra applications
- Understanding Remote Installation Service: design, procedures,
limitations and strengths
- How RIS works
- Setting up RIS images
- Controlling access to
RIS images
- Undocumented RIS
- Rolling out Server
with RIS
- Using $OEM$ features
with RIS
- Modifying the Client
Wizard to collect more information and roll out servers quickly
- Borrowing from
RIS: how Single Instance Store can help manage
space
- Finding and using Sysprep 1.1
- Useful 2000 Tools
2000 comes with a real wealth of tools and features that haven't gotten
much attention largely because many of us have been focused on the new big
things. This section ends the class with a description of some of the
more useful and often undocumented tools.
- Windows File Protection
- How it protects system files from overwriting
- How to disable it
- How to disable it for just one application
- APCOMPAT solves version number problems for Windows 2000
- Driver Verifier lets you test a driver before you trust it
- Recovery Console
- pathping
- runas: Unix's SU comes to 2000
Certification Preparation
This is not an "exam cram" class. My goal in this class is to help your
network professionals acquire essential job-related skills rather than to focus
on particular testing concepts. Don't misunderstand there's nothing
wrong with exam-focused classes but this class isn't one of them. Its
focus is to help your administrators plan for and learn to manage a 2000/2002-based
network.
Course Materials
The class works from PowerPoint presentations. Clients are strongly
urged to purchase Mastering
Windows 2000 Server from Sybex for students. That's not necessary for
public class students, as they receive the book as part of their course
registration.
Arranging a Course
Please contact our office at (757) 426-1431 or Assistant@Minasi.com to discuss scheduling
and fees. Or, if you don't have enough people for a private class, sign up
for a public class at www.minasi.com/pubsems.htm.
|