App-V Sequencer creates applications that can be run in a virtual environment. It monitors the installation and setup process for an application, and it records the information necessary for the application to run in a virtual environment.These applications does not interact with OS as they runs in virtual environment.

 
You can deploy the sequenced applications using SCCM 2012 to User based computers in more suitable way using Global conditions.

Somaning has shared his experience in sequencing SCCM Configmgr 2012 Admin Console using App-V 4.6 SP1 tool for Windows 7 64-Bit Service Pack 1.

For best practices how to sequence an application : http://technet.microsoft.com/en-us/library/dd351420.aspx

Complete Post via http://blogs.technet.com/b/appv/archive/2013/01/08/how-to-sequence-the-microsoft-system-center-2012-configuration-manager-admin-console-with-microsoft-app-v.aspx

would like to know how to Sequence SCCM 2007 R3 admin console ,Please refer http://blogs.technet.com/b/appv/archive/2012/03/20/how-to-sequence-the-system-center-configuration-manager-2007-r3-admin-console-with-microsoft-app-v.aspx

Note:If you are deploying the sequenced applications to clients using sccm 2012,ensure you have the Right version of App-V client on Target computers.The Supported version is App-V 4.6 SP1 cu5 !

If you are running issues like app-v service receives an exception and then crashes ,the service cannot be started because of the lost of the file system,You may have to install the hotfix available here on http://support.microsoft.com/kb/2693779

In this Week TechNet Radio show, Keith Mayer and Wally Mead Senior Program Manager from the System Center Client Management team and all-around ConfigMgr Guru continue their “What’s New” in System Center 2012 Configuration Manager Service Pack 1 series and in today’s episode they discuss how we can manage App-V 5 Virtual Applications. Tune in as they demo its new capabilities as well as walk us through a deployment of a virtual application in ConfigMgr 2012 SP1.

In this episode, we’ll be covering …

• New Support for App-V 5 virtual applications
• App-V 5 Connection Groups / Virtual Environments
• Deploying App-V 5 virtual applications
• Converting App-V 4.6 applications packages to App-V 5

Watch the video and complete post on http://channel9.msdn.com/Shows/TechNet+Radio/TechNet-Radio-Managing-App-V-5-Virtual-Applications-with-System-Center-2012-Configuration-Manager-SP

You can download this video from http://media.ch9.ms/ch9/fbd0/5241f663-c9b2-4308-8839-c902858afbd0/TNRAppVSCCMSP1_high.mp4

Sometimes pushing app-v Application doesn’t work on some machines and when looked at virtualapp.log file,you will see something like below.

“Failed to open the WMI namespace [root\microsoft\appvirt\client]” from C:\Windows\SysWOW64\CCM\Logs\VirtualApp.log.

What does the above Error says ? The WMI namespace was not created during the install of the App-V Client.

You can verify it by typing wmimgmt.msc from your RUN command .

If You want to connect to Remote Computer ,try below.

Right click on the WMI Control and select properties, click on the Security Tab:

Go to Root—>Microsoft ,you see appvirt is missing from it.

So ? How do you get it back ? Reinstalling the app-V client by uninstalling it and install again ?

I do the other way ,here it is:

Identify a Machine which is base build( not a machine setup for a user) and go to wmimgmt properties as we did above ,and select properties>go to the Backup/Restore Tab.

Click on “Back Up Now…” It asks you where to store and the file extension will be .rec

You can either take this file into Pen Drive or via network share onto failed machine.

Now Go back with your failed machine and click on backup/Restore to restore the backup file.

Now Open the WMI snap in again and confirm you can see “APPVIRT” under root–>Microsoft

Restart the computer once to take the changes effect (Ensure you restore the backup using admin account).

Hope it helps!

time to time while working with SCCM application virtualization, i come across several issues in troubleshooting why the virtual apps doesn’t load correctly /why they don’t go way when you say not applicable/not needed for someone using very powerful command WMIC.

Here are some of the WMIC commands :

What is WMIC : WMIC is Windows Management Instrumentation Command-line (WMIC), which uses the power of Windows Management Instrumentation (WMI) to enable systems management from the command line. WMIC extends WMI for operation from several command-line interfaces and through batch scripts. Before WMIC, you used WMI-based applications (such as SMS), the WMI Scripting API, or tools such as CIM Studio to manage WMI-enabled computers. Without a firm grasp on a programming language such as C++ or a scripting language such as VBScript and a basic understanding of the WMI namespace, do-it-yourself systems management with WMI was difficult. WMIC changes this situation by giving you a powerful, user-friendly interface to the WMI namespace.

More info ,please read http://technet.microsoft.com/en-us/library/bb742610 and http://ss64.com/nt/wmic.html

If you have referred my previous post in fixing issues on Virtual apps are not removing http://eskonr.com/2012/06/sccm-removal-of-app-v-applications-from-client-machines-script-based/,some command lines used in the script.

Run the below command line on target computer with administrative rights either manually or remotely using psexec tool .

The Basic command line syntax for all the below queries is :

WMIC /node: “Computername” /namespace:where the information located path classes name Get xxxx,xxxx,xxxx

If you are running the above command line on local computer,you can simply delete /node .

where the information located : It is the namespace for which information being stored.in this case,it is \\root\microsoft\appvirt\client

classes name : For each instances name,you will have n number classes could be of static or dynamic . in this case, it is package.

XXXX is what information you need.

List Virtual Apps – Name and SftPath

WMIC /namespace:\\root\microsoft\appvirt\client path Package Get Name,SftPath >C:\listapps.txt

List Virtual Apps – Name
WMIC /namespace:\\root\microsoft\appvirt\client path Package Get Name >c:\virtualapps.txt

List Virtual Apps – Name and SftPath (Remote Machine)
WMIC /node:"%MACHINE%" /namespace:\\root\microsoft\appvirt\client path Package Get Name,SftPath >C:\remotevirtualapps.txt

List Virtual Apps – Name (Remote Machine)
WMIC /node:"%MACHINE%" /namespace:\\root\microsoft\appvirt\client path Package Get Name >C:\remotevirtualapps.TXT

List Virtual Apps – Name (Remote Machine) with Condition
WMIC /node:"MACHINE%" /namespace:\\root\microsoft\appvirt\client path Package Where Name="adobe reader" Get Name,SftPath /format:csv

more information about format command line,refer http://msdn.microsoft.com/en-us/library/windows/desktop/aa394531%28v=vs.85%29.aspx

List Virtual Apps – Name (Remote Machine) with Condition
WMIC /node:"MACHINE%" /namespace:\\root\microsoft\appvirt\client path Package Where Name="Adobe Reader" Get Name,SftPath /format:csv

List Virtual Apps – Name (Client List)
WMIC /node:@clients.txt /namespace:\\root\microsoft\appvirt\client path Package Get Name,SftPath /format:csv

List Virtual Apps – Name (Client List)
WMIC /node:@clients.txt /namespace:\\root\microsoft\appvirt\client path Package Where Name="Adobe Reader" Get Name,SftPath /format:csv

List Virtual Apps – Name (Remote Machine) from SCCM
WMIC /node:"ESKONR" /namespace:\\root\sms\site_P01 Path SMS_Package where PackageType=7 Get PackageID,Name,PkgSourcePath >C:\listallapps-SCCM.txt

ESKONR : SCCM server name

P01: Site code of SCCM server name

Name: Adobe reader which is application name

machine : Remote computer name

Clients.txt : list of computers and full path should be given here in the command line.

I really like the last command which gives us list apps created in SCCM server with package source path rather looking at reports.

Hope it helps to someone

In Previous post ,we have seen Installation of Microsoft Application Virtulisation (4.6) Desktop Client 

In this Post ,We will see how to Configure settings of App-V Desktop Client and its Basic Troubleshooting Steps:

If you want to change the settings that are specified at the time of installation of App-V client  Or any customization do be done,you can do that Via Management Console(SftCMC) which is located in C:\Program Files (x86)\Microsoft Application Virtualization Client.

Click Start | Administrative Tools | Application Virtualization Client

click on Properties .

General Tab : If you want to record only error or warning messages,you can select it from Drop down “Log level” and the path of the log file(sftlog.txt) and other Settings as well. Take a look at Global Data Directory which is used to store all users data.You should see the default App V Application published into that.

Interface Tab: How do you want to show the notification Icon(app-V) on the system tray and how long do you want to display the error messages on the system tray icon.

Next is File System Tab: about client cache Configuration settings

Connectivity Tab: If you want to make the client to work in offline mode,you can check “Work Offline”. For more info “How to Work Offline or Online with Application Virtualization” : http://technet.microsoft.com/en-gb/library/cc817097.aspx

Permissions Tab :

Next is Applications:This list all the applications with status(running ,Not running) and what is the package status. Since the default application is not in Use, it says Not running.

The below shows the status of default application in running Mode.

If you want to know ,from where the application is loaded,application URL , Package ID,Version and what is the size of the package ,     Right click on the Default package ,go to properties.

If you want to set the publishing server or to change the existing one and set the refresh interval time for loading the applications etc ,Click on publishing server and go to properties.

The Above all settings also can be applied to group of computers Via Group Policy Object by importing ADM Template. Read the Document from http://download.microsoft.com/download/F/7/8/F784A197-73BE-48FF-83DA-4102C05A6D44/App-V_ADM_Template.docx

You can also Configure the App-V Client Registry Settings by Using the Command Line .Read more from http://technet.microsoft.com/en-gb/library/cc843710.aspx

Below is the Log file from my Windows 7 Desktop Client :

If you see any other errors ,please post it on the Forums.

Troubleshooting Tips :

Common Errors on the Microsoft Application Virtualization Client

The following sections list the most common errors encountered with Microsoft Application Virtualization

Desktop Client and the most common solutions to those errors.

1.When you attempt to refresh the server you get an error that says, “The client failed to download…” and “The server could not authorize you to access the requested data…”

2.The application shortcut is not on the Microsoft Application Virtualization Client desktop.

3.The application did not stream to the Microsoft Application Virtualization Client. If the application fails to stream you see the “Launch Failed” error message above the notification area.

Possible Causes

1. The user account used to log on to the Microsoft Application Virtualization Client is not a member of the Microsoft Application Virtualization Users group or is not a domain user account.

2. The .sft, .ico, and/or .osd files are not in the Microsoft Application Virtualization Management Server “content” folder. Copy these file to C:\Program Files\Microsoft Application Virtualization\Microsoft Application Virtualization Server\Application Virtualization Server\content.

3.There are typing errors in the .osd and .ico paths in the application record in Microsoft Application Virtualization Management Console.

4. The Microsoft Application Virtualization Client cannot access the “content” directory on the Microsoft Application Virtualization server. Check the permissions settings on the content share.

5. The Microsoft Application Virtualization Client cannot access the Microsoft Application Virtualization Management Server. Check network settings, cabling and firewall exceptions for the server services.

6. The “content” folder on the Microsoft Application Virtualization Management Server is not set to share or to be shared with everyone who has read access.

7.The Microsoft Application Virtualization Client is not a member of the domain.

8.The user lacks necessary permissions to access the application. Reread and follow the procedure regarding importing .osd files, paying close attention to setting the access group.

9.The operating system of the Microsoft Application Virtualization Client computer is not listed in the .osd file of the application.

If none of the above appears to be the cause of the problem, check the Microsoft Application Virtualization Client log (Sftlog.txt) in Desktop Client for errors. The file can be found here:

–>C:\Documents and Settings\All Users\Application Data\Microsoft\Application Virtualization Client: Windows XP, Windows Server 2003

–>C:\ProgramData\Microsoft\Application Virtualization Client: Windows 7, Windows Server 2008

References :

Application Virtualization Server :http://technet.microsoft.com/en-gb/library/cc817208.aspx

Application Virtualization Client: http://technet.microsoft.com/en-gb/library/cc817162.aspx

Application Virtualization Sequencer : http://technet.microsoft.com/en-gb/library/cc817192.aspx

Troubleshooting Information for the Application Virtualization Client: http://technet.microsoft.com/en-gb/library/cc843669.aspx

In Previous Guide,we have seen how to Install App-V 4.6 Management Server in windows Server 2008 and How to Publish the Default app-V applications in windows server 2008   to users. In this Guide we will see how to Install App-V desktop Client(4.6) on Windows 7 to receive published application from App-V server.

Before we proceed to run the Setup file,check the link for Client Hardware and Software Requirements http://technet.microsoft.com/en-us/library/cc843822.aspx

One you have all the components in place ,Get a App-V desktop client 4.6 from Microsoft and Extract it before Run.

Run the setup wizard which will scan for and prompt you to install Microsoft C++ 2005 SP1 and 2008 SP1 Redistributable Packages and Microsoft Application Error Reporting if they are not installed.

If you want change default folder location ,click Custom if not Go with Typical

Next On the Application Virtualization Data Location page, provide the path and  location to store data used by all users with Drive letter.

Next, On the Cache Size Settings page ,Provide the Cache size Limit value for data store.Here the max cache size is used 6 GB and also shows amount of free disk space available from installation Drive.You can change it as per the requirement.

Next on Runtime Package Policy Configuration page ,select the applicable configuration how to load the applications and if authrisation requires or not .

Next ,On the Publishing Server page ,Select Setup a Publishing server now ,enter the Display name(server name which can be changed later) ,select Type as “Application Virtualization Server” ,Hostname is App-V Mgmt server name(FQDN) with port 554(RTSP) and Leave the Automatically contact this server to update settings when a user logs in check box selected.

Click Next if you are ready with all the settings configured if not go back and change it.

Requires log off and login to effect changes . Once done,you will see Q Drive created which can’t be open directly like other drives.

Now you have installed App-V Desktop Client 4.6 on Windows 7 Computer.

You We are ready to test the basic functionality of the App-V system by launching the Default Application on the App-V Client that you just installed(http://eskonr.com/2010/12/configuration-of-app-v-4-6-management-server-in-windows-server-2008/). The Default Application is provided as part of the installation and is automatically copied to the Management Server during installation. It is used to verify that the server was installed and configured correctly, but it needs to be published to the client so that the user can access it.

Now Log in to the Desktop Computer as User who is member of Appv-Users which is Security group added to Default application Group in App-V mgmt Server.

As soon as the user logs in,You will see an Icon on desktop(settings above) and Task bar on right hand side which confirms that,desktop client is able to communicate to App-V Management server for receiving the sequenced applications.

From above,we can confirm that,App-V Client is working fine in talking to App-V Management server.

Next—>Configuration settings of App-V Desktop Client and Troubleshooting Steps.

In Last post,we have seen how toInstall App-V 4.6 Management Server in windows Server 2008 .In this post,we will configure management server to publish the default application to the users.

Log into App-V Management server with Account that must be a member of Appv-Admins Group which we created in earlier post in Active Directory.

Click Start | Administrative Tools | Application Virtualization Management Console

In the App-V Management Console, click Actions | Connect to Application Virtualization System

Click on Browse and select the OSD Path for Default application which can be located from \\servername\content\Defaultapp.osd and same do it for Icon Path also as shown below.Do not use localhost or a file path containing a drive letter such as C:\Program Files\..\..\content.

You must enter the UNC path because the applications that are published to the users will be accessed by Users who have read access to it(content folder)

click on the Shortcuts Tab and select how you want to Publish the Default application to the users.

Click the Access Permissions tab, and confirm that the AppV-Users (who requires the application to be published) group is granted access to the application.

click Ok to finish the configuration how to publish the Default application to users.

By default ,the OSD(Open Software Description) file uses the secure connection protocol(RTSPS) which we is not used while installing Management server and we also required to check the management server name is correct or not.so we have to Edit the .OSD file from content directory.so clients can connect to this share and read the OSD file for management server information,etc. It should look like below and save the changes.

Now you have completed how to publish the default application to users.

Next step > How to Install Microsoft Application Virtualization Desktop Client

Brief About What is App-V : Microsoft Application Virtualization enables you to deploy, update, and support applications as services in real time, on an as-needed basis. When you use App-V, you transform individual applications from locally installed products into centrally managed services. Applications become available everywhere they need to be—no computer pre-configuration or changes to operating system settings are required. Microsoft Application Virtualization consists of the following components. More info http://technet.microsoft.com/en-us/library/cc843848.aspx

Before I go into Installation of App-V,you will have to consider some prerequisites that are listed below (which I have in My Lab)

1. Active Directory 2008 functioning Properly.

2.Two AD Security Groups which are used in App-V server which are Appv-Admins and Other is Appv-Users.

— The below requirements should be installed on server which become a APP-V Management server

1.Windows 2008 server with IIS 7.0( components include  ASP.NET (and all required role services and features),Windows Authentication, IIS Management Scripts and Tools, IIS 6 Management Compatibility).

2.Windows SQL server 2008

Once all the above prerequisites are in place,then start the installation of App-V 4.6 Management server with local admin rights.

If you want to change the installation Directory or to select other components,you can go with Custom option.

I have 2 servers with SQL Installed that’s why it shows both in the drop down list.If you don’t see any server listed,please check the SQL server services are stated or not.

Enter the app-V admins group which will be managing the management server in all the cases.

The content folder is one which will be shared(bu default not shared) and keep all the sequenced application which will be used users that we see later how.

The wizard will copy the necessary files, install services, and create a database as specified in the preceding steps. When the wizard finishes, the Microsoft Application Virtualization Management Console shortcut is displayed in the Administrative Tools group.

After the installation wizard completes, It prompts you to restart the server,Click No,since we have to do some addition work here before we restart.

Share the content folder:

1. Open Windows Explorer.

2. Browse to C:\Program Files\Microsoft System Center App Virt Management Server\App Virt Management Server\content and share the content folder. Ensure that Read access to this folder is given to Everyone, and Full Control is given to the AppV Administrators group.
Note: If you are using a 64-bit operating system version, the folder will be under C:\Program Files (x86)\Microsoft System Center App Virt Management Server\App Virt Management Server\content.

Give permission on the SftMgmt.udl file for App-V Administrators group:

If the account you will be using to administer the App-V Server is not a member of the Domain Admins group, perform the following steps to avoid receiving a C800 error when logging in to the App-V Management Console.

1. Open Windows Explorer.

2. Browse to C:\Program Files\Microsoft System Center App Virt Management Server\App Virt Management Service.

Note: If you are using a 64-bit operating system version, the folder will be under C:\Program Files (x86)\Microsoft System Center App Virt Management Server\App Virt Management Service.

3. Right-click the SftMgmt file and select Properties.

4. Select the Security tab.

5. Add the AppV Administrators group, ensure the Read & Execute permission is selected and click OK.

Once all the above steps done,Restart the server.

When you restart the server,App-V services will be in stopped state and you ensure,both the app-V serveries are started.

Now You have completed the Installation of App-V 4.6 Management Server in Windows Server 2008

Next Step—>How to Publish the Default app-V applications in windows server 2008.