Managed Services
- Server Installations, configurations & support.
- Internet/Intranet & E-mail Solutions on Networks.
- VPN Installation & Configuration.
- ADSL Solutions including remote access and working from Home.
- Wireless Network Solutions.
- mySQL Server Installation.
- SharePoint Services.
- E-mail Security Solutions.
- Backup Solutions & disaster recovery options.
- Client & Server Support including 24x7 Facility Management.
- Implement MS security hot fixes.
- Verify Anti virus definitions & live updates.
- Diagnosing possible hardware issues.
- Firewall / security check.
- Complete documentation of Network Configuration.
- Migration: Active Directory, Exchange Servers
Domain Rename
- If you want DNS host names of domain controllers to match a new domain name, you must perform domain controller rename procedures after the domain rename operation is complete. The DNS host names of domain controllers are not changed automatically by the domain rename operation to reflect the new domain name. In other words, the primary DNS suffix of a domain controller will not match the new domain DNS name after the domain has been renamed. Having the host name of a domain controller decoupled from its domain name has no impact on forest service. However, domain controller rename requires a separate, multistep procedure after the domain rename operation is complete.
- The DNS suffix of host names for member computers in a domain that is being renamed might not match the new DNS name of the domain for a period of time. By default, the DNS suffix portion of member computer names is updated automatically when the domain to which the computers are joined changes (as happens when you rename a domain). In general, the period of time during which the DNS name of the domain does not match the DNS suffix of member computer names is proportional to the number of computers in the domain. In some cases, you might want to configure the computers to keep the computer names from being updated automatically.
Domain rename capabilities are available in a Windows Server 2003 forest that has a forest functional level of Windows Server 2003 and above. These capabilities are not available in Windows 2000 Server operating systems.
The structure of an Active Directory forest is the result of the order in which you create domains and the hierarchical names of those domains. Beginning with the forest root domain, all child domains derive their distinguished names and default DNS names from the forest root domain name. The same is true of every additional tree in the forest. The way to change the hierarchical structure of an existing domain tree is to rename the domains. For example, you can rename a child domain to have a different parent or rename a child domain to be a new tree-root domain. In each case, you reposition an existing domain to create a different domain-tree structure. Alternatively, you can rename domains without affecting the structure. For example, if you rename a root domain, the names of all child domains below it are also changed, but you have not created a different domain-tree structure.
The ability to rename domains provides you with the flexibility to make important name changes and forest structural changes as the needs of your organization change. Using domain rename, you can not only change the name of a domain, but you can change the structure of the domain hierarchy and change the parent of a domain or move a domain residing in one domain tree to another domain tree. The domain rename process can accommodate scenarios involving acquisitions, mergers, or name changes in your organization, but it is not designed to accommodate forest mergers or the movement of domains between forests.
