Quantcast
Channel: Windows 365 & Intune Management
Viewing all 144 articles
Browse latest View live

Sequence Adobe Reader 11.0.10 using App-V 5.1

$
0
0

1)  Launch the Microsoft Application Virtualization Sequencer from Start-> All Programs




2)  Select the create package (default) option.


3) Select the "Standard application" type in the type of application to be sequenced.


4)  Select "Perform a custom installation" in the select installer screen and click next.

5) Provide the virtual application name as Adobe Reader 11.0.10 and click next.


6) Click Next and Install the Adobe Reader application.

                           

                         
                         
Click Finish.
                             
Select I am finished Installing and click next.

                         
7) If there is any configuration to be done, you can do it in this stage. Or else click next.

                           
8) Click Next.


9) Run the shortcut to capture FB1. If not needed simply click on next.


10) Select the Operating system to be supported and click Next.

11) Select continue to modify the package using Package editor. Remove the desktop shortcut.


12) Create a Powershell script named supressupdates.ps1 with the following script in order to suppress the check for updates tab under Help.



set-location hklm:

new-item -path .\software\policies -name adobe 

new-item -path .\software\policies\adobe -name "Acrobat Reader"

new-item -path ".\software\policies\adobe\Acrobat Reader" -name 11.0

new-item -path ".\software\policies\adobe\Acrobat Reader\11.0" -name FeatureLockDown

new-itemproperty -path "HKLM:\software\policies\adobe\Acrobat Reader\11.0\FeatureLockDown\" -name "bUpdater" -propertytype dword -value 0

new-itemproperty -path "HKLM:\software\policies\adobe\Acrobat Reader\11.0\FeatureLockDown\" -name "bUsageMeasurement" -propertytype dword -value 0  

new-itemproperty -path "HKLM:\software\policies\adobe\Acrobat Reader\11.0\FeatureLockDown\" -name "bProtectedMode" -propertytype dword -value 0

    

Create a powershell script named RegDelete.ps1. This will remove the entry from the physical registry during removal of the appv package.

           Remove-Item -Path 'HKLM:\SOFTWARE\Policies\adobe\Acrobat Reader'–Recurse

Add these two scripts in the scripts folder in the appv package.

Navigate to Package > Scripts folder.

Right-Click the Scripts Folder and choose “Add” to add the above scripts into the package so that they can be leveraged on the client machine.



13) In the Package Editor Window, open the Advanced Tab and check the following checkboxes:

§  Allow COM Objects to interact with Local System.

§  Allow all named objects to interact with Local System.



14) In the Manifest file tab, click on export. This will export the AppxManifest.xml file to the local machine. choose the destination and click on save.
Open the exported AppxManifest.xml using AppVManifestEditor. You can download the tool from here AVME
You can select the checkbox on left hand side to enable the type of script you want, then enter the Path (Powershell.exe) and Arguments field. After editing, save the file using the SaveAs button found at the top right side.


The output of the AppvManifest.xml will be like this.


In the Package Editor, select Import and choose the modified AppxManifest.xml file and select save in the sequencer.This will create the virtual Adobe Reader package with inbuilt scripts in the AppxManifest.xml file.


Installation procedure Using Powershell 3.0:


Step - Enable the scriptexecution policy in the client by using the following command.


           Set-AppvClientConfiguration -EnablepackageScripts $true


This will enable the execution of scripts which we have added inside the package. If not set ,it will show error.


Step - Add the package using the following command.


          Add-AppvClientPackage "path of the Adobe Reader 11.0.10.appv file"


Step - Publish the package using the following command.

          Publish-AppvClientPackage "Adobe Reader 11.0.10"–Global


Step - Mount the package.
         Mount-AppvClientPackage "Adobe Reader 11.0.10"






Add custom scripts in AppxManifest.xml file using App-V 5.1 Sequencer

$
0
0
In the Package editor under advanced tab, you can see the Manifest file tab which has been introduced in App-V 5.1. This doesn't exist in earlier versions of App-V. Using this tab, you can export or import the AppxManifest.xml file.

Earlier if we want to do any custom changes we have to edit the deploymentconfig or userconfig.xml file(for adding scripts, editing FTA's etc). App-V 5.1 provides advanced way to edit those changes within the AppxManifest.xml.

To do so, click on export as highlighted below in the Manifest file tab. This will export the AppxManifest.xml file to the local machine. choose the destination and click on save.

Open the exported AppxManifest.xml using AppVManifestEditor. You can download the tool from here AVME

AVME is a simple yet powerful tool to edit the AppxManifest file.My recommendation is not to edit the AppxManifest file manually.

After opening the file using AVME,you can select the checkbox on left hand side to enable the type of script you want(Machine or User), then enter the Path (Powershell.exe) and Arguments field. After editing, save the file using the SaveAs button found at the top right side.


The output of the AppvManifest.xml will be like this.




In the Package Editor, select Import and choose the modified AppxManifest.xml file and select save in the sequencer.

This will create the virtual package with inbuilt scripts in the AppxManifest.xml file.

App-V 5.1 bug or expected behaviour?

$
0
0
Recently I came across a post in TechNet as the scripts added in deploymentconfig.xml file is not getting triggered when using the App-V generated MSI file for publishing in App-V 5.1.


I planned to do a simple test to check this case before giving out confirmation from my end. Below I have compared this scenario between App-V 5.0 SP3 and App-V 5.1 generated MSI's.


App-V 5.0 SP3:

Step 1- Created a virtualized package.
Step 2- Added a script in deploymentconfig.xml file which would do a simple file copy.




Step 3- Ran the App-V 5.0 SP3 generated MSI and found that it is using the deployment config file and triggered the script and copied the file as expected.
Step 4- Reverted the machine to clean state.
Step 5- Edited the deployment config file and removed / in </MachineScripts>



Step 6- Ran the MSI and see the below error.


Step 7- Checked in App-V event log and see the exact reason for failure that tag is not closed properly.


This proves that App-V 5.0 packages use deployment config file.

App-V 5.1:

Step 1- Created a sample virtualized package using App-V 5.1.
Step 2- Performed the same steps like above. Added a script in deploymentconfig.xml file which would do a simple file copy.




Step 3- Ran the MSI and found that it is not using the deployment config file and did not trigger the script. The file wasn't copied like expected.
Step 4- Reverted the machine to clean state.
Step 5- Edited the deployment config file and removed / in </MachineScripts>



Step 6- Ran the MSI and see that it is getting installed successfully. This shouldn't be the case.

This proves that App-V 5.1 has some sort of bug when installed through its generated MSI that it is not using the deploymentconfig.xml like previous App-V 5.0 version or is this the expected one that App-V 5.1 generated MSI will no longer use the deploymentconfig.xml file? Expecting Microsoft App-V Team to give their answer.

UPDATE:


Editing the App-V 5.0 SP3 PackageMsiTemplate.msi in c:\Program Files\Microsoft Application Virtualization\Sequencer\en-us shows that SetPublishPackage32 Customaction has condition set to below.

APPV_OR_MSI_FILE=[APPV_OR_MSI_FILE];APPV_DEPLOYMENTCONFIG=[APPV_DEPLOYMENTCONFIG];APPV_LOCAL=[APPV_LOCAL];MSI_TEMPLATE_REGKEY=Software\Microsoft\AppV\MsiTemplate\[ProductCode]

                  

Editing the App-V 5.0 SP3 sequencer generated MSI with ORCA shows that SetPublishPackage32 Customaction reflects the same as in PackageMsiTemplate.msi


APPV_OR_MSI_FILE=[APPV_OR_MSI_FILE];APPV_DEPLOYMENTCONFIG=[APPV_DEPLOYMENTCONFIG];APPV_LOCAL=[APPV_LOCAL];MSI_TEMPLATE_REGKEY=Software\Microsoft\AppV\MsiTemplate\[ProductCode]

                  

In App-V 5.1:


Editing the App-V 5.1 PackageMsiTemplate.msi in c:\Program Files\Microsoft Application Virtualization\Sequencer\en-us shows that SetPublishPackage32 Customaction has condition set to below.

APPV_OR_MSI_FILE=[APPV_OR_MSI_FILE];MSI_TEMPLATE_REGKEY=Software\Microsoft\AppV\MsiTemplate\[ProductCode]




It is missing APPV_DEPLOYMENTCONFIG=[APPV_DEPLOYMENTCONFIG] property and so App-V 5.1 generated MSI doesn't use the deployment config file while installing in standalone mode.


Many a thanks to App-V Techie Roy Essers for confirming this point.

Steps to create MS Project 2013 App-V 5.0 package using ODT 2013

$
0
0

    Download the Office Deployment Tool (ODT 2013) 
      http://www.microsoft.com/en-us/download/details.aspx?id=36778


      Once downloaded, run officedeploymenttool.exe and Accept the EULA

      Click-to-run EULA


      Select a folder so that the setup will extract the files.


      Edit the Configuration.xml file like below.





      To know more about configuration.xml, check the below link.


      https://technet.microsoft.com/en-us/library/jj219426.aspx?f=255&MSPPError=-2147217396


      After editing the configuration file, open up CMD and run as an administrator and run the below command.


      SETUP /download [path to configuration file]







      It will download the files to the path mentioned in Sourcepath. After download is completed, run the below command to generate the App-V 5.0 Package.


      SETUP /packager [path to configuration file] [output path]


      NOTE:
       /download  Downloads files to create an Office15 installation source.
       /packager   Produces an Office App-V package from an Office installation source.







      This process will run for sometime and will open a second CMD window and run a process called flattener.exe. Flattener.exe essentially removes the Click-to-Run standalone installation elements from the Office package and prepares the package for use with App-V.







      After sometime flattener will exit and you can find the App-V package created in the output path specified earlier.


      If there is any issue during flattening process, you can check in the flattener.log created in the WorkingDir folder.


      Note:
      To know more about supported Product IDs check here  http://support.microsoft.com/kb/2842297

      Create App-V 5.0 package for MS Visio 2013 standard using ODT 2013

      $
      0
      0
        Download the Office Deployment Tool (ODT 2013) 
          http://www.microsoft.com/en-us/download/details.aspx?id=36778


          Once downloaded, run officedeploymenttool.exe and Accept the EULA

          Click-to-run EULA


          Select a folder so that the setup will extract the files.


          Edit the Configuration.xml file like below.





          To know more about configuration.xml, check the below link.


          https://technet.microsoft.com/en-us/library/jj219426.aspx?f=255&MSPPError=-2147217396


          After editing the configuration file, open up CMD and run as an administrator and run the below command.


          SETUP /download [path to configuration file]







          It will download the files to the path mentioned in Sourcepath. After download is completed, run the below command to generate the App-V 5.0 Package.


          SETUP /packager [path to configuration file] [output path]


          NOTE:
           /download  Downloads files to create an Office15 installation source.
           /packager   Produces an Office App-V package from an Office installation source.







          This process will run for sometime and will open a second CMD window and run a process called flattener.exe. Flattener.exe essentially removes the Click-to-Run standalone installation elements from the Office package and prepares the package for use with App-V.







          After sometime flattener will exit and you can find the App-V package created in the output path specified earlier.


          If there is any issue during flattening process, you can check in the flattener.log created in the WorkingDir folder.


          Note:
          To know more about supported Product IDs check here  http://support.microsoft.com/kb/2842297

          Current Best Practices for Application Virtualization

          UPDATED: Best Practices for Application Virtualization (App-V)

          $
          0
          0
          Since previous video had some technical issues, updated the blog with the new one. This webinar is from Steve Thomas explaining current best practices for App-V.



          Hotfix Package 2 for Microsoft Application Virtualization 5.1 and Hotfix Package 3 for Microsoft Application Virtualization 5.0 SP3 available now


          How to run multiple scripts in App-V 5.1

          $
          0
          0
          Later today when I opened my blog to update a new post, I found that I already had quite some posts in drafts section. Few of them are outdated and few needed to be updated to the current date. I will be updating them and post them as soon as possible. The first post to clear from my draft bucket is how to add multiple scripts in App-V.


          Earlier in App-V 5.0 it wasn't possible to run multiple scripts in deploymentconfig.xml or userconfig.xml file.

          But in the latest App-V 5.1, it supports running multiple scripts both in deploymentconfig.xml or userconfig.xml file with the help of ScriptRunner.exe.


          ScriptRunner.exe comes along with the App-V 5.1 client and gets installed in the client folder.






          You can check how to use the ScriptRunner.exe and its parameters by opening up CMD and running ScriptRunner.exe /?






          You can add multiple scripts by adding them as arguments to the ScriptRunner.exe using -appvscript parameter. The scripts run in the order as how we give them. But note we need to add the -wait parameter. If not given the scripts will run without any order.


          We can add the -wait, -timeout, -rollbackonerror parameters using the -AppVScriptRunnerParameters to ScriptRunner.exe.It's not mandatory to provide all the -wait, -timeout,-rollbackonerror parameters. We can add them only when needed. But be sure to add -wait parameter if you want the scripts to run in an order to avoid issues.


          ScriptRunner.exe can be used in both the DeploymentConfig.xml and the UserConfig.xml files.It can also be used in AppxManifest.xml. To know more about how to export, edit and import the AppxManifest file check here - http://app2pack.blogspot.com/2016/01/add-custom-scripts-in-appxmanifestxml.html

          ScriptRunner.exe can be used in all the 8 trigger events both in the MachineScripts and UserScripts section.





          To know more check the official TechNet page:
          https://technet.microsoft.com/en-us/library/mt346534(v=vs.85).aspx

          Sequence & Customize Google Chrome 48.0 - App-V 5.1 HF2

          $
          0
          0
          To sequence Google chrome 48.0 follow the same steps as I have blogged earlier. Check the below link.
          http://app2pack.blogspot.com/2015/10/sequencing-google-chrome-using-app-v-50.html


          To customize further like setting a home page, show home button, check default browser, disable show welcome page, disable import history from other browsers etc.., follow the steps mentioned below.


          Create a file named master_preferences or edit the file in C:\Program Files (x86)\Google\Chrome\Application folder with the below contents during monitoring or configure phase while performing sequencing using App-V 5.1 Sequencer.


          {
           "homepage" : "
          http://app2pack.blogspot.com",
           "homepage_is_newtabpage" : false,
           "browser" : {
           "show_home_button" : true,
           "check_default_browser" : false,
            },
           "bookmark_bar" : {
           "show_on_all_tabs" : true
           },
           "distribution" : {
           "skip_first_run_ui" : true,
           "show_welcome_page" : false,
           "import_search_engine" : false,
           "import_history" : false,
           "create_all_shortcuts" : false,
           "do_not_launch_chrome" : true,
           "make_chrome_default" : false
           }
           }



          For more info about other preferences -


          https://support.google.com/chrome/a/answer/187948?hl=en


          http://www.chromium.org/administrators/configuring-other-preferences


          If you have already sequenced and want to replace only the master_preferences  file, then edit the sequenced package and in the package editor Package files tab remove the file and import the new master_preferences file into the package and save the virtual package.

          Issue with sequenced SAP GUI 7.40 "Unable to load GSS-API DLL named sncgss32.dll" - APPV 5.0

          $
          0
          0
          Hi folks, hope everything is going fine. First I would like to  thank all for your tremendous support. It's a sunny weekend here and I am sitting in home and blogging .


          Previously, one of my distance friend who is an App-V engineer asked me to help him with an issue he was facing when launching virtualized SAP GUI 7.40. When launching the SAP logon shortcut, he was facing this issue.





          When clicking yes, it prompts the below information.





          First and more most tool that helps us is the great handy PROCMON tool. When analyzing the issue it showed that the shortcut is looking for sncgss32.dll and it couldn't find it.We manually searched in the App-V location and yes we couldn't find it anywhere.





          We installed the source manually in a fresh machine and searched for the sncgss32.dll and we couldn't find it anywhere.


          Then comes our friend Google. we searched what might be the reason for failure. We found that it needed an  environment variable SNC_LIB of the client host system set to <Install_Path_SAP_GUI>\FrontEnd\SapGui\Encryption\secgss.dll"

          http://help.sap.com/saphelp_nw70ehp1/helpdata/en/b4/a040e5f0fe4ceeb7a4d6144f4d0f28/content.htm?frameset=/en/76/ea37bd31794c1da6f1ae9ba5a9df5d/frameset.htm


          I checked with him whether the environment variable was set during monitoring phase. Indeed his reply was that the environment variable was set during sequencing.


          We then opened up the virtual bubble of the sequenced SAP GUI package using the below command.


          cmd.exe /appvve:ProductID_VersionID


          We can see that the SNC_LIB environment variable inside the virtual environment using the SET command. Then why the application is failing to use it?





          We manually created the environment variable locally in the machine. Now when launching the shortcut it works fine as expected. But we didn't want this to be the solution. Lets try some other method.


          I often ask people to launch the shortcut inside the virtual bubble once whenever they face any error to eradicate issues in a simple way. The same we did here too.





          We tried to launch the shortcut exe inside the virtual bubble (which was opened earlier using cmd.exe /appvve:ProductID_VersionID). Viola!!! the shortcut works as expected.

          UPDATE:

          You can also modify the main shortcut and add CMD to run as a middleman.

          Example:

          cmd.exe /c start """C:\Program Files\myapp.exe"

          Thanks Dan Gough for pointing this out.

          Sequence Oracle SQL Developer client - App-V 5.0 SP3

          $
          0
          0
          Since Java is a dependency to the Oracle SQL Developer application, install the jdk1.6.0_23(I currently have this source and so I Am using it. In case you have the latest JDK version install it)


          Start the sequencing steps using App-V sequencer 5.0 SP3.


          Select create a new virtual package.


          Select create package.


          Select standard package.


          Select custom installation.






          After providing the Virtual application package name click next.


          Create a folder named SQLDEVELOPER in C:\ drive.


          Copy the source files to C:\SQLDEVELOPER


          Goto C:\SQLDEVELOPER\sqldeveloper\bin\ and edit the sqldeveloper.conf file and set the
          Java homepath.


          SetJavaHome C:\Program Files (x86)\Java\jdk1.6.0_23 (If you have the latest JDK, point it to that location)





          Create a shortcut named SQL Developer and point it to C:\SQLDEVELOPER\sqldeveloper.exe.


          Launch the shortcut and click on OK to configure the FTA's.





          Uncheck the Show Tip at startup and close the prompt.





          Goto Tools-Preferences and uncheck show splash screen at startup.





          These changes get stored in %appdata%\SQL Developer\system x.x.x





          Open the "%Appdata%\SQL Developer\system3.1.07.42\o.sqldeveloper.11.2.0.7.42\product-preferences.xml" file and click Ctrl+F and enter update and modify the value as shown below. This will suppress the updates available popup at startup.


           <hash n="oracle.ideimpl.webupdate.CheckForUpdatesPreferences">
                <value n="checkOnStartup" v="false"/>





          Now Installation is done, click "I am finished installing" and click next. I didn't launch the shortcut as I wanted the package to fault stream in the client side (As I wanted the first launch to be faster).






          Check the below options to allow COM object to interact and Allow full write access to VFS.





          Save the package and test it in the client side.


          Client Testing Using Powershell:


          Install the  jdk1.6.0_23 locally in the client machine.


          Open Powershell as admin. Set execution policy to bypass or unrestricted (testing purpose only)


          Publish the SQL Developer App-V package using the below command in PS.

          Add-AppvClientPackage "path to .appv file" | Publish-AppvClientPackage -Global | mount-AppvClientPackage

          Solution for Error 17002 when uninstalling Office 365 (2016) when apps like word, excel, outlook are open

          $
          0
          0
          When uninstalling office 365 silently, it is failing only when any applications like word, excel are kept open. This is because during uninstall, office checks for any running applications and prompts the user to close it which is not happening in silent uninstall.


          When uninstalling in UI mode, it prompts to close when any office apps are open. Since in silent mode office is not able to do this, it fails with an error code 17002.




          You can check in the log file for the error code 17002.





          To overcome this just add the property FORCEAPPSHUTDOWN with Value="True" in the uninstall config.xml file. This property will force shutdown any running office apps.


          Example:


          <Configuration>
           <Remove>
           <Product ID="O365ProPlusRetail">
           <Language ID="en-us" />
            </Product>
           </Remove>
          <Property Name="FORCEAPPSHUTDOWN" Value="TRUE" />
          <Display Level="None"/>
          <Logging Path="c:\temp\" Name="Uninstall.log"/>
          </Configuration>


          NOTE:


          Place  the  <Property Name="FORCEAPPSHUTDOWN" Value="True" /> part after  the <Remove>... </Remove> tags. If it is placed in between <Remove>... </Remove> tags, then it wont work.


          You can use the below online configuration xml editor to avoid issues when editing the XML file.


          http://officedev.github.io/Office-IT-Pro-Deployment-Scripts/XmlEditor.html

          Steps to sequence Mozilla Firefox 44.0.2 - AppV

          $
          0
          0
          Prior to sequencing Mozilla Firefox,create three files as below.These files are used to suppress updates,check for default browser check,set homepage,disable browser import and other configuration etc.. and lock the preferences so that user will not be able to edit them.
          First create a file named mozilla.cfg with your custom configuration.
          Example:

          // disable default browser check
          pref("browser.shell.checkDefaultBrowser", false);
          // disable application updates
          pref("app.update.enabled", false);
          // Set default homepage - users can change

          defaultPref("browser.startup.homepage", "http://home.example.com");

          Second create a file named local-settings.js and add the below contents.
          pref("general.config.obscure_value", 0);
          pref("general.config.filename", "mozilla.cfg");

          More about locking preferences - http://kb.mozillazine.org/Locking_preferences
          Third create a file named override.ini and add the below lines.This file is used to disable the browser Import Wizard on first run.
          [XRE]
          EnableProfileMigrator=false
          Copy these three files to a temp folder.
          Now start the sequencing steps using App-V sequencer 5.0 SP3.

          1. Select create a new virtual package.


          2. Select create package.


          3. Select standard package.


          4. Select custom installation.


          5. Type the name of the virtual package as Mozilla Firefox 44.0.




          6. Click Next. Install the given source package.


          7. Once Installation is completed. Copy the three files from Temp location to their respective paths.


          mozilla.cfg - This file needs to be added to "programfiles(x86)\Mozilla Firefox\" folder inside your package.

          local-settings.js - This file needs to be added to "programfiles(x86)\Mozilla Firefox\defaults\pref" folder inside your package.

          override.ini - This file needs to be added to "programfiles(x86)\Mozilla Firefox\" folder inside your package.

          Disable the Mozilla Maintenance Service to prevent updates. Run the below command in CMD.
          sc config MozillaMaintenance start= disabled


          After copying to the respective location click on "I am finished Installing"


          8. In the configure software phase, launch the shortcut to capture the Primary feature block (Feature block 1) and verify whether the settings have been incorporated from the above files added.You can also perform additional customization in this phase as the changes will be monitored here too.



          9. Click on save the package.



          10. Test the package using Powershell in a standalone environment.

          Set Execution policy to bypass or unrestricted mode.

          Publish the Mozilla Firefox 44.0 App-V package:

          Add-AppvClientPackage "path to .appv file" | Publish-AppvClientPackage -Global | mount-AppvClientPackage


          NOTE:

          In case if you are facing any issues after sequencing like application is not launching but process in running in task manager, do like this.



          1. Enable all the check-boxes in the sequenced package Advanced tab (COM Interaction, Full write access to VFS, Named objects interact with local system).
          2. Do not launch Mozilla firefox during sequencing.





          Sequence SPARX Enterprise Architect 12.0 - AppV 5.1

          $
          0
          0
          Select create a new virtual package.


          Select create package.


          Select standard package.


          Select custom installation.


          Type the name of the virtual package as Sparx Enterprise Architect 12.0.





          Click Next and Install the application.




















          Remove desktop shortcut. Select I am finished Installing.








          If you need to do any post install configuration like adding new registration key,Launch the shortcut “Enterprise Architect” and do it here.Once done click Next.





          Click Next and save the Package.






          App-V 5.1 sequencer fails to install with fatal error

          $
          0
          0
          Lat week I was asked by one of my friend to troubleshoot an issue which he was facing earlier.

          Question: When Installing App-V 5.1 sequencer, it fails to install with the below error.

           

          Solution: When Installing the sequencer, it places log files in %temp% location. We can analyze the possible reason by looking into it.


          When opened the appv_sequencer_xxxxx_0_CoreX64 log file (which is the actual MSI install log), and Ctrl+F search and giving Return value 3 we see that there is a pending restart needed before installing the sequencer. The sequencer msi has a Launch condition to check for any pending restart.

          We restarted the machine and again tried to install the App-V 5.1 sequencer setup. this time it got installed successfully.

          App-V 5.1 and App-V 5.0 SP3 generated MSI doesn't install without Administrator privileges Error code 0300000102- Solution

          $
          0
          0
          Question: When trying to run the App-V 5.1 or App-V 5.0 SP3 created MSI in the client machine, it fails with the error code 0300000102. How to resolve this.





          Corresponding Event log:





          Solution: Try running the CMD as Administrator and from here run the MSI file.This will resolve the issue. The MSI requires Admin privileges to run in the client machine.


          Ok, now this works but what might be the reason? This comes into everyone's mind. Let me explain further.


          Opened the App-V 5.1 sequenced MSI package and first checked in the Launch Condition table using ORCA. I see that there is a Privileged condition. I removed it by creating a Transforms file for the MSI. Tried Installing again and even this time it failed.





          Analyzed further by opening the MSI template file for App-V 5.0 SP2. The msi will be located in C:\Program Files\Microsoft Application Virtualization\Sequencer\en-US


          I see that the Custom Action PublishPackage32 and PublishPackage64 has Type to run in deferred execution in system context (3073)





          Now opened the MSI template file for App-V 5.1 and see that those Custom Action PublishPackage32 and PublishPackage64 has Type to run in deferred execution (1025)





          Ok now I have found a reason. It's time to test it. I created a Transforms file for the App-V 5.1 generated MSI package (Testpackage.msi) and changed the type for PublishPackage32 and PublishPackage64 to run in deferred execution in system context.


          Tried installing the MSI with the created Transforms file (MST). Viola!! it works fine without the need for CMD as admin.


          The same applies for RemovePackage32 and RemovePackage64 custom action also. This method works great for App-V 5.0 SP3 generated MSI also.


          NOTE:


          I heard from Dan Gough that he has created a Transforms file (MST) which would automate this case and resolves the need for Run as Admin. In addition to that he has also added support to include the deployment config.xml file too when installing. Hopefully he will be releasing it officially by this month. Once he releases it, I will be updating this blog with his Link to download the MST file.
           

          How to remove virtual services captured in package after sequencing - AppV 5.1 & App-V 5.0

          $
          0
          0
          Question: I need to remove the service that is in virtual services tab in the package editor, but I am not able to see an option to do it. How to achieve this?


          Workaround: If you have failed to remove the services that are not necessary like services that perform auto update during sequencing, then it is not possible to remove it in the package editor.


          From the sequencer guide Microsoft Application Virtualization 5.0 Sequencing Guide  :


          The Services tab displays the current configuration of virtualized application services and allows for changing the Startup Type, Log On and Dependencies configuration of virtualized services.
          Note: The services tab is read-only.  In order to disable a virtual service, set the service?s properties during monitoring using Services.MSC or by utilizing a dynamic configuration file post-sequencing, as described later in this document.


          With the release of App-V 5.1, we expected Microsoft will be providing the option to disable/delete the services that are captured in the package editor, but they didn't give us the option. So it is same like App-v 5.0. We need to do it in alternate ways. In this blog, I have taken an example Mozilla Firefox which is having a service Mozilla Maintenance Service which would be auto updating the application to latest version.





          Solution 1:


          Open the config file (deployment or user) and search for services. In the services tag, change the value from true to false.


                 <ServicesEnabled="false"/>







          Option 2:


          Open the package with the sequencer and perform an upgrade. Choose custom install. In this phase the sequencer will de-virtualize the package.







          Open registry and remove the service present (HKLM\System\CurrentControlSet\Services). This will remove the service getting captured.







          End the monitoring phase and save the package. Now when you edit the package using package editor, you can see that the service is not listed.







          NOTE: A kind request to the readers,if you support the need for disable/delete the services in the virtual services tab in the package editor, do vote it here App-V User Voice.


          Conclusion: With the  next update, at-least we can hope that Microsoft will provide an option to remove the services in the package editor itself.

          Sequence Excel addin for Adobe Analytics Report Builder 5.2 - AppV 5.1

          $
          0
          0
          There are some possible ways to make sequenced add-on work with the locally installed office product. I have listed them below. You can use whichever method suits your need.


          1.Create shortcut to local excel:


          Install the Microsoft office product locally in the machine prior to sequencing. Open the sequencer and select Add-on or plugin option.





          select I have installed the primary package and click next.





           Enter the virtual package name





          Install the Adobe Analytics Add-in .















          Create a shortcut for excel during monitoring phase and launch it to verify the Adobe Analytics addin.





          End the sequence and save the package. In the client side make sure that Office product is installed locally prior to publishing of Adobe Analytics virtual package.


          2. Using /appvve:


          Alternatively, if you do not want to create a separate shortcut you can make use of /appvve:


          Eg: Excel.exe /appvve:ProductID_versionID





          3. Using Runvirtual:


          You can create a registry entry for Excel to load inside the Adobe Analytics virtual environment using Runvirtual. From App-V 5.0 SP3 runvirtual supports both machine and user. i.e you can create entry in HKCU for user also.





          UPDATE:
          In case if you have multiple excel addon's then follow this link from Steve Thomas.


          http://blogs.technet.com/b/gladiatormsft/archive/2013/09/04/app-v-on-virtualizing-multiple-excel-add-ins.aspx




          NOTE: The above steps are for locally installed Office product. If office product is virtualized, then you would need to create a connection group.


          Also note plug-in package should be published globally to match the global settings of the published Office App-V package. Also verify that the Deployment Configuration File of the plug-in package has the same settings that the Office App-V package has.You can search the Deployment Configuration File for “COM Mode” and ensure that your plug-ins package has that value set as “Integrated” and that both "InProcessEnabled" and "OutOfProcessEnabled" match the settings of the Office App-V package you published. Open the Deployment Configuration File and set the value for Objects Enabled to false.


          For more Information, kindly refer the below link.


          https://technet.microsoft.com/en-us/library/mt590515.aspx#BKMK_custmz_manage_Office_pkgs

          How to create AppPaths for already sequenced application - App-V 5.0

          $
          0
          0
          Question: I have an App-V 5.1 sequenced application and I have a requirement. When entering the application name in Run command it should open up the App-V virtual application. For example, when we enter iexplore in Run, it opens up internet explorer.


          Solution: You can use the AppPath subsystem in App-v 5.0 and higher. This subsystem exposes the App Path registration of a virtual application to the native operating system. Using this registration, the operating system can find the application’s executable. This feature is usually used by an application to avoid modifying the system PATH environment variable.


          Reference - https://blogs.technet.microsoft.com/appv/2013/01/03/microsoft-application-virtualization-5-0-integration/


          So how can we implement this in the virtual package? If package has been already sequenced, then you can edit the Dynamic configuration file and add the AppPath subsystem.


          <AppPaths Enabled="true">
                  <Extensions>
                    <Extension Category="AppV.AppPath">
                      <AppPath>
                        <Name>app.exe</Name>
                        <ApplicationPath>[{ProgramFilesX86}]\app\app.exe</ApplicationPath>
                        <PATHEnvironmentVariablePrefix>[{ProgramFilesX86}]\app\</PATHEnvironmentVariablePrefix>
                        <ApplicationId>[{ProgramFilesX86}]\app\app.exe</ApplicationId>
                      </AppPath>
                    </Extension>
                  </Extensions>
           </AppPaths>



          In the below example we have added AppPath subsystem for AstroGrep.exe. After adding and publishing it with the dynamic config file, you can see the AppPath being created in the Local registry. Now when you type Astrogrep in Run command it will open up the virtual AstroGrep package.





          If you have published the package to user, then the AppPath will be created in the HKCU\Software\Microsoft\Windows\CurrentVersion\App Paths








          If you have published the package globally, then the AppPath will be created in the HKLM\Software\Microsoft\Windows\CurrentVersion\App Paths





          To know more about App Path check here - https://msdn.microsoft.com/library/windows/desktop/ee872121#appPaths


          Scenario:


          What if suppose already a local install of the same application may be a different version with App Path is present and App-V package is published.


          The App-V package will replace the App Path and point it to the virtual location of the exe and vice versa. Lets consider an example with Mozilla Firefox.


          First a local install of the Mozilla Firefox was done and we can see the App Path for firefox.exe pointing to the local install folder c:\Program Files(x86)\Mozilla Firefox\firefox.exe





          Now an App-v package for Mozilla Firefox with App Path subsystem is published globally. You can see that the App Path for firefox.exe has been modified to virtual package location
          %AllUSERSPROFILE%\Microsoft\AppV\Client\Integration\21546D08-2EEA-4DE8-8290-C7449E707457\Root\VFS\ProgramFilesX86\Mozilla Firefox\firefox.exe





          If you type firefox in Run command now, it will open the virtual package and not the local one as the App Path points to the virtual package exe.


          What happens when you unpublish the App-V package first. It will replace the App Path back to the local install location for firefox.exe.





          Suppose if the local package is uninstalled first, it will completely remove the App Path registry for firefox.exe. Now when you type firefox in Run, it wont work. In order to bring back the virtual path for firefox.exe in App path, you need to repair the firefox app-v package using Repair-AppvClientpackage -Extensions command.


          Viewing all 144 articles
          Browse latest View live