All VMware articles Application Delivery and Virtualization News. Citrix, Microsoft and VMware virtualization news and support site. Your source for the latest Citrix, Application Delivery Guides, Citrix XenServer Guides, Citrix XenApp Guides,Microsoft,VMware,VDI,Cloud Computing, Hyper-V,ESX,Citrix Application Virtualization and Streaming and downloads http://www.ervik.as/index.php/vmware-mainmenu Tue, 07 Sep 2010 13:09:33 +0000 Joomla! 1.5 - Open Source Content Management en-gb VMware ThinApp 4.6 now released http://www.ervik.as/index.php/vmware-mainmenu/vwmare-thinapp-mainmenu/2963-vmware-thinapp-46-now-released http://www.ervik.as/index.php/vmware-mainmenu/vwmare-thinapp-mainmenu/2963-vmware-thinapp-46-now-released VMware has released a new version of their ThinApp product.

Here is a short overview of what's new:

Full Support for Windows 7
ThinApp now supports Windows 7. You can now package legacy applications from older versions of Windows such as Windows XP and Windows Vista into ThinApp packages for deployment on Windows 7. Avoid costly recoding and regression testing and accelerate deployment of business applications to Windows 7 more quickly and securely.

Relink
If you’ve used previous versions of ThinApp to create application packages, these existing packages can be upgraded to the new ThinApp 4.5 format without the need of associated project files for the applications. This utility speeds up the upgrade process of existing ThinApp packages.

Performance Accelerator
Reduced page file usage for virtual applications and increased memory sharing between multiple instances of applications allows for quicker application invocation and improved application delivery to end users. This helps to improve user experience with ThinApp at the same time reduces network bandwidth consumption.

Registry Transaction Protection
Ensure the integrity of the registry file and eliminate potential data corruption due to crash or system failure by mapping to a backup registry file.

Enhanced Packaging Support Ecosystem
Customers can now elect to share application packaging results with VMware at the beginning of capture or contribute application packaging tips and recipes with a network of community users. By building out this ecosystem of support for users, we will have a better understanding of product usage to provide better product support.

{vimeo}12414125{/vimeo}

For more information on VMware ThinApp click here

]]>
aj@ervik.as (Alexander Ervik Johnsen) Vmware ThinApp Fri, 20 Aug 2010 07:50:13 +0000
VMware Announces Hyperic 4.4 to Enhance Application Monitoring Across Virtual Infrastructure http://www.ervik.as/index.php/vmware-mainmenu/vmware-vsphere-4/2940-vmware-announces-hyperic-44-to-enhance-application-monitoring-across-virtual-infrastructure http://www.ervik.as/index.php/vmware-mainmenu/vmware-vsphere-4/2940-vmware-announces-hyperic-44-to-enhance-application-monitoring-across-virtual-infrastructure VMware, Inc., the global leader in virtualization solutions from the desktop through the datacenter and to the cloud, today announced SpringSource® Hyperic™ 4.4, an award-winning solution for managing and monitoring custom applications. Through enhanced integration with VMware vCenter™ Server, Hyperic™ 4.4 now maintains a continually updated inventory of VMware vSphere™ ESX and ESXi hosts, enabling IT Administrators to more rapidly pinpoint, correct, and prevent application performance problems wherever they occur across physical, virtual, and private cloud infrastructures.

As organizations deploy an increasing proportion of their custom applications across virtual and cloud infrastructures, the dynamic nature of virtualized application resources has placed new demands on application operators needing visibility into the performance of those applications. Hyperic 4.4’s VMware vCenter Server integration enables application operators to ensure application performance despite this increased pace of change.

SpringSource Hyperic, a key element of SpringSource’s software suite, supports applications running on both physical and virtual infrastructure, providing in-depth real-time performance data on more than 75 technologies used to develop modern web applications and enabling customers to ensure that applications meet their service level commitments through reduced application downtime and improved performance.

“For some time, Hyperic has provided us with excellent visibility into the performance of our custom applications,” said Eric Schwalbe, technical advisor infrastructure integration, InterContinental Hotels Group. “By enabling us to understand performance at any point between the application and its ESX host, Hyperic 4.4 will enable us to extend this visibility across our virtualized infrastructure.”

"Without virtualization there is no cloud computing," said Rachel Chalmers, research director for infrastructure, The 451 Group. "The trouble with virtualization is that with it, datacenters become increasingly dynamic - not to say chaotic! That makes it extremely hard for the IT operations team to make sure applications are up and performing. What's needed are management tools that understand the whole software stack, from VM through OS to application payload - tools like Hyperic™."

“Hyperic™ 4.4 delivers a completely new level of integration with VMware vCenter Server designed to streamline the task of managing virtualized applications,” said Javier Soltero, CTO of Management Products for the SpringSource division of VMware. “Hyperic now provides system administrators complete, automatic visibility of virtual infrastructure resources as well as a completely new user interface built to enable analysis and correlation of every metric and event from VMware vSphere hosts up to the application.”

Hyperic 4.4’s VMware vCenter Server integration increases the effectiveness of IT operations teams in a range of critical application performance management activities that stem from the constant change inherent in virtualized datacenters, including:

Rapid Diagnosis of Virtualized Application Performance Problems: IT operations teams can now use Hyperic to rapidly pinpoint the cause of performance issues of applications running on virtualized infrastructure, by providing them with visibility into all application infrastructure layers, enabling them to determine whether the root cause of issues lies within an application, its guest operating system, or its ESX host. System administrators can easily compare performance data between an application and its corresponding virtual machine and ESX host via a new Hyperic user interface. This UI enables system administrators to reduce mean time to resolution (MTTR) and increase mean time between failures (MTBF).

Automatic Maintenance of Application Infrastructure Inventory: Hyperic 4.4 automatically discovers ESX hosts, virtual machines, and guest operating systems within minutes of their launch, and presents them in a unified topology so users can see which application components are running on which ESX hosts. This eliminates reliance on chronically out-of-date configuration management databases (CMDBs). Additionally, Hyperic detects when virtual machines are moved from one ESX host to another using vMotion™, and adjusts topologies accordingly: no monitoring data is lost and there’s no need to recreate alerting workflows. This exceptional level of automation saves system administrators time and lets them manage more applications and servers than ever before.

Virtualization-Aware Alerting: Hyperic 4.4 can distinguish between when a guest operating system has shut down unintentionally, and when it has been intentionally powered down or suspended. This prevents false alarms and enables system administrators to elastically scale their application infrastructure without triggering alert storms.

Additional Virtualization Features of Hyperic:
Hyperic 4.4 continues Hyperic’s tradition of leadership in the management of applications running in virtualized environments. In 2006, Hyperic delivered the industry’s first application performance monitoring for VMware ESX and GSX, and has long provided system administrators with the following capabilities, which remain in version 4.4:

Application Virtualization Migration Assurance: For IT teams running pilot projects to virtualize custom application workloads, Hyperic enables users to definitively quantify virtualization’s impact on application performance by baselining critical performance metrics for both physical and virtual infrastructure.

Automated Problem Resolution: Hyperic can automate common responses to application problems -- such as reverting a virtual machine to a snapshot, restarting a virtual machine, and rebooting a guest operating system. These automated recovery actions help fulfill virtualization’s promise of greater operational efficiency, especially for companies with global customers who need to keep consumer-facing applications running 24/7.

Virtualized Environment Event & Log Monitoring: Hyperic’s event management features provide visibility into the log events reported for every virtual machine. Log events provide system awareness for performance data, configuration changes, and security action changes, such as when a virtual machine has been reverted to a snapshot. These events can be used to generate alerts, or simply to correlate errors reported in the VMware logs with performance and health indicators elsewhere in the environment.

Availability and Support
Hyperic 4.4 is available immediately and can be purchased August 4, 2010. Additional Hyperic 4.4 details are available at http://SpringSource.com/hyperic44.

Upcoming Hyperic Webinar
SpringSource will host a free webinar entitled “The 10 Pitfalls to Avoid When Monitoring a Virtualized Environment -- Learn How the New Hyperic 4.4 Helps You Manage the Constant Change Inherent in Virtualized Datacenters,” on Thursday, August 19, 2010 at 9 am PDT. To register, visit http://j.mp/hyperic44.

]]>
aj@ervik.as (Alexander Ervik Johnsen) VSphere 4 Sun, 08 Aug 2010 07:55:17 +0000
A Guide to Updating a ThinApp http://www.ervik.as/index.php/vmware-mainmenu/vwmare-thinapp-mainmenu/2865-a-guide-to-updating-a-thinapp http://www.ervik.as/index.php/vmware-mainmenu/vwmare-thinapp-mainmenu/2865-a-guide-to-updating-a-thinapp

Updating a ThinApp can seem like a really tricky or difficult process, but in reality it is a very simple process (relatively speaking and, of course, dependent upon the application).

Updating an Application:

Regardless of ThinApp, with the nearly infinite number of Windows applications, there are literally just as many ways in which updates are performed upon those applications. Of all the ways application updates are accomplished, with regards to ThinApp, they can generally be boiled down into four types of updates.

  1. Manually changing the application or reconfiguration of the application’s settings from within the app.
  2. Copying in updates through Windows Explorer or manually entering in registry or config file modifications.
  3. Run the update directly from within the application via it’s built in update feature.
  4. Install a separate hotfix / update package to the application.
  5. Any combination of the above.

Whichever way is chosen, these options can also be used to update a ThinApp packaged application as well.

Application Updater

 

Try It, You’ll Like It!

One of the easiest ways to ensure you get your ThinApp package updated correctly is test it in the native world. This may seem redundant on some levels, but you will gain experience with the application if you are somewhat unfamiliar with how it works and how it’s updates are applied. Additionally, this can be done on a clean Capture and Build (CnB) system – giving you the opportunity to capture the app with the upgrade separately to give you a baseline of what the updated project should be similar to.

 

ThinApp Project Updating – Capturing the App:

One of the first ways we can update a ThinApp project is to just capture a new one. While this isn’t traditionally seen as an actual “update”, it is definitely an option.

Additionally, one can also capture just the update – although this is not recommended as it can be a cumbersome and troublesome process. Plus, there are easier ways to achieve the same results.

ThinApp 4.5 Setup  Capture Welcome

 

ThinApp Project Updating – Manually Customizing the Project:

Another option for updating a ThinApp project is to directly modify the application’s files/registry settings within the ThinApp project. A minimally skilled application packager can easily accommodate simple modifications to a ThinApp project by simple file manipulation. As ThinApp has no need for an external editor GUI, this is easily accomplished via Windows Explorer and Notepad.

Project Customization  in Windows Explorer

One can simply edit the files within the project just as they would on a natively installed version of the application. Simply replace the actual path with the variable path to find the files and folders you are looking for.


 

Virtual Registry Hive Mods - Beware!

One thing to beware of when modifying the virtual registry hive text files is to ensure the file is edited properly and spaces are left between each of the registry key sections.

Registry Hive Text  File Editing

 

ThinApp Project Updating - SBMERGE:

Aside from the above, the last way to update a ThinApp Project is to import the settings from within the Application’s Sandbox.

Remembering the sandbox to be a “Runtime Modification Storage Area”, this means if the application packager can install the update through the virtual bubble, the update is applied to the sandbox.

To do this…

  1. Start with a clean sandbox – otherwise one runs the risk of contaminating the application with additional modifications or settings which might be undesirable.

  2. If the application has a built in update feature, just launch the application and run the update feature. If the application update is via a separate hotfix / update, run the update.
    NOTE: The person who is the application packager may have to reconfigure the PACKAGE.INI in order to allow access to the virtual CMD or other tools to view the virtual file system and launch the hotfix / update. Typically this is a simple modification to the Entry Point for those items within PACKAGE.INI – setting the “Disabled=1” value to “Disabled=0” or remarking it out with a semicolon. This modification requires a rebiuld of the ThinApp package before applying the upate to the app sandbox and executing the sandbox merge into the project via SBMERGE.EXE. Then, once the updated sandbox is merged, resetting the “Disabled=0” value to it’s original state and rebuilding will remove access to the ThinApp via that specific Entry Point (i.e. CMD, etc.).
  3. Once the update is in the app and everything has been tested to work, use SBMERGE to merge the sandbox back into the project.


 

Simple SBMERGE Process:

Here is my simple SBMERGE procedure which works flawlessly every time:

  1. Make a copy of the original ThinApp Project WITH the BIN folder and it's contents (EXEs/Data Container).
  2. Clear the SANDBOX within the %APPDATA%\THINSTALL folder.
  3. Run the primary app in the project to be updated.
  4. Update the app with plugins, settings, updates, modifications. Close the app.
  5. Relaunch the app and test the updates exist and work.
  6. Close the app.
  7. Open CMD natively.
  8. Change Directories (CD) into the project to be updated.
  9. Type "SBMERGE APPLY"
    NOTE: If successful, the ThinApp Sandbox for this packaged app will have been removed from %APPDATA%\Thinstall.
  10. Execute BUILD.BAT within the project just updated by SBMERGE.
  11. Run new version of ThinApp packaged app to test updates/mods.
  12. Deploy via AppSync, Side-by-Side, MSI (via ESD), etc.

This was previously documented here on the ThinApp Blogs.

To learn more click here

]]>
aj@ervik.as (Alexander Ervik Johnsen) Vmware ThinApp Mon, 31 May 2010 10:15:03 +0000
VMware Fusion 3.1 with over 20 New Features and up to 5X Faster 3D Graphics http://www.ervik.as/index.php/vmware-mainmenu/fusion/2857-vmware-fusion-31-with-over-20-new-features-and-up-to-5x-faster-3d-graphics http://www.ervik.as/index.php/vmware-mainmenu/fusion/2857-vmware-fusion-31-with-over-20-new-features-and-up-to-5x-faster-3d-graphics VMware, Inc.  announced the worldwide availability of VMware Fusion 3.1 -- the best way to run Windows on the Mac -- as a free update to all VMware Fusion 3 users.


"We're excited to deliver the fastest and most reliable Windows on Mac experience available with VMware Fusion 3.1," said Pat Lee, director, personal desktop products VMware. "While we continued to deliver rock-solid reliability and ease of use with VMware Fusion 3, customers asked for even better graphics performance and more speed for their Windows applications. With VMware Fusion 3.1, we incorporated their feedback to deliver significant performance gains without disrupting the reliability they've come to expect from VMware." With more than 20 new features, key highlights of VMware Fusion 3.1 include: Faster: With faster application launching, more seamless scrolling, quicker resume from suspend, and better overall disk performance, VMware Fusion 3.1 delivers 35% better end-to-end performance compared to its predecessor, VMware Fusion 3.0.

Better 3D Graphics Performance: Greatly improved Windows Aero performance and OpenGL 2.1 support for Windows Vista and Windows 7 delivers up to 5X better 3D graphics performance. VMware Fusion 3.1 is also supported and recommended by Autodesk for AutoCAD 2011.

Switch to Mac with Ease: The fastest and least expensive way to bring a customer's entire PC to a Mac, VMware Fusion 3.1 includes all of the software tools needed to migrate over a standard Ethernet cable, FireWire cable or even wireless network -- saving customers from purchasing special cables that will only be used once.

USB EasyConnect: Makes it easier than ever to assign a USB device to a virtual machine or a Mac and remembers preferred choice.

Unity: Exclusive support for Mac OS X Snow Leopard's Dock Exposé makes it even more seamless to use Windows apps like Mac apps.

Support for Larger Virtual Machines: With added support for 8-way SMP and an increased virtual hard disk size from 950 GB to 2TB, advanced users get more power and punch out of the Mac Pro and Xserve from Apple.

"VMware Fusion 3.1 has made my Windows PC obsolete. With VMware Fusion 3.1, it's faster to start and use Windows on my MacBook Pro than it is to use my physical PC," said Tony Arnold, Founder of The Cocoabots. "The great leap in graphics performance makes Windows Aero sing, allowing me to play games I could never play before on my MacBook Pro." Availability and Pricing: VMware Fusion 3 users can automatically download the free update to VMware Fusion 3.1 via the built-in software update feature. Users who wish to upgrade from previous versions of VMware Fusion may do so online at vmware.com/fusion for $39.99 (USD). For new users, VMware Fusion is available at vmware.com/fusion, the Apple Online Store® (apple.com), Apple retail stores, Amazon.com, and other authorized resellers. The suggested retail price of $79.99 (USD) includes all of the software needed to switch from a PC to a Mac.

About VMware: VMware delivers solutions for business infrastructure virtualization that enable IT organizations to energize businesses of all sizes. With the industry leading virtualization platform -- VMware vSphere? -- customers rely on VMware to reduce capital and operating expenses, improve agility, ensure business continuity, strengthen security and go green. With 2009 revenues of $2 billion, more than 170,000 customers and 25,000 partners, VMware is the leader in virtualization which consistently ranks as a top priority among CIOs. VMware is headquartered in Silicon Valley with offices throughout the world and can be found online at www.vmware.com.

VMware and VMware Fusion are registered trademarks and/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. The use of the word "partner" or "partnership" does not imply a legal partnership relationship between VMware and any other company.

]]>
aj@ervik.as (Alexander Ervik Johnsen) Fusion Thu, 27 May 2010 18:02:10 +0000
VMware ThinApp 4.5 available for download http://www.ervik.as/index.php/vmware-mainmenu/vwmare-thinapp-mainmenu/2696-vmware-thinapp-45-available-for-download http://www.ervik.as/index.php/vmware-mainmenu/vwmare-thinapp-mainmenu/2696-vmware-thinapp-45-available-for-download VMware has released an updated version of their ThinApp software.

Here is a quick overview of what's new in ThinApp 4.5:

The 4.5 release adds the following features to improve usability, performance, and updates:

  • Support for Windows Server 2008 R2, 32-bit Windows 7, and 64-bit Windows 7 operating systems.
  • ThinApp version updates to incorporate the latest features or support enhancements without rebuilding packages. The relink.exe utility updates existing packages.
  • Compression of MSI packages that uses the MSICompressionType parameter to improve the ThinApp SDK performance.
  • Reduced memory consumption and page file usage to improve startup performance. The OptimizeFor parameter works with the CompressionType parameter to customize memory performance and startup time.
  • Anonymous collection of statistics to expand the support for applications. You can use the Setup Capture wizard or the QualityReportingEnabled parameter to help VMware build support for applications and help you migrate more native applications to a virtual environment.
  • Loading of DLL files as virtual DLL files without using API functions. The ForcedVirtualLoadPaths parameter loads external system DLL files that depend on DLL files inside the package.
  • Product interface updates to improve usability and link to video and documentation information. German and Japanese versions of the ThinApp User's Guide are available.

Click here to download VMware ThinApp 4.5

]]>
aj@ervik.as (Alexander Ervik Johnsen) Vmware ThinApp Wed, 17 Mar 2010 11:11:13 +0000
VMware Workstation 7.1 Beta released for download http://www.ervik.as/index.php/vmware-mainmenu/vmware-workstation/2684-vmware-workstation-71-beta-released-for-download http://www.ervik.as/index.php/vmware-mainmenu/vmware-workstation/2684-vmware-workstation-71-beta-released-for-download The VMware Workstation 7.1 Beta includes several new features and hundreds of minor improvements. Some release highlights include:

  • OpenGL 2.1 support for Windows 7 and Vista guests: The addition of hardware accelerated OpenGL 2.1 support to the WDDM driver enables many more graphics applications to run inside of your virtual machines.
  • Improved graphics performance: Significant enhancements have been made to the VMware WDDM driver that have produced benchmark results that are up to 80% faster. The updated driver also produces smoother video playback and addresses many reported rendering issues. Of course games run better as well!
  • 8-way SMP support plus virtual disks up to 2TB in size: The virtual hardware continues to become more powerful to meet the needs of Workstation customers who are running server class applications.
  • OVF 1.0 support: Including the OVF Tool with this release enables users to easily import or export virtual machines and vApps and move them to vSphere or up into the cloud.
  • Direct Launch: Blur the distinction between running native and virtual applications by launching an application installed in a virtual machine directly from the start menu or taskbar of the host system.
  • Automatic software updates: These VMware applications can now detect when a new version is released and are able to update at the click of a button.
  • Fedora 12 virtual machines: We are excited about finally offering support for running one of the most popular Linux distributions on the planet!

Click here to download and read more

]]>
administrator@ervik.as (Administrator) Vmware Workstation Mon, 15 Mar 2010 10:29:00 +0000
F5 and VMware Solution Yields 10x Improvement in Long Distance Live Migration Performance Using VMware VMotion http://www.ervik.as/index.php/vmware-mainmenu/vmware-vsphere-4/2613-f5-and-vmware-solution-yields-10x-improvement-in-long-distance-live-migration-performance-using-vmware-vmotion http://www.ervik.as/index.php/vmware-mainmenu/vmware-vsphere-4/2613-f5-and-vmware-solution-yields-10x-improvement-in-long-distance-live-migration-performance-using-vmware-vmotion F5 Networks, Inc. (NASDAQ: FFIV), the global leader in Application Delivery Networking (ADN), today announced deployment guidance and test results that illustrate and validate the value of deploying F5® and VMware solutions in concert to extend live migration capabilities across long distances for VMware vSphere 4 environments in a secure, accelerated manner.

Building on the previous announcement and demo at VMworld 2009, these test results confirm that organizations can securely migrate live, virtualized web applications - and their associated storage - between data centers thousands of miles apart without downtime or user disruption using F5® and VMware products available today.

The integrated solution enables organizations to rapidly respond to changing application and business requirements by seamlessly migrating live applications across geographically dispersed data centers.

Details

VMware VMotion is deployed in production by a significant number of VMware customers to migrate virtual machines and data. The joint F5 and VMware solution helps solve latency, bandwidth, and packet-loss issues, which historically have prevented customers from performing live migrations between data centers. Long distance virtual machine migration across distributed data centers typically required the operator to halt online sessions, suspend the image, migrate the image to the new data center, and then bring the virtual machine back online at the new data center. This process could require significant downtime. Moreover, once the virtual machine was back online at the new data center, clients with previously established sessions would still be unable to access the migrated application until they received an updated DNS record aligning with the new location. This new solution mitigates the impact of migrating virtual machines across long distances - allowing live migration and automatic redirection of sessions - thus making the experience seamless to users.

A flexible Application Delivery Network is the fundamental component required to extend live migration capabilities beyond a single data center. There are two key ADN components to the new solution:

  • BIG-IP® WAN Optimization Module (WOM) secures and accelerates VMware VMotion and VMware Storage VMotion traffic up to 10x when compared to attempting long distance live migration without the solution—even over links that are subject to bandwidth, latency, or packet-loss issues. BIG-IP WOM encrypts and compresses data between BIG-IP devices, extending the effective distances of migrations and decreasing replication time for offline transfers.
  • BIG-IP Local Traffic Manager (LTM) and BIG-IP Global Traffic Manager (GTM) enable local and global redirection of established and new web application sessions before and after the migration. This overcomes many of the networking hurdles that previously prevented organizations from migrating live applications between data centers.

Supporting Quotes

“VMware VMotion and Storage VMotion capabilities are significant differentiators for VMware vSphere,” said Parag Patel, Vice President, Alliances at VMware. “F5’s technology complements VMware solutions, making it possible to execute live workload migrations over greater distances. Combining VMware vSphere with BIG-IP® solutions expands the many use cases possible, and adds to the value we’re able to offer customers.”

“According to recent ESG research, increasing server virtualization usage is the top overall IT priority facing organizations over the next 12 to 18 months,” said Mark Bowker, Senior Analyst with Enterprise Strategy Group. “The mobility of virtual machines now provided by F5 and VMware will help companies distribute workloads across data centers, relocate applications closer to the end-user, and perform live data center migrations.”

“F5 and VMware are working closely to integrate Application Delivery Networking and virtualization with the goal of making our customers’ application infrastructures more resilient and responsive to business needs,” said Jim Ritchings, VP of Business Development at F5. “This joint solution frees applications from infrastructure constraints for maximum flexibility and business agility. We look forward to continued collaboration and innovation with VMware to address the growing demand for flexible virtualization solutions.”

Availability

F5’s step-by-step solution deployment guide for long distance live migrations performed with VMware VMotion can be downloaded from f5.com. This resource includes general guidelines on expected performance gains and the types of applications best suited to long distance live migrations with VMware VMotion.

All products integrated within the joint solution are available today from F5 and VMware, respectively.

To learn more about how F5 and VMware solutions help customers virtualize their infrastructures and improve IT agility, please visit www.f5.com/solutions/applications/vmware/virtualization/

]]>
aj@ervik.as (Alexander Ervik Johnsen) VSphere 4 Mon, 08 Feb 2010 13:03:26 +0000
VMware View and ThinApp Integration Guide http://www.ervik.as/index.php/vmware-mainmenu/vwmare-view-3-mainmenu/2586-vmware-view-and-thinapp-integration-guide http://www.ervik.as/index.php/vmware-mainmenu/vwmare-view-3-mainmenu/2586-vmware-view-and-thinapp-integration-guide Many of you who design, administer, and implement VMware View environments have probably encountered the discussion of how to integrate ThinApp into View desktops.  So FYI there is a series of posts on the ThinApp Blog which discuss a strategy for integration. The ThinApp Blog has a series of posts, Integrating ThinApp Packages with View Part 1Integrating ThinApp Packages with View Part 2View and ThinApp Integration Guide - Part 3 or you can download the end product of that series . . . the VMware View and ThinApp Integration Guide.  The guide discusses several of the topics covered in the previous posts but brings it all together with some task based scenarios that walk you through initial setup and configuration with screenshots and sample scripts.

 

So if you are looking for answers to these questions, this guide is for you.
  1. How does ThinApp fit in with View Persistent and Non-Persistent Pools?
  2. Should I stream all my ThinApp packages from a fileshare or deploy them into the VMs?
  3. How do I use ThinApp and View Composer together?
  4. Where you I put my ThinApp packages? On the C:, the User Data Disk, a fileshare?
  5. How do I manage updates after the packages are in use?
  6. Will users keep their unique settings like toolbar buttons when running ThinApps from different desktops?
  7. How do I manage shortcuts and FileTypeAssociations for multi-user VMs?


Click here to read the full article
]]>
administrator@ervik.as (Administrator) Vmware View Fri, 22 Jan 2010 10:22:59 +0000
VMware Announces Go Virtualization Solution http://www.ervik.as/index.php/vmware-mainmenu/vmware-go/2564-vmware-announces-go-virtualization-solution http://www.ervik.as/index.php/vmware-mainmenu/vmware-go/2564-vmware-announces-go-virtualization-solution VMwareVMware Go™ provides a quick and easy way for small businesses with limited IT resources and time to get started with virtualization

PALO ALTO, Calif.,– January 13, 2009 – VMware, Inc. (NYSE: VMW), the global leader in virtualization solutions from the desktop through the datacenter and to the cloud, today announced the availability of VMware Go™, a web-based service that allows small or medium businesses (SMBs) to virtualize servers and create running virtual machines with just a few clicks of a mouse. VMware Go™ provides SMBs with an easy on-ramp to virtualizing their applications by automating the installation and configuration of the industry-leading hypervisor, VMware ESXi.

“With VMware Go™, we are eliminating the skill barrier for getting started with virtualization, so companies who are concerned about not having the IT resources or expertise, especially SMBs,  can now more quickly and easily enjoy the many benefits of virtualization,” said Dan Chu, Vice President of Emerging Products and Markets, VMware. “Both VMware Go™ and VMware ESXi are free offerings that can provide instant cost-savings with improved server utilization, reduced energy use and centralized management of the datacenter so IT can focus more on innovation and less on maintenance.”

One of the major barriers of SMB adoption of virtualization has always been a lack of confidence that the implementation process will work right the first time," said Tim Cox, Principal at Cox Technical Services. "As such, I welcome VMware Go because it opens virtualization to a large market of SMBs who didn't think they had the knowledge to virtualize their servers. It is an awesome tool to introduce people to virtualization or reintroduce them if they've been away from it for awhile."

VMware Go™ has already successfully created over three-thousand virtual machines for over one-thousand beta testers. VMware Go™ together with VMware ESXi provides companies with a quick way to reduce overhead and simplify business operations by running multiple operating systems and applications on a single server – spending less money on hardware, power and cooling, and server administration.

“As I talk to IT Admins in the SMB market, what I have learned is that as their business grows, IT  maintenance and the need for more servers grows even faster,” said David Davis, vExpert, VCP, and VMware video training author at computer training provider Train Signal. “With VMware Go and VMware ESXi, these same SMB IT centers can handle large influxes of server growth or perform virtual consolidation while saving time, money and resources in the process.”

VMware Go™ Dramatically Simplifies and Accelerates Virtualization In Three Simple Steps
1. Initial ESXi server setup

  • Unique web-browser interface and intuitive wizard guides and accelerates installation and setup process
  • Built in hardware compatibility check automates the process of selecting physical server environments

2. Virtual machine creation

  • Leverage existing physical server configuration, install a prebuilt virtual appliance, or start with a new, clean virtual machine.

3. Manage ESXi servers and virtual machines

  • Centralized management interface simplifies changes to a virtual environment.
  • Monitor virtual machines for basic performance and resource utilization.
  • Scan and update virtual machines from a central console.

Cost-conscious businesses looking to move to the cloud might consider WMware's "Go" virtualization offering.

Virtualization specialist VMware announced the release of of VMware Go, a Web-based service that helps small to medium-size businesses to virtualize servers and create running virtual machines simply and efficiently. The company positions Go as an on-ramp for SMBs virtualizing their applications by automating the installation and configuration of the hypervisor VMware ESXi, which allows midmarket companies to run multiple operating systems on a single server and reduce hardware costs.

VMware said Go has already created more than 3,000 virtual machines for more than 1,000 beta testers and together with VMware ESXi provides companies with a faster way to reduce overhead and simplify business operations by running multiple operating systems and applications on a single server, resulting in spending less money on hardware, power and cooling, and server administration.

"With VMware Go, we are eliminating the skill barrier for getting started with virtualization, so companies who are concerned about not having the IT resources or expertise, especially SMBs, can now more quickly and easily enjoy the many benefits of virtualization," said Dan Chu, vice president of emerging products and markets for VMware. "Both VMware Go and VMware ESXi are free offerings that can provide instant cost-savings with improved server utilization, reduced energy use and centralized management of the datacenter so IT can focus more on innovation and less on maintenance."

Chu said Go simplifies and accelerates virtualization in three steps: Initial ESXi server setup, through a Web-browser interface and intuitive wizard guides that accelerates installation and setup process and built in hardware compatibility check that automates the process of selecting physical server environments, virtual machine creation that helps SMBs leverage existing physical server configuration, install a prebuilt virtual appliance, or start with a new, clean virtual machine, and lastly, manage ESXi servers and virtual machines with a centralized management interface that simplifies changes to a virtual environment, the ability to monitor virtual machines for basic performance and resource utilization and scan and update virtual machines from a central console.

"As I talk to IT admins in the SMB market, what I have learned is that as their business grows, IT maintenance and the need for more servers grows even faster," said David Davis, vExpert, VCP, and VMware video training author at computer training provider Train Signal. "With VMware Go and VMware ESXi, these same SMB IT centers can handle large influxes of server growth or perform virtual consolidation while saving time, money and resources in the process."

For further information about VMware Go™, please visit http://www.vmwarego.com/

]]>
aj@ervik.as (Alexander Ervik Johnsen) VMware Go Thu, 14 Jan 2010 19:46:04 +0000
Application Troubleshooting Tools and Tips for VMware ThinApp http://www.ervik.as/index.php/vmware-mainmenu/vwmare-thinapp-mainmenu/2550-application-troubleshooting-tools-and-tips-for-vmware-thinapp http://www.ervik.as/index.php/vmware-mainmenu/vwmare-thinapp-mainmenu/2550-application-troubleshooting-tools-and-tips-for-vmware-thinapp Here are the most commonly asked tips and tricks as well as tribal knowledge and types of tools are good to use when working with and troubleshooting cumbersome applications. This article is meant to be a general guide on types of application troubleshooting tools and tips and tricks with regard to troubleshooting applications and ThinApp projects.

Requirements

The following items and knowledge are required for use of this procedure:

DISCLAIMER!

This site may contain information about third party products, services, tools and/or applications that are not owned or controlled by Ervik.as.Ervik.as does not endorse or make any representations or warranties about such third party products, services, tools and/or applications referenced in this site.

Notes:

It should be noted that the tools and applications listed are just examples of what can be used for application troubleshooting in general and techs should not limit themselves to just the applications/tools mentioned.  Don't just think "outside the box" - think inside the app.  What does the app need or want to see?  What tool will tell you or help you find out what that app is looking for?  Once this information is found, how can you get the application to behave in a manner that works properly in your network environment?  Is there some tool which will help you make that cumbersome app work the way you want/need it to?

Those are the general things to keep in mind when working with an application, regardless of ThinApp or not.

Application Troubleshooting Tools


Running Process Viewers

One of the first things needed is a process viewing tool which, at minimum, shows all running processes in a detailed manner.  Having a process viewer which shows what files, registry keys and other objects processes have open, which DLLs they have loaded, etc., is a big plus when trying to find out what the troublesome application is attempting to do.

An example of a process viewer which provides more details than the built in tool is Process Explorer by Microsoft.

Activity Loggers

It is a must to have a process monitoring tool which will log all activity of an application and allow a tech to review which folders, files, registry keys, registry entries, and other objects is a must.  This kind of tool can be used as a first step in troubleshooting a misbehaving application in general (ThinApp non-specific).

An example of a process monitoring tool is Process Monitor by Microsoft.  Additionally, Microsoft has retained the predecessors to this tool which are FileMon and RegMon by Sysinternals.


Dependency Viewers

A dependency viewing tool will allow a tech to select an application's executable and view all modules it is dependent upon.

A tool that falls into this category is Dependency Walker – a free tool that is available for download from http://www.dependencywalker.com.


Open Handle Viewers

Every now and then it is necessary to see what open handles are locking a file or registry entry.  Having a tool which shows that is a plus.

An example of something that shows this is Handle by Microsoft.


File Explorer

The majority of all techs use the built in Windows Explorer and Command Line to browse and manipulate the file structure but there are plenty of other file explorer and editing tools available for free or for a small price on the Internet.

Examples of 3rd party file explorers which should work within a ThinApp packaged application are the A43 File Manager (which does not need to be installed but can be copied into a package) and Windows File Explorer by Soft32.com (which requires an installation at the same time as the application).


Registry Editor

To mirror the file explorer comments, most techs use the built in Windows Registry Editor to view, browse, and modify the registry of a Windows system.  There are plenty of free and inexpensive registry editors available for download from the Internet which have different functionalities.


ThinApp Packaging and Troubleshooting Tools


Folder Isolation Viewer

While there is no substitute for knowing how to work with a file structure in Windows Explorer and a Command Line, it is sometimes necessary to get a different view of the file structure with isolation levels.  Having a graphical interface tool which can quickly display a ThinApp project's folder isolation settings can prove to be very helpful.

There are plenty of free tools which can be used for this.  Examples are the Thinstall Helper by the CIS Group and the Folder Isolation Viewer by Bob Carter.


NOTE: 3rd party tools should be used with care as some of them are written for specific versions of either ThinApp or Thinstall and may not work correctly with projects created by newer versions of ThinApp.


Registry Isolation Viewer

To mirror the comments about the Folder Isolation Viewer, there is no substitute for knowing how to work within the Windows Registry; however, there are times when a graphical representation can help.

There are a number of freely available tools on the Internet.  Examples are the Thinstall Helper by the CIS Group and the Registry Isolation Viewer by Bob Carter.


NOTE: 3rd party tools should be used with care as some of them are written for specific versions of either ThinApp or Thinstall and may not work correctly with projects created by newer versions of ThinApp.


ThinApp Log Monitor

ThinApp's own log monitor utility is great for monitoring everything a packaged application does or attempts to do.   It can provide numerous amounts of information with regards to any issue the package application may be having.


Large Text File Viewer

It is essential to have a text editor for viewing large log files and ThinApp registry files.  While Windows Notepad is easy to use in a pinch, because of the fact that ThinApp's Log Monitor utility can generate text files in excess of 1GB in size, it is beneficial to have a text file editor which can view and manipulate text files of larger sizes as Windows Notepad cannot handle files beyond 1GB very well.

EditPad Lite by JGSoft and Notepad Lite by GridinSoft are examples of free text editors capable of reading large text files.


Comparison Utility

Having a tool which can compare files, folders, and registries is highly beneficial for comparing ThinApp Projects for differences when one package works and another package doesn't.

A comparison utility available for purchase is Beyond Compare by Scooter Software.
NOTE: At last check, Scooter Software gives 20% discounts on Beyond Compare purchases by entering the discount code of "THINAPP".


Multilanguage Scripting Editor

Another tool worth having is a Multilanguage script editor – specifically something that can handle VBS, BAT, CMD, and INI files, and give abilities to interface with DBs, LDAP, ADSI, WMI, and COM objects.  Having a script editor which can also build executables out of the scripts which it can support is also a plus.

An editor that falls into this category is Admin Script Editor by iTripoli.
NOTE: At last check, iTripoli gives 20% discounts on any purchase of Admin Script Editor by entering the discount code of "THINAPP".


ThinApp Multi-Version Builder Utility

When testing against issues which may potentially be related to ThinApp, it is very beneficial to have a way to easily test a package against multiple versions of ThinApp.  This tool easily allows the building of ThinApp projects into packages with different versions of ThinApp.

This tool can be found on the T3chNot3s blog.


NOTE: This is a 3rd party blog which is NOT sponsored in any way by VMware. 3rd party tools should be used with care as some of them are written for specific versions of either ThinApp or Thinstall and may not work correctly with projects created by newer versions of ThinApp.


ThinApp Multi-Version MSI Loader

This tool works in support of the afore mentioned ThinApp Multi-Version Builder Utility as it allows techs to easily load up ThinApp MSIs for multiple different versions of ThinApp.

This tool can be found on the T3chNot3s blog.


NOTE: This is a 3rd party blog which is NOT sponsored in any way by VMware. 3rd party tools should be used with care as some of them are written for specific versions of either ThinApp or Thinstall and may not work correctly with projects created by newer versions of ThinApp.


ThinApp Tips


Long File Names Issue

Often times when packaging larger projects, techs will run into long file name issues when using the default folder of "C:\Program Files\VMware\VMware ThinApp\Captures".  An easy fix for this is to not use the Captures folder in this location but to create another captures folder off the root of the C: drive ("C:\Captures").  Another way to easily fix this issue is to create a substitute drive which maps directly to the "C:\Program Files\VMware\VMware ThinApp" folder.  The command is as follows:
SUBST.EXE "C:\Program Files\VMware\VMware ThinApp"


NOTE:  The above command can also be placed in a shortcut located in the Startup folder of the packaging system.


Running Explorer and 3rd Party File Browsers

Running an application which spawns a Windows Explorer window will, by default, launch that EXPLORER.EXE process outside the virtual environment.  This is due to embedded settings within the Windows Operation System and EXPLORER.EXE itself.  The EXPLORER.EXE process is actually designed to first check to see if another instance of EXPLORER.EXE is running and, if not, launch itself as the desktop shell.  Therefore, all Windows Explorer processes will always reside in the physical environment unless the initial EXPLORER.EXE process is launched within the virtual environment.  See the ThinApp blog article on Running EXPLORER.EXE Inside the Bubble as well as the blog article on Creating Windows Entry Points for Troubleshooting ThinApp Packages – both can be found on the VMware ThinApp Blogs.


A number of 3rd party file browsers are present on the Internet for download which can be utilized to give the user and/or administrator of the ThinApp packaged application a view into the virtual file system – or at least, what the application thinks is the real file system.

An example of a free file browser is the A43 File Manager.  To utilize this tool, place a copy of it into your ThinApp project and create an entry point for it within your ThinApp Project's PACKAGE.INI file.


Folder Sharing

Sharing out the VMware ThinApp folder on the host system is also a great way to allow VMware Workstation VMs running on that system access to save ThinApp Project captures by default (without manual intervention).  This means that ThinApp does not have to be installed onto the VMs prior to capturing and project folders do not need to be manually copied off the VMs prior to restoring the VMs to a known good snapshot.

See the article on How to Make a ThinApp Application Package on the VMware ThinApp Blogs.


Sandbox Redirection

Redirecting the default sandbox for test systems to a folder of easy access (i.e. "C:\TEMP\SANDBOX") may be a way in which to easily troubleshoot packaged applications.

See the "Controlling the Sandbox Location" section of the ThinApp Online Documentation for more information.


Using Compression

If troubleshooting or fine tuning a ThinApp package where constant rebuilds are occurring, it may improve efficiency in testing on larger projects if FAST compression is used as this decreases the time of the subsequent builds/rebuilds of the package in question.  This occurs because ThinApp creates a Build Cache where it stores all compressed files in the event of subsequent builds of the project.


Note:  Some files or file types in a project may have issues with being compressed.


Adjusting the SNAPSHOT.INI

In some instances, you may be wondering how to not continually capture a specific file or registry setting. The default settings of ThinApp can be modified by editing the SNAPSHOT.INI file in the VMware ThinApp folder. These are the default settings with which ThinApp Setup Capture operates by.


Why would you modify this file? Well, maybe you have a utility program set to run upon startup of your VM and you don't wish for the outcome of that to be captured by ThinApp. Or, maybe you need to capture a Windows setting which, by default, is set to NOT be captured so that your application will properly run when packaged with ThinApp. Or maybe you are building specific versions of the same application and you know you need certain folders or registry settings to always be set to WriteCopy vs. Full or Merged. These types of modifications can be made by customizing your SNAPSHOT.INI.


NOTE: It is recommended to make a backup of the SNAPSHOT.INI prior to any modifications!!


Periodic Cleanup

Periodically performing cleanup of the ThinApp Build Cache is function which can keep the build system from running out of disc space.  Check the size of the "%USERPROFILE%\Local Settings\Application Data\Thinstall\BuildCache" folder and delete its contents if you deem it safe to do so.

Run the App

One of the biggest tips for properly capturing an application is, once the application is installed, run the application.  This is not only for testing the application - for an application which won't work natively in Windows will not work as a ThinApp packaged app either (i.e. Junk In - Junk Out) - but also for the many types of applications which don't finish their setup until the first run of the application.  An example would be applications which ask for file type associations upon first launch.

 

VMware Workstation Snapshots

VMware sells ThinApp with a licensed copy of VMware Workstation for a couple of reasons.  First and foremost, this is done to give customers an environment which is not intermixed in any way with their production system.  Secondly, this is done to keep customers from having to reallocate a production system or purchase a lab specific system for packaging, and finally, it's done to add in the snapshot abilities of VMware Workstation.

A single clean Windows VM can be snapshotted at the clean build state and cloned (full or linked) to create a near infinite number of test environments.  Because of this, one can conduct a pre-installation ThinApp Setup Capture, install the application, test it, and keep this configuration for later troubleshooting, but still be able to role back to a clean build for additional application packaging.

 

Setup Capture Command Line for GUI

A big benefit of using ThinApp over competitor products to package applications is it's use of the tried-and-true delta snapshot technology and it's non-requirement to be running during the installation of an application.  In short, this means one can install the application exactly the same way they would install it on a regular workstation.  More importantly, this means the clean VM can be rebooted as many times as necessary.  After each reboot of the VM, ThinApp Setup Capture will re-launch, picking up where it left off.  If the application installation or configuration is not complete, simply cancel the setup capture or close it by clicking the red "X".

This information to relaunch the GUI upon login is stored in registry under the following key.
HKEY_CURRENT_USER\SOFTWARE\MICROSOFT\WINDOWS\CURRENTVERSION\RUN
Entry:  ThinApp Setup Capture Continue
Value:  "<DRIVE:\><PATH\>SETUP CAPTURE.EXE" "<DRIVE:\><PATH\><SNAPSHOT FILE.SNAPSHOT>" "<SCAN ITEMS>"
Type:  REG_SZ:

It should be noted for those who use the GUI that some applications installations will wipe the HKEY_CURRENT_USER\SOFTWARE\MICROSOFT\WINDOWS\CURRENTVERSION\RUN registry key of all it's entries, and in doing so also remove the ThinApp Setup Capture Continue entry as well.

To work around this, simply locate the initial SNAPSHOT file - usually located in the account's %TEMP% folder although sometimes found in the %PROGRAMFILES%\VMware\VMware ThinApp\ folder- and run the value from the run window or command line.

NOTE:  You will need to remember your initial scan settings.  Default is the C: drive, the HKEY_LOCAL_MACHINE and HKEY_USERS hives.

Example:
"C:\Program Files\VMware\VMware ThinApp\Setup Capture.exe" "C:\DOCUME~1\Admin\LOCALS~1\Temp\{7498EF29-9F66-4018-BAD3-B0B5E645CACB}.snapshot" "C:\ HKEY_LOCAL_MACHINE HKEY_USERS"

NOTE:  The above command line is a single line but may appear word wrapped in your browser.

ThinApp Packaged App Troubleshooting - Slow Apps

Often times we hear the app works but starts up slowly.  The first thing to help you here is this; does it start slowly the first time ONLY or does it start slowly each and every time.  Remembering the application is creating, building, and extracting contents to the sandbox a little more so the first time it executes, we can assume that if the application only runs slow the first time, it must be something which is being extracted, created, built, or otherwise dumped to the sandbox.

Regardless of this, here are some additional items to check:

  • Services are starting up.  It could be the case the services are not needed – if so, disable the services either in the ThinApp Project registry (HKEY_LOCAL_MACHINE.TXT file) or set the AutoStartServices=0 BuildOption in the PACKAGE.INI.  If the services are needed and they are taking a long time to launch, test the services start/stop times on a native Windows clean VM and see if the same thing happens there.  If so, a call to the app manufacturer is in order.
    Example:  Office will load and set the Machine Debug Manager (MDM.EXE) service and CTFMON.EXE services to auto-start.  These are not necessarily needed to launch a ThinApp'ed version of Office and can usually be disabled.
  • Fonts being extracted on the fly to the sandbox during initial startup.  Look for a %FONTS% folder in the sandbox and copy it into the ThinApp project.  Rebuild the ThinApp project and retest this.
  • Awaiting numerous fonts to be loaded.  Sometimes an app will load every font it can find.  In this scenario, it might be wise to remove all but the necessary fonts from the %FONTS% folder in the ThinApp Project and install them natively to the Windows host.
  • Auto-repair functions.  Most apps will auto-repair themselves when they detect something incorrectly configured – and sometimes ThinApp will cause this if isolation or other settings are not properly configured in the ThinApp package.  Look for things like the MSIEXEC.EXE process/service running (attempt to stop if possible) and other app-specific auto-repair functions or processes.  Seeing these run may indicate a misconfigured application and often times kick off an auto-repair of the application without even showing this process to the user executing the application (ThinApp’ed or not).
  • Excessive package size.  If the ThinApp project is excessive in size (there is no specific size here - it's specific to what the environment can handle), it can take longer to load depending upon how the application works and loads itself, and - of course - the environment it is running on.  Remove unnecessary items from the ThinApp project before building.  Typically items such as the following can be removed from a project (MAKE A BACKUP OF THE PROJECT FIRST!):
    • %SYSTEMROOT%\INSTALLER — The contents of this folder will likely contain some MSI files – these MSI files can usually be removed if they are not needed.
    • %APPDATA%, %LOCAL APPDATA%, and %PROFILE% -- Since these folders are all part of the user’s “profile”, if the application is installed to the entire system (meaning, anyone can login to the specific system the app is installed on and launch the app), then the contents of these folders are not typically needed unless it is desired to package the customer user configuration information with the application.
    • %PROGRAMFILESDIR%\<app folder>\<app backup folder> -- Sometimes an application will install a backup of itself into a subfolder of the %ProgramFilesDir%\App folder. This is typically for auto-repair functionality as well, much like the %SYSTEMROOT%\INSTALLER folder contents are for repairing the app.
      Example:  Adobe products (depending upon the product and the version of the product) will often store a complete backup of the installation source code in %PROGRAMFILESDIR%\ADOBE\<Product>\Setup Files.  Sometimes it's hidden in %PROGRAMFILESDIR%\ADOBE\ADOBEPATCHFILES as well.  So...it boils down to "Know Thine App"!
    • %COOKIES%, %HISTORY%, and %INTERNET EXPLORER CACHE% -- Unless actually capturing an IE application or an IE plugin/addon, these folders may not be needed for your specific application, and thus the entire folder can be removed.
Click here to read the full article

]]>
aj@ervik.as (Alexander Ervik Johnsen) Vmware ThinApp Mon, 11 Jan 2010 13:26:19 +0000
ThinApp PACKAGE.INI File Explained http://www.ervik.as/index.php/vmware-mainmenu/vwmare-thinapp-mainmenu/2529-thinapp-packageini-file-explained http://www.ervik.as/index.php/vmware-mainmenu/vwmare-thinapp-mainmenu/2529-thinapp-packageini-file-explained So what is this PACKAGE.INI file anyways? What does it contain, why do I need it, and how can I use or modify it? These are common questions we get around the PACKAGE.INI file.

What is the PACKAGE.INI?

First and foremost, the PACKAGE.INI file is the the brains behind the project.

What does it contain?

It is where ThinApp stores all of the settings to the questions you answered within the ThinApp GUI.

In addition, it stores settings and configurations not configurable through the ThinApp GUI such as MSI, AppLink, and AppSync parameters.

Can I modify it?

Absolutely! Simply open it with NOTEPAD or any other text editor to modify it to fit your needs.

Where can I find help on the contents of the PACKAGE.INI?

For a very detailed read on every single setting within the PACKAGE.INI, you can go to the ThinApp Online Documentation and you will be able to find every single entry and subsequent values listed.

NOTE: Not ever entry will be present within your PACKAGE.INI, however default values will still be assumed.

What are the contents of the PACKAGE.INI File?

Notes and Help

ThinApp's Developers and Engineers took great care to make the PACKAGE.INI lay out in a logical format for easy access, reading, and manipulation. To that end, the very first thing listed is a URL. This URL, when pasted into your browser of choice, will bring up the very latest online help for your version of ThinApp!.

Compression and Isolation

The first two sections of note are COMPRESSION and ISOLATION. Under COMPRESSION is the CompressionType value which is quite simple as it's either NONE or FAST ("Fast" being the actual name of the PKZIP compression algorithm).

Specifically for ISOLATION, the Default Directory Isolation Mode (DirectoryIsolationMode) is the entry found underneath it. Another entry which can be manually entered underneath the ISOLATION section is the "RegistryIsolationMode". Both entries have values of either "Merged" or "WriteCopy". For further explanation on Isolation Modes, see the ThinApp Blog article (and subsequent embedded video) ThinApp 101: Differences Between the Isolation Modes.

NOTE: Do not use "Full" isolation in either "DirectoryIsolationMode" or RegistryIsolationMode" entries as this will prevent the application from seeing the Windows Operating System.

Build Options

Under the Build Options, you'll find numerous other settings, so I'll attempt to stick with the basics here to help keep things simple. It should be noted, however, the Build Option entries do not need to appear in any specific order or even at all since, as previously stated, any option not specifically present will have it's default value assumed.

MSI Parameters

Under this section you'll find every value you need in order to not only create an MSI but create it in any number of fashions - even allowing a regular user to execute the MSI or doing such things as configuring the parameters to use an MSI to update a ThinApp'ed application previously deployed with an MSI.

AppSync Parameters

The AppSync Parameters are remarked out by default and only placed within the PACKAGE.INI as an example of what to do in order to configure Application Syncing.

For additional information on Application Syncing, see the ThinApp Blog article (and subsequent video), AppSync Explained.

Parameters used only during Setup Capture
This title is not entirely true for this section as the AccessDeniedMsg entry is used for when the PermittedGroups or PermittedComputers entries are enabled and utilized.

 

As for the other entries, you'll find CapturedUsingVersion which simply denotes the ThinApp Version used to capture the application package in question and OutDir which tells ThinApp the folder to create and then dump the packaged app to.

General Purpose Parameters
    Under this section, you'll find a various set of entries. The typical ones being the following:

  • SandboxName= This is the name of the Sandbox folder created for the application (typically under the %APPDATA%\THINSTALL folder within the user's profile).
  • NOTE: Make sure you also read up on the Search Order for the Sandbox.

  • InventoryName= This is what is used to determine the default names of the project folder and sandbox during the application capture process.

  • ;PermittedGroups= The Active Directory or Local Windows Security Groups of users defined who may execute the ThinApp packaged application in question. Typically this is remarked out unless defined within the GUI.
  • NOTE 1: This value like any other PACKAGE.INI value, may be defined after the fact. Defining the PermittedGroups value after the fact can be done by entering the Security Group name or SID value. Using a Security Group's Name requires the system doing the build process have access to enumerate the Active Directory Group in question to look up it's respective SID value. NOTE 2: PermittedGroups and PermittedComputers entries can also be defined under each Entry Point for a packaged application suite such as Office in order to define specific security settings for each individual Entry Point (i.e. Word, Excel, Outlook, etc. only open for users of those respective groups - even if a user is only a member of the Word group and not the Excel or Outlook Groups - hence they cannot open Excel or Outlook, only Word).

  • ;RemoveSandboxOnExit= Remarked out by default but used to tell ThinApp to wipe the application's Sandbox upon exit of all parent and child applications within the respective ThinApp package.

  • ;SandboxNetworkDrives= This value, remarked out be default, is used to tell ThinApp to use the Sandbox for Network Drive access. The default is NOT to use the sandbox for Network Drives.

  • ;SandboxRemovableDisk= This value, remarked out be default, is used to tell ThinApp to use the Sandbox for Removable Media access. The default is NOT to use the sandbox for Removable Drives.

  • ;VirtualizeExternalOutOfProcessCOM= This entry, remarked out by default, controls whether external out-of-process COM objects can run in the virtual environment or not.

  • ;OptionalAppLinks and ;RequiredAppLinks entries are both remarked out by default. They are used to link the respective Parent ThinApp packaged application to any number of child ThinApp packages either on an optional or required basis. For additional information on Application Linking (AppLink) see the Configuring Dependent Applications with Application Link and the Application Linking articles in the online help.

  • VirtualDrives= The VirtualDrives entry is used to define what drive letters are to be virtualized by the ThinApp Virtual Operating System (VOS) for the application to see an interact with. A virtual drive can either exist natively as any other drive type or not exist natively but only virtually. Using this entry, one can create such things as a virtual CD drive for an application which normally requires a physical CD be inserted for proper execution - and then include the contents of the CD within the ThinApp package to eliminate the need for the physical CD.
  • NOTE: ONLY ONE VirtualDrives entry can be used within the PACKAGE.INI file. The second, remarked out, ";VirtualDrives" entry is for demonstration purposes only!

  • AnsiCodePage= This entry uses a numerical value to specify the country locale where you captured the application. ThinApp uses the value to translate multibyte strings.

  • LocaleIdentifier= This entry parameter displays a numeric ID for the locale information. The value for this entry locates the correct language resources from the application.

  • ;Wow64= This entry is used to simulates a 32-bit environment for 32-bit applications which cannot run (at least not properly) on a 64-bit Windows operating system. As the note within the PACKAGE.INI says, if you have problems running your 32 bit application under 64 bit Windows, try enabling this line and rebuilding your project.

Entry Points

Your entry points will appear within the PACKAGE.INI at this point forward. Typically the first entry point will be the Primary Data Container, as denoted by the "ReadOnlyData" entry underneath it. The ReadOnlyData entry defines the ThinApp Virtual Registry package container and, as stated by the entry name, is Read Only. All other entry point sections will link back to this Data Container by use of the Shortcut entry underneath each of the Entry Point names.

For additional settings which can be defined underneath each Entry Point, see the Configuring Individual Applications article in the Online Help.



These are the basics for each ThinApp PACKAGE.INI. Remember, additional information can always be found in the Online Help!


Read Full Article
]]>
aj@ervik.as (Alexander Ervik Johnsen) Vmware ThinApp Sun, 03 Jan 2010 12:19:48 +0000
Multiple Instances of an Application with ThinApp http://www.ervik.as/index.php/vmware-mainmenu/vwmare-thinapp-mainmenu/2530-multiple-instances-of-an-application http://www.ervik.as/index.php/vmware-mainmenu/vwmare-thinapp-mainmenu/2530-multiple-instances-of-an-application Here is a little overview kinda q&a style of running multiple instances of an application with VMware ThinApp.

 

I can't run more than one instance of my ThinApp?

Have you ever tried to ThinApp multiple instances of Adobe Reader or Firefox and then execute them at the same time on the same system? If you have, then you'll know it doesn't work!

Why is that??

This is because the application (in our examples here, Firefox and Adobe Reader) check to see if an instance of the application is already being executed. Now, most applications will not check to see if there is already an instance of the app's primary process being executed and residing in memory. However, more and more applications are starting to do this.

Why doesn't ThinApp resolve this?

First and foremost, ThinApp does not (and will not ever) virtualize the process list. While there are a number of reasons for this, the simplest explanation is, hiding the processes of an application is a bad thing! It's what black hatters (a.k.a. bad hackers) do.

Secondly, this is not an issue with ThinApp but rather the application which you are attempting to package with ThinApp as the application is probably designed to re-use the parts of itself already in memory vs. executing additional copies of itself for whatever reasons (maybe the application requires a large amount of memory to execute one instance of itself or maybe it can only lock certain files or memory addresses once).

So how can I make multiple instances of my application work under ThinApp?

The solution is actually not directly a ThinApp solution, but an application solution, since it is an application issue. In our examples of Adobe Reader and Firefox above, these applications look for previous running instances of themselves to save on memory and screen real estate. This functionality for these two applications is solved very simply by a command line switch which disables the check for an existing instance of themselves. In the case of Adobe Reader, the command line switch is a "-k". For Firefox it is a "--no-remote" command line switch.

How do I configure my ThinApp package to utilize a Command Line switch?

Very simply, make an entry point or modify an existing entry point and add the "CommandLine=" entry to the Entry Point. It's value will be the "source" plus the command line switch or switches you wish to add.

Example: Here's an example of Firefox with a CommandLine entry to disable the pre-existing instance checking (i.e. allow multiple instances of Firefox).

[Mozilla Firefox.exe]
ReadOnlyData=bin\Package.ro.tvr
Source=%ProgramFilesDir%\Mozilla Firefox\firefox.exe
WorkingDirectory=%ProgramFilesDir%\Mozilla Firefox
FileTypes=.htm.html.shtml.xht.xhtml
Protocols=ftp;http;https
Shortcuts=%Desktop%;%Programs%\Mozilla Firefox;%AppData%\Microsoft\Internet Explorer\Quick Launch
CommandLine=%ProgramFilesDir%\Mozilla Firefox\firefox.exe --no-remote

How do I find Command Line Switches or Arguments for my application?

Here's where I can't be a lot of assistance (since there are millions of Windows apps). I usually Google these myself. A good reference, though, is Rob Vanderwoude's Command Line Switches page, which is worth reading.

Probably the best suggestion I can give you is to open your favorite browser, go to your favorite Search Engine, and search for your application's command line options using one of the following set of keywords.

"<your app> Command Line Options"

"<your app> Command Line Switches"

"<your app> Command Line Arguments"

If none of these work, I would then suggest browsing your application manufacturer's support section of their web site for these. If not found here, my only other suggestion is to contact your application's manufacturer by phone or email for this information.

My application doesn't have Command Line Option for allowing multiple instances? Is there anything else I can do?

If you've contacted your application's manufacturer and they have specifically told you a command line option doesn't exist to allow multiple instances to be executed...all is not entirely lost (I'd be surprised if this were the case since this means the app likely won't run on a Terminal Server). My suggestion here is make an official request to the app manufacturer requesting this feature. Next, there are scripting options and potentially 3rd party options.

For scripting options, see the ThinApp Scripts section for support. It may be possible to use a validation option to see if the application is already running since virtually anything scripted can be ThinApp'ed. While there are numerous ways you might be able to make this work (I won't speculate as the options are nearly infinite here) the worst case here is you just don't let the 2nd instance execute until the 1st instance is shut down.

The same thing goes for 3rd party solutions - you may be able to make your own application "wrapper" or have one built which accomplishes a viable goal.

One other thing, check to see if you can rename the source EXE (in my Mozilla Firefox example that would be "firefox.exe") to something different. This, combined with a script, could accomplish the goal to execute multiple instances of the app at the same time.


Read Full Article
]]>
aj@ervik.as (Alexander Ervik Johnsen) Vmware ThinApp Sun, 03 Jan 2010 12:19:48 +0000
VMware ThinApp - Microsoft Office 2010 Beta http://www.ervik.as/index.php/vmware-mainmenu/vwmare-thinapp-mainmenu/2477-vmware-thinapp-microsoft-office-2010-beta http://www.ervik.as/index.php/vmware-mainmenu/vwmare-thinapp-mainmenu/2477-vmware-thinapp-microsoft-office-2010-beta

With this Beta release, there have been some substantial changes that we need to account for. I will summarize these the best I can.

  • MS has added a Software Protection Service to the product. This service is meant to prevent piracy of Office and forces the application to check for a valid license. This new service is administered via a couple of methods we will describe shortly.
  • In connection with bullet #1, MS has eliminated the VLK key that we always told ThinApp users to use when packaging Office 2003/2007. As such, there are now only 2 licenses available. The MAK (Multiple Activation Key) which needs to call home to the mothership to activate and 2) the KMS (Key Management Server) key which requires the Key Management service on the network. In either case, the use of the VMAT (Volume Activation Management Tool) to install the licenses is the preferred method. So, this means there is no longer a key that can be used without the need to activate against some server or service.

So, where does this leave us? Well, Microsoft just released notes and software around a Deployment Kit for Office 2010 that places the majority of the files and services locally on the workstation in order for Office to be licensed and work properly. This new process is both good and bad. The bad is that you will have to have an additional piece of software installed on your local workstation to support Office 2010 in a licensed environment and to ensure certain functions work correctly. The good is that we have a process that you can use to test Office 2010 with in an “unofficially licensed mode”. Of course, we always recommend that you install and run in the licensed mode to ensure compliance with your purchases. However, we would be remiss in not explaining the options available to configuring both modes with ThinApp.

Rest assured, we will be looking at how to bring these local services into the virtual environment in order to achieve a single, uniform and reproducible .exe that doesn’t require local software of any kind. Remember, this is a Microsoft thing right now, so we just want to ensure you can use Office 2010 in the manner they expect it to function. Also, these procedures are for use with the VMware ThinApp 4.0.4 version to ensure that your final package can run on both Windows XP and Windows 7.

So, here we go. The first process I am going to give you is the one that will allow you to capture and run Office 2010 in an “unlicensed mode”. The key for doing this is to allow you to test during the beta of Office around features and functionality (given the absence of a license doesn’t prevent this) so as to avoid handling many activation requests. The second is the process by which you will use the deployment kit in both the capture and production environments. The idea is that by placing the kit on the capture system, we will exclude the services that Microsoft wants present on the deployment workstation so that it may interact with the licensing requirements.

Process #1: Unlicensed and fully virtual

  1. On a Windows XP SP3 environment, ensure that you have .NET 3.0 locally installed. But since MS only support SP3 on XP the odds are that you are already patched to .NET 3.5 SP1 so no worries there.
  2. Next, using ThinApp 4.0.4, make a capture of Office 2010 with any components you like. Be sure to follow the guideline of choosing items to either be installed or not installed. Never leave anything for Run on First Use.
  3. When complete, save your project out and copy in this script [Download Office2010] to the root of the project. The script will take care of the items necessary to make Office 2010 work.
  4. Build using 4.0.4 and run on Windows XP and Win7!!!


Process #2: Licensed using Deployment Kit

  1. On a Windows XP SP3 environment, ensure that you have .NET 3.0 locally installed. But since MS only support SP3 on XP the odds are that you are already patched to .NET 3.5 SP1 so no worries there.
  2. Now you need to install the Microsoft Office 2010 Deployment Kit. I used the following command against the .msi for my testing.
    1. msiexec /i OffVirt.msi PROFESSIONALPLUS=1
  3. Next, install and capture Office 2010 with any components you like. Be sure to follow the guideline of choosing items to either be installed or not installed. Never leave anything for Run on First Use.
    1. TIP: The Windows Live ID service is something I left off. I didn’t need it and it adds a few additional seconds to my start-up time since it is a service launched when I invoke any of the applications. There are ways to keep that from happening later, but for now, I just dropped it.
  4. Now, add the following values to the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Search\Preferences registry key:
    • {4154494E-BFF9-01B8-00AA-0037D96E0000}={REG_DWORD}1
    • {C0A19454-7F29-1B10-A587-08002B2A2517}={REG_DWORD}1
    • {70fab278-f7af-cd11-9bc8-00aa002fc45a}={REG_DWORD}1
    • {c34f5c97-eb05-bb4b-b199-2a7570ec7cf9}={REG_DWORD}1
    • {0077B49E-E474-CE11-8C5E-00AA004254E2}={REG_DWORD}1
  5. When complete, perform your post scan, save your project out and build.


Process #2a: Running on a Workstation with the Deployment Kit

Now that you have a copy of Office 2010 captured for use with the Deployment Kit, you can test on a workstation. The following are the steps required to pre-set your workstation using the Office Deployment Kit from Microsoft.

  1. On a Windows XP SP3 environment, ensure that you have .NET 3.0 locally installed. But since MS only support SP3 on XP the odds are that you are already patched to .NET 3.5 SP1 so no worries there.
  2. Now you need to install the Microsoft Office 2010 Deployment Kit. I used the following commands against the .msi for my testing.
    • msiexec /i OffVirt.msi PROFESSIONALPLUS=1
    • msiexec /i OffVirt.msi PIDKEYS=xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx
    • TIP: You can use the VMAT tool against the workstation to install the product code as well, I just found using the PIDKEYS= value a bit easier for testing. I would assume you would want to use the VMAT for large-scale deployments for either MAK or KMS keys.
  3. Now you just have to run your ThinApp copy of Office 2010. The activation dialog will appear and allow you to activate the key you inputted.

Pretty simple stuff! This is VMware's first pass at this so your results may vary based on your configuration and need but they are confident that the above recipe will help guide you through your testing.  As information comes available and/or the product changes in RC, we will keep you posted on any changes we discover or recommendations we have on how to package and run Office 2010.

Happy ThinApping!


Read Full Article
]]>
aj@ervik.as (Alexander Ervik Johnsen) Vmware ThinApp Thu, 03 Dec 2009 12:51:12 +0000
ThinApp - Differences between the Isolation Modes http://www.ervik.as/index.php/vmware-mainmenu/vwmare-thinapp-mainmenu/2428-thinapp-differences-between-the-isolation-modes http://www.ervik.as/index.php/vmware-mainmenu/vwmare-thinapp-mainmenu/2428-thinapp-differences-between-the-isolation-modes {youtube}pFH4iRc0P88{/youtube}

Since understanding what the Isolation Modes will do to your package and the differences between them is essentials to be successful with ThinApp I put together a whiteboard video. I hope you find it useful.

]]>
aj@ervik.as (Alexander Ervik Johnsen) Vmware ThinApp Wed, 11 Nov 2009 16:22:49 +0000
ThinApp 4.0.4 is released http://www.ervik.as/index.php/vmware-mainmenu/vwmare-thinapp-mainmenu/2421-thinapp-404-is-released http://www.ervik.as/index.php/vmware-mainmenu/vwmare-thinapp-mainmenu/2421-thinapp-404-is-released Please make sure you download the latest release. More information: http://www.vmware.com/support/thinapp4/doc/releasenotes_thinapp404.html


Read Full Article
]]>
aj@ervik.as (Alexander Ervik Johnsen) Vmware ThinApp Tue, 10 Nov 2009 09:00:22 +0000