The Information Technology (IT) field is sensitive and needs much caution to be exercised. Different domains have different challenges and potential threats that need to be addressed. When a company buys another company’s domain as well as its general IT system, much has to be done which includes stages of orientation and troubleshooting. Evaluation and debugging of the systems is also necessary. Another important factor to take care of is trust. Trust in the IT field is highly vulnerable and at times volatile. This is because of unknown potential threats, system protocols that are unfamiliar and distance between domain hosts denoted by servers. It is a rather challenging task to manage a merger between two distant IT companies which had individual systems of operation. The two companies in focus here are Crescent Inc. and Quality Corporation where the latter has brought the former to a merger. As such, this paper outlines the different ways that, two merging IT companies can establish trust relationships on their two domains, consolidate core networks and eliminate service duplication.
Building trust relationships between the two company domains is paramount. In the process of building the trust, the information of the companies should remain visible only to the two merging companies. If any information leaks that might result to blackmail as well as loss of the companies’ top operational secrets which give them a competitive advantage in the technology industry. One way of building a trust relationship bearing in mind that Crescent Inc.’s domain is the one being configured for visibility of documents by the two companies, is by creating a referral service to the trusting domain which uses authentication (Microsoft, 2015). It will therefore be necessary to have Quality Corporation develop and assign its domain trust protocol through a secret key. The secret key will be a pass-through authentication which will be to interlink the two domains where there should be an initial referral to the first domain and then a security code that will be needed for synchronizing the two domains for data access.
The second way in which trust relationship can be built is through SID filtering (Microsoft, 2014). This is because the two companies have their domains in different forests. The different forests pose a significant threat to the security of the different domains because authorized parties may unknowing or intentionally cause harm to the same domains. SID filtering therefore develops user authentications for trusted administrators. This helps prevent the administrators elevating any form of potential attacks knowingly or unknowingly. The different levels of domain administrators are grouped categorically and has the principal as the senior most person in the process of domain administration. SID looks at the different authorities of different persons at different levels where when the principal logs on, it selects the resources accessible to the principal alone. Quality Corporation should therefore involve SID filtering when building a trust relationship with Crescent Inc.
Thirdly, the process of building a trust relationship between two domains such as in the case of Quality Corporation and Crescent Inc. requires ping tests (Al-Beruni, 2009). The ping tests are to ensure that proper routing is done. The tests are done from the end of each domain for ensure both ends are functional. However, the ping tests get rid of any firewalls in the systems which might be risky but when the two domains are well interlinked, the firewalls are put in place. The two provided domains have different authority certifications which need engineers of each party to be cooperative with each other to create a seamless creation of a trust relationship. The firewalls stand to prevent unauthorized personnel because they notify the administrator of attempts to hack the system.
Coordinating core network services is essential in the IT merger and can be achieved through the use of a single physical machine to host several SQL server instances. The core services found in Crescent Inc.’s domain will be hosted in Quality Corporations physical machine. This will lead to reduction of management costs, efficiency will be increased, standardization and centralization, and creation of space (Hsueh, Zong, & Arumugam, 2014). Reduction of costs and improvement of efficiency is achieved through the reduction of numbers of machines in the network system which means less maintenance cause, easy management and increased performance which defines efficiency. Standardization and centralization are achieved by eliminating data sprawl. Networks have different databases and consolidating them under one machine increases organization, makes audit of the hardware systems easier and helps make predictable workflows which will be a good thing for Quality Corporation. Space is created through the narrowing down of several machines to one. New and upgraded machines are also acquired for increased performance and occupy less space than old technology machinery which can result to higher performance as well as scalable growth.
The two companies here have distinct active directories (AD’s) that fall under different forests. Individual AD’s have replication of service abilities and when merged the replication is amplified. It can be a disastrous thing that can lead to poor performance of service which included erroneous information. As such a plan that can comprehensively eliminate duplication of service between Quality Corporation’s server and Crescent Inc.’s, is listed as follows: ensure an active local area network (LAN), devise a name for each domain, ensure hardware equipment meet with the standard of the current technologies and are uniform on both ends and lastly assign a potential number of domain controllers.
The LAN enables the different domains to access information faster and with ease due to the close connection a LAN offers. The LAN should also have high speeds where Quality Corporation will have to invest in high speed LAN. High speed LAN helps relay information faster and with less attenuation which at the end limits technology. A name for each domain should be distinctly devised to ease the administration of the given domains. This case has Quality.ad and Crescent.ad domains which the specific companies have already embraced. This will enable responsible control of connections and information from potential administrators. Therefore, replication will be eliminated where Microsoft, 2014 stresses that a reasonable number of persons should be left to oversee the process of domain administration.
Hardware equipment is necessary and needs to be compatible with the given servers. Servers that are matched with their specific hardware exemplify seamless functioning which does not have any replications of service. The hardware equipment should also be updated with current software to eliminate duplication of service which is a bad occurrence.
Conclusively, merging two IT companies is challenging and requires calculated moves such as building trust through pass-through authentication. As a result, Quality Corporation and Crescent Inc.’s domains remain visible to the two of them only. Quality Corporation is able to access documents it needed without any threat as a result of a trust relationship. Eliminating replication of network service is important to ensure physical and virtual space is saved and performance of the merger increased.
Al-Beruni, R. (2009, August 5). How to create an external trust between two seperate domains/forests. Wintel Guru. Retrieved from: https://araihan.wordpress.com/2009/08/05/how-to-create-an-external-trust-between-two-domains/
Hsueh, S., Zong, A., & Arumugam, M. (2014, November 3). Server consolidation guidance. Tech Net. Retrieved from: https://technet.microsoft.com/en-us/library/ee819082%28v=sql.100%29.aspx
Microsoft. (2014, November 19). Security considerations for trusts. Tech Net. Retrieved from: https://technet.microsoft.com/en-us/library/cc755321%28v=ws.10%29.aspx
Microsoft. (2015, April 13). Establishing trust telationships . Tech Net. Retrieved from: https://technet.microsoft.com/en-us/library/cc960593.aspx