How to configure or install sql server on app-v

I am working as a software professional with sql server. Recently we heard regarding Microsoft Application Virtualization (App-V) which enables enterprises to meet the requirements of users as well as IT by empowering wherever productivity in addition to accelerated application deployment. App-V offers anywhere user access to applications that are dynamically accessible on some certified PC without application installs. We make use of App-V because it increases business quickness through quicker application deployment plus updates with no user intermissions. It reduces clashes flanked by applications, permitting enterprises to decrease application compatibility testing time. So our main goal is to provide users with a reliable experience and steadfast access to applications along with business data, no matter their site as well as connection to the Internet. So all we do is with App-V together with Microsoft User State Virtualization (USV) . but we are not known regarding the actual size it consumes in sql server. So I need to inquire regarding SQl server size allocation to save the apps details. In addition to this , we are not able to locate the info file of the apps in SQL server and need location. Also , we need more brief information regarding user Vol settings file as well as Global File settings in the client machine.size is must as it will give us idea about what are the necessary requirements and which should be given first preference.

As you inquired regarding location of the info file of the apps in SQL server I need to tell you something about it. Soto begin with the installation path , the folders paths, are valid for default installation moreover for Windows Vista Operating System. though for other operating systems you are able to locate the right path with no trouble. You need to just ensure your client management console,along with some of the properties of Application Virtualization.
And regarding folders.
App-V ROOT: C:\Program Files\Microsoft Application Virtualization Client
User Data (Local Cache): C:\Users\ username \AppData\Local\SoftGrid Client
User Data Directory: C:\Users\username\AppData\Roaming\SoftGrid Client
Global Data Directory: C:\Users\Public\Documents\SoftGrid Client
Client Log: C:\ProgramData\Microsoft\Application Virtualization Client .
You can make use of App-V to use the built-in management to stream applications to users on demand in addition to permit users to update applications without detaching or else rebooting. allot applications to users by means of Active Directory, and retire applications speedily by removing the assignment and to do the same you don’t require any installation. You are also able to track application licensing furthermore meter usage.
Regarding App-V ROOT , we give it a name like this since it encloses the binary files which generates the App-V client. The interesting fact with this folder is it just don’t store binaries inside it moreover, it is capable of storing bunch of App-V DLLs. In addition it is also capable of storing some executables but also it holds some useful logging information as well. In addition, if you set the NtaLogMask registry key in Client/Configuration registry it also creates Sftnta.txt in this folder. This log file is helpful while diagnosing particularly network layer issues.

I have some information regarding app v which I would like to share. Hope you will understand with this post. So App-V solution tightly puts together with Active Directory with the intention that the applications are only delivered to those users that are permitted to make use of applications. as a result administrator describes security group in Active Directory as well as defines users which should take delivery of the application on their desktop. After the user logs on to a system he will see all virtual applications immediately. Tight integration of App-V resolution with Active Directory has a valuable consequence on the OS deployment procedure, as well as usually process of generating the OS image. By default, companies are creating fat OS images with a variety of preinstalled applications so that each department is covered with all applications. This adds to the size of the OS image, as well as users frequently have applications which they do not make use of. conversely, if using App-V, OS image can be “clean” with possibly not many preinstalled applications, while other users agree to virtual applications immediately they firs log on to domain. The most recent version also comes with a complex option of shared cache , which is mainly helpful in Virtual Desktop Infrastructure (VDI) answers.In VDI solutions virtual machines are situated in data centers and users access them from their sytem, or else making use of thin clients. certainly, users will access these virtual machines to employ firm applications. If those applications are installed independently on every virtual machine, then the capability of these virtual machines occupies a quite great quantity of storage. Take for instance that the regular virtual machine user have about 20 applications by way of an entire capacity of 10 GB. intended for 100 users,in this case it is essential to book 1000 GB of disk space only for applications. By making use of App-V shared cache all applications doesn’t have to be positioned in every virtual machine independently. as an alternative applications can be placed on shared storage. as a result all virtual machines will utilize similar shared cache of virtual applications which is for example 10GB, which means that you could potentially put aside 90% or supplementary of storage space. So you can consider this case where you will able to save good amount of space.

The earlier post says it correctly but according to me, the folder information would have enhanced this topic to an great extent. So regarding Global Data Directory it tends to be global to all users who make use of that client machine. Its location is under Users/Public folder. It encloses ordinary files which are used by majority of users. AppFS Storage is one of a kind. This folder is used by transport layer with virtualization layer of AppV Client. .BLD, .DO , .MD along with .BM files are shaped by transport layer openly within the AppFS Storage folder. These files are package precise and enclose information concerning disconnected mode, package metadata, block map and so forth. as well to these files, AppFS Storage has folders for every package. These folders begin with package name and they are formed by virtualization layer to remain system specific information regarding packages that are used by virtualization.


Also regarding OSD Cache: When a latest OSD file comes to the client, it is parsed in a provisional storage. If parsing is completed productively, that OSD file is moved to OSD Cache so that all users will start on the identical application from similar OSD file which is in Global Data Directory. for the reason that OSD files aren’t user specific, App-V tends to store them under Global Data Directory. Something similar as OSD Cache is ICON Cache . every application, shortcut and file type association might have an ICON file which is connected with it. We also have a folder such as Client Log with which this folder holds only our log file which is sftlog.txt. This is a very significant file to diagnose troubles. It`s logging level along with path can be altered from management console. Don’t forget that you are able to set some of the folder paths from Client Management Console. There is another folder named as User Data (Local Cache) with which you are able to parse the OSD files in a temporary location. This is the temp folder for users. When you do Publishing Refresh, OSD files are downloaded here before their real location which is Global Data Directory. After a successful parsing; if OSD file is appropriate for that client, it is moved to Global Data Directory. as well, this folder is utilized as a temp directory for user package volume which tends to be present in User Data Directory. When you launched an application, user setting file for the package is read from User Data Directory and you will be with an temporary .pkg file which will be created in User Data (Local Cache) folder. following client finish using that application, updated temporary .pkg file is moved to its actual position which tends to be User Data Directory.

The App-V Full Infrastructure replica consists of an App-V Management Server, the App-V Data Store on a SQL Server, in addition to the App-V Windows Desktop Client. throughout normal operations the App-V Client will carry out the following steps:
1. A publishing refresh.
2. In addition with a load or else stream applications.
3. Begin the launch of applications.
Throughout these operations, the infrastructure workings will be used to obtain the essential information required to publish, load, and launch virtual applications. The SQL database merely contains references to the position you have placed the files in. No files are accumulated within the database. And no files are saved inside the database. The App-V SQL database is a necessary component in an App-V Full Infrastructure with a Management Server. The database encloses configuration information as well as accumulates usage information for the App-V infrastructure. App-V Infrastructure operations that use the database are Publishing Refresh as well as Application Load, Application Launch Authorization, as well as the Server Management console. majority of these are lightweight operations along with will place a very small load on the SQL Server. Though, the offline metering will put a load together on the server as well as network based on the figure of users and the amount of application usage data that is composed. A latest characteristic of App-V 4.5 is the aptitude of the Management Server to cache the application publishing information for each and every application from the SQL Server to its own cache. This was done to decrease the quantity of queries next to the database for every publishing refresh operation. The application publishing information will raise in size based on the amount of applications that are available and the number of objects connected with each application. Regarding Database Size and Growth, database sizings as well as growth are mainly reliant on application launches along with reporting information. These operations are continuing and frequently append to the size of the database. These two procedures will require to be used in cooperation with the database cleanup settings to forecast the correct size of the database. Additional database process such as adding an application with new App-V Clients, errors of some clients will not considerably augment the size of the database.

You will be definitely with UsrVol_sftfs_v1.pkg issue as you also need to know regarding sid. As this is an important part in your explanation, sid denotes, is a unique worth of variable length which is used to recognize a security principal or security group in Windows OS. recognized SIDs are a group of SIDs that make out generic users or else generic groups. Their values lingers steady across all operating systems.