What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange. All rights reserved. Covered by US Patent. Come for the solution, stay for everything else. Welcome to our community! Hello, I recently took over a system that includes a terminal server running on Windows Server I need to upgrade software on it quickbooks for users to be able to access but I have little experience with Terminal Server.
I have done some research and found these steps on how to install software, but wanted to run it past the community to see if this is correct. Is there anything else I need to be concerned with, or is there a different, easier, better way? Log on to the terminal server as an administrator and close all applications. To open a command prompt, click Start, point to All programs, point to Accessories, and then click Command prompt.
Subsequently, whenever a user launches an application, the server checks for the proper registry entries in the real HKLM and the user's HKCU and compares those to the entries that the system previously recorded from the software installation.
Ordinarily, a Terminal Server operates in "execute mode. When adding new software this way, you're given the choice as to whether you are installing the software for the current user only causing the server to remain in execute mode or for any user that logs on temporarily setting the server into install mode.
Install mode and execute mode work the same for both Terminal Services on Windows and Windows Both versions of Windows contain logic that attempts to "force" you to remember to use install mode for installing applications. If you try to run a program like setup. This is a nice feature, because there were many occasions with early versions of Terminal Server when people installed applications only to realize later that they forgot to place the server into "install mode.
Some applications need to wait for a reboot in order to complete certain installation. Any program listed in this key is executed one time after the server is rebooted. Terminal Server is smart enough to use install mode for all entries that are listed in the "runonce" key, even after a reboot. Dealing with configuration files introduces a whole other set of issues. Generally, bit and even some bit applications read a user's settings from some type of configuration files.
The most common files are. INI files, but. CFG and. DAT are not unheard of. The problem resides not with the files themselves but with how the applications attempt to locate them. If an application was hard-coded to look for its. INI file can be a problem. Home folders are discussed in Chapter 6. With new applications, at worst you would have to copy the required INI files to the user's home directory.
INI, you may be out of luck. Microsoft made several changes to the registry in Windows Server Technically these changes were introduced in Windows XP. For example, the Windows registry has no size limit and doesn't consume nearly as much memory, but those attributes are more relevant to server sizing. We'll cover them in Chapter Relevant here is the fact that Windows changes the way "classes" are managed in the registry.
In the Windows registry, "classes" and their associated "class IDs" refer the filename associations and data associated with COM objects. Quite simply, it means that with Terminal Server , individual users can each have their own class settings. This is important for two reasons:. Now you can begin the actual process of installing your applications. Although installing an application on a Terminal Server is similar to installing an application on any standard workstation, adhering to some best practices ensures your application is installed properly:.
Many applications used in Terminal Server environments have "workstation" and "server" install modes. These applications have two components: the server component and the workstation component. Since your Terminal Servers are essentially gigantic shared workstations, you need to perform a "standard" workstation install on your servers. If there's ever a situation in which you don't know which installation options to choose for an application when you're installing it on a Terminal Server, choose the options that you would use if you were installing the application onto a standard user's workstation.
For example, some applications have a "thin client" mode of installation. At first this might seem like the perfect installation option to use on a Terminal Server. But for a lot of applications the "thin client" mode of installation indicates that the bulk of the application's client files have been preinstalled onto a file share somewhere, and that the local workstation install only needs to contain user configuration information.
If your application offers it, there's nothing wrong with using this type of "thin client" installation option on your Terminal Server, but you shouldn't automatically use it just because you're using Terminal Services. Again, the bottom line is that you should install your application with the same options as if you were performing a standard end user workstation install.
Microsoft well, technically Citrix had to do quite a bit of engineering and redeveloping of many Windows components to allow multiple users to be simultaneously logged on "locally" to servers in Terminal Server environments. Even with the work that was done to the OS, the vendors who create software applications don't always take Terminal Server environments into consideration when writing their applications.
You will get a window that asks for the name of the machine to which you would like to connect. If you provide a machine name, the client will connect to that machine and prompt you for login credentials, after which you'll get a desktop, unless the administrator has created a different profile for you. Click the Options button to expand this window beyond just the server name. You'll see five tabs:. The General tab, shown in Figure D , lets you provide the Terminal Services server name along with an appropriate user name, password, and domain.
You can also opt to save the password so you are automatically connected to the Terminal Services server. Use the Display tab, shown in Figure E , to determine the resolution and number of colors that will be used for the connection.
The more colors you use and the bigger the screen, the more data that has to be sent over the network. For slow connections, use lower settings. You continue to make use of certain local devices from inside your remote connection by enabling or disabling options on the Local Resources tab, shown in Figure F.
For example, if you want to have access to your local floppy drive from inside the connection, click the Disk Drives option on this tab. The Programs tab, shown in Figure G , provides you with the ability to start a specific program upon successful connection to a Terminal Services server. Just specify the path to the program and, optionally, a starting folder. Terminal services connection performance is somewhat dependent on which features you enable on the Experience tab, shown in Figure H.
For slower connections and slower Terminal Services servers, disable some of these options. If you have sufficient bandwidth and faster servers, you can enable these options. When you're done, you can save this information to a shortcut on your desktop by clicking the Save As button on the General tab.
When you're ready to start the program, double-click the shortcut on the desktop, or press the Connect button from the shortcut. If you have opted to share local disk drives, you'll get a warning indicating that this is a potential security problem unless you fully trust the computer.
I configured it with my username and password, so I just need to double-click the shortcut and Paint Shop Pro loads. The Terminal Services Manager application is the place where you manage connections to the server. When you initially open Terminal Services Manager Start Administrative Tools Terminal Services Manager , and select your server, you're shown a list of all the server's active connections, as shown in Figure J. Notice that the Administrator account at the top of the list is shown in green with a session of Console listed.
This means exactly what it says—the Administrator is currently logged in to the physical server console. Beneath that connection is an RDP connection to the terminal server that is currently active.
Right-click the connection to get a menu of options, including an option to disconnect the user immediately, send the user a message, reset a connection, get the status of the connection, or log the user off. In the left-hand pane, click an active RDP connection to see a list of processes in use by that particular connection.
0コメント