Understanding Printing Problems

1. Printer drivers are not written to be used on Terminal Servers
   
   Finally, though, a lot of printer manufacturers see the necessity of developing their drivers to be used on Terminal Servers. But there are still printer drivers which are written for usage on a workstation by one user at the time. Printer drivers not written for Terminal Servers are, most of the time, not capable of handling so many printing jobs. When the driver becomes overwhelmed, this can cause the spooler services to crash, or even worse the operating system will blue screen.
   
2. Printjobs use a lot of bandwidth
   
   Printjobs normally consume a large amount of bandwidth. This is not specifically related to Terminal Server environments, but most times it is a bigger issue when using Terminal Services. Because Terminal Services are used a lot when users need access from co-locations, home locations or supplier/customer offices where the bandwidth is limited to the location where the Terminal Servers are. Within environments with a small amount of bandwidth and lots of printjobs these jobs can use the full amount of bandwidth. This actually means that users are not able to work anymore because Terminal Server related traffic is brought to a stand still by the printer traffic.
   
3. Version conflicts by third party drivers
   
   Often (especially with new printers) the Windows operating system doesn’t have the driver for that printer. To use all the functionality of that printer the driver made by the manufacturer must be used. It may happen that one new driver overwrites a DLL also used by another driver. It may also happen that the printers using the pre-existing DLL do not function anymore. Therefore every new printer driver must be tested extensively before using it in a production environment.
   
4. All printer drivers need to be available on all Terminal Servers
   
   The most important rule in the Terminal Server world is that all servers hosting the same applications must be 100% identical. This rule also applies to the printer drivers. It is a difficult job to keep all related files to printer drivers identical on all servers especially if you have lots of printer drivers.

Taken from MSterminalservices.org

Please Install Yahoo Messenger

All FOREX users are encourage to install and use yahoo messenger on their local machine(PC). To all those users who are not yet using Yahoo Messenger, please download and install yahoo messenger. You can download the messenger at messenger.yahoo.com or click here. For installation instruction please follow the one provided by Yahoo.

After you have installed and you have created your own account on yahoo, it's time to add these yahoo id to your yahoo buddy list, for support:

My yahoo id : Tenshinshoden
Edetera : Eggsdetera

You can use yahoo to send quick notes, question and request support.

You can still call me for support anytime on the same phone no. that you have.

How do I know which printer drivers work with Terminal Services?

All of the Microsoft-supplied printer drivers are tested with Terminal Services and guaranteed to work. Before using a third-party printer driver, make sure it has been certified for Terminal Services. There is a Windows Hardware Quality Labs (WHQL) program for getting third-party printer drivers certified on Terminal Services. Please ask your printer driver vendor to secure such certification.

Now, in the Forex Cargo domain, we have noticed that the most compatible printer brand is the

1. Epson
2. Canon
3. HP

THE LIST IS ORDERED BY COMPATIBILITY.

Note: If you are going to get a new printer for use with remote desktop, get a regular printer, don't get the All in Ones. If you already have a All In One printer, there is a work around, but you have to do the adjustments manually on your end. Meaning you have to change some settings on your pc's registry which we don't recommend.

I will post the registry settings soon.

Printing Problem.

The most common problem in Terminal Services / Remote Desktop Connection is the printing problem. There are times a users can't find their specific printers or the print out prints on the wrong printer. The first thing a user should do is close the application that they are using (remittance or cargo) and log off the server.

Doing this should delete the printer initially assigned to your session and will free server resources. When you relogin the server will recreate a virtual printer for your session.

If you are still having the same printing problem please notify your administrator.

Logging Off

All users are requested to log off properly. When we say proper, all users must go through the normal procedure:

1. Click on Start
   
2. Click on Log Off

WHY IS THIS IMPORTANT?
When a user logs off, the session and other server resources are closed and released back to the server. The virtual printer that is created for that specific user is also deleted from the printer list, does minimizing printing error problems.

WHAT HAPPENS WHEN A USER DON'T LOG OFF?
When a user disconnects from a session, by just closing his/her remote desktop application. All applications that he/she is using are still up and running and are still using server resources. And with this Virtual Printer that is created for you stays in the printer list. This is not a good practice.

Disconnected Sessions are automatically ended after 10 to 15 minutes.

Idle Sessions are also automatically ended after 30 minutes.

Remote Desktop Connection Client for Mac

Remote Desktop Connection Client 1.0.3 for Mac OS X

TO DOWNLOAD Remote Desktop Connection Client 1.0.3 for Mac OS X CLICK HERE.
Be sure to read this article for more information.

With Remote Desktop Connection Client for Mac, you can connect from your Macintosh computer to a Windows-based computer and work with programs and files on that computer. Mac users who have access to a Windows-based computer on a network, including users on Intel-based Macs, can use Remote Desktop Connection as an alternative to Microsoft Virtual PC for Mac.

Remote Desktop Connection Client for Mac allows you to connect to a Windows-based computer and work with programs and files on that computer from your Macintosh computer. To connect to a Windows-based computer, you need network access and permissions to connect to the computer, and the computer must be running Terminal Services or Remote Desktop Services. The following Windows products support Remote Desktop connections: Windows XP Professional Windows Server 2003 Windows 2000 Server Windows 2000 Advanced Server Windows 2000 Datacenter Server Windows NT Server 4.0, Terminal Server Edition What's New: Remote Desktop Connection Client 1.0.3 for Mac provides improved stability when you minimize the client window and when you copy and paste data from the client window to Macintosh applications. Stability is also improved for users of Mac OS X 10.3 and later, and when Remote Desktop Connection Client is used on Macintosh computers with PowerPC G5 processors.

System requirements

To use Microsoft Remote Desktop Connection Client 1.0.3 for Mac, your Macintosh computer must meet the following minimum requirements:

• Processor: Macintosh PowerPC.
• Operating system: Mac OS X version 10.2.8 or later.
• Memory: 128 MB of RAM.
• Hard disk: 3 MB of available hard disk space temporarily required to complete installation; after installation, 1.1 MB of hard disk space.

  Note The hard disk should be in Mac OS Extended (HFS+) format, the default format for Mac. Microsoft does not currently support running Remote Desktop Connection from a hard disk that is in another format. To determine the format of your hard disk, on the Apple menu, click About This Mac, and then click More Info.

• Network: Connection to a local area network, either directly or via a modem capable of 28.8 Kbps or higher.
• Internet access: Internet connection through either an Internet service provider (ISP) or a network. Internet access might require a fee to an ISP; local or long-distance telephone charges might also apply.

Tip If you're not sure whether your computer meets these requirements, you can display information about your computer by using the Apple System Profiler program included with Mac OS X. To start the program, on the Apple menu, click About This Mac, and then click More Info.

Installation instructions

Before you install this download:

Depending on the file format you choose to download, make sure StuffIt Expander version 6 or later and Apple Disk Copy version 10.1 or later are installed on your computer. By default, Mac OS X includes the correct versions of these programs.

To install this download:

1. Print this page if you want to use it as a reference when you are offline.
2. Make sure your computer meets the minimum system requirements for this download.
3. In the table above, click the language version and file format you want.
4. If prompted, save the file to your hard disk.
   If you are using Internet Explorer, the Download Manager saves the file to the desktop unless you specified a different download folder in the Preferences dialog box (Download Options pane).
5. On your hard disk, double-click the file that you downloaded in step 4 to expand it using StuffIt Expander. For example, if you downloaded an English language version of the file, a new file called RDC103EN.dmg is created.
   Depending on the Web browser that you are currently using, this step might be performed for you automatically.
6. Double-click the .dmg file you downloaded (for example, RDC103EN.dmg) to mount the Remote Desktop Connection volume.
7. On the Desktop, open the Remote Desktop Connection volume.
8. Copy the Remote Desktop Connection folder from the Remote Desktop Connection volume to your hard disk.
9. If the Remote Desktop Connection folder was copied to your hard disk successfully, you can move the Remote Desktop Connection volume, the .dmg file, and the original file you downloaded in step 4 (if present) to the Trash.
10. On the Windows computer, open Control Panel, double-click System, click the Remote tab, and then select the Allow users to connect remotely to this computer check box.
11. To complete the installation, run the program by opening the Remote Desktop Connection folder that you copied to your hard disk in step 8, and then double-click Remote Desktop Connection.

Terminal Services / Remote Desktop Connection

Terminal Services or Terminal Server Edition (TSE) is a component of Microsoft Windows NT operating systems (both client and server versions) that allows a user to access applications or data stored on a remote computer over a network connection. Terminal Services is Microsoft's take on server centric computing, which allows individual users to access network resources easily.

Based on the Remote Desktop Protocol (RDP), Terminal Services was first introduced in Windows NT 4.0 (Terminal Server Edition). The products Windows 2000 Server, Windows 2000 Advanced Server, Windows 2000 Datacenter Server and Windows Server 2003 have introduced several improvements and new features. Microsoft used Terminal Services in Windows XP for the Remote Assistance feature. Windows XP (Professional Edition only) includes a single-user Terminal License using the Remote Desktop feature.

Microsoft provides the client software Remote Desktop Connection (formerly called Terminal Services Client), available for most 32-bit versions of their Windows operating systems and Apple's Mac OS X, that allows a user to connect to a server running Terminal Services. Third-party developers have created client software for other platforms, including the open source rdesktop client for common Unix platforms. Both Terminal Services and Remote Desktop Protocol use Port 3389 by default.