App-V 5.0 – Sequence MDesign 2012

Install all components and after that the installer will ask you following question.

mdesign1

Choose “No” and install FlexLM.

After that it will ask you to create a Hostfile. Say again “No”.

mdesign2

Now here comes the problem. If you copy your License files to the standard folder (C:\Q\MDesign\License files) the FlexLM client won’t find the license files if you start the application because the folder names have to much characters. Normally the path looks like this on the client machine: C:\ProgramData\AppV\PackageID\VersionID. This is to long for the FlexLM client. As a workaround we copy the License files to the Windows folder when we Sequence.

I created following folder structure:

C:\Windows\App-V\MDesign\License files

and in this folder i put the license files. After that we must start the FlexLM client. You can find it under C:\Q\MDesign\License files. Start lmtools.exe with administrator rights.

mdesign3

Now switch the tab to “Config Services” and type in the path where the license files are stored.

mdesign4

Restart the server and everything should work. πŸ™‚

Print Friendly, PDF & Email

AppV 5.0 – Sequence Software Eagle

You can sequence the application normally. But if you publish and test your application with a Domain User which has no Admin Rights you will get a error message, that you have no rights to read/write the license file. For this problem you must change the rights on the eagle license file. My solution was to create a script which change the permission on this file. The script look like this:

Please note: Change the path that it matches your PackageID.

$license_file = "C:\ProgramData\App-V\A6D812CF-A1DA-4CA3-9114-F5B2C64EBB8E\112A1E05-5958-477E-BDFF-DD95322E201F\Root\EAGLE-6.4.0\bin\eagle.key"

$acl = Get-Acl $license_file
$arguments = "Everyone","Modify","Allow"
$accessRule = New-Object System.Security.AccessControl.FileSystemAccessRule $arguments
$acl.SetAccessRule($accessRule)
$acl | Set-Acl $license_file

In the XML default Configuration add following:

<MachineConfiguration>
<MachineScripts>
<PublishPackage>
<Path>powershell.exe</Path><Arguments>-ExecutionPolicy ByPass -File \\app-v.yourdomain.at\scripts$\Eagle\eagle.ps1</Arguments>
<Wait Timeout="120" RollbackOnError="true"></Wait>
</PublishPackage>
</MachineScripts>
</MachineConfiguration>
Print Friendly, PDF & Email

App-V 5.0 – Howto run scripts

The way you deploy scripts on App-V 5.0 changed a lot in front of App-V 4.6. I tried a lot to get scripts working. This howto is maybe not the best solution but for me it works now well. So let’s beginn.

First of all you need a file share where you can place your scripts. For example:

\\app-v.yourdomain.at\scripts$

Attention: On this share “Everybody” must have read rights!

In our example i have a program that should copy some files to the Windows folder. So i created a folder with the software name (in my case “Celcat”) and put in the files i want to copy.

appv_script1

In the SysWOW64 folder are my files which i want to copy. The other file “celcat.ps1” is the script. This is our script. Here is the content of my celcat.ps1 script:

Copy-Item '\\app-v.yourdomain.at\scripts$\Celcat\SysWOW64\*' 'C:\Windows\SysWOW64\' -Recurse -Force

After that you can login to your Admin Console through the Web Browser. Then select your Application and with right click select: “edit default configuration“. Then click on “(4) Advanced” and then “Export configuration“. Now you can save the .xml file on your computer.

appv_script2

I highly recommend to use an XML Editor. We must add now our script. These are the lines we must add:

<MachineScripts>
  <PublishPackage>
    <Path>powershell.exe</Path>
    <Arguments>-ExecutionPolicy ByPass -File \\app-v.yourdomain.at\scripts$\Celcat\celcat.ps1</Arguments><Wait Timeout="120" RollbackOnError="true"></Wait>
  </PublishPackage>
</MachineScripts>

The full .xml file you can findΒ here.

For the Server side we are now finished. Now we can configure our Client to run the script. We must enable scripts on the client with following command:

Set-AppvClientConfiguration -EnablePackageScripts $true

After that we can run the Publishing Command:

Publish-AppvClientPackage -Name * -Global

Now the script should run and you can look in your Windows folder if the files are now present. You can see the result of the script status in the Event Viewer.

Usefull stuff

You can add the option to publishing all applications on login, when you add a App-V Publishing Server. Use this command:

Set-ExecutionPolicy unrestricted
Import-Module AppvClient
Add-AppvPublishingServer -Name app-v.yourdomain.at -URL http://app-v.yourdomain.at:12346 -GlobalRefreshEnabled $true -GlobalRefreshOnLogon $true
Print Friendly, PDF & Email

AppV – Eclipse 4.2

  1. Download Eclipse IDE for Java EE Developers
  2. Get all URLs for the Plugins

    http://download.aptana.com/studio3/plugin/install
    https://dl-ssl.google.com/android/eclipse/
    http://dl.google.com/eclipse/plugin/4.2

  3. Start the Sequencer and unpack the Eclipse to Q:\eclipse.010\Eclipse
  4. After you unpack create a shortcut on the Desktop
  5. After that, say in the Sequencer you are finished installing
  6. On the first start of Eclipse you must enter your Workspace path. Create a folder in Q:\eclipse.010\Workspace
  7. After that you can install all your needed plugins and set the correct path in your settings. For example the Android SDK path and for the Git (Team – Git)
  8. Now you can finish your setup and finalize your AppV Package.
  9. Now you must change your .osd file. If you didn’t do this your settings will be gone if a user starts Eclipse. So i copy the Workspace from Q:\ to the users private drive.
<DEPENDENCY>
		<CLIENTVERSION VERSION="4.6.0.0"/>
		<SCRIPT EVENT="LAUNCH" TIMING="PRE" PROTECT="TRUE" WAIT="TRUE"> 
		<HREF>xcopy Q:\eclipse.010\Workspace\* \\files.fhv.at\%username%$\Profile\workspace\ /e /d /y</HREF>
</SCRIPT>
</DEPENDENCY>
Print Friendly, PDF & Email

AppV 5.0 Beta 2 – Client Installation

Start the setup and install the client. You must add a Server but this could only be done with Powershell.

First load the Modules and enable scripts:

Set-ExecutionPolicy unrestricted
Import-Module AppvClient

Than add your server. Note this is the URL and Port number from the Publishing Server not the Management Console.

Add-AppvPublishingServer -Name appv-server -URL http://appv-server:82 -GlobalRefreshEnabled $true -GlobalRefreshOnLogon $true

See also:
AppV 5.0 Beta 2 – Import Applications on the Server
AppV 5.0 Beta 2 – Sequencer
Windows Server 2012 – AppV 5.0 Beta 2 Server
AppV 5.0 Beta 2 – Client Installation

Print Friendly, PDF & Email

AppV 5.0 Beta 2 – Import Applications on the Server

First login to your Management Console. Go to the “Packages” section and click on the right side “Add or Upgrade Packages”.

Now enter the UNC or HTTP path. If you enter a UNC path the streaming works with SMB. Otherwise it will use HTTP. The AppV Server makes the choice automatically.

After successfully imported you must give the user rights. Click on AD Access “Edit” and type in your Group which should have access. Don’t forget to type in the Domain Name.

Finally you must publish you application with a right click on the application.

See also:
AppV 5.0 Beta 2 – Import Applications on the Server
AppV 5.0 Beta 2 – Sequencer
Windows Server 2012 – AppV 5.0 Beta 2 Server
AppV 5.0 Beta 2 – Client Installation

Print Friendly, PDF & Email

AppV 5.0 Beta 2 – Sequencer

Install the Sequencer and restart your computer. After that make sure you have disabled following services:

  • Windows Search
  • Windows Defender

Let’s Sequence one application. Mainly the interface is the same as on AppV 4.6 SP1 but anyway there are some things different from the previous version. For example there are no more .osd files. This is now all saved in two .xml files and an .appv file, which you can rename to a .zip file, so you can see the content. Also you doesn’t need any additional drive to sequence. You can sequence to any directory on your C:\ drive.

Start the Sequencer and Create a new Package. Select a name and where to install (Old Q-Drive)

Select your correct installation location.

Install the programm and let the Sequencer collect the changes. After that you can start every application and set your needed preferences. Finally say “Customize” so you can prepare your package for streaming. Let’s create the package and you can import it on your server.

See also:
AppV 5.0 Beta 2 – Import Applications on the Server
AppV 5.0 Beta 2 – Sequencer
Windows Server 2012 – AppV 5.0 Beta 2 Server
AppV 5.0 Beta 2 – Client Installation

Print Friendly, PDF & Email

Windows Server 2012 – AppV 5.0 Beta 2 Server

Introduction

For the AppV Server you need some requirements. First of all you need a Domain Controller on a seperate Server. If you have the Domain Controller on the same machine you can’t install AppV Server. Furthermore you need an SQL Server. Note: For now it looks like that the SQL Express Edition’s doesn’t be supported. This could be installed on the same machine.

Add your AppV Server to your domain

Install the SQL Server

I have used the MS SQL Server 2012 Standard Edition.
Select here what you need. I select a default install.

Select “Default Instance”

Under SQL Administrators add your AppV-Admin Group. In my case my Domain Name is AD and the group called “AppV-Admins”

Finish the setup and you are done with the SQL setup.

Attention:Β Add your Domain Administrator to the AppV-Admins Group!!!

Install the IIS Webserver

Goto to the Server Manager and add a Role. Select “Webserver IIS”.

At the point were you select the features make sure you select all like this to screenshots.


After the installation you shoud register .Net in your IIS. You can make this with following command:

dism /Online /Enable-Feature /all /FeatureName:IIS-ApplicationDevelopment /FeatureName:IIS-ASPNET /FeatureName:IIS-ASPNET45

AppV Server Installation

Now we can start the Setup for the AppV Server. I would suggest to login on your server as the Domain Administrator and then start the setup. Otherwise i have problems to connect afterwards to the SQL Database.

First start the setup and select only: “Management Server DB”. Click next and select your SQL Server address or Local instance.

Add your AppV Admin Group.

After setup is finished start again the Setup for the AppV Server. You must do this so that the setup create the correct SQL Database for you. Select now the Management Server.

Specify the AppV Admin Group and the Port for your Management Server.

After successfull installation you should now be possible to login to your Management Console with following URL:

http://yourservername:81/Console.html

But we are not finished yet. πŸ˜‰ Start again the installer and select Publishing Server.

Now speciffy the Url of your Management Console. A few steps before we typed in following Management Console URL:

http://appv-server:81

Also enter a Port for the Publishing Server. In my case i use Port 82.

Now it should all work and you can login to your Management Console.

See also:
AppV 5.0 Beta 2 – Import Applications on the Server
AppV 5.0 Beta 2 – Sequencer
Windows Server 2012 – AppV 5.0 Beta 2 Server
AppV 5.0 Beta 2 – Client Installation

Very helpful sites:
http://appvid.blogspot.co.at/
http://blogs.technet.com/b/appv/archive/2012/05/08/walking-through-the-app-v-5-0-beta-server-setup-part-1.aspx
http://cliffdavies.com/blog/appv/installing-app-v-5-0-beta-part-1/

Print Friendly, PDF & Email

AppV – Altova Missionkit

Start the Sequencer and the installer. At the installer make following settings.

Attention: At this point we must select the correct installation location for each application. Also unselct the Online Help & Tutorial.

After the installation is complete start the License application. Select the license file and write in the username.

You must change some settings in some applications. Start Altova UModel and XMLSpy. Goto Tools – Settings and unselect “Activate Scripting” or change the path.If you don’t do this you get error messages on start, because the example scripting files could not be found. These are stored under Documents on your local sequencer machine.

Note: First of all start all programs. After that you can copy the files under your local user account Documents\Altova to your Q-Drive.Then start Altova UModel and XMLSpy and change the path.

Go further in the sequencer assistent. At the shortcut window delete the License Manager and the Introduction. Then also remove the version in the .osd files name, if you want.

When you start the application Altova SchemaAgent to perform for sequencing make sure you close the local agent in the systray.

That should it be.

Print Friendly, PDF & Email