Some applications, like the Office 365 Suite, can be sequenced using an accelerator. The method for sequencing an application is different depending on the app. An application is sequenced and delivered as a virtual app to endpoints. I checked the package folder and there was a Test.msi available.App-V helps organizations deliver applications on-demand. Pressing Enter resulted in the installation of the English 32-bit Language Pack.Īfter building a new package, or editing an old package, and choosing File / Save, the error no longer occurred. enus) and BB for the OS bit version (32-bit= 86, 64-bit= 64) for the version you want to use. Replace XXXX with the language code (i.e. So I opened up a command prompt and, in my case, typed C:\extracted\appv_sequencer_LP_XXXX_xBB.msi ACCEPTEULA=1. Simply double clicking them would have been too easy though. Of course they had to be somewhere and there they are the language packs. Having saved the setup file to C:\temp, I opened up a command prompt and entered c:\temp\appv_sequencer_setup.exe /layout /layoutdir=”c:\extracted”. “It also extracts the Windows Installer (.msi) and script files to a folder without installing App-V 5.0.” Interesting. The /LAYOUT parameter however caught my eye. This Technet article however shows that there no options to set the language while doing an unattended installation. Knowing that the solution had to be in some sort of language setting, I decided to explore the language options of the appv_sequencer_setup.exe. Upon arrival I immediately noticed there was no EN-US folder, only a nl-nl folder. I opened up Explorer went to C:\Program Files\Microsoft Application Virtualization\Sequencer. The error is, of course, in Dutch due to the Dutch MUI being installed through MDT. I opened the error with Event ID 5013 to view its details. The log can be found in Applications and Services Logs / Microsoft / AppV / Sequencer. A report.xml and the MSI were missing.Īs hinted by the error message, I looked in the Event Viewer. This also resulted, as was to be expected, in an incomplete package folder. The moment I clicked Save, an error popped up saying that the MSI couldn’t be generated. That is until I made the first package on the machine. We experienced a problem with the App-V sequencer which was caused by the MUI language pack.Īfter the installation of the new sequencer everything seemed to work fine. All client types are installed unattended, including the App-V sequencer. We installed an English Windows with a Dutch MUI pack. For a customer we’re creating a Windows 7 environment, using App-V 5.0 SP1 for application virtualization.
0 kommentar(er)
