softgrid advanced sequencing

SOFTGRID ADVANCED SEQUENCING

April 23-25, 2007 BriForum 2007: Chicago 1

April 23-25, 2007

SoftGrid Advanced Sequencing

Michael Burke



What is Sequencing?• True virtualization of

– File system– Registry– INI– Environment variables– COM objects

• True isolation of applications

• Reorganization into a streaming format

• Done without modification of source code



“Suite-ing” Applications• Two or more applications that share the same virtual

environment• Application dependencies

– Java, ActiveX, etc.– API calls

• Required because of the nature of Softricity isolation

• Available external application access:– File associations– Local application access– Basic copy and paste (text and graphics)



The Concept of “The Bubble”

Operating System

App1 App3App2

XSuite A Suite B

X X

SystemGuardSystemGuard



Sequencing Phases• Planning/Preparation• Sequence Process• User Acceptance Testing• Remediation• Deployment• Support/Update• Retire



To Sequence or Not to Sequence

• Sequencing may not be applicable in all scenarios, such as:– Drivers/run-time dependencies– Application dependencies – Supportability– Functionality/performance



Environment Planning• Standardize on a virtual drive letter (Q:)• Asset Directory Naming Convention

– 8.3 ONLY! (ex. AcroRd80.V1), no spaces– Do not reuse

• Suite Naming Convention– Vendor_Application_AppVer_SeqVer (ex. Adobe_AcrobatReader_8.0_v1)– No spaces– Avoid reuse

• Process methodology– SoftGrid Application Request Form– Process for requests

• Sequence lifecycle tracking process– Track package details (apps, dependencies, asset directory, max block size,

etc.)– Track progress on application sequences– File share, Spreadsheet, database, MS SharePoint site, etc.



The Sequencer Machine• Operating Systems

– W2K Pro/Server– WXP Pro– W2K3 Server

• Resources– Single (Fast) CPU– 1GB+ RAM– FAST disk subsystem– Adequate free space

• Min. Two Partitions– C: (System)– Q: (Sequence)– Ghost images (opt.)

• Basic Build– “Plain vanilla” install– Mirror platform in prod use– No pre-installed software unless

part of standard build– Recommended: Don’t pre-install

sequencer application

• Use Multiple Sequencers– Multi-task– Leverage Virtualization

(Snapshot/revert VMs)– Ghost Physical Machines– Disable machine account

password changes



Sequencer Setup• Basic OS build

– No security software (Cisco CSA, firewalls, etc.)– No antivirus (preferred)

• Partitions– Partition 1 - C: System OS and Sequencer [10-20GB]– Partition 2 - Q: Drive [10GB]– Partition 3 - Ghost images (omit if VM) [10GB]

• Create a dummy printer• Create dummy System and File DSNs• Set Explorer “Launch folder windows in a separate process”• Add Sequencer Exclusion Items

– C:\Documents and Settings\<username>\ntuser.dat– C:\Documents and Settings\<username>\Application Data\

VMware\hgfs.dat (VMware Workstation only)



Preparing to Sequence• Know your applications!

– Requirements and dependencies– Configuration– Use-case scenarios

• Gather resources– Media, network locations, license keys – no activating keys– Key people / documentation

• SoftGrid application request form• Identify target operating system(s)

– Sequence on least common denominator OS– Are multiple sequences required?

• Determine sequence options– VFS or Mount-point install– Block size and compression– FB1 and FB2 delineation



Preparing to Sequence• Perform a test installation prior to sequencing

– Become familiar with install options, requirements, and use• Install any dependent applications prior to sequencing

– Applications assumed part of base build• Create asset directory on Q: prior to sequencing• Map necessary drives

– Source files and application-specific• Pre-extract files to temporary directory• Document the Sequence

– The process (recipe)– Sequence options (Sequencer version, max block size, who did it, etc.)– Errors, resolutions, changes– Dependent applications (for patching/upgrading)



Sequencing Process

1. Installation media

2. Installation Phase

3. Shortcut Wizard

4. Save Package

5. Test, test, test!

6. Production release

7. Patch/update

SystemGuard

.SFT .OSD .ICO .SPRJ

SystemGuard Production

1 2

3

4

5

6

7

Sequencer

Client VAS Server



The Results• .SFT

– The sequenced application(s)– Record of files, directories, registry, etc.

• .OSD – XML-based file containing information about the app and how to

launch it• .ICO

– Icon file, created in conjunction with the OSD• .SPRJ

– The Sequencer Project file– Contains sequence information– Record of associated SFT, OSD and ICO file names



Package Configuration• Suite Name

– vendor_appname_appversion_seqver– Ex: Adobe_AcrobatReader_8.0_v1

• Comments– Sequencer version, OS, Person, Asset directory name, suited

applications, etc.• Hostname

– %SFT_SOFTGRIDSERVER%, FQDN or IP• Path

– <suitename> or <department>\<suitename>– Establishes the directory structure of content share

• Operating Systems– Remove all unless package is for specific platform



Sequencing the Application• Compression and Block Size• Install to

– Q:\<assetdir>\<app_name>\– “Program Files” = <assetdir>

• Use MSI logging if possible– Create a .bat file with /l*v

option• No “install on first use”• Pre-configure apps while

monitoring– Disable automatic updating– Accept EULA– Pre-configure application

defaults– Clear IE cache and cookies

• Stop monitoring– When finished with all apps in

suite– To process necessary interim

reboots• Always include MSI



Shortcut Wizard• Clean up shortcuts

– Remove unneeded shortcuts

– Clean up version numbers

– No spaces in OSD file names

– Modify shortcut locations– Limit number of file type

associations

• Launch applications– Designating FB1 and

FB2– Use “Launch All” or

CTRL+click– “Top 10” features– Some do not terminate

automatically

• Finish– Sequences blocks



Finishing Up• Check for drivers

– File system tab

• Save the Package– Directory = suite name– SPRJ file = suite name– Include MSI log of install

• Move Package Off Sequencer– VAS content share– Network location

• Clean Up Sequencer– Revert or re-image

• Complete Documentation– Recipe– Change control– Document package size,

launch size and max block size

• Notify Appropriate Personnel for Testing



User Acceptance Testing (UAT)• Encourage the documentation of Use Cases• Test on Production OS Deployment

– Include security software, AV, etc.– Group Policy in effect– Test on all intended OS recipients

• Check Event Logs for Errors• Get Qualified Personnel Involved• Document Issues

– Update change control– Document resolutions– Document required OSD scripting

• Obtain Sign-off of Success



Upgrading a Package• Open for upgrade• Perform changes/additions• File -> Save (Active Upgrade)

– SFT file incremented

• File -> Save As (package branch)– New asset directory name– New suite name– New GUID is generated automatically– Be sure to modify package configuration first



Editing OSD Files• Disable Word Wrap in Notepad• Use an XML-aware editor

– Ex. EditPlus• Clean Up Readability

– Align CODEBASE items• Remove/Add OS tags• Scripting and Custom Registry

Modifications



Advanced Sequencing

• Leveraging local applications in a sequence– As Primary Application (iexplore.exe)

• Custom OSD calling local binary

FILENAME=“%PROGRAMFILES%\Internet Explorer\iexplore.exe”

– As Supporting Applications (Office, Lotus Notes Client, Acrobat Reader)

• Supporting apps installed on Sequencer machine prior to sequencing



Passing Parameters

• Modify OSD <CODEBASE> Tag

– FILENAME=“%PROGRAMFILES%\Internet Explorer\iexplore.exe” PARAMETERS=“http://www.briforum.com”

– FILENAME=“Off2k3.V1\MSOffice2003\Office11\ msacess.exe” PARAMETERS=“H:\Databases\briforum2007.mdb”



OSD Scripting• Script Timing and Events

– PRE STREAM– POST STREAM– PRE LAUNCH– POST LAUNCH– POST SHUTDOWN

• Protect– Protect=TRUE (script runs inside virtual environment)– Protect=FALSE (script runs outside virtual environment)

• Timeout– Timeout=xx (wait xx seconds for script to complete before reporting error)– Timeout=0 (wait indefinitely for script to complete)

• Wait– Wait=TRUE (wait for script to complete before continuing)– Wait=FALSE (do not wait for script to complete before continuing)



OSD Script Event Timing



OSD Scripting Options• <SCRIPTBODY>

– Can call non-executable commands (md)

– Creates a temporary script on the client, which executes and is then deleted

– Uses escape ( \ ) character

– DOS window appears

• <HREF>– Used to call direct

executables (xcopy)– No non-executables

permitted– Command is executed

directly on the client– No DOS window appears



SCRIPTBODY Examples



HREF Examples



Registry and Environment Variable Scripting



Dealing with Drivers

• Check sequencer file list for /drivers directory

• Determine if drivers are necessary• Extract drivers and install separately

– SMS package– Script through OSD



Troubleshooting Packages• No icons

– Active Directory group membership– Access to Content share– Shortcut locations

• Package won’t launch– Check SoftGrid Client log for errors– %SFT_SOFTGRIDSERVER% variable– Check Event Viewer– Max block size– Clear client cache

• User settings keep resetting– Identify settings file in the package– Mark as user data



Getting Inside the Bubble• Create a debug OSD

– Append “Debug” to SOFTPKG NAME tag– FILENAME=“%WINDIR%\System32\cmd.exe”– SUBSYSTEM VALUE=“console”

• Explorer.exe /separate• Filemon and Regmon

– Registry modifications outside the bubble first (see Microsoft KB 931819)



Dealing with Side-by-Side• Check Event Viewer• Locate the issue

– Dependent binary (.exe)– Dependent directory– WinSxS library dependencies

• OSD scripting workaround– Pre-launch dependent binary– Copy WinSxS entry to local system



Identifying Errors• Client Logging

– C:\Program Files\Softricity\SoftGrid for Windows Desktops\sftlog.txt– Logging level:

• HKEY_LOCAL_MACHINE\SOFTWARE\Softricity\SoftGrid Client\CurrentVersion\Configuration\LogMinSeverity=n

• 4 is default, 5 increases log detail• Restart client service

• May be useful information in the log– Ex. “The system cannot find the file specified.”

• Research error codes on MS KB– Search on the last error code block– Error code: 40023B-0060926C-80070002



Sequencer Log Files• sft-seq-log.txt

– Main log for the sequencer• sftrbt.txt

– Records actions during reboot processing• SFTCallBack.txt

– Log of SystemGuard-watched processes• filter.log

– File-activity log recorded by SystemGuard– Use dumplog.exe to decode

• files.txt– Log of all files in the VFS– Not enabled by default– HKLM\Software\Softricity\SoftGrid Sequencer\CurrentVersion\

FileManifest=1



When All Else Fails…• Install application on plain Windows install

– See it work– Identify where application fails

• Try a VFS installation– Not recommended for large packages (> 800MB)

• Try streaming to a clean system– Basic Windows install with SoftGrid client– No security software, AV, GPO



Questions?



Thank You!

Michael Burke

[email protected]

softgrid advanced sequencing

Technology

sequencing applications

chicago x suite

application compression

sequencer project file

sequence ghost images

dependent applications

sequence options vfs

bat file