Read more at: http://communities.vmware.com/message/1530517

Often, App-V administrators will leverage multiple App-V Management Servers sharing a common database. The process usually involves pointing additional server to the existing SQL server and database during installation. Key databases values that govern server behavior will be stored in the DBO.SERVERS and DBO.SOFTGRID_SERVERS tables.

These settings can also be configured using the App-V Server Management Console (navigating to Application Virtualization Systems-<hostname of App-V Management Service front-end to SQL data store> - Server Groups - <Name of server group> and then right-clicking that group and selecting “New Application Virtualization Management Server.”)

This allows you to pre-create a server object with specific values configured in advance. This allows for smoother deployment of App-V server farms for high availability. When you pre-create a server object using the wizard, you have the option of setting the following values:

• Display Name
• DNS Host Name
• Memory Allocation
• RTSP Security/Certificate
• RTSP/RTSPS Port

During installation of the additional App-V server (matches the DNS hostname,) an administrator will point to the existing database and the corresponding server record will also be slightly modified.

So what is modified?

There are additional values not specified in the MMC interface that govern behavior of the App-V Server. The key values are specified in the tables below where each table represents a list of values contained inside of the App-V SQL data store that are affected by this process.

For each value, an explanation of what the default value will be is included depending on how the server object is created.

Pre-created Values: This refers to the vales that will be put in upon server object pre-creation in the App-V console (navigating to Application Virtualization Systems-<hostname of App-V Management Service front-end to SQL data store> - Server Groups - <Name of server group> and then right-clicking that group and selecting “New Application Virtualization Management Server.”)

New Installation Values: These are the values that will be put in place if you simply bypass pre-creation of the server object and let the installation process create that server object during installation.

Value when installed after pre-creation: These are the values that reflect changes to the pre-created defaults. If you notice in the table, some are modified during installation, others are not.

Table: List of server object values affected by pre-creation process (yet not configurable in the MMC.)

Dbo.SERVERS

Dbo.SOFTGRID_SERVERS

Why is this important to know?

With these values having suboptimal configuration values, this could create some potential server problems. While the core_procs (Number of Core Processes) value is configurable in the MMC, it is still listed here as an important configuration value to double-check as it too is affected by the pre-creation process.

Here are some common issues that can arise from inconsistent and sub-optimal server configuration values:

· Inconsistent server behavior in server farm or load-balanced configuration: If you are working with a load-balanced or any similar configuration to establish high availability, ensuring that configuring is consistent across the board is a necessity. This can be a problem especially is the max_conns and core_procs values differentiate.

· Periodic/Intermittent loss of database connectivity: If multiple servers are sharing the same back-end SQL database, you may have issues with some servers who may have the core_timeout value set to low losing database connectivity (especially for geographically dispersed App-V servers.

· Service may fail to start: This can also happen if the core_timeout value is set too low (such as 10)

· General Performance issues: With the max_conn, core_timeout, and core_procs set too low (such as the case when pre-created server objects are used,) general performance issues will arise and there will be a significant difference in overall performance versus servers configured with the default installation values (without server object pre-creation.)

Recommendations:

For the reasons mentioned above, it is recommended that you bypass server pre-creation and have the server installation process create the server record.

If you find your App-V server environment is already in this inconsistent state, you can modify these values to reflect the recommended default values using SQLCMD or SQL Management Studio.

Steve Thomas | Senior Support Escalation Engineer

Read more at: http://blogs.technet.com/b/appv/archive/2010/05/10/pre-creation-of-server-objects-may-yield-certain-sub-optimal-values-in-the-app-v-sql-database.aspx

This has worked just fine, untill Spotify auto updated to the latest (0.4.3) version last week. (Auto updates worked fine previously though).

Now they've made a sanity check or something and our users got notified that spotify.exe was damaged. Since we'd captured the original install using ThinApp 4.0.3 I figured maybe we'd just update. I repacked the capture with ThinApp 4.0.4 with no difference, and then I tried 4.5.

With ThinApp 4.5 the ThinApp unpacker launches and then... does nothing. No error message, no running/hanging process. It just exits.

I've since tried manually upgrading the spotify application, doing a fresh reinstall/capture with both 4.0.4 and 4.5 and the result is always the same.

Built using 4.0.3/4.0.4 I get the damaged spotify.exe

Built using 4.5 I get nothing.

Anyone else using Spotify that got it to work???

Read more at: http://communities.vmware.com/message/1530310

Read more at: http://communities.vmware.com/message/1530261

Read more at: http://communities.vmware.com/message/1530239

Read more at: http://communities.vmware.com/message/1530260

Read more at: http://communities.vmware.com/message/1530222

1: Prescan, Install Steam, Postscan, Build sandbox, Run sandboxed Steam, Install TF2, Run TF2

2: Prescan, Install Steam, Run normal Steam, Install TF2, Run TF2, Postscan, Build Sandbox, Run sandboxed Steam+TF2

Anyone have any experience with Steam and Thinapp?

If not, what I would like to do is to run an external application (ie. TF2) in the sandbox of a different application (ie. Steam). Does anyone know how to accomplish this?

Read more at: http://communities.vmware.com/message/1530227

http://blogs.vmware.com/thinapp/2009/03/common-system32-dlls.html

Best regards,
Linjo

If you find this information useful, please award points for "correct" or "helpful".

Read more at: http://communities.vmware.com/message/1530101

Read more at: http://communities.vmware.com/message/1529847