Home > Uncategorized > App-V 5: Capturing Data Source Configuration

App-V 5: Capturing Data Source Configuration


You may have noticed that in previously releases of Softgrid and App-V, it was recommended as a best practice to manually create a dummy (I hate that word – I prefer “artificial”) ODBC data source (DSN) connection on the sequencing prior to sequencing anything that interacts with ADO/ODBC. The reason for this has to do with how these settings get captured during the sequencing process and how default registry opacity is handled. If the settings for ODBC are empty than any settings that are captured during the sequencing will be reconciled as “Override” since there will be no existing ODBC registry keys on the sequencer.

The problem this creates is the override settings will prevent the virtual application from seeing any existing ODBC settings that may exist on the client workstation. Given that the application may need to interface with a database client or middleware that needs these settings, this could be problematic. If you create a dummy (as it has been called) ODBC connection in advance, then only the settings for the connection parameters (DSN) captured during sequencing will be collected and the opacity will be set to “Merge.”

With the advent of the 4.6 SP1, many sequencing best practices were implemented into the workflow of the sequencer software. Among them was this very creation of an artificial DSN. As a result, people stopped having to worry about it. Well . . .

It is time to start doing this again. With the 5.0 Sequencer (including the latest SP2 release) you will need to create an artificial ODBC connection in advance of sequencing. Otherwise, you will still run into registry opacity issues with ODBC settings that are captured during sequencing. In most cases, virtual machines are used so I would simply add this to the default configuration of your base sequencing machine.

Categories: Uncategorized Tags: , , , , ,
  1. CNemnom
    November 30, -0001 at 12:00 am

    Thank you Steve,

    Could you please advise how to add the ODBC connection is advance of sequencing?
    Is this will apply to all applications that will be sequenced?

    Regards,

  2. Steve TH - MSFT
    November 30, -0001 at 12:00 am

    It’s OK, I knew it was you, Alex🙂 I have a dummy printer created on my App-V 5.0 base sequencer snapshots, yes.

  3. Anonymous
    November 30, -0001 at 12:00 am

    Start odbcad32.exe. Go to System DSN tab. Click Add.Click Finish (or select another driver). Fill in Data Source Name (dummy or artificial) Click OK or Finish (depending on the driver you selected).Click OK to close the ODBC Administrator. Take snapshot. Start sequencing. @Steve: Is it also needed to create a dummy printer manually again?

  4. Alex Sweserijnen
    November 30, -0001 at 12:00 am

    Forgot to login first: Start odbcad32.exe. Go to System DSN tab. Click Add. Click Finish (or select another driver). Fill in Data Source Name (dummy or artificial) Click OK or Finish (depending on the driver you selected).Click OK to close the ODBC Administrator. Take snapshot. Start sequencing.

    @Steve: Is it also needed to create a dummy printer manually again?

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: