Seminar Report

GREEN COMPUTING

1. INTRODUCTION

1.1. About the GREEN COMPUTING

Green computing, green IT or ICT Sustainability, refers to environmentally sustainable

computing or IT. In the article Harnessing Green IT: Principles and Practices, San Murugesan

defines the field of green computing as "the study and practice of designing, manufacturing,

using, and disposing of computers, servers, and associated subsystems—such as monitors,

printers, storage devices, and networking and communications systems — efficiently and

effectively with minimal or no impact on the environment."The goals of green computing are

similar to green chemistry; reduce the use of hazardous materials, maximize energy efficiency

during the product's lifetime, and promote the recyclability or biodegradability of defunct

products and factory waste. Research continues into key areas such as making the use of

computers as energy-efficient as possible, and designing algorithms and systems for efficiency-

related computer technologies.

Fig 1.1. Green computing

1.1.1. What is Green Computing?

DEPARTMENT OF ELECTRONICS&COMMUNICATION ENGINEERING, GPCET Page 1

GREEN COMPUTING

Green computing is the environmentally responsible use of computers and related resources. Such practices include the implementation of energy-efficient central processing units (CPUs), servers and peripherals as well as reduced resource consumption and proper disposal of electronic waste (e-waste).

One of the earliest initiatives toward green computing in the United States was the voluntary labeling program known as Energy Star. It was conceived by the Environmental Protection Agency (EPA) in 1992 to promote energy efficiency in hardware of all kinds. The Energy Star label became a common sight, especially in notebook computers and displays. Similar programs have been adopted in Europe and Asia.

Government regulation, however well-intentioned, is only part of an overall green computing philosophy. The work habits of computer users and businesses can be modified to minimize adverse impact on the global environment. Here are some steps that can be taken:

Power-down the CPU and all peripherals during extended periods of inactivity. Try to do computer-related tasks during contiguous, intensive blocks of time, leaving

hardware off at other times. Power-up and power-down energy-intensive peripherals such as laser printers according

to need. Use liquid-crystal-display (LCD) monitors rather than cathode-ray-tube (CRT) monitors. Use notebook computers rather than desktop computers whenever possible. Use the power-management features to turn off hard drives and displays after several

minutes of inactivity. Minimize the use of paper and properly recycle waste paper. Dispose of e-waste according to federal, state and local regulations. Employ alternative energy sources for computing workstations, servers, networks and

data centers.

1.1.2 How can we reduce E-waste?

Electronic waste, e-waste, e-scrap, or Waste Electrical and Electronic Equipment (WEEE)

describes discarded electrical or electronic devices. There is a lack of consensus as to whether

the term should apply to resale, reuse, and refurbishing industries, or only to product that cannot

be used for its intended purpose. Informal processing of electronic waste in developing countries

may cause serious health and pollution problems, though these countries are also most likely to

reuse and repair electronics. Some electronic scrap components, such as CRTs, may contain

contaminants such as lead, cadmium, beryllium, or brominated flame retardants. Even in

developed countries recycling and disposal of e-waste may involve significant risk to workers

and communities and great care must be taken to avoid unsafe exposure in recycling operations


GREEN COMPUTING

and leaching of material such as heavy metals from landfills and incinerator ashes. Scrap

industry and USA EPA officials agree that materials should be managed with caution, but some

believe that environmental dangers of used electronics have been exaggerated..

Fig 1.1.2.1.E-WASTE

To reducing CPU E-waste we are using thin clients.

1.2. What is a thin client?

A thin client (sometimes also called a lean or slim client) is a computer or a computer program which depends heavily on some other computer (its server) to fulfill its traditional computational roles. This stands in contrast to the traditional fat client, a computer designed to take on these roles by itself. The exact roles assumed by the server may vary, from providing data persistence (for example, for diskless nodes) to actual information processing on the client's behalf.

Thin clients occur as components of a broader computer infrastructure, where many clients share their computations with the same server. As such, thin client infrastructures can be viewed as the amortization of some computing service across several user-interfaces. This is desirable in contexts where individual fat clients have much more functionality or power than the infrastructure either requires or uses. This can be contrasted, for example, with grid computing.

Thin-client computing is also a way of easily maintaining computational services at a reduced total cost of ownership.

The most common type of modern thin client is a low-end computer terminal which concentrates solely on providing a graphical user interface to the end-user. The remaining functionality, in particular the operating system, is provided by the server.


GREEN COMPUTING

Thin clients have their roots in multi-user systems, traditionally mainframes accessed by some sort of terminal computer. As computer graphics matured, these terminals transitioned from providing a command-line interface to a full graphical user interface, as is common on modern thin clients. The prototypical multiuser environment along these lines, UNIX, began to support fully graphical X terminals, i.e., devices running X server software, from about 1984. X terminals remained relatively popular even after the arrival of other thin clients in the mid-late 1990s. Modern UNIX derivatives like BSD and GNU/Linux continue the tradition of the multi-user, remote display/input session. Typically, X server software is not made available on thin clients; although no technical reason for this exclusion would prevent it.

Windows NT became capable of multi-user operations primarily through the efforts of Citrix Systems, which repackaged NT 3.5.1 as the multi-user operating system Win Frame in 1995. Microsoft licensed this technology back from Citrix and implemented it into Windows NT 4.0 Terminal Server Edition, under a project codenamed "Hydra". Windows NT then became the basis of Windows 2000 and Windows XP. As of 2011 Microsoft Windows systems support graphical terminals via the Remote Desktop Services component.

The term thin client was coined in 1993 by Tim Negris, VP of Server Marketing at Oracle Corp., while working with company founder Larry Ellison on the launch of Oracle 7. At the time, Oracle wished to differentiate their server-oriented software from Microsoft's desktop-oriented products. Ellison subsequently popularized Negris's buzzword with frequent use in his speeches and interviews about Oracle products. Size comparison - traditional Desktop PC vs. Clientron U700

The term stuck for several reasons. The earlier term "graphical terminal" was chosen to contrast such terminals with text-based terminals, and thus puts the emphasis on graphics. The term thin client was also not well-established among IT professionals, most of whom had been working on fat-client systems. It also conveys better the fundamental hardware difference: thin clients can be designed with much more modest hardware, because they perform much more modest operations.


GREEN COMPUTING

Components:

The notion of a thin client extends directly to any client–server architecture: in which case, a thin client application is simply one which relies on its server to process most or all of its business logic. This idiom is relatively common for computer security reasons: a client obviously cannot be trusted with the logic that determines how trustworthy they are; an adversary would simply skip the logic and say "I'm as trustworthy as possible!"

However, in web development in particular, client applications are becoming fatter. This is due to the adoption of heavily client-side technologies like Ajax and Flash, which are themselves strongly driven by the highly interactive nature of Web 2.0 applications.

A renewed interest in virtual private servers, with many virtualization programs coming to a ripe stage, means that servers on the web today may handle many different client businesses. This can be thought of as having a thin-client "virtual server" which depends on the actual host in which it runs to do all of its computation for it. The end result, at least, is the same: amortization of the computing service across many clients.

Single point of failure:

The server, in taking on the whole processing load of several clients, forms a single point of failure for those clients. This has both positive and negative aspects. On the one hand, the security threat model for the software becomes entirely confined to the servers: the clients simply do not run the software. Thus, only a small number of computers need to be rigorously secured, rather than securing every single client computer. On the other hand, any denial of service attack against the server will harm many clients: so, if one user crashes the system, everyone else loses their vital data.

For small networks, this single-point of failure property might even be expanded: the server can be integrated with file servers and print servers particular to its clients. This simplifies the network and its maintenance, but might increase the risk against that server.

In practice redundancy is provided both in the form of additional connectivity from server to the network as well as in the servers themselves, using features like VMware High Availability and Fault Tolerance or Citrix XenApp's load balancing.

Cheap client hardware:

While the server must be robust enough to handle several client sessions at once, the clients can be assembled from much cheaper hardware than a fat client can. This reduces the power consumption of those clients, and makes the system marginally scalable: it is relatively cheap to connect additional client terminals. The thin clients usually have a very low total cost of


GREEN COMPUTING

ownership, but some of that is offset by requiring a robust server infrastructure with backups and so forth. This is also reflected in terms of power consumption: the thin clients are generally very low-power and might not even require cooling fans, but the servers are higher-power and require an air-conditioned server room.

On the other hand, while the total cost of ownership is low, the individual performance of the clients is also low. The costs of compiling software, rendering video, or any other computationally intensive task will be shared by all clients via the server.

Client simplicity:

Gigabyte TA7 thin client

Since the clients are made from low-cost hardware with few moving parts, they can operate in more hostile environments than conventional computers. However, they inevitably need a network connection to their server, which must be isolated from such hostile environments. Since thin clients are cheap, they offer a low risk of theft in general, and are easy to replace if stolen or broken. Since they do not have any complicated boot images, the problem of boot image control is centralized to the server.

On the other hand, to achieve this simplicity, thin clients sometimes lag behind thick clients (PC Desktops) in terms of extensibility. For example, if a local software utility or set of device drivers are needed in order to support a locally attached peripheral device (e.g. printer, scanner, biometric security device), the thin client operating system may lack the resources needed to fully integrate the needed dependencies. Modern thin clients attempt to address this limitation via


http://en.wikipedia.org/wiki/File:Gigabyte_TA7.JPG

GREEN COMPUTING

port mapping or USB redirection software. However, these methods cannot address all use case scenarios for the vast number of peripheral types being put to use today.

Thin Clients has many advantages, so different people define thin clients in different way basing one of its advantage. Below are the few common definitions & sentences people often use to define thin client. Simply, Thin Client is nothing but a computer, but with very less configuration (specifications /capacity / power), still users can able to run all the latest Operating Systems and Applications (software), with the help of SERVER Computer which is connected to it through LAN Means, In Thin Clients you need not to install any OS or Applications, you have to install Only in SERVER where all thin clients are connected to it, all the OS and Applications will run on server and results are displayed in Thin Clients (user computers) Several users can run the same program simultaneously, but the program only needs to be loaded once with a central server. In Traditional PC, We have to Install OS and Applications Locally and use its Local Resources (CPU, Ram, HDD) for its Processing and Storing, where as in Thin Client you need not install any OS or Applications in Thin Client, but you can access OS and Applications from SERVER.

Thin Clients computing means server based computing, Different Company people are using different names (viz, virtual computing)

People call Traditional PC’s as “Thick Clients / FAT PC’s”, “Conventional PC’s” People often call Thin Clients as “Diskless PC’s” Thin Client Computers also will be having Micro processors, Ram & Flash Memory

(HDD) but with LOW configuration (example, 300/800/100MHz, 64/128 MB Ram, 128/256/512 MB Flash Memory)

Run your computer without Hard disk, a computer without hard disk Run New Software on your OLD Hardware (with Thin Client PXE Cards) Run Your OLD Computers at the Speed of Today’s High Speed Computers Server Based Computing, no OS or Applications run in the local PC (Thin Client) rather

run in the SERVER, Thin Client is a dumb computer, no processing does locally, only takes input from the

user, request server to process the request, and displays the result Thin clients are Low Configuration Computer, off course does not require high

configuration coz all the OS/Application processing done by the server(s) Physically, most Thin Clients are small in size, One fourth of size in traditional PC’s

(CPU), and few models are still smaller in size, say your palm size Normally to compare Peer to peer networking, Client server networking, Thin Client

computing

Working model of Thin Clients:

Thin Client Computing you can replace the expensive, high-maintenance PC on every employee's desktop with a thin client device that’s one third the size of a PC and has no moving parts. Using only screen updates and keyboard/mouse input, the thin client communicates with commonly used applications such as Microsoft Word, PowerPoint, Excel, Outlook, Internet Explorer, Adobe Acrobat Reader running on a central server.


GREEN COMPUTING

Once the user logs into the server via a web-portal, the familiar Windows environment is displayed on the thin client's monitor and the user now has full access to applications, network drives, internet, e-mail and printers. In most cases the user is not even aware that he is using a thin client. Best of all once the thin client desktop is installed; the IT staff never needs to visit the employee's desk again!

Advanced thin client protocols supporting the transfer of display data and keyboard/mouse input such as Citrix ICA and Microsoft RDP typically require a minimum of 20Kbits per second. This means that remote users and branches experience faster performance over much smaller connections.


GREEN COMPUTING

1.3. Why Thin Clients?

It will reduce your Capital Costs (up to 60%) It will reduce Maintenance Costs (up to 80%) It will reduce Energy Consumption (up to 95%) It will reduce future up gradation costs (up to 70%)

By and Large, There are 100’s of advantages with thin client technology, but we’ll try to understand as many as possible. Advantages for CFO/Owners

Reduce your Capital Costs (up to 60%)

Reduce Maintenance Costs (up to 80%) Reduce Energy Consumption (up to 95%)

1. Reduce future up gradation costs (up to 70%)2. Thin Clients Occupies Less Space against to FAT Clients, so you can save on your real

estate also, means you can install more numbers of clients in the same place


GREEN COMPUTING

3. Even YOu can Save Amount on your furniture also where you are going to place your computers

4. you can save LOT of amount on your UPS also, because you require only 30-40% of the capacity of UPS required against to the traditional PC setup

5. you can save on your UPS bills also6. even wear and tear is very less7. Mean Time Before Failure (MTBF), life of PC is 25,000 hours, where as life of Thin

Clients is 175,0008. Depreciation costs are very less against to traditional pc

Thin Clients & Security/SafetyIn a traditional PC environment there are many opportunities to steal unprotected data or to install unwanted data via USB-stick, CD or DVD. Effective control of this, is nearly impossible to achieve. Data is often stored on client PCs, which makes the situation even worse.Server Based Computing offers substantial advantages, not only regarding possible attacks from the outside or theft of data. It has great potential in data safety and availability as well.It doesn't take much effort, compared to decentral organised PC networks with spreaded server locations, to build an efficient data storage and a highly available and fail proof (redundant) infrastructure.

Thin Clients & Green ITWith the ongoing debate about climate change, the question how to save energy has been brought to the centre of attention in the IT-world right now. The Fraunhofer institute UMSICHT has compared the energy and resource consumption of PC and Thin Client infrastructures in a

recent study.In doing so they considered the whole product life cycle, including the production, operation and recycling phases. The conclusion was, that Thin Clients weigh about 70% less than normal PCs even if the server is included and take about 80% less transportation volume.The production of Thin Clients itself needs less resources and energy than the production of normal PCs. The devices offer substantial advantages in production and logistics.During normal use, Thin Clients only need half of the energy a normal PC would and in doing so they are not only economically but also ecologically a good alternative to avoid CO2 emissions and electronic waste.

thin client product family:

The Thin Client product family offers a powerful, universal solution for the Thin Client Computing needs of a wide range of organizations. In its open source version the software - consisting of the thin client Manager, the thin client OS and the thin client Server - is freely available. It may be used, customized and extended to your needs.

Hardware & Support:


GREEN COMPUTING

If you are looking for Thin Client Hardware or need support for your Thin Client environment, you may take a look at thin client the business edition of Thin Client.

Get involved:

Great, so you think Thin Client is cool (we do, too) and you want to get involved. You don't need to be necessarily a coding guru to help with this wiki documentation and to offer support help to other users on the mailing lists.

Advantages for CTO/Systems Administrators:

1. users can not tamper either OS, Applications & data, coz everything stored in the server2. If you want to install/update any application, you have to do it only once in the server,

not in all the clients 3. because of the enhanced security with win2003 as server OS, desired user wise securities

can avail4. if any of the client broke down with various reason, then you can replace with another

client in minutes, no need to install/configure anything, coz everything is all ready in the server

5. Support Engineers no need to sacrifice many nights at the times of re installing PC’s with Operating Systems and Applications in all the machines

6. You can have a Bullet proof security with the Server OS ( win2003 or Linux)7. you can maintain sufficient hardware spares also, because it cost very less, so that your

downtime will be almost negligible when your hardware broke down8. Chances of Thin Client hardware broke down is very less, because it has got ZERO

moving components (No CPU Fans, NO SMPS FAN, NO HDD)9. at the time of relocating to another place, carrying is very easy because of its very very

small in size

Advantages for Users:

1. In Thin Client Environment, possibility of getting the same speed in all the clients, users no need to fight with management to provide latest PC or high configuration PC

2. users can access his/her data from anywhere in the network, he no need to sit in the same pc to continue his yesterdays work

3. Rich Computing Experience

1.4. Where Thin Clients can be used:

1. Almost all educational institutes’ applications like (c, c++, MS office, vb, oracle, java, etc)

2. Most of the Office Automation Applications like (client server, ERP, CRM etc.,)3. Excellent works for Internet Applications


GREEN COMPUTING

Accessing the Software from a Thin Client:

This task explains how to set up thin clients for accessing the Version 5 software over the network.A thin client can run Windows XP.This type of scenario is sometimes referred to as a "code server" scenario. The advantages of this type of scenario are:

you save time: the code is installed on the code server only, and not on the clients; and future upgrades and installation of service packs are easier since you only have to upgrade the software on the server, and not the clients

You save disk space: code is installed on the server only, so you save disk space on the clients.

The drawbacks with this type of scenario are:

The code is sent over the network to the client, so you will experience problems if the network is not efficient or goes down

The code is executed on the client, so performance may vary depending on the power of the client computer and the amount of memory on the client.

Note that the default installation path can be:

WindowsInstallPath (Windows XP Pro)WindowsInstallPath (64-bit code on Windows XP Professional x64 Edition)WindowsInstallPathx86 (32-bit code on Windows XP Professional x64 Edition)

1. Log on as administrator onto the server computer, install the Version 5 software, for example, in the following folder, for example on 32-bit Windows XP Pro:


GREEN COMPUTING

WindowsInstallPath

then share the disk and folders in the installation path.

2. Log on as administrator onto the client computer. 3. Run the Windows Explorer.

You need to use the Explorer to connect to the server over the network and access the C:\Program Files folder on the server.

4. Select Tools->Map Network Drive...

The Map Network Drive dialog box is displayed, and looks something like this:

5. Select a drive. 6. Select the folder Program Files on the server, and click Finish.

This is the folder containing the Dassault Systemes folder in which you installed the Version 5 software.

Note that selecting the folder displays the server name and folder name in the Path field:

\\server\Program Files

In the All Folders list in the left window of the Explorer, you will now see the connection to the server, for example:

Program Files on 'server' (F:)


GREEN COMPUTING

where "server" is the server name, for example, and "F:" is the name of the drive you mapped.

7. Still on the client computer, open a Command Prompt window and go to the following directory:

F:\Program Files\Dassault Systemes\B18\intel_a\code\bin (Windows XP Pro)F:\Program Files\Dassault Systemes\B18\win_b64\code\bin (64-bit code on Windows XP Professional x64 Edition)F:\Program Files (x86)\Dassault Systemes\B18\intel_a\code\bin (32-bit code on Windows XP Professional x64 Edition)

where, for example, "F:" is the name of the mapped drive and represents F:\Program Files.

8. Open a Command Prompt window to go back to the directory where you were before,

Then, run the following command using exactly the syntax indicated, depending on whether you are running CATIA, ENOVIA DMU Navigator or DELMIA:

cnext /regserver -env MyEnvironment -direnv MyEnvDirectorydmu /regserver -env MyEnvironment -direnv MyEnvDirectorydelmia /regserver -env MyEnvironment -direnv MyEnvDirectory

where "MyEnvironment" is the name of the environment, and "MyEnvDirectory" the name of an existing folder containing the environment on the client, if you intend to create an environment on the client as described in step 10a.

If you intend to use the environment on the server (step 10b), run the command:

cnext /regserver dmu /regserver

delmia /regserver

This activates OLE support which ensures that double-clicking Version 5 document icons on the client will run a Version 5 session.

9. Run the following command, depending on whether you are running CATIA, ENOVIA DMU Navigator or DELMIA:

setcatenv -tools -cs MyProductLine -e MyEnvironment -d MyEnvDirectory

to set up the Start->Programs->MyProductLine->Tools menu containing the Batch Management VersionNumber, Environment Editor VersionNumber, Nodelock Key Management VersionNumber, Printers VersionNumber, Settings Management

VersionNumber and Software Management VersionNumber commands.

At this point, you have two possibilities:


GREEN COMPUTING

create the runtime environment on the client (step 10a) or access the server environment via the network, to avoid creating an environment on

the client (step 10b).

Create the runtime environment on the client.

To do so, you have two possibilities:

from the directory:


run the following command:

setcatenv -p "F:\Dassault Systemes\EnvNameSuffix" -e MyEnvironment -d MyEnvDirectory -a global -desktop yes -cs MyProductLine

where "MyEnvironment" is the name of the environment, "MyEnvDirectory" is the name of the folder containing the environment and "MyProductLine" is the name of the product line.

or, use the Start->Programs->MyProductLine->Tools->Environment Editor VersionNumber command. In this case:

1. Select the Environment->New command to display the New Environment dialog box.2. Select the Options menu, then the Set Global Storage Directory command, and

set the environment storage directory to the same location you set in step 8.3. Enter the same environment name you also set in step 8.4. Enter the path of the shared installation folder on the server as follows:

F:\Dassault Systemes\EnvNameSuffix

5. Select Global for the Mode.6. Select your Product Line.7. Click OK.

In both cases, a global environment is created on the client computer which can be used by all users who log onto the client.

10b. You can also access the server environment via the network. To be able to do so, the code and the runtime environment on the server must be installed in a shared location so you can map it from the client.

For illustration purposes, let's suppose you installed the code for example on 32-bit Windows


GREEN COMPUTING

XP Pro in:

E:\Program Files\Dassault Systemes\EnvNameSuffix

To facilitate access to the runtime environment over the network, the environment must be located in a shared easily accessible location, and NOT in the default location in the All Users profile on the server which is:

C:\%WINDIR%\Profiles\All Users\Application Data\DassaultSystemes\CATEnv

For illustration purposes, let's suppose you created the runtime environment on the server in the following shared location:

E:\CATEnv

To access the environment over the network:

1. Map a drive to the shared folder on the server.You must choose the same drive letter on the client as the drive on which the code was installed on the server, for example "E:".

2. Open a Command Prompt window and go to the directory "E:", then to the directory:

E:\Program Files\Dassault Systemes\EnvNameSuffix\intel_a\code\bin (Windows XP Pro)E:\Program Files\Dassault Systemes\EnvNameSuffix\win_b64\code\bin (64-bit code on Windows XP Professional x64 Edition)E:\Program Files (x86)\Dassault Systemes\EnvNameSuffix\intel_a\code\bin (32-bit code on Windows XP Professional x64 Edition)

3. To start a session, run the command:

cnext -env MyEnvironment -direnv E:\CATEnvdmu -env MyEnvironment -direnv E:\CATEnvdelmia -env MyEnvironment -direnv E:\CATEnv

where "MyEnvironment" is an example for the name of the runtime environment on the server.

Note that this scenario will only work if the drive letter on the client and the drive letter on the server are identical. In certain cases, you may not be able to use the same drive letter on the client and the server. For example, the code is installed on "E:" on the server, but the drive "E:" on the client is not free, so you map the drive "K:". If you then try to start a session, the runtime environment will not be found because the paths referenced in the runtime environment point, for example, to "E:..." like this (32-bit code on Windows XP):

...CATInstallPath=E:\Program Files\Dassault Systemes\EnvNameSuffix\intel_aCATDLLPath=E:\Program Files\Dassault Systemes\EnvNameSuffix\intel_a\code\bin


GREEN COMPUTING

...

whereas on the client there is no software installed on the "E:" drive.

To bypass this problem, create a new global environment on the server using the following command:

setcatenv -e NewEnvironment -d \\servername\home\CATEnv -a global -p "\\servername\home\Program Files\Dassault Systemes\EnvNameSuffix" -desktop no

where "\\servername\home" is the UNC name of the server and shared folder, and "NewEnvironment" is the new environment name. Creating a new environment this way will create the correct UNC paths as follows (32-bit code on Windows XP):

...CATInstallPath=\\servername\home\Program Files\Dassault Systemes\EnvNameSuffix\intel_aCATDLLPath=\\servername\home\Program Files\Dassault Systemes\EnvNameSuffix\intel_a\code\bin...

This time, your attempt to start a session will be successful if you use the following command:

cnext -env MyEnvironment -direnv \\servername\home\CATEnvdmu -env MyEnvironment -direnv \\servername\home\CATEnvdelmia -env MyEnvironment -direnv \\servername\home\CATEnv

Note also that if you disconnect the drive you mapped, you will have to remap it as before for the scenario to continue to work.

11. If you require extended font support, run the following command:

VE0IFONT.exe -env MyEnvironment -direnv MyEnvDirectory

from the directory:


For more information, refer to "Using and Customizing Fonts" in your Infrastructure Users Guide.

12. If you want to record and replay macros, and Microsoft Visual Basic for Applications (VBA), Version 6.0 is not already installed on your client, you have to install VBA manually from the product CD-ROM.


GREEN COMPUTING

To install Microsoft Windows installer if it is not installed on the workstation:

Pathcdrom\VBA\MSI\INSTMSIW.exe /Q

To install VBA6 on all Windows platforms, run the command:

msiexec /q /i pathcdrom\VBA\VBA6.msi

However, note that VBA is supported on Windows XP Professional x64 Edition with Version 5 32-bit code.

13. You will need to install the VC8 Runtime prerequisite on each client computer. This has to be installed before running any Version 5 executable programs on this platform.

To do so, open a Command Prompt window, go to the first CD-ROM folder, then to the folder:

INTEL (32-bit media)WIN64 (64-bit media)

and run the following commands for 32-bit media:

msiexec /i InstallDSSoftwarePrerequisites_x86.msi /q (for 32-bit Windows)msiexec /i InstallDSSoftwarePrerequisites_x86_x64.msi /q (for 64-bit Windows)

and the following command for 64-bit media:

msiexec /i InstallDSSoftwarePrerequisites_x86_x64.msi /q for 64-bit Windows)

14. If you need access to the communications backbone and peripheral device broker, the associated port numbers must be set up on the client.

Used to support process interoperability (for example, between CATIA and DMU), the backbone needs to be set up on each computer running applications which need to communicate.

To set up the ports using the default values:

1. Log on as administrator.2. Open a Command Prompt window and go to the installation directory, for example:

F:\Program Files\Dassault Systemes\B18\intel_a\code\bin (Windows XP Pro)F:\Program Files\Dassault Systemes\B18\win_b64\code\bin (64-bit code on Windows XP Professional x64 Edition)F:\Program Files (x86)\Dassault Systems\B18\intel_a\code\bin (32-bit code on Windows XP Professional x64 Edition)


GREEN COMPUTING

3. Enter the commands:

setV5Ports

\\Server\"Program Files\Dassault Systems\EnvNameSuffix\intel_a\code\bin"\BBDemonService -create

where "server" is the name of the server machine. The UNC path must be used imperatively.

For more information about the communications backbone, refer to Communications Backbone Files.

15. If you created a runtime environment on the client, start a session by double-clicking the environment icon on the desktop or by selecting the command to start the product from the Start->Programs menu.

Make sure that you have set up your licenses (either network or nodelocked) before starting a session.

16. If you created an environment on the client, and want to delete this environment, run the following commands:

To update the registry (deactivate OLE support):

CNEXT /unregserver -direnv MyEnvDirectory -env My EnvironmentDMU /unregserver -direnv MyEnvDirectory -env My EnvironmentDELMIA /unregserver -direnv MyEnvDirectory -env My Environment

To delete the reference environment:delcatenv -d MyEnvDirectory -e My Env -a global -desktop yes -CS My Product Line

To delete the Start menu entries:delcatenv -tools -cs MyProductLine

Where Thin Clients are not suggested:

1. Multimedia Applications like Maya, 3D Studio max, CorelDraw etc.,2. Structural applications like AutoCAD, Stadd etc.,

How Does A Thin Client Work?

About 1/3 Size of PC. Works In A Same Way And At Same Speed As Desktop PC. Supports GUI and Windows Environment. Can Be Configured On As Low As 16Mb Of RAM. Same Feel As Working On Any Windows Based OS.


GREEN COMPUTING

Remote Computation….Server Takes Care Of All the Processing. Works On either Citrix`s ICA Or Microsoft’s RDP Protocols (Both Require Only 20Kbps

Speed Over Network To Work). User Logs On TO the Server via Web Portal and a Familiar Windows Base Environment

is Replicated On TO Users Screens with Access to Application, Internet, Mail, Drives, Printers, Etc.

Advantages Over Desktop Pc`s:

Dramatically Decreases The TCO by 54% to 57%. Decreases IT Cost By 80% through Reduced Staff and Centralized Software

Management. (Does not Crash, NO Help DESK) Greatly Simplifies The Software Upgrade Over The Network. Eliminates The Hardware Upgrades On Client Side. Increases End User Productivity. (Limited Access To Authorized Applications & Storage) Increased Life Time Of Client. (NO Moving Part ,Less Power Usage) Provides Higher Security. (Authentication, virus protection, data on server, theft). No Access to HDD, FDD, CD-ROMS. (Avoids Downloads, installations, Junk Data on

to the HDD) Thin Clients Are Virus Proof. (Since No OS And HDD Resides On It) Reduced Power Consumption. Centralized Backup. (Home Directory Mapping) 286,386,486 PCs Can Be Converted To Thin Client And Can Work At Speed Of 800Mz

Celeron Processor.

Potential Disadvantages of Thin Clients:

• Entry costs are high for servers and installation expertise.• More bandwidth is required; multimedia, project-based learning applications run very

slowly.• Thin-client doesn’t allow the flexibility to load software on the spot, constricting the

“teachable moment.”• PC’s are coming down in costs, and many educators believe users need the fully-

functioning capabilities of a desktop.

What Services Can We Deliver Through Thin Clients?

• Access to Internet through Common Browsers like IE.• Access to Subscription Database.• OPAC Browsing.• Microsoft Office.• Audio.• Several Application Software • Printing.

What Services Are Not Suitable For Thin Client?


GREEN COMPUTING

• Streaming Video• Video Games• DVD Movies

Major Developers of Thin Client Technology:

• Citrix and Microsoft partnership

Win Frame and Meta Frame

• National Semiconductor• Sun Microsystems• Wyse Technology• Acer• Compaq• Dell• IBM• Gateway


GREEN COMPUTING


GREEN COMPUTING


GREEN COMPUTING


GREEN COMPUTING


GREEN COMPUTING


GREEN COMPUTING


GREEN COMPUTING


GREEN COMPUTING


GREEN COMPUTING


GREEN COMPUTING
