Integrating Windows Server 2003 into Existing Domains

If you plan to install Windows Server 2003 servers configured as domain controllers into an existing 70-291 Exam domain, you’ll have to run the Adprep.exe command line utility. This utility is located in the 1386 directory of the Windows 2003 Server installation CD-ROM, You’ll have to run the command adprep /forestprep on your existing Windows 2000 Server domain controller holding the schema operations master role. You’ll have to run adprep /domainprep on the Windows 2000 Server domain controller holding Infrastructure Operations Master role. Be sure to search for articles concerning ADPREP at http://sufport.microsqft.com before you actually run these commands.
When you convert from Windows 2000 mixed or Windows Server 2003 interim functional level to the Windows 2000 native or Windows Server 2003 functional level, keep in mind the following:
Support for pre-Windows 2000 replication ceases. Because preWindows 2000 replication is gone, you can no longer have any domain controllers in your
domain that are not running Windows 2000 Server or later.
You can no longer add new pre-Windows 2000 domain controllers to the domain.
The server that served as the primary domain controller during free 70-291 test questions migration is no longer the domain master; all domain controllers begin acting as peers.
The change in domain functional level is one-way only; you cannot change from the Windows 2000 native or Windows Server 2003 functional level to the Windows 2000 mixed or Windows Server 2003 interim functional level.

Read more on Integrating Windows Server 2003 into Existing Domains…

Security Option Recommendations to Follow When Creating Security Templates

Set to Enabled to prevent access using accounts with no passwords over the network. Of course, on all client Microsoft exam 70-297 computers no account should have blank passwords, and this can be controlled by local security policy. However, if users have local Administra?tor rights, they can change the local password policy. They can change this security option as well, but they might not see a need to because they are only wanting easier local access.
Reduce the attack surface by obscuring the name of this powerful account. Enabling this setting does not change the description of the Administrator account.
Enable this setting to ensure an attacker is not given account names. The last logon name is normally displayed when a user attempts to log on at the console. This scenario provides an attacker with a valid account name; the attacker then only has to guess the password. If no account name is provided, an attacker must guess both the account name and password.
Provide a logon warning prepared by your legal department that identifies the restrictions on logon on this computer. Doing this will not prevent an attacker from logging on if the attacker knows or can deduce an authorized account and password, but it will prove that she was not “invited” in.
Allow Floppy Copy And Access To All Drives And Folders When Using Recovery Console Consider disabling this setting for all client computers. If an attacker can use the recovery console, he can copy the local 70-297 practice test Security Accounts Manager (SAM) and attack it on a computer where he is administrator. He can also copy sensitive files that might be protected otherwise, or access and delete sensitive files. This setting is sometimes enabled to allow technicians an easier way to repair a computer. This might be acceptable for some client systems, especially those that do not store sensi?tive information, but it is not acceptable for systems that require a high security level.

Read more on Security Option Recommendations to Follow When Creating Security Templates…