RavenTech, LLC will migrate all clients systems currently running the Microsoft Windows XP Operating System (OS) to a Linux-based OS. The migration will occur in discrete, well-defined, stages to allow for testing, validation and rollback as required. Users will experience the minimum amount of productivity interruption required to complete the migration. The overall migration plan consists of 7 steps: 1) Procedure Preparation, 2) Domain Modification, 3) User Data Migration, 4) Network Modifications, 5) Hardware Upgrades, 6) Linux OS Install & Migration and 7) XP OS Removal & Clean-up Tasks (Table 1). RavenTech management would like the migration to occur with minimal risk and cost to the business, however is willing to allocate a reasonable …show more content…
There are a total of 500 clients systems owned by RavenTech, LLC. They are evenly distributed between desktops and laptops, and between Windows 7 OS and Windows XP OS machines (Table 2). The Windows 7 machines are not being modified at this time, and will be primarily unaffected by this migration. The desktops and laptops that are currently running Windows XP were new at the time of purchase. While the hardware is older than the Windows 7 machines, it is still functional, and parts for these machines are still easily obtainable for the near future. The Windows XP computers have an Intel Core 2 Duo E6400 processor in the desktop systems, and a P8400 processor in the laptop systems. The desktops and laptops each have 2GB DDR3 1066MHz RAM, and can be upgraded to at least 8GB DDR3 RAM. The laptops have a port for connecting an external monitor. Excluding the OS, RavenTech uses software applications that are available for Windows and Linux, or are cloud-based Software as a Service (SaaS), so employee training on new productivity software will not be required. The company uses Virtual Local Area Networks (VLANs) and private IP space on the internal network. A minimum of one desktop XP machine …show more content…
The server specialists will create a full backup of the Domain Controller (DC) and all other servers on the network to an off-network storage medium. This will ensure that there is a known good configuration to roll back to incase issues arise due to configuration changes. The Dynamic Host Configuration Protocol (DHCP) settings will be adjusted to provide network interface configuration information to hosts detected on the planned Linux VLAN. The DNS server configurations do not need to be changed, as the DNS server will respond to any DNS query it receives via IP. The servers will need to install the “Server for NFS” role (and associated feature), and modify the existing file shares to use the Network File System (NFS) with Kerberos v5 authentication and privacy and the Server Message Block (SMB) protocol (Microsoft, 2012). This will allow the Linux clients to securely access the same file shares that the Windows 7 clients are accessing. Some modifications to the AD database will be required to support resolving user and group names (Windows user properties) to User ID (UID) and Group ID (GID) (Linux user properties) (Banck, 2014). This entails adding certain Lightweight Directory Access Protocol (LDAP) attributes for groups and
In our world today there are so many different types of operating systems as well as features and applications that run on them. There are many similarities as well as differences between Windows 7, Linux and Windows Server 2008. The one enduring similarity is that all three are intended to be utilized as an operating system is meant to.
The church required that the workstations be replaced as they are no longer supported by the hardware manufacturer. The workstations operating Windows XP can no longer receive a software patch and are no longer supported by Microsoft. These workstation are extremely vulnerable to attack. Wireless connectivity through the church campus was a requirement as the church was to be able to access information from multiple locations. Setting up hardware to maintain and secure all data and information. The sponsor liked our team’s suggestion to migrate them from a peer to peer network environment to a server domain environment. With all of these upgrades and updates, network security needed to be addressed so the installation and setup of a firewall became a requirement. The
Twenty systems will initially be imaged for Linux and configured to run on the existing network environment. A testing group will be compiled from departments across the organization to determine how the operating system meets user needs in various departments. After a ten day testing period, any problems identified can be resolved as required to support a seamless transition. The phased migration can then be completed 50 systems at a time, cycling the Linux systems in and the XP systems out. As the XP systems are collected, Linux will be installed on them to continue with the phased concept. Diagram B displays how the systems will be tested, configured and distributed. Additional factors need to be taken into consideration for this project
The hospital’s administrative network consists of Apple iMACS and thin computers that use 1000Base T with CAT 6 cables. All work stations belonging to Executive Management has Apple iMAC computers with 24” monitors, 2.4 GHz speed, 2 GB RAM, and a 500 MB hard drive. Human Resources, OPNS, and the Finance Senior Managers have Apple iMACS with 20” monitors, 2 GHz speed, and a 350 MB hard drive. All of the systems have OS virtualization and use the MAC Operating System X, Leopard, and Windows XP. OS virtualization allows separate, isolated virtual environments to be used on a single server. The MAC Operating System X is a UNIX system that is both simple and powerful. Leopard further enhanced the system by making it faster and more reliable. Windows XP is a product of Microsoft but it is able to be installed on any MAC using a native version of Microsoft Office. This way users are able to create documents using MS Word, make presentations using PowerPoint, and
at a time,they are commonly connected to a LAN and run multiuser operating system.The resources which has to be managed
MHS is seeking proposals for converting the existing desktop PC’s currently configured as a “thick client” into a “thin client environment”. The back end infrastructure will need to be part of this proposal and the overall configuration. a.
There are various types of equipment that the company should look for when considering this network. The first item to look at when considering equipment is the Operating system and software that we would need. Next, the group took into consideration the type of server the company needs to make this network a reality. Another thing that we looked at is the possibility of having ThinClients over regular desktops for all workstations. Of course, it was taken into consideration that some employees would not want ThinClients. So, we show the type of tower we plan to place into those spaces, along with any peripheral device for both. Then, we will look at the network devices that will go into each building that include switches, routers, repeaters, hubs, and wireless access points. Finally, the group will note guidelines for choosing a local ISP at each site. Each Item outlined helps to build a network based on the specifications given by the company.
Windows 7, 8, 8.1 64bits. These types of an operating system have good performance and new features. These are the latest operating systems and same familiar OS should be used. These OS will be used in every client PC’s in the department.
The company’s servers and most of their computers were purchased over a decade ago and are creating issues with the newer properties thin clients ability to communicate with the network. ULH’s servers are located within their headquarters in California and are still operating on Windows NT 3.51. The company wants to increase the manageability and performance of the network in addition to being able to infinitely upgrade the network as growth requires. Currently, ULH is in a position where their IT network is creating a bottle neck to their growth. The network was functioning sufficiently when they just had 2 properties all operating on the same outdated operating systems, however acquisition of newer properties has created many issues with network functionality.
corporate desktops and notebooks? how can the success of opteron in the server segment be
We have a choice of using either Windows or Linux for operating system, since they are already preloaded on the servers we are purchasing. In making our decision, we had to first take a look at the features that each system provided and which one would be the best for what we are doing.
In conclusion, the report proposes that any migration path is applicable for migration. The only element that must get considered becomes the merits associated with each case. The resource availability is another factor that determines the path that must get followed. The complexity and scope of the cases must get dealt with during the migration
In the workplace today there are many different options for operating systems be they providers of server related services or end-user desktops there is a different Linux distribution for many different applications. There are also a number of advantages and disadvantages to adding onto or switching network operating systems within a company. In the following pages I
On-time guarantee. We know how long your migration will take because we have an unparalleled depth of expertise in data migration. We are so sure of the accuracy of our quotes, we are the only vendor to offer an On-time guarantee.
Three operating systems discuss in this paper each have their advantages and disadvantages from one another. The biggest advantage for Microsoft is the widespread use and compatibility with most every type of program out there. If you 're a Linux fan then you appreciate not only the price which is usually free but also that it is