Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Horizon 7.5 JMP server installation may write SQL username and password to a log file (56360)

Last Updated: 7/31/2018Categories: InformationalTotal Views: 4097Language:
Chinese (Simplified)JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Purpose

The purpose of this article is to respond to a report that username and password is being written to a log file during Horizon 7.5 JMP server installation. The new JMP (Just-in-Time Management Platform) Integrated Workflow features in Horizon Console allow users to easily define and manage desktop workspaces that consist of a desktop operating system, applications, and settings. To enable this workflow users need to install Horizon JMP server which orchestrates communications across various Horizon components such as Horizon View, App Volumes and User Environment Manager.

Background

As part of Horizon 7.5 JMP server installation, Node.js package manager and package launcher (npm) is used to configure a component service and perform certain database actions. During installation sequence, user can either choose Windows Authentication or SQL authentication for SQL server connection. Choosing Windows authentication is the preferred industry practice. In two specific instances, the credentials are written to a log file.

Issues

Issue A
After installation of the Horizon 7.5 JMP Server, command line arguments passed to npm which include the DB credentials are automatically logged by the npm caching module at  %USERPROFILE%\Appdata\Roaming\npm-cache\_logs folder if:

SQL authentication is chosen
AND

The installation fails

Issue B
Optional log files (xms_install.log, uem_install.log) are generated in the Log_Folder_Path that contain all msi properties including the SQL authentication credentials provided as part of the installation if:

SQL authentication is chosen
AND

The installer is run from a command prompt with /log:“Log_Folder_Path”

Mitigating Factors

If user installs JMP server without using command line options and if installation completes successfully, neither Issue A nor Issue B will occur.

If user chooses Windows Authentication for SQL connection during JMP server installation, neither Issue A nor Issue B will occur. This is the recommended mechanism of setting up such services. For more information, see Authentication in SQL Server.

The log file in Issue A is in the profile folder of the user who performed the installation and provided the password. This is most likely an admin user. Access to this file on the local machine would only be available to someone who has local admin privileges on the local machine.

The log files xms_install.log and uem_install.log are only generated if installation is performed from command line using the /Log option. User performing the installation has control of the location where this is created.

Resolution

For new installs:

The Horizon 7.5 JMP Server installer has been updated and is now available on the download site. The updated installer has a Product Version of 1.0.1.529 which can be confirmed in the Details tab of File Properties.
The updated installer restricts npm module from creating the log file containing SQL DB credentials at  %USERPROFILE%\Appdata\Roaming\npm-cache\_logs folder. This removes issue A.
If installation is done using the command line option of /log:“Log_Folder_Path”, the updated installer has also been modified so that msi properties containing the SQL  DB credentials are no longer written to log files xms_install.log and uem_install.log. This removes issue B.

For existing users:

Check for any files in %USERPROFILE%\Appdata\Roaming\npm-cache\_logs folder of the user account that was used to perform the installation. Delete files that are in this folder.

Check for any files in Log_Folder_Path that may have been used while installing JMP server using the command line option of /log: :“Log_Folder_Path”. Delete all the files in that folder.

Check for any files named uem_install.log and xms_install.log in %temp% folder of the user account that was used to perform the installation. Delete those files.

You may also choose to update the password of the login account for SQL Authentication that was provided during JMP Server installation. If the password is changed, the JMP Server services will have to be updated to use the new password. For more information, see the VMware Horizon JMP Server Installation and Setup Guide.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Horizon

Related Versions:

VMware Horizon 7 version 7.5.x

VMware Horizon 7

Take Our Survey

Support Assistant