• No results found

Application Manager 8 FR7 SP1

N/A
N/A
Protected

Academic year: 2021

Share "Application Manager 8 FR7 SP1"

Copied!
5
0
0

Loading.... (view fulltext now)

Full text

(1)

Application Manager 8 FR7 SP1

Release Notes

AppSense Application Manager 8 FR7 Service Pack 1 is an update to Application Manager 8 FR7 (Build Version 8.7.126.0) which is a pre-requisite for this Service Pack. Please refer to the AM 8 FR7 release notes if you are installing AM for the first time.

• Components in this Release

• Service Pack Installation

• Bugs Fixed

• Known Issues and Limitations

Components in this Release

Component Version File Name

Agent 8.7.131.0 ApplicationManagerAgent32.msp

ApplicationManagerAgent64.msp

Analysis Service 8.7.131.0 ApplicationManagerAnalysisService32.msp ApplicationManagerAnalysisService64.msp

Console 8.7.131.0 ApplicationManagerConsole32.msp

ApplicationManagerConsole64.msp

Documentation 8.7.30.0 ApplicationManagerDocumentation32.msi

ApplicationManagerDocumentation64.msi

(2)

Application Manager 8 FR7 SP1 - Release Notes

Service Pack Installation

Service Packs are delivered as MSP files, commonly known as patch files, and contain updates to the original application. Patches can be viewed inside the Windows Control Panel (Control Panel >

Programs > Programs and Features > Installed Updates).

How to install a Service Pack

Service Packs (MSPs) can be installed or deployed using the same technology and techniques that are used to install MSIs. Both Microsoft

®

System Center and the AppSense Management Center FR 4 and later are capable of deploying MSPs. If neither of these products is available for Service Pack deployment and installation, then it is also possible to install the Service Pack using MSIExec.

To just install the Service Pack run the following command:

e.g. msiexec.exe /p agentpatchfile.msp

To install the Service Pack and the base version simultaneously, run the following command:

e.g. msiexec.exe /i agentbasefile.msi PATCH=c:\fullpath\agentpatchfile.msp

System restarts

The use of MSPs reduces the need for restarts but doesn’t completely avoid them. If a file is in use during the install then a restart prompt will be shown.

Note

If you are deploying the patch via the CCA, at least one restart is required.

Rollback procedure

If for any reason the Service Pack needs to be uninstalled, this can be accomplished from inside the Windows Control Panel (Control Panel > Programs > Programs and Features > Installed Updates) or using the AppSense Management Center FR4 (or higher) for agent rollback. If a Service Pack is uninstalled the installation will revert back to the previous latest build, be that a hotfix, previous Service Pack or the base version.

Manually Adding the Service Pack Console to the Management Center Download Page When the service pack is manually applied, the updated console is not automatically added to the Management Center Download Page. Until it is added, the download page will continue to provide access to the base version of the console.

To add the service pack console, follow these steps on the Management Server:

• Create a folder for the build number (for example 8.7.300.0) at the following location:

• C:\Program Files\AppSense\Management Center\Server\Web Site\Downloads\Application Manager

• Copy ApplicationManagerConsole32.msp and ApplicationManagerConsole64.msp to the new folder

Note

This will automatically occur if the installation is performed by the Suite Installer.

(3)

Application Manager 8 FR7 SP1 - Release Notes

Bugs Fixed

Support Calls

The following support calls have been resolved in this release:

TFS ID Title Details

38931 AM intermittently uses incorrect user environment block

User variables can expand incorrectly, causing accessible items based on their values to fail to match the rule and be blocked.

38935 Scripted Rules are incorrectly evaluated against Application Termination on AM Agent restart

Restarting the Application Manager service while users are logged on to a terminal server will cause every application of every user that is prohibited by default but allowed by a scripted rule to be

terminated (event #9017)

38975 Trusted Vendor check fails to get certificate from signed MSI

Customer has been trying to apply a trusted vendor rule (Certificate) for MSI files, however, even after manually importing the certificate in the console, the AM Agent fails to read the certificate returning "error 7"

38976 AM console fails to read certificate from signed MSI/MSP files

When the AM console attempts to read the digital certificate from signed MSI/MSP files, a message box is returned stating 'The selected file has not been signed'

38979 File ownership changed to user that has no access to write

Customer is using a universal print driver, UniPrint, that when starting up during logon performs a

"create file" action but receives an "access denied"

result as the file in question is within the Program Files folder.

42101 Typo in Application Manager interface

In the Trusted Owner's ribbon button the term 'Security Principles' is used. The correct term should be 'Security Principals'.

44515 AM Rules Analyzer saves XML as UTF-8 but sets Encoding as UTF- 16

When exporting a Rules Analyzer log from the Application Manager console, the file is saved in UTF-8, however, the opening XML string states: xml version="1.0" encoding="utf-16"

44646 Saving a Rules Analyzer log with an invalid filename truncates text rather than prompt

When saving (exporting) a Rules Analyzer log, if invalid characters, such as a colon (:) are added to the filename, the file is saved with all text before the last invalid character removed.

46358 AM Extract self-extracting ZIP files doesn't work with all software vendors

Some self-extracting zip files are denied despite the option to 'Extract self-extracting ZIP files' being enabled.

46733 Scroll Bar issues with AM Console 8 FR6

Customer has a large number of User Rights defined. When the AM window is too small to display them either no scroll bar displays, or when it does it only moves the list up or down for one or two items, not all of them.

48867 Run as administrator not restored after uninstall of AM

When removing AM from a computer, any user who

had an account being managed by AM can no

longer see the "Run as Administrator" option when

they right click.

(4)

Application Manager 8 FR7 SP1 - Release Notes

TFS ID Title Details

49644 Self-Authorize and Self Elevate - Self Elevate message box is not shown after Self Authorization

Customer has self-authorized a group and has also enabled self-elevation for all files for the same group. When they launch a non-trusted owned application they get the self-auth (allow for this session or permanently) prompt, but then they get a UAC prompt.

51035 Typo in AM8 FR7 console - Edit 'aconfiguration' (no space)

In the Application Manager 8 FR7 Console, when you click on Open > Configuration from Group Policy, there is a space missing between "a" and

"configuration"

55707 ANAC Hostname rules do not allow for multiple hostnames resolving to same IP Address

When attempting to deny or allow multiple

hostnames within ANAC, if multiple hosts resolve to the same IP (typically multiple intranet pages hosted on the same webserver), a single allowed hostname for that IP Address will cause all hostnames on the same IP Address to be allowed.

56748 AM Agent paged pool memory leak in Se pool tag in mini filter driver

Following an upgrade to AM8 FR7 paged pool memory usage of the AMAgent increases over time.

62383 AM URM not adding or removing non-admin groups

In order for the 'Install as Trusted Owner' option to work correctly in the agent, the URM policy associated with the URM item must have BUILTIN\Administrators group membership, therefore, if the URM policy associated with the URM item doesn't have BUILTIN\Administrators group membership, a message will appear next to the 'Install as Trusted Owner' checkbox to prompt you to add the necessary group membership to the policy.

Internal Bugs

The following internally raised bugs have also been resolved in this release:

TFS ID Title Details

53378 ANAC: Host names not resolved on network reconnect

If there is no network connection present when the configuration is saved, host names are not resolved. This then means that if the host is an accessible item, and its IP is prohibited, the host is still seen as prohibited.

53397 Allowing prohibited ANAC item does not work when Regular expression is turned on

If the same URL is added to both prohibited and accessible items, using a regular expression, then the URL is incorrectly prohibited

53408 AM Console - Add Prohibited URL - inconsistency between versions, not accepting valid URL

The AM console no longer accepts URLs using the ASCII Compatible Encoding (ACE) prefix "xn--"

53409 ANAC Rules not applied in IE11 on Win8.1, 2012r2 and Windows 7

URLs configured as prohibited can still be browsed using IE11 on Windows 7, 8 and Server 2012R2

60970 URM Console: Drag & Drop not working when adding application group to User Rights rules node

Neither the rule items contained in, nor the

application group itself, are added to the User

Rights elevation/self-elevation views, after drag and

drop.

(5)

Application Manager 8 FR7 SP1 - Release Notes

Known Issues and Limitations

The known issues and limitations are now detailed on myAppSense. Navigate to

https://www.myappsense.com/, log in and select Software > DesktopNow > Application Manager

> AM Known Issues.

References

Related documents