Introduction to Domain and Forest Trusts

By using Windows Server 2003 domain and forest trusts, service administrators can create or extend collaborative relationships between two or more domains or forests. Windows Server 2003 domains and forests can also trust Kerberos realms and other Windows Server 2003 forests, as well as Microsoft Windows® 2000 domains and Windows NT® 4.0 domains.

When a trust exists between two domains, the authentication mechanisms for each domain trust the authentications coming from the other domain. Trusts help to provide controlled access to shared resources in a resource domain (the trusting domain) by verifying that incoming authentication requests come from a trusted authority (the trusted domain). In this way, trusts act as bridges that allow only validated authentication requests to travel between domains.

How a specific trust passes authentication requests depends on how it is configured. Trust relationships can be one-way, providing access from the trusted domain to resources in the trusting domain, or two-way, providing access from each domain to resources in the other domain. Trusts are also either nontransitive, in which case a trust exists only between the two trust partner domains, or transitive, in which case a trust automatically extends to any other domains that either of the partners trusts.

In some cases, trust relationships are established automatically when domains are created; in other cases, administrators must choose a type of trust and explicitly establish the appropriate relationships. The specific types of trusts that are used and the structure of the resulting trust relationships in a given trust implementation depend on such factors as how Active Directory is organized and whether different versions of Windows coexist on the network.

  • Do you want to become  Real MCSE, CCNA or CCNP certified?
     
  • Do you want to Payless for certification?
     
  • Do you want to finish in 2/3 weeks?

 

 
 
 
 

MCSA : MCSE : MCSE + Security : CCNA : CCNP : Bootcamp : MCSE training : Vibrant MCSE : Vibrant CCNA : Vibrant CCNP : camp :: Home : links : Resources : Ref1 : Ref2

 

CCNA Bootcamps

 

MCSE Boot Camp, CCNA Bootcamps, CCNP Boot camp Certification Training
 
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

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
 

 

How can I change the default location of the i386 folder?

After installing Windows 2000 or XP, if I ever need to add a component to it (like DHCP etc.) it always asks me for the CD, even if I copy the i386 files to my local drive. Can I fix this?

Yes you sure can.  

  1. Open the registry editor and go to

  1. Highlight the Setup folder.

  2. On the right pane, locate the SourcePath.

  3. Double-click the SourcePath and replace the drive letter in the box to C:\ (if you copied the files to your C:\ drive). Make sure it's C:\ and not C:\i386.

  4. Close the registry editor.

  5. If the system ever needs files from the i386 folder, it will automatically look in the C:\i386 folder.

You can also do the trick with Windows 2000 and XP Professional client computers that were installed from a shared folder on your network, but do not copy the i386 folder to the local drive of each computer. Instead, copy the i386 folder to a share located on a network server. Edit the registry for the Windows 2000 or XP Pro machines and make it point to the UNC path of the network server.

Also, if you installed from a RIS server, keep the RIS server running. Your system is smart enough to grab the files from the RIS server when it needs extra files.

This tip works for service packs too. You'll notice at the registry string from step #1 that it says servicepacksourcepath. Extract the SP from the command prompt to a folder on your hard drive using the w2ksp# -x switch, make the path in the registry where you put the files, and you won't have to go fishing for service pack disks again.

 


© Vibrant Worldwide Inc.