Same error by all tested users. These are all local users. Does an RD Gateway need to be used for local users? We are using trusted certificates. Thanks for your help! I have a test group of about 20 users that are all using RemoteApps on a single single server.
RemoteApps all work great for all the users. All the users are in one building, on one subnet, and the RemoteApp server is in a different subnet. All users have the problem. Thanks a lot! Sorry for the delay in responding. The first of the year is super busy for us. I found no events listed either in Server Manger or going into Event Viewer.
There were, of course, some events, but they all were verbose or information. That caused a few problems initially, but they were, I thought, all worked out. I noticed in the RDP file that the gatewayhostname was using. I tried setting gatewayhostname to domain. Do you know from where it gets the gatewayhostname? For consistency, I'd prefer that it also used the domain.
Our file type associations also have a problem when they try to open the file. When we double-click on a file from the client, the application opens, but then we receive an error that the file can't be opened. If that is the case, it makes sense that the file type associations don't work either.
Cloud services and managed services providers can benefit with our products. Please provide us with a brief description of the issue you're facing. One of our support agents will get back to you shortly.
This website uses cookies to improve user experience. By using our website you consent to all cookies in accordance with our Cookie Policy. Privacy details I accept. Open a ticket. Chat with us. Customer login. Forgot your password? UniTwain Universal Twain Driver. Server 3. Client 3. Latest Release - Major Update 3. BUG FIXES - Solved issue with automatic client update on older versions - Solved a problem when temp log files were created on the server - Fixed issue with Open locally for Mac clients - Fixed compatibility issue for older Mac clients - Solved problem with GDI error on redirected printer - Solved problem with offline printer redirection.
Show All Releases. Releases Major Release 3. Minor Release 3. Mac Client Release 1. Major Release 3. Server Release 2. Minor Release 2. Linux Client Release 2. Some of the files installed on a Fedora distribution are libraries which may provide functions to multiple applications. When an application requires a specific library, the package which contains that library is a dependency. To properly install a package, Fedora must first satisfy its dependencies.
The yum utility uses package dependency data to ensure that all of requirements for an application are met during installation.
It automatically installs the packages for any dependencies not already present on your system. If a new application has requirements that conflict with existing software, yum aborts without making any changes to your system. Understanding Package Names. Each package file has a long name that indicates several key pieces of information. For example, this is the full name of a tsclient package:.
Package name: tsclient. Package name with version and release numbers: tsclient Package name with hardware architecture: tsclient. For clarity, yum lists packages in the format name.
Repositories also commonly store packages in separate directories by architecture. In each case, the hardware architecture specified for the package is the minimum type of machine required to use the package. Some software may be optimized for particular types of Intel-compatible machine. Use the short name of the package for yum commands.
This causes yum to automatically select the most recent package in the repositories that matches the hardware architecture of your computer. Specify a package with other name formats to override the default behavior and force yum to use the package that matches that version or architecture.
Only override yum when you know that the default package selection has a bug or other fault that makes it unsuitable for installation. Package Names You may use any of the following formats to specify a package in a yum operation: name , name. Software Management Tools in Fedora Core. The yum utility is a complete software management system.
Fedora Core also includes several other applications that can supplement yum. On your desktop is an Alert Icon that keeps you informed about package updates. Until your system is updated the icon appears as a red circle with a flashing exclamation mark. The Alert Icon is part of the up2date application, which enables you to easily install system updates. Fedora Core also includes system-config-packages. Unlike up2date and yum , system-config-packages installs software packages from your Fedora Core installation discs only, and does not use repositories.
This application is used on systems that do not have a network connection. The rpm command-line utility has many functions for working with individual RPM packages. You may use it to manually install and remove packages from your system. If you install software with the rpm utility, you must manually check and install any dependencies.
For this reason, yum is the recommended method for installing software. Current Package Versions The up2date and yum utilities ensure that you have the most recent version of software packages. Other methods do not guarantee that the packages are current. Managing Software with yum. Use the yum utility to modify the software on your system in four ways:. To install new software from package repositories.
Installing Software from a Package File The yum commands shown in this section use repositories as package sources. To use yum , specify a function and one or more packages or package groups. Each section below gives some examples. For each operation, yum downloads the latest package information from the configured repositories.
If your system uses a slow network connection yum may require several seconds to download the repository indexes and the header files for each package. The yum utility searches these data files to determine the best set of actions to produce the required result, and displays the transaction for you to approve. The transaction may include the installation, update, or removal of additional packages, in order to resolve software dependencies.
This is an example of the transaction for installing tsclient :. Review the list of changes, and then press y to accept and begin the process. If you press N or Enter , yum does not download or change any packages. Package Versions The yum utility only displays and uses the newest version of each package, unless you specify an older version.
The yum utility also imports the repository public key if it is not already installed on the rpm keyring. This is an example of the public key import:. Check the public key, and then press y to import the key and authorize the key for use. If you press N or Enter , yum stops without installing any packages. To ensure that downloaded packages are genuine, yum verifies the digital signature of each package against the public key of the provider.
Once all of the packages required for the transaction are successfully downloaded and verified, yum applies them to your system. You may only read this file with root access. Downloads are Cached The yum utility keeps downloaded data files and packages for reuse. If you remove a package from the cache, you do not affect the copy of the software installed on your system. Installing New Software with yum.
To install the package tsclient , enter the command:. Enter the password for the root account when prompted. Updating Software with yum. To update the tsclient package to the latest version, type:.
New Software Versions Require Reloading If a piece of software is in use when you update it, the old version remains active until the application or service is restarted. Kernel updates take effect when you reboot the system. Removing Software with yum. To remove software, yum examines your system for both the specified software, and any software which claims it as a dependency. The transaction to remove the software deletes both the software and the dependencies.
To remove the tsclient package from your system, use the command:. Data and Configuration File Retention The removal process leaves user data in place but may remove configuration files in some cases.
If a package removal does not include the configuration file, and you reinstall the package later, it may reuse the old configuration file.
Searching for Packages with yum. Use the search features of yum to find software that is available from the configured repositories, or already installed on your system. Searches automatically include both installed and available packages. The format of the results depends upon the option. If the query produces no information, there are no packages matching the criteria. Searching by Package Name and Attributes. To search for a specific package by name, use the list function.
To search for the package tsclient , use the command:. To make your queries more precise, specify packages with a name that include other attributes, such as version or hardware architecture. To search for version 0. Valid Package Attributes Refer to Section 2. Advanced Searches. If you do not know the name of the package, use the search or provides options.
Alternatively, use wild cards or regular expressions with any yum search option to broaden the search critieria. The search option checks the names, descriptions, summaries and listed package maintainers of all of the available packages to find those that match. For example, to search for all packages that relate to PalmPilots, type:.
0コメント