The History Of The System Management

Published Date: 02 Nov 2017

Fundimental approach behind thin client:

Instead of running applications locally applications can be run from a centralised point.

Works by delivering screen updates and i/o input and outputs to client

Thin clients can cut costs considerably

Simplified software deployment rapidly reduces roll-out costs.

Reduced power consumption directly lower energy and lowers cooling requirements

Thin clients remove the need for remote servers

No desktop configuration needed

No redesigning and integrate email architectures

It is almost plug and play

This can outsource desktop management, only needing remote access into servers

Thin systems genrally wont have floppy discs or cd drives or be able to install applications. (positive/negative)

Server security and resilience is of

Thin client Evolution (15 marks)

Disscuss benifts of VDI (10 marks)

Broaden Discussion of VDI, include negatives (10 marks)

Compare Contrast VDI vs Thin Client

-Task 2

Company wanting to move from XP Pro to Win 7 Pro or Enterprise

There are two methods:

Method A: Symantec 2.4 ghost solution

According to (SYMANTEC, 2011) The Ghost console is a windows server based application, this allows for remote management of client PCs from a centralised location. The application is fully windows 7 capable and has numerous features to help deployment of windows 7. Ghost 2.4 features a simple and familiar GUI, states (SYMANTEC, 2011) allowing for ease of use, with the added ability of changing how your resources are displayed, between list, thumbnails, and folders. Within the GUI there is a task status area. (SYMANTEC, 2011) States this area provides the user with information and status of tasks during the different steps within deployment.

Some of the basic preferences and storage options that can be accessed using (SYMANTEC, 2011) Ghost 2.4’’, are the options to display, start and stop log messages .when starting or finishing a task an adjustable task log (defaulted to thirty days) which can be viewed from the console and the ability to change the storage locations, for Backup Images and user Migration package. Ghost 2.4 includes data throughput options, which allows control of how much bandwidth is used. Such as multicast, unicast and directed broadcast. (SYMANTEC, 2011) Recommend the use of multicast, as this allows for the transfer of files to a number of client computers simultaneously and minimise impact to bandwidth.

(SYMANTEC, 2011) Ghost 2.4 applications allow management and tasks to be executed on the Client PC. The client software would have to be installed on every Client PC that is intended for the Windows 7 deployment. This is as simple as inserting the supplied software Disc and selecting install (SYMANTEC, 2011) Ghost, then install Ghost console client. (SYMANTEC, 2011) Setup wizard is loaded, after accepting the user agreement an option window appears. A server then needs to be identified that is running the Ghost 2.4 console. According to (SYMANTEC, 2011) doing this allows for a connection to been created between client’s pc and the Ghost 2.4 console, this allows for tasks to be executed on the Clients PC

Ghost 2.4 inventory features, is paramount to the deployment of Window 7. (SYMANTEC, 2011) States this feature allows for planning and identifying which client PC on the network are Windows 7 compatible and creates reports of Windows capable Client PCs. Ghost 2.4 implements this by creating "Dynamic Machine Groups". Specifically there are predefined filter templates for the dynamic groups that can mark out the minimum requirements for Windows 7 PCs , Similarly another feature that lets more information be collected into a report this is called ‘View’ this allows hardware specifications to be displayed within the report. Furthermore after creating a dynamic group the non-capable Client PCs can be isolated from the Windows 7 capable PCs, states (SYMANTEC, 2011).

Before an image can be created a placeholder must be created on the Server where the Windows 7 Image will sit .Another feature of (SYMANTEC, 2011) Ghost 2.4 allows you to select the properties which you want to set for the new image.  Subsequently an image definition is then created including a name, location and description of the Ghost console. In addition the image create task is executed which selects the computer from which to take the image, specifies the image definitions that is to be associated with it and sets the network and Sysprep parameters. Ghost 2.4 then captures the image from the model client computer; the image is then transferred back to the Ghost Console states (SYMANTEC, 2011).

Sysprep is a (MICROSOFT, 2005) utility that you can use alongside Ghost 2.4 to make the cloning process more versatile by making cloning possible among computers with different hardware setups. Even though (SYMANTEC, 2011)claims to have full Sysprep support there is still the need to create a unattend file using "Windows System Image Manager", (MICROSOFT, 2005).

Once all this is done an image is ready to be created, this is done by clicking new task icon, sequentially opening another properties window, and within in this window it will ask you to specify the source Client PC from which the Windows 7 image is to be captured. Before capturing select the system resource file that was created earlier, this allows for any editing needed to Sysprep such as disabling Bluetooth etc., states (SYMANTEC, 2011). Click, execute and Ghost 2.4 will start creating an image.

On the Clients PC a warning message will appear warning that (SYMANTEC, 2011) Ghost 2.4 Client application is going to load on the Client PC. Once the application executes a status bar which indicates how much of the image is captured. As soon as the image is captured it is then available on the Console. Ghost 2.4 Console Application also has the ability to explore the captured image.

(SYMANTEC, 2011) Boasts about a feature of Ghost 2.4 called user migration; this refers to capturing user’s personal files and settings and restoring them to a new Client PC or to the same Client PC after installing a new operating system. (SYMANTEC, 2011) Ghost 2.4 allows a template for migration to be created. Once created another window opens giving a list of programs (SYMANTEC, 2011) explains that u can include or exclude in the migration package also allowing folders and shortcuts to be imported. This feature stops any ‘valuable’ personal data from being lost and stopping, ‘non-valuable’ files from being imported by excluding there file extensions, for example *mp3.

(SYMANTEC, 2011) Provides a properties window for user migration, this window allows for the migration package to be saved on the Client PC, saving bandwidth, or transferring to the Console. Once this is configured pressing execute will start the user migration capture to be performed. If the migration package was imported to the Console the properties sheet becomes available for viewing it will display basic information about the capture such as machine name and capture date. Also (SYMANTEC, 2011) provides an option to explore the migration package not unlike before.

(SYMANTEC, 2011) States," In order to restore the package to the Client PC a new task is created to restore user data." Once clicked a new window opens asking for destination Client PC, once a destination is chosen the option to save for future use and execute once again become available. Ghost 2.4 ensures the stored user migration package is not overwritten during the cloning process if stored locally. (SYMANTEC, 2011) Explains that this also acting as a safe guard should Ghost 2.4 be unable to create the user migration package. Ghost 2.4 also has further ability to capture multiple users who have accessed the chosen Client PC or excluding them from capture if necessary. (SYMANTEC, 2011)Believe this is useful if you know a particular user has no access to the destination Client PC.

(SYMANTEC, 2011) Ghost 2.4 has the option to restore to a particular partition or drive this allows for multiple image deployment. In the properties tab there is an option to keep destination IP address and computer name which are stored on the Ghost 2.4 console when the client is first installed on Client PC. After all this is completed the Windows 7 image is ready to be deployed on the Client PC, the status can be followed and a (SYMANTEC, 2011) report is generated to signify any errors developed.

Method B: Windows Deployment Service (WDS)

WDS is the updated and redeveloped version of Remote Installation Services (RIS). Windows Deployment Services permits you to deploy Windows operating systems over the network, which means that you do not have to install each operating system directly from a CD or DVD.

There are certain con-straights before WDS can be run that need to be met such as AD DS. A Windows Deployment Services server must be either a member of an AD DS domain or a domain controller for an AD DS domain. You must have a functioning DHCP server with a dynamic range on the network because Windows Deployment Services uses PXE, which relies on DHCP for IP addressing. You must have a working DNS server on the network before you can run Windows Deployment Services. The server running Windows Deployment Services requires an NTFS file system volume for the image store.

Steps for installing Windows Deployment Services

You can install Windows Deployment Services by using the Initial Configuration Wizard, Server Manager, or the command line.

To install the role by using the Initial Configuration Wizard, click Add roles on the Initial Configuration Tasks startup screen. Click Next and then select Windows Deployment Services.

To install the role by using Server Manager, click Add roles, which is located in the Roles Summary pane. Click Next and then select Windows Deployment Services.

To install the role by using the command line, run one of the following two commands:

For Deployment Server, run ServerManagerCmd -install WDS.

For Transport Server, run ServerManagerCmd -install WDS-Transport.

During the installation, you have the following two role services to choose from. For a detailed comparison of these options, see Using Transport Server (http://go.microsoft.com/fwlink/?LinkID=115298).

Deployment Server. To install this option, ensure that both Deployment Server and Transport Server are selected on the second screen of the installation wizard. This is the most common option because it provides the full functionality of Windows Deployment Services, which you can use to configure and remotely install Windows operating systems. Note that Deployment Server is dependent on the core parts of Transport Server. 

Evaluate the deployment methods A/B

Above