MCSE Boot Camp Training

2.The Seven OSI Model Layers"Please Do Not Throw Sausage Pizza Away" - as told by Gordo
OSI Layer     Function
*Application Layer   Serves as a window for applications to access net services. Handles general network access, flow control and error recovery.
*Presentation Layer  Layer is the network's translator. The redirector operates here. Determines format for data. Responsible for protocol conversion, translating and encrypting data, and managing data compression.
*Session Layer      Allows applications on two PC's to connect and establish a session. Provides synchronization between communicating computers.
*Transport Layer Responsible for packet handling. Ensures error-free delivery. Repackages messages, divides messages into smaller packets, and handles error handling.
*Network Layer      Responsible for addressing, determining routes for sending, managing network traffic problems, packet switching, routing, data congestion, and reassembling data.
*Data Link Layer Sends data frames from network layer to physical layer. Packages bits to frames.
*LLC- Manages link control and defines SAP's (Service Access Points).
*MAC- Communicates with adapter card.
*Physical Layer     Transmits data over a physical medium. Defines cables, cards, physical aspects.
Additional notes:
*LLC - (Logical Link Control) Upper sublayer of DLL - manages DL communication and defines the use of logical interface points - defined by 802.2
*MAC - (Media Access Control) Lower sublayer of DLL - provides shared access for the NIC Physical layer - is responsible for delivering error-free data between 2 computers - defined by 802.3, 802.4, 802.5, and 802.12

 

MCSE Bootcamp Training : Free MCSE

MCSE Bootcamp Training : Free MCSE Training

MCSE Bootcamp Training : Microsoft MCSE

MCSE 2003 Bootcamp Training : Microsoft MCSE 2003 Training

MCSE Bootcamp Training Books

MCSE CCNA CCNP Bootcamp Training

MCSE Braindumps

MCSE Certification

MCSE Exams

Free MCSE Bootcamp Training : Microsoft MCSE Training Free

MCSE, MCSE Bootcamp, CCNA Training, CCNP Certifications, MCSE Training Boot camps, MCSE Jobs

MCSE Bootcamp certification Training

MCSE Bootcamp Training : Microsoft MCSE Training Online

MCSE Bootcamp Training : Microsoft MCSE Online Training

MCSE, MCSE Bootcamp, MCSE Training, Microsoft MCSE Boot Camp Training, CCNA, CCNP, certifications

MCSE Bootcamp Training : MCSE Training, MCSE boot camp Practice Exams

MCSE Bootcamp Training : MCSE Practice Tests

MCSE Bootcamp Training : Microsoft MCSE Training Requirements

MCSE Bootcamp Training : MCSE Resume

MCSE Bootcamp Training : MCSE Salary

MCSE Bootcamp Training : MCSE Self Paced Training Kit Boot Camp

MCSE Bootcamp Training : MCSE CCNA CCSA CCNP Study Questions Training

MCSE Bootcamp Training : MCSE CCNA CCNP Exam Study Guide / Training

MCSE Bootcamp Training : MCSE Study Guide

MCSE Bootcamp Training : MCSE Test

MCSE Bootcamp Training : MCSE Testing

MCSE Bootcamp Training : Microsoft MCSE Training

MCSE Bootcamp Training : Microsoft MCSE Training Kit

MCSE Bootcamp Training : MCSE Training Video : UK, USA, Japan

MCSE Bootcamp Training : MCSE 2000 and MCSE 2003 Training

MCSE Bootcamp Training : Microsoft MCSE Training

MCSE Bootcamp Training : Training MCSE

MCSE Bootcamp Training : MCSE Certification Exam Training : Windws 2000 MCSE

 

 

MCSE Bootcamp Training - Microsoft MCSE certification

 

MCSE Boot Camp, CCNA Bootcamps, CCNP Boot camp Certification Training

MCSE Guide

Free MCSE
Free MCSE Training
MCSE
MCSE 2003
MCSE Books
MCSE Boot Camp
MCSE Brain dumps
MCSE Certification
MCSE Exam
MCSE Free
MCSE Jobs
MCSE Logo
MCSE Online
MCSE Online Training
MCSE Practice
MCSE Practice Exams
MCSE Practice Tests
MCSE Requirements
MCSE Resume
MCSE Salary
MCSE Self Paced Training Kit
MCSE Study
MCSE Study Guide
MCSE Study Guides
MCSE Test
MCSE Testing
MCSE Training
MCSE Training Kit
MCSE Training Video
MCSE Windows 2003
Microsoft MCSE Training
Training MCSE
Windows 2003 MCSE

 

 

Method #2 - By using Netdom.exe

This method is considered by most professionals to be much safer and better than the first method. By using the Netdom.exe tool, you ensure that there is little or no disturbance for the domain and client operations.

Important: To rename a domain controller using the Netdom.exe tool, the domain functional level must be set to Windows Server 2003.

In order to use Netdom.exe you must first install the Windows Server 2003 Support Tools. Double-click the Suptools.msi file found on the \Support\Tools folder on the installation CD (also see Download Windows 2003 SP1 Support Tools
).

To rename a DC with the name from SERVER101 in the DPETRI.NET domain to ZEUS follow the next steps:

  1. Open Command Prompt and type:

 

This command will update the service principal name (SPN) attributes in Active Directory for this computer account and register DNS resource records for the new computer name. The SPN value of the computer account must be replicated to all domain controllers for the domain and the DNS resource records for the new computer name must be distributed to all the authoritative DNS servers for the domain name. If the updates and registrations have not occurred prior to removing the old computer name, then some clients may be unable to locate this computer using the new or old name.

You can verify the new name was indeed added to the computer object by viewing it through Adsiedit.msc (like Netdom.exe, installed when you install the Windows Server 2003 Support Tools). Navigate to the computer object and right-click it. Select Properties:

 

Scroll down in the list of available attributes till you reach the attribute called msDS-AdditionalDnsHostName:

 

Notice that the new name should appear in the attribute's properties.

  1. Ensure the computer account updates and DNS registrations are completed, then type:

 

Again, you can inspect the change with Adsiedit.msc. Scroll down in the list of available attributes for the computer object (notice how the server now appears with the new name) till you reach the attribute called msDS-AdditionalDnsHostName:

 

Notice that the old name should appear in the attribute's properties.

  1. Restart the computer.

  2. From the command prompt, type:

 

  1. Make sure that the changes have successfully been replicated to all the DCs.

Renaming a domain controller requires that you first provide a FQDN as a new computer name for the domain controller. All of the computer accounts for the domain controller must contain the updated SPN attribute and all the authoritative DNS servers for the domain name must contain the host (A) resource record for the new computer name. Both the old and new computer names are maintained until you remove the old computer name. This ensures that there will be no interruption in the ability of clients to locate or authenticate to the renamed domain controller, except when the domain controller is restarted.