![]() ![]() ![]() | ![]() | ![]() | |
![]() | |||
![]() | |||
![]() | ![]() | ![]() | ![]() |
![]() | ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() | ![]() ![]() ![]() |
The following limitations apply to the Windows Terminal Service environment.
These limitations are built in Windows Terminal Service or MetaFrame.
MetaFrame's [Auto-creating client printers]
Using [Auto-creating client printers] can select a logical printer created by copying the client's local printer data to the MetaFrame server. We strongly recommend testing this function in your network environment before using it for your work.
The settings for optional equipment will not be stored in the server after the equipment is disconnected. The settings for optional equipment will be restored to its defaults each time the client computer logs on to the server.
When printing a large number of bitmap images or using the server in a WAN environment over dial-up lines such as ISDN, printing may not be possible or errors may occur, depending on data transfer rates.
MetaFrame's [Printer driver replication]
Using [Printer driver replication] can distribute printer drivers across all servers in a server farm. We strongly recommend testing this function in your network environment before using it for your work.
If the printer drivers are not properly copied, install them directly onto each server.