The problem was traced to changes in the security settings of new servers at the NWS. The MetFetch program was changed to use a different method for downloading the observation data. The NWS data stream was on some occasions sending partial or incomplete forecast data which was not being detected and handled by MetFetch. Resolved an issue with MetFetch buttons not being visible at some screen settings. Added an option to the MetFetch user interface to allow the program to access an alternate source of forecast data.
The standard resolution option uses the operational service 3-hour temporal and 5 km spatial resolution while the high resolution option uses the experimental service 1-hour temporal and 2. Updated the MetFetch user interface to move the station database field from the main tab to the settings tab. That field is rarely changed and it makes more sense as a setting.
This website uses cookies to improve your experience. We'll assume you're ok with this, but you can opt-out if you wish. Accept Opt-Out Read More. Close Privacy Overview This website uses cookies to improve your experience while you navigate through the website. Out of these cookies, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website.
These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may have an effect on your browsing experience.
Necessary Necessary. Non-necessary Non-necessary. When you recover an Edge device, you can open the files you need without having to wait for the Edge device to finish downloading content from HCP Anywhere. Add up to 60 million files and folders to an Edge device.
You can now add up to 60 million files and folders to an Edge device. In previous releases, you could only add up to 20 million files and folders. You can now add up to 20 million files and folders to a filesystem. In previous releases, you could only add up to 1 million files and folders. You can now add up to 50 thousand files and folders to a directory.
In previous releases, you could only add up to 20 thousand files and folders. Support for Windows 10 on Edge. Support for Windows Server Support for the BlackBerry file transfer feature. Support for certificate-based authentication on mobile applications. In previous releases, certificate-based authentication was only supported on the User Portal , Windows desktop application, and Microsoft Outlook Add-in.
Configure mobile applications with registration keys. Note: These registration keys are only available for mobile applications distributed through MobileIron.
For more information, see Configuring silent registration. Create an Impressum. An Impressum is a summary of a company's contact and copyright information.
If you want to tell your users that your company is responsible for the content on the HCP Anywhere User Portal , you can create a customized hyperlink to your company's Impressum. Create a privacy policy. A privacy policy is a statement or legal document that discloses some or all of the ways a party or legal entity gathers, uses, discloses, and manages customer data and device information.
If you want to tell your customers how your company uses their data, you can create a customized hyperlink to your company's privacy policy. Several bug fixes.
These fixes include bug fixes to the virus scanning feature on the Management Console and the Edge application. For more information, see Issues resolved in release 4. Support for Swedish. HCP Anywhere now supports up to one million files and folders for each filesystem. In previous releases, HCP Anywhere only supported , files and folders for each filesystem. This change only applies to file sync and share and Edge devices.
This update does not apply to backup filesystems. Users can now share up to 60 personal folders on HCP Anywhere. In previous releases, users could only share up to 30 personal folders. Users can now join up to team folders and personal folders on HCP Anywhere. In previous releases, users could only join up to team folders and personal folders. Modified OVF template size to support up to users. This new OVF template is ideal if you are looking to set up HCP Anywhere for a smaller number of users, as you will no longer have to use the larger disk size.
You can also increase the disk size to support a larger configuration. Support for 20 million files per Edge device. Each Edge device supports up to 20 million files, including folders. Support for one million files per Edge folder. Each Edge folder now supports up to one million files, including folders. In previous releases, each Edge folder only supported , files. Support for several Windows Server features on Edge. Important: DFS-R doesn't work with stubbed files. Customize Edge database location to optimize space and performance.
Share data from one Edge device to another with the new mirror folders feature. With this feature, you can seamlessly distribute data from one Edge device to another using HCP Anywhere 's centralized device management. Mirroring folders also ensures that any changes made to the Edge folder are reflected across all the Windows Servers that contain that folder.
Create a cookies policy notice. If you want to tell users how HCP Anywhere uses cookies, you can create a cookies policy notice that's customized for your company. A cookies policy notice can even include a link to your company's cookies policy.
Support for smart card authentication. Certificate-based authentication uses the digital certificate stored on the smart card to identify a user rather than his or her username and password.
This tab allows you to:. These fixes include a new version of libcurl to address a crash condition on the Mac client, a new version of Fedora OS to address Java security, Spectre, and Meltdown vulnerabilities, kernel updates to prevent DoS attacks, and additional bug fixes to centralized Device Management and the HCP Anywhere Edge client. Centralized device management.
This release introduces centralized device management for all your HCP Anywhere devices. This management includes:. Before this release, you could manage your HCP Anywhere devices on a per-user basis but not from a central location. Move data to the cloud with the new Edge application.
Edge is a software-only solution designed to take the data on your Windows Servers network-attached storage and back it up to HCP Anywhere cloud storage. Edge is meant to be deployed on all the Windows Severs in your organization, taking the NAS data that is currently spread across your company and bringing it into HCP Anywhere where it can be managed from a single location.
The new Edge application is the perfect way to:. Support for ESXi 6. View last 25 uploads on desktop application. On the HCP Anywhere desktop application, you can now view the last 25 uploads that the desktop application performed. Until now, you could only view the last 10 uploads. These fixes include a new OpenSSL version to address a CBC-mode cipher vulnerability, better log handling for the desktop applications, and improved integration with Trend Micro for virus scanning.
Dropping support for HDI device management. Important: Do not upgrade to release 4. You can upgrade an HCP Anywhere system to release 4. To upgrade from a release earlier than 2. You cannot downgrade HCP Anywhere to a previous release.
Important: If you are using a single-node system that is running on release 4. If any certificates are invalid, desktop and mobile applications will be unable to connect to the system. If a user identified the HCP Anywhere system by IP address or by only the first part of the fully qualified domain name when registering the desktop application, the desktop application will be unable to connect to HCP Anywhere after the upgrade.
In this case, the user needs to reconfigure the application to use the fully qualified domain name for the HCP Anywhere system.
Upload and apply the upgrade package through the Management Console. After you upload the upgrade package, you can view a list of all features included in the upgrade package.
This section describes the major impacts of upgrading HCP Anywhere from release 3. Upgrading to version 4. For example, during an upgrade:.
Beginning in release 4. This section describes the major impacts of upgrading HCP Anywhere from release 2. The impact of upgrading from 2. Upgrading to release 4. Although more secure, enforcing TLS 1. Specifically, enforcing TLS 1. On Windows 8. Important: If TLS 1. If your users have any of these applications, you can allow them to connect those applications to HCP Anywhere by doing one of these:. Enable TLS 1. However, you are now using TLS 1. If you use a network appliance for example, a load balancer to direct traffic to HCP Anywhere, you can:.
Verify that Enable TLS v1. Verify that the network appliance supports TLS 1. Unencrypt SSL traffic at the network appliance. This option enables TLS 1. This option only applies to the:. Applying update KB to your Windows 7 machines. Setting the DefaultSecureProtocols registry key to in the following registry paths:.
Setting the SecureProtocols registry key to A80 in the following registry paths:. Note: You can also prompt your users to upgrade their HCP Anywhere applications to the current release.
In release 3. For any User Portal pages you have bookmarked, simply re-bookmark the pages in the new User Portal that correspond to your old bookmarks. File synchronization and sharing. Maximum number of users without a file sync and share license. Maximum number of registered users 1. Maximum file size 2. The default is 10 GB. This number is configurable using registry keys. The maximum number of registered users your HCP Anywhere system can support is limited by your file sync and share license.
User Portal, desktop application, and Outlook Add-in languages:. Other ESXi versions may work but have not been formally tested. Each virtual machine requires a certain number of CPUs and a certain amount of memory. These amounts are determined by both the number of users the system can support and the number of nodes in the system:. Note: If you plan to use an HCP Anywhere Edge application with your system, configure your single-node system or multi-node system to use 16 CPU cores and GB of storage regardless of the number of users in the system.
The Management Console and User Portal support these web browsers:. The security level cannot be set to High. Note: On macOS This is the default file system format for macOS On macOS For the Outlook Add-in to be installed, these programs need to be installed on the Windows machine:. NET version 4. Edge Windows has been qualified for use with these operating systems:.
Edge Linux has been qualified for use with these operating systems:. HCP Anywhere is qualified for use with these platforms for distributing the desktop applications:. If the desktop application is not installed on the master VM image, when a user installs the desktop application on a VM, the memory of that VM fills, causing the VM to become inaccessible. You can integrate the following third-party applications with HCP Anywhere.
Note: By default, HCP Anywhere attempts to connect to every domain in the forest, except for domains in the forest with international names. HCP Anywhere does not support domains with international names. HCP Anywhere does not synchronize files in which viruses are detected.
Note: HCP Anywhere is platform agnostic. HCP Anywhere 4. Users of HCP Anywhere 4. To do this:. From the Apple menu, select System Preferences. From the System Preferences window, select Extensions. In the Extensions window, select All or Finder Extensions on the left pane. Select AW Finder Extensions. Then follow the steps above. The table below lists the issues that have been resolved in release 4.
The issues are listed in order by reference number. Fix: This issue is resolved. The error notification is dismissed for subsequent uploads. Pressing Enter or Return initiates login. Files in the folders AppData and ProgramData are synchronized to the HCP Anywhere Windows server even though they aren't defined by the user or administrator for protection.
Fix: Files are returned to their correct state following a POD recovery procedure. Updating the HCP Anywhere 4. When the connection to HCP is temporarily interrupted, the message for the notification incorrectly indicates that there is a failure. Fix: The notification message now indicates that there was only an interruption to HCP connectivity. Processes on the HCP Anywhere Linux client might attempt to hydrate files at the same time, causing the files to double in size.
When a user tries to register the Android application with a certificate that was signed by a certificate authority CA that is not one of the standardized Android-trusted system CAs, the application rejects the certificate if the application is running on Android 7. Fix: The Android application now accepts certificates that have been signed by a user-provided CA if the application is running on Android 7. When an administrator changes a file with the compression attribute on an Edge device that has been mirrored to another server, the mirrored Edge device doesn't pull down the compression attribute of the file when the mirrored Edge device syncs with the HCP Anywhere server.
Fix: The mirrored Edge devices pulls down the compression attribute of the original file when it syncs with the HCP Anywhere server. However, the REST endpoint for that authentication provider remains active. All enabled forms of authentication appear to the user, even if the associated authentication provider AD or SAML is not part of a profile. Fix: If an authentication provider is not in any profile, its associated forms of authentication are no longer displayed in the HCP Anywhere User Portal or applications.
HCP Anywhere uses a version of Java that contains several security vulnerabilities. Fix: HCP Anywhere uses a version of Java that is no longer affected by these security vulnerabilities.
Each field contains information about the devices registered with the HCP Anywhere system, such as the device status, operating system of the device, and last time the device communicated with HCP Anywhere.
When a field is toggled on, it displays as one of the columns on the page. You can toggle on and off fields as needed. However, whenever the Device Management page is refreshed, the page resets to its default fields. Fix: The Toggle fields value persists when refreshing or navigating back to the Device Management page on the browser. When the Edge device on a server shuts down and a user renames a file that the device is monitoring from the User Portal , Edge pushes the original file and receives the renamed file from HCP Anywhere after the administrator performs a POD recovery.
When users access the HCP Anywhere server, they see both the renamed file and the original file. When a user is added to a group in Active Directory that has already been added to an Edge folder, Edge sends the user an invitation to the folder instead of adding the user to the folder.
Fix: Edge adds the user to the folder after the administrator syncs the membership for the Active Directory group in the management portal. When an administrator invites two AD groups with different permissions to the same folder, HCP Anywhere alternates permissions for users in both groups.
For example, if group 1 is invited to a folder as Collaborator and group 2 is invited to the folder as Viewer and user 1 is in both folders, HCP Anywhere changes user 1 from Collaborator to Viewer every 24 hours. Fix: HCP Anywhere no longer alternates permissions for these users. When users attempt to upload files on any application, HCP Anywhere fails to upload those files.
When a user clicks on File sync status in the HCP Anywhere dashboard of the desktop application, the icons that appear on each row of the Recently Completed and Issues tables are individually generated, causing the desktop application to use a large amount of memory.
Fix: The HCP Anywhere desktop application uses one icon for each option and repeats that icon throughout both the Recently Completed and Issues tables, reducing the amount of memory used. The table below lists previously identified issues that were resolved in release 4.
When the desktop application cannot download a file from HCP Anywhere , the file becomes a remote unsyncable.
Typically, this only occurs when the hard disk drive on the computer reaches its capacity. However, even if you resolve the issue that caused a file to become a remote unsyncable, the desktop application does not download the remote unsyncable from HCP Anywhere. Fix: The desktop application now attempts to download all its remote unsyncables once a day. The HCP Anywhere system incorrectly restarts several of its resources when the HCP system it is using for storage takes longer than five minutes to respond to certain management API requests.
This can cause the HCP Anywhere system to become unavailable. Links on the Files Activity page in the User Portal can redirect you to a file version that has already been pruned from the system, resulting in a Folder Not Found error. Fix: When a file version is pruned from the system, the link for that file version on the Files Activity page is removed.
The activity events in the User Portal display in English even when the web browser is set to display text in another of the supported HCP Anywhere languages. Fix: If the language is supported by HCP Anywhere , the activity events in the User Portal now correctly display in the language set in the browser. Attempting to join an AD computer account to HCP Anywhere results in a pre-authentication error when a user exists in the same domain as the computer account and the user has a username that is:.
Fix: HCP Anywhere can now successfully join an AD computer account to itself even when a user exists with the same username as the computer account. The desktop application only stores 50 MB of logs at any given time. Once the desktop application reaches 50 MB of logs, the oldest available log is deleted from the computer.
Fix: The desktop application now keeps MB of logs on its computer, increasing the ability for the HCP Anywhere support team to troubleshoot desktop application issues. When the authentication token for a desktop application expires, the desktop application displays an authentication prompt.
However, the link fails to open a web browser. Fix: The link in the desktop application authentication prompt now correctly opens a web browser to the login page of your SAML provider. When a user with the Manager role is removed from a team folder , any AD groups that Manager invited to the folder are also remove from the folder. For those groups to regain access to the team folder , another Manager must reinvite those groups to the folder.
Fix: When a Manager is removed from a team folder , the groups the Manager invited to the folder are no longer removed from the folder. When the desktop application contains a large number of unsyncable files, opening the desktop application dashboard can cause a memory overflow on the computer, which causes the desktop application to shut down.
Fix: The desktop application dashboard now only displays unsyncable files at one time in the desktop application dashboard. This prevents the desktop application from causing a memory overflow on the computer. When an HCP Anywhere system is upgraded from a 2. Fix: The desktop application no longer deletes any proxy server that was entered when it was registered.
Each time the desktop application starts, the tray icon looks like this and reports a connection error for several minutes before reporting that it is up-to-date. Fix: The tray icon no longer incorrectly reports a connection error when the desktop application starts. Each time a file is updated, a new file version is created for that file. Fix: File versions created through public links now correctly appear in the File history window, which allows you to restore a file to that file version.
Fix: If you set the number of entries to return to a number that is too large, the Edge CLI gives you an error message and Edge keeps running. The table below lists known HCP Anywhere issues for which workarounds exist. You can lower a user's storage quota to a size that's smaller than the amount of data that the user has already stored in HCP Anywhere. This causes the user to be over the user's storage quota. In this situation, the user cannot add any new files to HCP Anywhere. While over the storage quota, if the user moves a file from one folder in the HCP Anywhere folder to another folder within the HCP Anywhere folder , the file is deleted from the HCP Anywhere system and from the user's other devices but not from the computer on which the file was moved.
This happens because HCP Anywhere synchronizes the removal of the file from the original location but does not synchronize the addition of the file to its new location. Workaround : To be able to move files, the user should do one of these:. The following scenario describes what happens when a user adds two files with the same name from two different HCP Anywhere applications, where one file can be synced and the other cannot:. On another device, the user adds a file that has the same name as the unsyncable file.
This second file is of a type that HCP Anywhere can synchronize. The file is synchronized to the user's devices, except for the computer that contains the unsyncable file. The user deletes the unsyncable file from the HCP Anywhere folder.
The file from the second application is not automatically synchronized to the computer from which the unsyncable file with the same name was deleted. Workaround: Edit or rename the syncable file. This causes the file to be synchronized to the computer from which the unsyncable file was deleted. However, this alert is generated by only one node in the system.
This means that depending on the node to which your Management Console session is connected, you may or may not see the alert. Workaround: Check the Overview page alerts for both nodes.
To view the file sync and share Overview page, click File Sync and Share. Log out of the Management Console.
When an HCP Anywhere system is recovered after a serious hardware failure, a user's desktop applications may be unable to synchronize files with the system. Workaround: To resume file synchronization, restart the desktop application.
After creating an exported filesystem, if you import that filesystem before its data has been has migrated to HCP, users will be unable to view any of the data in the imported filesystem. In this case, the Events tab for the device with the imported filesystem displays these errors:. Workaround: Verify that the exported filesystem has migrated its data before trying to import the filesystem. To do this, check Health Report tab for the device on which you created the exported filesystem.
If you've already created the imported filesystem, delete it. Then import the exported filesystem again after verifying that the data has been migrated.
0コメント