4-4 Project One

docx

School

Southern New Hampshire University *

*We aren’t endorsed by this school

Course

22EW2

Subject

Information Systems

Date

Feb 20, 2024

Type

docx

Pages

11

Uploaded by lunarminded

Report
IT 202 Project One Site Survey Template Complete this template by replacing the bracketed text with the relevant information. Additional details can be found in the Project One Organizational Needs document. Stakeholder Info This section lists the project stakeholders: Chief Information Officer Systems Security Officer Assistant Vice President of Finance IT Project Manager Systems Architect [Megan Miller] Operating Systems Provide approximate number of users who currently use each OS: Windows [30] macOS [3] Linux [7] *If there is additional information required, such as details of the OS version or different OSes being used, include here: [The organization currently uses a mix of operating systems. Most users (30 out of 40) are on Windows 7, with three users on Windows Server 2012 R2 and seven users on Linux RedHat.] Server Determine whether the desktops are on a hardware or cloud-based server. Also specify the version of the OS server. Physical [Insert X and specify version if server is physical.] Cloud-based [Regarding the server for the desktops, it is not explicitly stated whether it is hardware- based or cloud-based. However, given the organization's emphasis on cloud-based applications such as Windows Office 365 and ServiceNow ITSM, it is likely that the server for the desktops is cloud-based] Standard Hardware for Operating System Types Determine the hardware requirements: 1
[For Windows 7 and Windows Server 2012 R2, the standard hardware requirements include a 1 GHz or faster processor, 1 GB of RAM for 32-bit systems and 2 GB of RAM for 64-bit systems, at least 16 GB of available hard disk space for the operating system, a DirectX 9 graphics device with WDDM 1.0 or higher driver, and a display with a minimum resolution of 800x600 pixels. For Linux RedHat, the hardware requirements can vary depending on the specific distribution and version being used. The hardware requirements for Linux RedHat will need to be determined based on the specific distribution and version being used. However, in general, Linux distributions typically have lower hardware requirements compared to Windows operating systems. For the proposed operating systems, it is recommended to have standard hardware that meets or exceeds the following requirements: For Windows 10, the recommended hardware requirements include a 1 GHz or faster processor, 2 GB of RAM for 32-bit systems and 4 GB of RAM for 64-bit systems, at least 32 GB of available hard disk space for the operating system, a DirectX 9 graphics device with WDDM 1.1 or higher driver, and a display with a minimum resolution of 800x600 pixels. For Linux Ubuntu, the recommended hardware requirements include a 2 GHz dual-core processor, 4 GB of RAM, at least 25 GB of available hard disk space, a graphics card capable of 1024x768 resolution, and a sound card. Based on the sources, Linux is a popular choice for server operating systems in terms of security and compatibility with various software. Based on the site survey, it is recommended to continue using Linux as the server operating system.] Network Connection Determine whether the network is wired or wireless. Select one of the following: Wireless [X, Assignment didn’t specify, but if I am picking, I would like to pick wireless] Applications Determine what applications are already on-site and/or which applications employees want to use, as well as which OS supports that application. Indicate by selecting below: MS Office [X, Windows] Adobe Desktop Publishing Software [X, Windows and Mac OS support this application] Corel Desktop Publishing Software [X, Windows and Mac OS support this application] Oracle or SAP [X, Windows and Linux support these applications] Virus Protection [X, Windows, Mac OS, and Linux have various antivirus software options available] PeopleSoft HR [X, Windows, Mac OS, and Linux have various antivirus software options available] ServiceNow [X, Windows, Mac OS, and Linux support this application] SolarWinds [X, Windows, Mac OS, and Linux support this application] SAP [X, Windows and Linux support this application] 2
TalentLMS [X, Windows, Mac OS, and Linux support this application] LogRhythm [X, Linux, Windows both support LogRhythm] Splunk [X, Linux is the OS that is best to support this, there is a legacy mode that does work for Windows but not as efficient] Utipro [X, Windows, and Mac] ICIMs Hiring Suite [This is web based and not exclusive by OS] 3
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help
Systems Architect Name: [Megan Miller] Date: [11/22/2023] Proposal I. Desktop Footprint Proposal: To optimize our desktop environment, I have assessed your current system and identified which desktop systems require upgrading. This assessment involved evaluating any other operating systems in use within our organization. By understanding the existing desktop setup, we can create a plan for upgrading and ensure a seamless transition for all users. When upgrading the operating systems, it's important to consider user readiness. In the past, deploying Windows 7 had complex options for joining domains and setting up accounts that were great for developers but challenging for other users. To make future upgrades easier, all users should have standardized hardware and applications across departments. Empowering users and maintaining productivity is crucial during rapid deployment, with features like rollback scenarios and self-service capabilities. Remote users need special attention as they constitute a significant portion of employees in most organizations. It is vital to consider the needs of remote users, who may have varying internet connections. Approximately one-third of our full-time employees are remote users, and another third may be remote at any time during the deployment. To ensure a successful upgrade process, it is essential to consider the specific applications used by each department within the organization. The organization currently uses a mix of operating systems. Most users (30 out of 40) are on Windows 7, with three users on Windows Server 2012 R2 and seven users on Linux RedHat. The IT department relies on software applications such as SolarWinds Server and Application Monitor, SolarWinds Storage Resource Monitor, and SolarWinds Virtualization Manager, as well as Windows Office 365, Adobe Acrobat Pro, and ServiceNow ITSM for ticketing system. The Finance department utilizes SAP for accounting and finance, as well as Windows Office 365. The Training department relies 4
on Windows Office 365, Adobe Captivate Prime LMS, Adobe Acrobat Pro, and TalentLMS for corporate learning management. From the information gathered, it is recommended that the organization select and implement Windows 10 as the operating system for its desktop systems for most of the company. Additionally, it should be noted that the employees in each department rely on certain software applications for their daily tasks. To ensure smooth operations and productivity, it is crucial to have standardized hardware and applications for each department outside of the IT department. For the proposed operating systems, it is recommended to have standard hardware that meets or exceeds the following requirements: For Windows 10, the recommended hardware requirements include a 1 GHz or faster processor, 2 GB of RAM for 32-bit systems and 4 GB of RAM for 64-bit systems, at least 32 GB of available hard disk space for the operating system, a DirectX 9 graphics device with WDDM 1.1 or higher driver, and a display with a minimum resolution of 800x600 pixels. For Linux Ubuntu, the recommended hardware requirements include a 2 GHz dual-core processor, 4 GB of RAM, at least 25 GB of available hard disk space, a graphics card capable of 1024x768 resolution, and a sound card. For Linux RedHat, the hardware requirements can vary depending on the specific distribution and version being used. The hardware requirements for Linux RedHat will need to be determined based on the specific distribution and version being used. However, in general, Linux distributions typically have lower hardware requirements compared to Windows operating systems. I. Recommending an OS while Considering the Alternatives Based on the analysis of the organization's current desktop environment and considering the potential risks and vulnerabilities, it is recommended to upgrade the desktop systems to Windows 10. This operating system provides robust security features and regular updates, which can help mitigate the risk of OS-based attacks. Additionally, Windows 10 offers improved compatibility with the organization's existing software applications, ensuring a smooth transition and minimal disruption to operations. 5
As part of the desktop upgrade process, it is also important to explore alternative operating systems that may be suitable for the organization's needs. This could include investigating the benefits and drawbacks of different operating systems, such as macOS, Ubuntu, or other Linux distributions. Based on the information provided, it is recommended that the organization consider migrating to Windows 10 as the primary operating system for their desktop systems. This recommendation is due to most of the desktop systems already running Windows 7 and upgrading to Windows 10 would provide a more modern and secure operating environment. Additionally, Windows 10 offers compatibility with a wide range of software applications commonly used in various departments, including Microsoft Office 365, Adobe Acrobat Pro, and SAP. Furthermore, Windows 10 provides a familiar user interface for employees, minimizing the need for extensive retraining. It is recommended that the organization implement a standardized hardware and application environment for each department. This will ensure consistency across the organization and simplify future upgrades. II. Geographical Distribution of Desktop Computers When considering the geographical distribution of desktop computers within the organization, it is important to consider the needs of remote users. As mentioned in the previous section, a significant portion of the organization's employees are remote users either full-time or part-time. These remote users may have varying internet connections, some with good connectivity and others with metered connections. To ensure a smooth deployment and adoption of the new operating system, it is crucial to provide remote users with the necessary resources and support. This includes ensuring that they have access to the same standardized hardware and applications as their colleagues in the office. To address the needs of remote users, it may be beneficial to consider a cloud-based solution for the operating system for those who will be working remote. A cloud-based solution would allow remote users to access their desktop systems through a browser and the internet without the need to install the operating system locally. III. Risk and Vulnerability Assessment 6
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help
Before proceeding with the desktop system upgrade and OS migration, it is important to conduct a risk and vulnerability assessment. To conduct a thorough risk and vulnerability assessment before implementing the new operating system. My evaluation is made up of the following steps: i. Evaluate the current security measures in place and identify any vulnerabilities or gaps that need to be addressed. This may include outdated antivirus software, lack of encryption protocols, or weak password policies. ii. Assess the compatibility of existing software applications with the new operating system. This evaluation will help identify any potential issues that may arise during the migration process and ensure that all necessary updates or replacements are made before implementing the new OS. iii. Analyze the network infrastructure and identify any potential risks or vulnerabilities that could impact the performance and security of the new operating system. This may include outdated routers or switches, weak authentication protocols, or insecure wireless networks. iv. Consider the potential risks and vulnerabilities associated with using a cloud-based operating system. This can include assessing the security measures and protocols in place within the cloud provider's infrastructure, evaluating the reliability and availability of the internet connection for remote users, and considering the potential risks of data breaches or unauthorized access to sensitive information. IV. On-Premises vs Cloud-Based Systems: A Comparative Analysis My recommendation would be to go with a hybrid of using both On-Premises and Cloud Based Systems. Data Privacy and Compliance would be the key factor for using On-Premises with some of the desktops. By choosing to deploy on-premises, the organization can keep sensitive data within their own infrastructure and enforce their security protocols. This aligns with the organization's preference for maintaining control over sensitive data. User Experience and Performance with an on-premises deployment, users can enjoy faster access to applications and resources without relying on internet connectivity or potential limitations of cloud-based infrastructure. Alternatively, the organization should 7
consider implementing a cloud-based deployment for some of the desktops opting to go hybrid and have both on premise and cloud-based systems depending on the specific needs and requirements of each department. On premise being required more for departmental applications that involve sensitive data and require faster access, while cloud-based deployment can be considered for applications that are not as sensitive and require flexibility and scalability. VII. Implementing the Recommended Operating System The migration should be carried out in an on-premise environment to ensure full control and flexibility over the desktop systems. Cloud-based options can also be considered for certain departments or applications, such as Windows Office 365 for finance and training departments. Additionally, the organization should consider upgrading any non-Windows OSes from the IT department to ensure uniformity and ease of management. Given the complexity of the enterprise organization and the current use of Windows 7 in most computers, upgrading to Windows 10 would be a logical choice. To implement the recommended operating system, the organization should follow a structured deployment plan. This plan should include the following steps: i. Migration Strategy: Develop a detailed migration strategy that outlines the sequence of upgrades, prioritizing critical departments or users. Consider factors such as user readiness, empowering users, and maintaining productivity during the migration process. ii. Testing and Pilot Deployment: Before executing a full-scale deployment, perform testing and pilot deployments on a small subset of desktop systems. This will help identify and address any issues or compatibility issues that may arise during the migration process. iii. Deployment Phases: Divide the deployment into phases to manage the process effectively. Start with a small number of desktop systems and gradually scale up to ensure a smooth transition. 8
iv. Training and Support: Provide adequate training and support to users during the migration process. This will help ensure a smoother transition to the new operating system and minimize disruption to daily operations. v. Data Migration: Develop a plan for migrating data from the old operating system to Windows 10. This may involve backing up and transferring files, settings, and applications to ensure a seamless transition for users. vi. Systems based Security and Vulnerability Assessment: Conduct a thorough security and vulnerability assessment to identify any risks or vulnerabilities in the desktop environment. Address any security gaps and implement appropriate measures to mitigate these risks, such as updating antivirus software, enabling firewall settings, and implementing user access controls. vii. Backup and Disaster Recovery: Implement a robust backup and disaster recovery strategy to ensure the safety of important data during the migration process. This includes regular backups of data and systems, as well as testing the recovery process to ensure that critical information can be restored in the event of a failure or data loss. Recommendation: Based on the information provided, it is recommended to migrate the desktop systems to Windows 10. Windows 10 offers enhanced security features, improved performance, and compatibility with the latest software applications. 9
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help
References Li, H., Guo, Y., Sun, P., Wang, Y., & Huo, S. (2021). An optimal defensive deception framework for the container‐based cloud with deep reinforcement learning. Iet Information Security , 16 (3), 178–192. https://doi.org/10.1049/ise2.12050 Babu, S. R., Kulkarni, K. G., & Sekaran, K. C. (2014). A generic agent based cloud computing architecture for E-Learning. In Advances in intelligent systems and computing (pp. 523– 533). https://doi.org/10.1007/978-3-319-03107-1_58 Morris, A. (2022, December 20). Windows 10: Should your small business upgrade to Microsoft’s brand new OS? AllBusiness.com. https://www.allbusiness.com/windows-10- should-your-small-business-upgrade-to-microsofts-brand-new-os-23807-1.html Muchmore, M. (2023, January 9). Windows, MacOS, Chrome OS, or Linux: Which operating system is right for you? PCMAG. https://www.pcmag.com/picks/windows-vs-macos-vs- chrome-os-vs-ubuntu-linux-which-operating-system-reigns Yadav, A. K., Ritika, & Garg, M. L. (2019). Monitoring based security approach for cloud computing. Ingénierie Des Systèmes D’information , 24 (6), 611–617. https://doi.org/10.18280/isi.240608 10
11