Windows Server 2003 Active Directory and Network Infrastructure

It is a hierarchical representation of all the objects and their attributes available on the network. It enables administrators to manage the network resources, i.e., computers, users, printers, shared folders, etc., in an easy way. The logical structure represented by Active Directory consists of forests, trees, domains, organizational units, and individual objects. This structure is completely independent from the physical structure of the network, and allows administrators to manage domains according to the organizational needs without bothering about the physical network structure.

Following is the description of all logical components of the Active Directory structure:


Forest: A forest is the outermost boundary of an Active Directory structure. It is a group of multiple domain trees that share a common schema but do not form a contiguous namespace. It is created when the first Active Directory-based computer is installed on a network. There is at least one forest on a network. The first domain in a forest is called a root domain. It controls the schema and domain naming for the entire forest. It can be separately removed from the forest. Administrators can create multiple forests and then create trust relationships between specific domains in those forests, depending upon the organizational needs.


Trees: A hierarchical structure of multiple domains organized in the Active Directory forest is referred to as a tree. It consists of a root domain and several child domains. The first domain created in a tree becomes the root domain. Any domain added to the root domain becomes its child, and the root domain becomes its parent. The parent-child hierarchy continues until the terminal node is reached. All domains in a tree share a common schema, which is defined at the forest level. Depending upon the organizational needs, multiple domain trees can be included in a forest.


Domains: A domain is the basic organizational structure of a Windows Server 2003 networking model. It logically organizes the resources on a network and defines a security boundary in Active Directory. The directory may contain more than one domain, and each domain follows its own security policy and trust relationships with other domains. Almost all the organizations having a large network use domain type of networking model to enhance network security and enable administrators to efficiently manage the entire network.


Objects: Active Directory stores all network resources in the form of objects in a hierarchical structure of containers and subcontainers, thereby making them easily accessible and manageable. Each object class consists of several attributes. Whenever a new object is created for a particular class, it automatically inherits all attributes from its member class. Although the Windows Server 2003 Active Directory defines its default set of objects, administrators can modify it according to the organizational needs.


Organizational Unit (OU): It is the least abstract component of the Windows Server 2003 Active Directory. It works as a container into which resources of a domain can be placed. Its logical structure is similar to an organization's functional structure. It allows creating administrative boundaries in a domain by delegating separate administrative tasks to the administrators on the domain. Administrators can create multiple Organizational Units in the network. They can also create nesting of OUs, which means that other OUs can be created within an OU.
In a large complex network, the Active Directory service provides a single point of management for the administrators by placing all the network resources at a single place. It allows administrators to effectively delegate administrative tasks as well as facilitate fast searching of network resources. It is easily scalable, i.e., administrators can add a large number of resources to it without having additional administrative burden. It is accomplished by partitioning the directory database, distributing it across other domains, and establishing trust relationships, thereby providing users with benefits of decentralization, and at the same time, maintaining the centralized administration.

The physical network infrastructure of Active Directory is far too simple as compared to its logical structure. The physical components are domain controllers and sites.


Domain Controller: A Windows 2003 server on which Active Directory services are installed and run is called a domain controller. A domain controller locally resolves queries for information about objects in its domain. A domain can have multiple domain controllers. Each domain controller in a domain follows the multimaster model by having a complete replica of the domain's directory partition. In this model, every domain controller holds a master copy of its directory partition. Administrators can use any of the domain controllers to modify the Active Directory database. The changes performed by the administrators are automatically replicated to other domain controllers in the domain.

However, there are some operations that do not follow the multimaster model. Active Directory handles these operations and assigns them to a single domain controller to be accomplished. Such a domain controller is referred to as operations master. The operations master performs several roles, which can be forest-wide as well as domain-wide.


Forest-wide roles: There are two types of forest-wide roles:

Schema Master and Domain Naming Master. The Schema Master is responsible for maintaining the schema and distributing it to the entire forest. The Domain Naming Master is responsible for maintaining the integrity of the forest by recording additions of domains to and deletions of domains from the forest. When new domains are to be added to a forest, the Domain Naming Master role is queried. In the absence of this role, new domains cannot be added.


Domain-wide roles: There are three types of domain-wide roles: RID Master, PDC Emulator, and Infrastructure Master.

RID Master: The RID Master is one of the operations master roles that exist in each domain in a forest. It controls the sequence number for the domain controllers within a domain. It provides a unique sequence of RIDs to each domain controller in a domain. When a domain controller creates a new object, the object is assigned a unique security ID consisting of a combination of a domain SID and a RID. The domain SID is a constant ID, whereas the RID is assigned to each object by the domain controller. The domain controller receives the RIDs from the RID Master. When the domain controller has used all the RIDs provided by the RID Master, it requests the RID Master to issue more RIDs for creating additional objects within the domain. When a domain controller exhausts its pool of RIDs, and the RID Master is unavailable, any new object in the domain cannot be created.

PDC Emulator: The PDC emulator is one of the five operations master roles in Active Directory. It is used in a domain containing non-Active Directory computers. It processes the password changes from both users and computers, replicates those updates to backup domain controllers, and runs the Domain Master browser. When a domain user requests a domain controller for authentication, and the domain controller is unable to authenticate the user due to bad password, the request is forwarded to the PDC emulator. The PDC emulator then verifies the password, and if it finds the updated entry for the requested password, it authenticates the request.

Infrastructure Master: The Infrastructure Master role is one of the Operations Master roles in Active Directory. It functions at the domain level and exists in each domain in the forest. It maintains all inter-domain object references by updating references from the objects in its domain to the objects in other domains. It performs a very important role in a multiple domain environment. It compares its data with that of a Global Catalog, which always has up-to-date information about the objects of all domains. When the Infrastructure Master finds data that is obsolete, it requests the global catalog for its updated version. If the updated data is available in the global catalog, the Infrastructure Master extracts and replicates the updated data to all the other domain controllers in the domain.

Domain controllers can also be assigned the role of a Global Catalog server. A Global Catalog is a special Active Directory database that stores a full replica of the directory for its host domain and the partial replica of the directories of other domains in a forest. It is created by default on the initial domain controller in the forest. It performs the following primary functions regarding logon capabilities and queries within Active Directory:


It enables network logon by providing universal group membership information to a domain controller when a logon request is initiated.

It enables finding directory information about all the domains in an Active Directory forest.

A Global Catalog is required to log on to a network within a multidomain environment. By providing universal group membership information, it greatly improves the response time for queries. In its absence, a user will be allowed to log on only to his local domain if his user account is external to the local domain.


Site: A site is a group of domain controllers that exist on different IP subnets and are connected via a fast and reliable network connection. A network may contain multiple sites connected by a WAN link. Sites are used to control replication traffic, which may occur within a site or between sites. Replication within a site is referred to as intrasite replication, and that between sites is referred to as intersite replication. Since all domain controllers within a site are generally connected by a fast LAN connection, the intrasite replication is always in uncompressed form. Any changes made in the domain are quickly replicated to the other domain controllers. Since sites are connected to each other via a WAN connection, the intersite replication always occurs in compressed form. Therefore, it is slower than the intrasite replication.

Setting Up and Securing Your Wireless Network

There are more and more individuals opting to work from home than ever before. The advantages to this are many including avoiding the morning and evening rush hours, being able to spend time with your kids and significant other, and doing everything on your own time. Though the pitfalls are many, the one that I will be focusing on in this article is that of setting up a secure wireless network for your home based business. Right now somewhere out there, there is someone with a receiver waiting to pick up on an unsuspecting person’s wireless local area network. Their hope is to garner some sensitive information that may lead to identity theft, and stolen proprietary business information.

Most businesses owners are not technically inclined, though they may be power users, in general security settings is not one of the first things they want to mess around with in their day to day operations. This makes most wireless LANs a great target for information predators.

Here are some general guidelines to follow in setting up your wireless network. Though it may vary from vendor to vendor, the gist is more or less the same:

1. Setup the wireless access/router point via a wired client.
2. Always change the factory setting password to something difficult for someone to guess.
3. Enable 128-bit Wired Equivalency Privacy (WEP) encryption on both your access point and network card. From time to time change the WEP key entries. If your hardware does not support a minimal of 128 bit WEP encryption, then it may be time to replace this dinosaur. WEP is only a minimal security precaution, which is better than none at all.
4. Alter the factory default SSID on the access/router point to a convoluted difficult to guess string. Initiate your computer to connect to this configured SSID by default.
5. Setup your access point not to broadcast the SSID if available.
6. Block off anonymous internet requests and pings.
7. P2P Connections should be disabled.
8. Enable MAC filtering.
9. Enable firewall on the network router/access point with demilitarized zone function disabled. Enable client firewalls for each computer in the network.
10. Update router and access point firmware as updates become available.
11. Make sure the physical router is hidden so that a random person can’t reset the settings.
12. Position the physical router near the middle of the establishment as opposed to near windows to prevent others outside from receiving the signals.

These and other settings will collectively help prevent any unwanted intrusions on your private data.

Overcoming Small Business Networks Sales Objections

Do you need help overcoming sales objections?

Do you sell computer networks, or other IT-related products and services to small businesses?

This article provides tips and hints so you can be overcoming the most common sales objections heard when selling networks to small business prospects, customers, and clients.

The problem generally begins when you start talking about a network upgrade. Around the time, many small business prospects, customers and clients will dwell on cost.

These small business prospects, customers and clients often neglect to consider the soft costs of not properly investing in a network… such as lost employee productivity when imprudent corners are cut, downtime when fault-tolerance is an afterthought, and service costs from computer consultants when difficult-to-support or "dead-end" solutions are selected primarily because of their low price tag.

No matter how thorough your initial consultation, IT audit, site survey and network design reports, some unforeseen client objections may pop up just before you get the client's authorization to proceed (generally a signed contract and retainer or deposit check).

Why Overcoming Sales Objections is SO Crucial

Because one relatively minor concern might threaten to derail the entire sale, you need to gain the critical business development skills for overcoming sales objections, with some of the biggest small business network deal-closing obstacles.

Empowered with these strategies for overcoming sales objections, you'll be much less apt to get emotional, defensive or just plain annoyed. You can then stay focused on keeping your eye on the ball and figuring out the best way to solve the prospect's or future client's problems …and of course, close the sale. Remember, your company isn't in business to solve prospects' problems; only those of paying clients.

Overcoming Sales Objections: Apathy

I hope you get a good night's sleep before this sales objection rears its ugly head. You need a powerful force to overcome apathy.

If small business decision-makers have an apathetic outlook toward the prospect of implementing a network, your decision-makers might take weeks, months, or perhaps even years before feeling a sense of urgency about your proposed network project.

However, once you discover the roots of this apathy, you'll be better able to push (or at least nudge) the approval process along.

Here's a typical example you'll find in the field: The small business owner sees no problem with their existing peer-to-peer network. One or two seemingly innocuous foul-ups, however, can cause the small business owner to see the "light".

With a Microsoft Windows peer-to-peer network, for example, the "server" seems perfectly reliable until the person working on the PC functioning as the server inadvertently hits the reset button with his or her knee.

If you need to be overcoming more of the common sales objections, you must be very adept and recounting these kinds of cautionary tales with the right timing, delivery and empathy.


Using Network Reliability to Overcoming Sales Objections

PC/LAN network reliability can also get called into question when the user of the peer-to-peer server inadvertently performs an unannounced, unscheduled shutdown and restart because a software setup program prompted a reboot.

With peer-to-peer networks, protecting data is usually also an afterthought. If the peer-to-peer server isn't protected with fault tolerant hard drives, a reliable tape backup drive, a server-class UPS, and updated antivirus software, a peer-to-peer server becomes an accident waiting to happen.

So while any of these factors can turn apathy into your opportunity, sometimes a little divine intervention steps in to help you in overcoming sales objections.

One day a lightning storm and blackout pushes your client's "server" over the edge. When power's restored, the server cannot even boot up to its welcome or logon screen. So now, the small business owner is scrambling with the internal guru at 2 a.m. trying to restore the company's corrupted contact management database, which contains 25,000 records and three years of data.


Fear of Catastrophic Data Loss and Overcoming Sales Objections

Situations such as catastrophic data loss, although horrible tragedies for those affected, are great motivators for combating apathy and overcoming sales objections. All of a sudden, the small business owner becomes extremely receptive to your suggestions about your proposed networking solution, which of course features centralized security and data protection.

Discontinued technical support is another powerful counterforce for overcoming apathy-rooted sales objections, especially when you're talking about vertical, industry-specific software, such as niche applications designed for accountants, attorneys, physicians, realtors, auto body shops and restaurants.

After a certain point, the independent software vendor (ISV) selling vertical, industry-specific software draws a line in the sand and stops providing technical support, annual updates, and patches for older versions of their product.

So if your client is an accounting firm that needs updated tax tables (they'd basically be out of business without them), your client is forced to upgrade the tax software, which often in turn forces an upgrade of the server. This results in a call to your firm to upgrade their server (and several related highly lucrative product sales and service opportunities for your firm), all as a result of the "domino effect" from an ISV calling the shots.

With this kind of scenario, you don't even need to do much of the work in overcoming this sales objection. Your prospect's, customer's, or client's vertical ISV has done the “heavy lifting” so to speak in overcoming sales objections.

So besides fears of unreliable systems and vendor-mandated upgrades, you can also overcome apathy by discussing your prospect's, customer's or client's competition (without naming names, of course). If you work with many small businesses in the same industry, and you're seeing a software or more general technology trend that drastically alters the competitive landscape in your prospect's or client's industry, by all means call this to your prospect's or client's attention, as a means of overcoming sales objections.

The Bottom Line

If you sell and service IT-related products to small businesses, you need to develop your sales skills for overcoming sales objections. This article introduces you to three different major categories of small business IT sales objections and helps you understand simple anecdotal closing strategies for overcoming those sales objections… and most importantly, closing more big-ticket sales.

Copyright MMI-MMVI, ComputerConsultantsSecrets.com, All Worldwide Rights Reserved. {Attention Publishers: Live hyperlink in author resource box required for copyright compliance}

Cisco CCNP / BCMSN Exam Tutorial: The Core Layer Of Cisco's Three-Layer Model

In this section, you're going to be reintroduced to a networking model you first saw in your CCNA studies. No, it's not the OSI model or the TCP/IP model - it's the Cisco Three-Layer Hierarchical Model. Let's face it, just about all you had to do for the CCNA was memorize the three layers and the order they were found in that model, but the stakes are raised here in your CCNP studies. You need to know what each layer does, and what each layer should not be doing. This is vital information for your real-world network career as well, so let's get started with a review of the Cisco three-layer model, and then we'll take a look at each layer's tasks. Most of the considerations at each layer are common sense, but we'll go over them anyway!


Today we’ll take a look at the core layer of the Cisco model.

The term core switches refers to any switches found here. Switches at the core layer allow switches at the distribution layer to communicate, and this is more than a full-time job. It's vital to keep any extra workload off the core switches, and allow them to do what they need to do - switch! The core layer is the backbone of your entire network, so we're interested in high-speed data transfer and very low latency - that's it!

Core layer switches are usually the most powerful in your network, capable of higher throughput than any other switches in the network. Remember, everything we do on a Cisco router or switch has a cost in CPU or memory, so we're going to leave most frame manipulation and filtering to other layers. The exception is Cisco QoS, or Quality of Service. QoS is generally performed at the core layer. We'll go into much more detail regarding QoS in another tutorial, but for now, know that QoS is basically high-speed queuing where special consideration can be given to certain data in certain queues. (You’ll soon find that this is a very basic definition!)

We always want redundancy, but you want a lot of redundancy in your core layer. This is the nerve center of your entire network, so fault tolerance needs to be as high as you can possibly get it. Root bridges should also be located in the core layer.

The importance of keeping unnecessary workload off your core switches cannot be overstated. In the next part of this BCMSN tutorial, we’ll take a look at how the other layers of the Cisco three-part model do just that.

Cisco CCNA Exam Tutorial: Mapping The OSI Model To The TCPIP Model

The OSI model is the model that most networking personnel are familiar with, but to earn your CCNA, you need to know the OSI model, the TCP/IP model, and how the two map to each other.

The four layers of the TCP/IP architecture can be compared to certain levels of the OSI model. It’s important to know what each level of the TCP/IP protocol architecture does, and how these layers map to the OSI model.

The Application Layer of the TCP/IP model performs much the same tasks as the Application, Presentation, and Session layers of the OSI model.

The Transport layer in the TCP/IP architecture is similar to the Transport layer in the OSI model. This layer can use TCP or UDP as well.

The Internetwork layer in the TCP/IP architecture uses IP addresses to determine how packets should be routed. Remember that the OSI model uses IP addresses, or “Layer 3 Addresses”, at the Network layer. The two layers do much the same thing. This layer is also referred to in the TCP/IP model as the Internet layer.

The Network Interface layer in the TCP/IP architecture serves to define the protocols and the hardware needed to actually deliver the data across the network. The Network Interface model does the work of both the Data Link and Physical Layers in the OSI model.

Keeping all this straight can be very confusing when you first start your CCNA studies. Concentrate on the OSI model in your studies, but make sure you know how the TCP/IP model maps to that model and you'll be ready for CCNA exam success!