VMware THINAPP 4.6 - MIGRATING APPLICATIONS TECHNICAL NOTE Manuale Utente Pagina 62

  • Scaricare
  • Aggiungi ai miei manuali
  • Stampa
  • Pagina
    / 64
  • Indice
  • SEGNALIBRI
  • Valutato. / 5. Basato su recensioni clienti
Vedere la pagina 61
AdminStudio 2013 Release Notes ADM-2013-RN5 62
Release Notes
IOA-000075351 When a MSI package that has a MST and a MSP is imported to a Software-
Repository-enabled Application Catalog, the MSI, MST, and MSP are copied to
the
Patches folder in the Software Repository, but only the MSI is copied to the
Packages folder in the Software Repository. Then, when executing tests on this
package, tests are skipped because the transform file is missing.
IOA-000075439 If the default Detection Method entries are deleted, and the user goes to
another view and then returns to the Detection Methods tab, a .NET
Framework error appears. The Detection Methods tab cannot be accessed
again. The only way to fix this issue is to delete the package and reimport.
IOA-000075681 The Microsoft App-V Sequencer sets application binaries to be Application
Data and does not set the Application Data or User Data flag for most of the
rest of the files (except for a few extensions that might be set to User Data).
However, AdminStudio sets most files to be Application Data. This causes a
problem in multi-user scenarios because changes made to most of the files by
one user will be present for the other users.
IOA-000075743 Cannot import packages from SCCM 2007 into an Application Catalog when
using Windows Authentication.
IOA-000075858 The Repackager Installation Monitoring method fails to capture
XCopyFile
calls in a batch file correctly.
IOA-000076029 Request to update the Creating Customizable Reports help topic to explain how
to display and group custom reports in the Report Center ribbon.
IOA-000076418 If you attempt to import a merge module that exceeds 1040 characters,
Application Manager hangs without adding any merge modules to the list.
IOA-000076488 During the import process, both the application name and the deployment type
name are based off of the name of the executable specified during import using
Invoke-ASPublish. Would like to be able to rename an existing deployment
type during import using the
Set-ASProperty API command.
IOA-000076489 You can set defaults for newly imported applications on the Import Options >
Application Model Defaults of the Options dialog box. A couple of these
settings are not being applied correctly, such as Application Task Sequence
and Deployment option when client is on slow network.
IOA-000077141 When users create custom ACE rules, and then check applications or
packages against these ACE rules, the results of those tests do not show up in
the Test Center.
IOA-000077411 When repackaging a Windows Installer package using Repackager or
Automated Application Converter, the resultant App-V package will fail to
launch due to an incorrect
WORKINGDIR value in the .osd file.
IOA-000077541 Request to provide operating system compatibility testing for App-V packages.
Issue Number Issue Summary
Vedere la pagina 61
1 2 ... 57 58 59 60 61 62 63 64

Commenti su questo manuale

Nessun commento