DOCSLIB.ORG

Thinapp User's Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Thinapp User's Guide ThinApp User’s Guide ThinApp 4.0.3 EN-000117-03 ThinApp User’s Guide You can find the most up-to-date technical documentation on the VMware Web site at: http://www.vmware.com/support/ The VMware Web site also provides the latest product updates. If you have comments about this documentation, submit your feedback to: [email protected] © 2009 VMware, Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws. VMware products are covered by one or more patents listed at http://www.vmware.com/go/patents. VMware, the VMware “boxes” logo and design, Virtual SMP, and VMotion are registered trademarks or trademarks of VMware, Inc. in the United States and/or other jurisdictions. All other marks and names mentioned herein may be trademarks of their respective companies. VMware, Inc. 3401 Hillview Ave. Palo Alto, CA 94304 www.vmware.com 2 VMware, Inc. Contents About This Book 9 1 Installing ThinApp 11 ThinApp Requirements 11 Operating Systems, Applications, and Systems That ThinApp Supports 11 Applications That ThinApp Cannot Virtualize 11 Recommendations for Installing ThinApp 12 Using a Clean Computer 12 Using the Earliest Operating System Required For Users 13 Install ThinApp 13 2 Capturing Applications 15 Reviewing the Capture Process 15 Assessing Application Dependencies Before the Capture Process 15 Recommended Tasks Before the Capture Process 16 Capture an Application with the Setup Capture Wizard 16 Specify Entry Points, Data Containers, and Inventory Names 17 Specify Active Directory Access and Sandbox Locations 18 Specify Isolation Modes 18 Specify Location, MSI, and Compression Options 21 Review Project Files and Build Application Packages 21 Modifying Isolation Modes 22 Modifying Settings in the Package.ini File 22 Edit the Package.ini File 23 Modifying Settings in the ##Attributes.ini File 23 Edit the ##Attributes.ini File 23 3 Deploying Applications 25 Reviewing ThinApp Deployment Options 25 Deploying ThinApp With Deployment Tools 25 Deploying ThinApp in the VMware View Environment 25 Deploying ThinApp on Network Shares 26 Deploying ThinApp Using Executable Files 26 Establishing File Type Associations with the thinreg.exe Utility 26 Application Sync Effect on the thinreg.exe Utility 26 Run the thinreg.exe Utility 27 Optional thinreg.exe Parameters 27 Building an MSI Database 29 Customizing MSI Files with Package.ini Parameters 29 Modify the Package.ini File to Create MSI Files 30 Controlling Application Access with Active Directory 31 Reviewing Package.ini Entries for Active Directory Access Control 31 Using ThinApp Packages Streamed from the Network 32 How ThinApp Application Streaming Works 32 Reviewing Requirements and Recommendations for Streaming Packages 33 Stream ThinApp Packages from the Network 34 VMware, Inc. 3 ThinApp User’s Guide Using Captured Applications with Other System Components 34 Performing Paste Operations 34 Accessing Printers 34 Accessing Drivers 34 Accessing the Local Disk, the Removable Disk, and Network Shares 35 Accessing the System Registry 35 Accessing Networking and Sockets 35 Using Shared Memory and Named Pipes 35 Using COM, DCOM, and Out‐of‐Process COM Components 35 Starting Services 35 Using File Type Associations 35 Sample Isolation Mode Configuration Depending on Deployment Context 36 View of Isolation Mode Effect on the Windows Registry 36 4 Updating Applications 39 Application Updates That the End User Triggers 39 Reviewing the Application Sync Utility 39 Reviewing the Application Link Utility 41 Application Updates That the Administrator Triggers 45 Force an Application Sync Update with AppSync.exe 45 Reviewing the sbmerge.exe Workflow 45 Automatic Application Updates 47 Dynamic Updates Without Administrator Rights 47 Upgrading Running Applications on a Network Share 48 Reviewing File Locks 48 Upgrade a Running Application 48 Sandbox Considerations for Upgraded Applications 48 5 Monitoring and Troubleshooting ThinApp 49 Providing Information to VMware Support 49 Using Log Monitor 49 Troubleshoot Activity with Log Monitor 50 Perform Advanced Log Monitor Operations 50 Log Format 52 Troubleshooting Specific Applications 56 Troubleshoot Registry Setup for Microsoft Outlook 56 Viewing Attachments in Microsoft Outlook 57 Starting Explorer.exe in the Virtual Environment 57 Troubleshooting Java Runtime Environment Version Conflict 58 A Configuring Applications with Package.ini Parameters 59 Isolation and Virtualization Parameters 59 AllowExternalProcessModifications 59 ChildProcessEnvironmentDefault 60 ChildProcessEnvironmentExceptions 60 DirectoryIsolationMode 60 ExternalCOMObjects 61 ExternalDLLs 61 IsolatedMemoryObjects 61 IsolatedSynchronizationObjects 62 RegistryIsolationMode 62 SandboxCOMObjects 63 VirtualizeExternalOutOfProcessCOM 63 4 VMware, Inc. Contents General Purpose Parameters 64 AddPageExecutePermission 64 AllowUnsupportedExternalChildProcesses 64 AnsiCodePage 64 AutoShutdownServices 65 AutoStartServices 65 BlockSize 65 CachePath 66 CapturedUsingVersion 66 CompressionType 66 DisableTracing 67 ExcludePattern 67 FileTypes 68 LocaleIdentifier 68 LocaleName 68 LogPath 69 NetRelaunch 69 ObjectTypes 69 OutDir 70 Protocols 70 RuntimeEULA 70 Shortcuts 70 UACRequestedPrivilegesLevel 71 UACRequestedPrivilegesUIAccess 71 UpgradePath 71 VirtualComputerName 72 VirtualDrives 72 Wow64 73 Access Control Parameters 74 AccessDeniedMsg 74 PermittedGroups 74 Parameters for Individual Applications 75 CommandLine 75 Disabled 75 Icon 76 ReadOnlyData 76 ReserveExtraAddressSpace 76 RetainAllIcons 77 Shortcut 77 Source 78 StripVersionInfo 78 Version.XXXX 78 WorkingDirectory 78 Application Link Parameters 79 Application Link Path Name Formats 79 RequiredAppLinks 79 OptionalAppLinks 80 Application Sync Parameters 80 AppSyncClearSandboxOnUpdate 81 AppSyncExpireMessage 81 AppSyncExpirePeriod 81 AppSyncURL 81 AppSyncUpdateFrequency 82 AppSyncUpdatedMessage 82 VMware, Inc. 5 ThinApp User’s Guide AppSyncWarningFrequency 82 AppSyncWarningMessage 82 AppSyncWarningPeriod 82 MSI Parameters 83 MSIArpProductIcon 83 MSIDefaultInstallAllUsers 83 MSIFilename 83 MSIInstallDirectory 84 MSIManufacturer 84 MSIProductCode 84 MSIProductVersion 84 MSIRequireElevatedPrivileges 85 MSIUpgradeCode 85 MSIUseCabs 85 Sandbox Parameters 86 InventoryName 86 RemoveSandboxOnExit 86 SandboxName 87 SandboxNetworkDrives 87 SandboxPath 87 SandboxRemovableDisk 88 B ThinApp Sandbox 89 Search Order for the Sandbox 89 Controlling the Sandbox Location 91 Store the Sandbox on the Network 91 Store the Sandbox on a Portable Device 91 Sandbox Structure 92 Making Changes to the Sandbox 92 Listing Virtual Registry Contents with vregtool 92 C ThinApp Directory Files 93 D Snapshot Commands and Customization 95 Methods of Using the snapshot.exe Utility 95 Creating Snapshots of Machine States 95 Creating the Template Package.ini file from Two Snapshot Files 96 Creating the ThinApp Project from the Template Package.ini File 96 Displaying the Contents of a Snapshot File 97 Sample snapshot.exe Commands 97 Create a Project Without the Setup Capture Wizard 97 Customizing the snapshot.ini File 98 E ThinApp Virtual File System 99 Virtual File System Formats 99 Merged and Virtual Views of the File System 99 Using Folder Macros 100 List of Folder Macros 100 Processing %SystemRoot% 101 6 VMware, Inc. Contents F ThinApp Scripts 103 Callback Functions 103 Example Scripts 104 .bat Example 104 Timeout Example 104 Modify the Virtual Registry 105 .reg Example 105 Stopping a Service Example 105 Copying a File Example 105 Add a Value to the System Registry 106 API Functions 107 AddForcedVirtualLoadPath 107 ExitProcess 107 ExpandPath 108 ExecuteExternalProcess 108 ExecuteVirtualProcess 109 GetBuildOption 109 GetFileVersionValue 109 GetCommandLine 110 GetCurrentProcessName 110 GetOSVersion 111 GetEnvironmentVariable 112 RemoveSandboxOnExit 112 SetEnvironmentVariable 112 SetfileSystemIsolation 113 SetRegistryIsolation 113 WaitForProcess 113 Index 115 VMware, Inc. 7 ThinApp User’s Guide 8 VMware, Inc. About This Book The ThinApp User’s Guide provides information about how to install ThinApp, capture applications, deploy applications, and upgrade applications. You can refer to this guide to customize parameters and perform scripting. Intended Audience This book is intended for anyone who installs ThinApp and deploys captured applications. Typical users are system administrators responsible for the distribution and maintenance of corporate software packages. Document Feedback VMware welcomes your suggestions for improving our documentation. If you have comments, send your feedback to [email protected]. Technical Support and Education Resources The following sections describe the technical support resources available to you. To access the current version of this book and other books, go to http://www.vmware.com/support/pubs. Online and Telephone Support To use online support to submit technical support requests, view your product and contract information, and register your products, go to http://www.vmware.com/support. Customers with appropriate support contracts should use telephone support for the fastest response on priority 1 issues. Go to http://www.vmware.com/support/phone_support. Support Offerings To find out how VMware support offerings can help meet your business needs, go to http://www.vmware.com/support/services. VMware Professional Services VMware Education Services courses offer extensive hands‐on labs, case study examples, and course materials designed to be used as on‐the‐job reference
Load more

Recommended publications
  • Tadiran-Coral-Voicemail-User-Guide-Steadfasttelecom.Com .Pdf
    Coral Message Center (CMC) User Guide Version 2.1 for Windows The flexible way to communicate . © 2002-2003 Active Voice LLC To access your mailbox from inside your organization All rights reserved. First edition 2003. 1. Call the voice messaging system. 1 for Yes, 2 for No, PhoneBASIC, Repartee, TeLANophy, 2. When the system greets you, enter: ViewCall, and ViewMail are trademarks of Active Voice, LLC. Personal ID ______________________________________________________ All other brands and product names used in this docu- ment are trademarks of their respective owners. Security code (if required) ___________________________________________ Licensed under one or more of the following patents: U.S. Nos. 4,994,926; 5,291,302; 5,459,584; 4,696,028; To access your mailbox by computer 4,809,321; 4,850,012; 4,922,526; 4,935,958; 4,955,047; 1. Launch Mailbox Manager. 4,972,469; 4,975,941; 5,020,095; 5,027,384; 5,029,196; 5,099,509; 5,109,405; 5,148,478; 5,166,974; 5,168,519; 2. When the system greets you, enter: 5,249,219; 5,303,298; 5,309,504; 5,347,574; 5,666,401; 5,181,243; 5,724,408; and Canadian No. 1329852. Host name_______________________________________________________ Extension _______________________________________________________ Security Code _____________________________________________________ For assistance, call: Name___________________________________________________________ Extension _______________________________________________________ Contents Introduction ii Changing your mailbox setup 21 Using quick message actions and shortcuts 47 Setting up your mailbox .......................................iv Working with the Mailbox Manager ....................22 Changing your security code..............................24 Quick message actions ...................................... 48 Checking and leaving messages 1 Changing your recorded and spelled names......25 Shortcuts...........................................................
    [Show full text]
  • Resolving Issues with Forms
    C1261587x.fm Page 265 Thursday, November 15, 2001 3:51 PM Resolving Issues with Forms In 1988, Alan Cooper demonstrated a prototype called Ruby to Bill Gates. Ruby provided a form designer that allowed you to drag and drop controls, then known as gizmos, to quickly and easily create composite forms—such as dialog boxes, entry forms, and report forms. Microsoft took Cooper’s Ruby product and combined it with Basic to create Microsoft Visual Basic 1. Microsoft has since shipped a version of Ruby with every version of Visual Basic, versions 1 through 6. With every version, that is, until Visual Basic .NET. Visual Basic .NET provides a new forms package called Windows Forms. Although the Windows Forms package was designed using the same basic prin- ciple as Ruby—it is a form designer that allows you to drag and drop controls and set properties—it was never meant to be an extension of, nor to be com- patible with, Ruby. Therefore, there are fundamental differences between the two forms packages that affect the way you create Visual Basic applications. This chapter focuses on some of the fundamental differences between the Ruby and Windows Forms packages. Specifically, it discusses issues that the Upgrade Wizard does not handle for you. Before we get into the differences, however, let’s look at what Windows Forms and Ruby have in common. Similarities in Form Structure When you create a new project in Visual Basic .NET, you will find yourself at home in the environment. The way you create and design forms is the same in Visual Basic .NET as it is in Visual Basic 6.
    [Show full text]
  • VI. Lotus Domino
    Le groupware - 1 / 60 - Sommaire I. Introduction ................................................................................................ 2 A. Histoire (Source : Michel Alberganti) ................................................................................ 2 B. Définition................................................................................................................... 2 C. L'offre....................................................................................................................... 2 1. Intranet / Internet................................................................................................. 2 2. Messagerie........................................................................................................... 3 II. Les clients de messagerie ............................................................................... 3 A. Windows Messaging : Msmail........................................................................................... 4 1. Installer et administrer un bureau de poste .................................................................. 4 2. Propriétés du client MAPI......................................................................................... 7 B. Utiliser Outlook ......................................................................................................... 15 1. Les options .........................................................................................................15 2. Envoi de messages ................................................................................................20
    [Show full text]
  • Desktop Containers
    Data Sheet Desktop Containers Desktop Containers In today’s complex world, desktop and web applications make it difficult to keep moving forward—testing costs, application conflicts, framework requirements, or incompatibility with modern Windows operating systems and browsers are just a few of the hurdles you have to overcome. Micro Focus® Desktop Containers enables you to solve these problems by building containerized desktop applications from most Windows- compatible software, allowing you to easily eliminate these hurdles and distribute the application via USB, your favorite endpoint management tool, or the included web portal. Product Overview Test beta or newly released versions System Requirements of applications without impacting the Micro Focus Desktop Containers helps you over- For detailed product specifications and system come the challenges associated with applica - installed version. requirements, visit: wwww.novell.com/ tion conflicts and the ever changing desktop and Eliminate application failures caused by documentation/mfdc browser landscape by allowing you to create ap- .dll conflicts, overwritten registry entries plications that can be packaged once, and run and other problems that often occur when on any Windows XP or higher device. These ap- you introduce new software into complex Extend application access to those outside plications can then be given to users on a USB user environments. your IT environment while maintaining stick, through a file share, or from an endpoint control of your applications. Embed frameworks required by applications, ® management tool like ZENworks . Or you can such as .NET and Java, into the application Understand what containerized applications host applications on the included web portal. so that you don’t need to worry about are being run, by whom, and from what Imagine quickly and easily packaging an old ver- whether it is present before deploying device.
    [Show full text]
  • OEM Windows Co-Brand Guide
    OEM Windows Co-Brand Guide March, 2016 Microsoft Confidential Welcome to the OEM Windows Co-Brand Guide! This guide contains important Windows 10 and Office brand elements and guidelines to help tell our brand story together. Our logo is a window—and an iconic symbol known the world over. This symbol has an active feeling to it, representing a person’s unique perspective on their world. When communicating general Windows brand information, use the Windows logo with no The Windows logo includes the Windows symbol and logotype, which version attached. must be used together in a horizontal lockup. The symbol must not be used by itself, and OEMs must not put a box, circle, or other confining When the conversation is shape around the Windows logo. specific to Windows 10 or Trademark symbols highlighting Windows 10 specific features, always use the Logos provided without trademark symbols (TM and ®) should Windows 10 logo lockup. be used in marketing materials only. Trademark symbols are still required in certain places in and on product, and on Minimum size product packaging. More trademark information http://www.microsoft.com/en- us/legal/intellectualproperty/Trademarks/EN-US.aspx Clear space Clear space We respect the logo by giving it some space. The preferred clear space is equivalent to the height of the symbol. Minimum size In print, the logo should never appear smaller than 1” (25 mm). On-screen, it must appear at least 70 pixels wide. Download the Windows logo here: https://omap.microsoft.com/ The Logo Artwork Is Available in Three sizes Windows Logo Color Select the appropriate asset by determining the height Contrast is important — use a white logo on color backgrounds and required for your layout.
    [Show full text]
  • BCM 4.0 Unified Messaging Configuration Guide
    BCM 4.0 Unified Messaging Configuration Guide Business Communications Manager BCM 4.0 Document Status:Beta Document Version: 1.0 Part Code: N0060611 Date: January 2006 Copyright © Nortel Networks Limited 2006 All rights reserved. The information in this document is subject to change without notice. The statements, configurations, technical data, and recommendations in this document are believed to be accurate and reliable, but are presented without express or implied warranty. Users must take full responsibility for their applications of any products specified in this document. The information in this document is proprietary to Nortel Networks. Trademarks *Nortel, Nortel (Logo), the Globemark, and This is the way, This is Nortel (Design mark) are trademarks of Nortel Networks. *Microsoft, MS, MS-DOS, Windows, and Windows NT are registered trademarks of Microsoft Corporation. Citrix is a registered trademark of Citrix Systems, Inc. All other trademarks and registered trademarks are the property of their respective owners. Revision history 3 Revision history July 2005 Draft document submitted for external technical review. Review comments received and incorporated. January 2006 Beta document submitted. BCM 4.0 Unified Messaging Configuration Guide 4 Revision history N0060611 5 Task List Getting started . 9 Configuring your system for Unified Messaging . 15 To check that Business Communications Manager is not configured to use DNS........17 To check that a Host Name is entered on the Business Communications Manager.....17 To configure access
    [Show full text]
  • Managed Services Guide for Unity
    Cisco Unified Communications MIBs, Syslogs, and Alerts/Alarms for Managed Service Providers For Cisco Unity Release 7.0(2) Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 527-0883 Text Part Number: OL-19789-01 THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS. THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY. The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California. NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE. IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
    [Show full text]
  • The Expert's Guide for Exchange 2003 Preparing For, Moving To, and Supporting Exchange Server 2003
    The Expert's Guide for Exchange 2003 Preparing for, Moving to, and Supporting Exchange Server 2003 by Steve Bryant iii Books Contents Chapter 3 Consolidating Your Exchange Services . 34 Server Ownership Costs . 34 Exchange Server Proliferation . 34 Consolidating Protocols . 35 Exchange 2003 and AD . 37 Front-End Exchange Servers . 39 Front-End Servers and Performance . 45 Balancing Front-End and Back-End Servers . 45 Consolidating Servers . 46 Storage Space and Recovery . 46 Configuration and Memeory . 47 Mailbox Consolidation Concerns . 47 Creating Server Redundancy . 48 Spreading the Load . 48 Clustering . 48 Deploying High- or Continuous-Availability Servers . 50 Consolidating Mailbox Servers . 50 Move Mailbox Tool . 50 Consolidating Sites . 51 Consolidating Your Exchange Organization . 52 Consolidating Exchange 2003 and Exchange 2000 Organizations . 52 Tools for Merging Exchange Organizations . 53 Using the Exchange Migration Wizard . 53 Copying Public Folder Data . 53 Copying the Organizational Forms Library . 54 Copying Contacts from One Organization to Another . 54 Collecting Group Distribution Memebership . 55 Completing the Consolidation . 57 More Consolidation Details . 64 Next: Installing Exchange 2003 . 64 34 Chapter 3: Consolidating Your Exchange Services At the heart of most successful and cost-effective Microsoft Exchange 2003 and Exchange 2000 deployments lies consolidation. Fewer Exchange servers translates to fewer server licenses, smaller data centers, easier administration, and a reduced cost of doing business. These benefits of consolidation are often the desired end results that prompt – and justify budgets for – upgrading and consolidating Exchange deployments. Estimating the savings that your consolidation efforts can realize will require some intelligent speculation because you’ll derive your overall savings from multiple sources.
    [Show full text]
  • Configuring Mail Clients to Send Plain ASCII Text 3/13/17 2:19 PM
    Configuring Mail Clients to Send Plain ASCII Text 3/13/17 2:19 PM Sign In Sign-Up We have copied this page for reference in case it disappears from the web. The copyright notice appears at the end. If you want the latest version go to the original page: http://www.expita.com/nomime.html Turning Off HTML or MIME to use a Remailer System. Index (5 topics) Introduction E-mail client programs (Turning Off HTML or MIME to use a Remailer System) Suggestions for HTML users Examples of HTML/MIME messages References What is wrong with sending HTML or MIME messages? There are now six main reasons for NOT doing this: 1. Many E-mail and Usenet News reader programs, usually the mail and news reader programs that come with browser packages, allow users to include binary attachments (MIME or other encoding) or HTML (normally found on web pages) within their E-mail messages. This makes URLs into clickable links and it means that graphic images, formatting, and even color coded text can also be included in E-mail messages. While this makes your E-mail interesting and pretty to look at, it can cause problems for other people who receive your E- mail because they may use different E-mail programs, different computer systems, and different application programs whose files are often not fully compatible with each other. Any of these can cause trouble with in-line HTML (or encoded attachments). Most of the time all they see is the actual HTML code behind the message. And if someone replies to the HTML formatted message, the quoting can render the message even more unreadable.
    [Show full text]
  • Operating System Virtualization
    Introduction to virtualisation technology Predrag Buncic CERN CERN School of Computing 2009 Introduction to Virtualisation Technology History . Credit for bringing virtualization into computing goes to IBM . IBM VM/370 was a reimplementation of CP/CMS, and was made available in 1972 . added virtual memory hardware and operating systems to the System/370 series. Even in the 1970s anyone with any sense could see the advantages virtualization offered . It separates applications and operating systems from the hardware . With VM/370 you could even run MVS on top - along with other operating systems such as Unix. In spite of that, VM/370 was not a great commercial success . The idea of abstracting computer resources continued to develop 2 Predrag Buncic – CERN Introduction to Virtualisation Technology Resource virtualization . Virtualization of specific system computer resources such as . Memory virtualization . Aggregates RAM resources from networked systems into Memory virtualized memory pool . Network virtualization . Creation of a virtualized network addressing space within or across network subnets . Using multiple links combined to work as though they Networking offered a single, higher-bandwidth link . Virtual memory . Allows uniform, contiguous addressing of physically separate and non-contiguous memory and disk areas . Storage virtualization Storage . Abstracting logical storage from physical storage . RAID, disk partitioning, logical volume management 3 Predrag Buncic – CERN Introduction to Virtualisation Technology Metacomputing . A computer cluster is a group of linked computers, working together closely so that in many respects they form a single computer. The components of a cluster are commonly connected to each other through fast local area networks. Grids are usually computer clusters, but more focused on throughput like a computing utility rather than running fewer, tightly-coupled jobs .
    [Show full text]
  • Mastering Windows XP Registry
    Mastering Windows XP Registry Peter Hipson Associate Publisher: Joel Fugazzotto Acquisitions and Developmental Editor: Ellen L. Dendy Editor: Anamary Ehlen Production Editor: Elizabeth Campbell Technical Editor: Donald Fuller Electronic Publishing Specialist: Maureen Forys, Happenstance Type-O-Rama Proofreaders: Nanette Duffy, Emily Hsuan, Laurie O'Connell, Yariv Rabinovitch, Nancy Riddiough Book Designer: Maureen Forys, Happenstance Type-O-Rama Indexer: Ted Laux Cover Designer: Design Site Cover Illustrator: Sergie Loobkoff Copyright © 2002 SYBEX Inc., 1151 Marina Village Parkway, Alameda, CA 94501. World rights reserved. The author(s) created reusable code in this publication expressly for reuse by readers. Sybex grants readers limited permission to reuse the code found in this publication or its accompanying CD-ROM so long as the author is attributed in any application containing the reusable code and the code itself is never distributed, posted online by electronic transmission, sold, or commercially exploited as a stand-alone product. Aside from this specific exception concerning reusable code, no part of this publication may be stored in a retrieval system, transmitted, or reproduced in any way, including but not limited to photocopy, photograph, magnetic, or other record, without the prior agreement and written permission of the publisher. First edition copyright © 2000 SYBEX Inc. Library of Congress Card Number: 2002100057 ISBN: 0-7821-2987-0 SYBEX and the SYBEX logo are either registered trademarks or trademarks of SYBEX Inc. in the United States and/or other countries. Mastering is a trademark of SYBEX Inc. Screen reproductions produced with FullShot 99. FullShot 99 © 1991-1999 Inbit Incorporated. All rights reserved.FullShot is a trademark of Inbit Incorporated.
    [Show full text]
  • Browser Security Comparison – a Quantitative Approach Page| I of V Version 0.0 Revision Date: 12/6/2011
    Browser Security Comparison A Quantitative Approach Document Profile Version 0.0 Published 12/6/2011 Revision History Version Date Description 0.0 12/26/2011 Document published. Browser Security Comparison – A Quantitative Approach Page| i of v Version 0.0 Revision Date: 12/6/2011 Contents Authors .......................................................................................................................................................... v Executive Summary ....................................................................................................................................... 1 Methodology Delta ................................................................................................................................... 1 Results ....................................................................................................................................................... 2 Conclusion ................................................................................................................................................. 2 Introduction .................................................................................................................................................. 3 Analysis Targets ........................................................................................................................................ 4 Analysis Environment................................................................................................................................ 4 Analysis
    [Show full text]