Welcome to app-V.in

Home

Sitemap

Call Us

General

Management Server

Sequencer

Client

Streaming Server

General

Can I upgrade from Microsoft App-V Application Virtualization 4.2 to App-V 4.5 with System Center Configuration Manager 2007 R2?

Yes, When migrating from App Virtualization 4.5 stand-alone to System Center Configuration Manager 2007 R2 you must

Import packages and create advertisements.
Enable the integration through the Advertised Programs Agent to remove all previously deployed virtual application packages that have been published through Full Application Virtualization server or the MSI utility.
SCCM Advertisements and policy will be evaluated and the virtual applications will be re-added to the system.
There is no need to re-sequence your packages.

Different log files and their locations in App-V

This section describes several App-V log files that contain information that can be helpful in troubleshooting issues with App-V application delivery and execution.
Note: The App-V software only writes events to the log files listed below. App-V does not log events to the System Event log or Application Event log.
App-V Server Log File:
•    The default location of the App-V server log file follows:
%ProgramFiles%SoftricityApp-V Serverlogssft-server.log
The location of the server log file may differ depending on where the App-V server software was installed.
App-V Client Log Files:
•    The main log to consult is sftlog.txt. This log does not wrap around and therefore the size of this file should be monitored and reset if necessary. Sftlist.exe /resetlog will archive the logs current contents to sftlog000#.txt, increasing the number on each execution. A batch process can collect or delete these files.

•    The default locations of the log files for the App-V client for Windows desktops follows:
                          %ProgramFiles%SoftricityApp-V for Windows Desktops sftlog.txt
To adjust the log levels see http://support.microsoft.com/kb/931803
•    The default locations of the log files for the App-V client for terminal servers follows:
                          %ProgramFiles%SoftricityApp-V for Terminal Serverssftlog.txt
App-V Management Console Log File:
•    The default location of the log file for the App-V Management Console follows:
                         %ProgramFiles%SoftricityApp-V Management ConsolesftMMC.log
The App-V Management Console log file is disabled by default and must be enabled as follows:
If the App-V Management Console is running, close it now.
Launch the Registry Editor.
Add the following DWORD registry value:
        HKEY_LOCAL_MACHINESOFTWARESoftricityApp-V Management ConsoleLogLevel = 1
Exit the Registry Editor and Launch App-V Management Console.

Note: The log is only created when an error occurs.

Changing drive Q: assignment in App-V

The recommended practice is to choose a virtual drive assignment and stick to it. Commonly, this is drive Q: so what happens if you want to change to something else. For example, V: If all applications were equal and followed recommended practice, then simply changing the environment variable %SFT_MNT% on the client would enable you to change the virtual drive at will and no applications would need to be re-sequenced. However, not all applications are equal and this can cause some issues.

Some applications hard code the installation drive in the registry or configuration (INI) files - This means you have several options:-

Re-sequence the application to the new virtual drive letter.
Sequence the application to the C: drive (be aware of the performance impact of doing this)
Manually edit the applications registry entries or configuration files.
As with all applications, if you decide to have a different client virtual drive compared to the sequencer then testing will be paramount.

	What App-V Server versions are supported with App-V 4.5 clients?
	Microsoft support server versions 4.1.056 and above with 4.5 clients however it is recommended that all servers remain at the same revision level.

What types of software licensing types are supported by the App-V platform?

There are four types of software licensing models that are supported by App-V. These are:
Named user licensing – only named users (users specifically identified in the system) are granted permission to use the application.

Concurrent user licensing – this is where a block of licenses is available to the user pool on a first-come-first-serve basis. For example if a company has purchased 100 concurrent licenses for an application, 100 users can log in, and be assigned a license for the duration of its use. If the 101st person tries to gain access to that application, he or she will be unable to log in.

Unlimited licensing – this is where the system is set up to allow any user with permission to access the server would also have access to that application. One example of where this would be useful is the case in which a company had a set of applications they developed in-house, and deployed them on a App-V system. The applications could be made generally available to all or a subset of users.

What operating systems can the App-V 4.5 Terminal Server Client be installed to?

The App-V 4.5 Terminal Server Client can be installed on the following operating systems
Windows Server 2003 Standard (SP1, R2, SP2, SP2+R2)
Windows Enterprise Server 2003 (SP1, R2, SP2, SP2+R2)
Windows Server 2003 Datacenter Edition (no SP, SP1, R2, SP2, SP2+R2)
Windows Server 2008 Standard Edition (no SP)
Windows Server 2008 Enterprise Edition (no SP)
Windows Server 2008 Datacenter Edition (no SP)

What are virtual processor, virtual RAM, virtual NIC, & virtual disk?

From working with servers and PCs, you are familiar with common components like CPU, RAM, Disk, network, and so on. When using server virtualization, each guest operating system will have its own virtual components such as the virtual CPU, virtual memory (RAM), virtual disk, virtual network, and so on. Inside the guest operating system, the OS will see these devices as physical devices and you may or may not have the vendor’s virtualization driver loaded for that device. These virtual devices are configured in the virtual guest configuration for that VM, in the management interface for your virtualization software.

What is Virtualization?

Virtualization is a general and ambiguous term that typically means to run multiple instances of something inside something that was intended to only run a single instance. When most people talk about virtualization, they are usually referring to server virtualization. With server virtualization, you can run multiple operating systems inside a single physical server. For example, with a server virtualization product you could run, say, 5 Windows Server and 5 Linux servers on one physical server - with all servers functioning as if they are on their own hardware. In another example, you could run 1 Linux Workstation and 1 Windows Workstation on your office PC, each in their own environment, by using a server virtualization product.

	Is the operating system virtualized when using App-V and, if yes, is that usage right covered under the customer’s existing EA/Select/Campus/School Agreement?
	App-V virtualizes the application and its dependencies for execution in a single operating system instance. This is different than Virtual Server or Virtual PC, which virtualizes the entire operating system. App-V can dynamically deliver and virtualize the applications in a virtual operating system image as well.

Can I buy App-V outside of the Microsoft Desktop Optimization Pack for Software Assurance today?

Yes, App-V is available in a perpetual license standalone today outside of volume licensing. However Microsoft App-V Application Virtualization for Desktops will only be available in Microsoft Desktop Optimization Pack for Software Assurance once Volume Licensing is in effect. Microsoft App-V Application Virtualization for Terminal Services will continue to be sold as a perpetual CAL, but will be eligible for Software Assurance starting January 1st, 2007.

1 2 3 4 5 Next Last