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
The domain rename process to change the names of your domains, and you can also use it to change the structure of the domain trees in your forest. This process involves updating the Domain Name System (DNS) and trust infrastructures as well as Group Policy and service principal names (SPNs).
Because the domain rename process involves updating the DNS and trust infrastructures as well as Group Policy and SPNs, a domain rename operation affects every domain controller in the forest. Domain rename is a multistep process that results in updates to the directory and in other side effects. This section provides details about the domain rename process and its interactions with Active Directory Domain Services (AD DS), DNS, Group Policy, and security.
The following conditions and effects are inherent in the domain rename process:
- Domain rename is supported in a forest in which Exchange Server 2003 with Service Pack 1 (SP1) is deployed. However, domain rename is not supported in an Active Directory forest in which Exchange 2000 Server is deployed. When the domain rename tool detects this condition, it will not proceed with the domain rename process.
Domain rename is also not supported in a forest in which Exchange Server 2007 or Exchange Server 2010 is deployed. - Remote management is helpful in the domain rename process. Each domain controller in the forest is contacted individually with the domain rename changes; the changes do not spread across the forest through AD DS replication. This condition does not imply that each domain controller in the forest has to be visited physically by an administrator. However, if you want to rename a domain in a large forest, it is highly recommended that you implement remote management of the domain controllers in the forest. In the event that some domain controllers do not respond during the domain rename process, remote management greatly improves your ability to troubleshoot the problem.
- All domain controllers must either complete the domain rename operation successfully or be eliminated from the forest. The domain rename takes effect even if it is impossible to update some domain controllers in the forest. For the domain rename operation to be complete, every domain controller in the forest must be contacted and updated. If you declare your domain rename operation complete without updating some number of domain controllers because you could not contact them, you must remove all the domain controllers that you could not contact from the forest.
- Each member computer that is joined to a renamed domain must be rebooted twice after all domain controllers are updated. Computers running Windows NT 4.0 must be un-joined and then rejoined to the renamed domain instead of being rebooted.
