Windows Server 2003

1. Click Start, Administrative Tools, and then click DNS to open the DNS console.

2. In the console tree, select the DNS server that you want to create a new DNS zone.

3. From the Action menu, click the New Zone option.

4. On the initial page of the New Zone Wizard, click Next.

5. Select the zone type that you want to create. The options are Primary, to create a new standard primary zone; Secondary, to create a copy of the primary zone; and Stub, to create a copy of zone but for only the NS record, SOA record, and the glue A record.

6. Select the default selected option - Primary zone.

7. To integrate the new zone with Active Directory, and if the DNS server is a domain controller; then you can select the Store the zone in Active Directory (available only if DNS server is a domain controller) checkbox.

8. Click Next.

9. On the Active Directory Zone Replication Scope page, accept the default setting for DNS replication: To all domain controllers in the Active Directory domain. Click Next.

10. Select the Forward lookup zone option on the following page which is displayed by the New Zone Wizard, and then click Next. 1

11. Enter a zone name for the new zone. Click Next. 1

12. The options that you can select on the following page pertain to dynamic updates. The Allow only secure dynamic updates (recommended for Active Directory) option is only available if you are using Active Directory-integrated zones. Click Next. 1

13. Click Finish to add the new zone to your DNS server.

Web server

a pice of jumk you shove up you a@??

It's up to you. People usually have different ip addresses for gateways and DNS/DHCP servers. It's because a separate server is used for gateway.

In Windows Server 2008, unlike previous server operating Systems, there is an additional step that needs to be taken before running DCPROMO to promote the server to Domain Controller and installing Active Directory on it. This step is the installation of Active Directory Domain Services (AD-DS) role on the server.(dcpromo ad-ds) The AD-DS role is what enables the server to act as a Domain Controller, but you will still need to run DCPROMO from the run.

Hello,

If you are talking about server users then SAM is the system file which holds information of users. But this file is in encrypted format and you can not edit it.

You haven't indicated what operating system you are using. For windows, using the 'ipconfig /all' command will show you what the DHCP server address is.

Its a wizard which guides the user through the setup

kindly refer to the link

http://www.commodore.ca/windows/exchange/how_to_setup_exchange_2007_in_2hours.htm

12C3 = 12*11*10/(3*2*1) = 220

its a structure dude, for example there is no example and you have to find that example out to know the example.

did you get it yo

external trust

Use external trusts to provide access to resources located on a Windows NT 4.0 domain or a domain located in a separate forest that is not joined by a forest trust

When a trust is established between a domain in a particular forest and a domain outside of that forest, security principals from the external domain can access resources in the internal domain. Active Directory creates a foreign security principal object in the internal domain to represent each security principal from the trusted external domain. These foreign security principals can become members of domain local groups in the internal domain. Domain local groups can have members from domains outside of the forest.

Directory objects for foreign security principals are created by Active Directory and should not be manually modified. You can view foreign security principal objects from Active Directory Users and Computers by enabling advanced features. For information about enabling advanced features, see To view advanced features.

In domains with the functional level set to Windows 2000 mixed, it is recommended that you delete external trusts from a domain controller running Windows Server 2003. External trusts to Windows NT 4.0 or 3.51 domains can be deleted by authorized administrators on the domain controllers running Windows NT 4.0 or 3.51. However, only the trusted side of the relationship can be deleted on the domain controllers running Windows NT 4.0 or 3.51. The trusting side of the relationship (created in the Windows Server 2003 domain) is not deleted, and although it will not be operational, the trust will continue to display in Active Directory Domains and Trusts. To remove the trust completely, you will need to delete the trust from a domain controller running Windows Server 2003 in the trusting domain. If an external trust is inadvertently deleted from a domain controller running Windows NT 4.0 or 3.51, you will need to recreate the trust from any domain controller running Windows Server 2003 in the trusting domain

a server for a royal or famous person and he watches out for them

Andy Roddick would probably win at tennis, but Harry Callahan would win a gunfight.

The concept of "booting" a machine takes on a different meaning when talking about the virtual world. You will start with a physical machine on which you have installed an operating system. When you boot that machine, the OS loads into memory, takes inventory of all the devices connected to the machine, and runs any routines or applications you have specified.

Using virtual server management software, such as a product from VMware, that runs on the above machine, you will define a virtual machine, or virtual server, to which applications and users connect. The virtual server software controls the virtual server and acts as if it were a physical machine. Booting a virtual server can mean shutting down the virtual server with the vm management tool you use and restarting it.

One advantage to using virtual servers is being able to do maintenance with little to no downtime. With the right software, you can move the application load from one virtual server to another and do your maintenance on the original machine. It is useful to have your virtual servers spread across several physical servers. Should one physical server fail, you can shift the load to other servers and take the failed box offline. Once the server is repaired or replaced, you can start your virtual servers back up again and move the load back.

Depending on the vm software you use, you can specify that the virtual machines come up when you boot the physical machines. Because they will all be competing for the same pool of resources (cpu and disks), make sure to stagger the vms so they all don't try to start up at once. This will also make sure that the right devices have come online before booting certain vms that need those devices.

You can also control the shutdown of virtual machines when you shut down the host OS. Most vms can be saved in their point-in-time state. This is useful if you need to boot the physical machine, for instance, after applying an OS patch.

http://content.dell.com/us/en/enterprise/virtualization

Yes, LDAP exists in both versions.

A. The PTR resource record.

No, it is not.

RemoteApp is available on Server 2008 only.

To access Server2008 RemoteApps you have to use RDP6.x TS Clients. As Server 2003 provides RDP5.x RemoteApp is not available on Server2003.

login to DNS server

Click start->click run-> type cmd

type IPCONFIG /all

this will give you MAC address of server

a. Dig

Root Hints (page 81 of the 70-642 Microsoft Press Book)

Yes it is possible that a forest has one or more domains which have trusts between them