This is the exact setup in thousands of Indian offices: TallyPrime lives on a server, staff connect over RDP, and invoices have to come out of the small printer on each person's own desk. It works - until the day Tally starts printing to the wrong place or nowhere. The cause is almost always one naming trap.
Tally does not know anything about your desk. It prints to whatever printers the Windows session offers it. When you connect over RDP with printer redirection, the session offers your local printer under a name like HP LaserJet (redirected 2). Select that in Tally and the invoice travels back through your connection and prints beside you. Simple - except the number. Tomorrow you are session 5, the name is (redirected 5), and every saved setting pointing at yesterday's name is quietly broken.
mstsc with Show Options > Local Resources > Printers ticked, as in the main setup guideThe number in the redirected name is your session number on the server. It changes when you log off and on, when the server restarts, when others log in first. Anything that memorised the old name - Tally's remembered printer for a report, a saved print configuration, your own habit of clicking the first HP in the list - now aims at a printer that no longer exists. Jobs then seem to vanish, or Tally silently falls back to a different printer, sometimes the office copier in another building. No setting in Tally can fix this, because Tally did nothing wrong. It is how Windows redirection names things.
Offices that print from Tally over RDP all day eventually stop tolerating the renaming. That is the real reason tools like TSPrint, shown in the video, get installed: inside the session there is a printer called TSPrint Default - the same name, every session, every day - which prints to whatever the client's default printer is. Tally's saved selections keep working because the name never changes, and no printer driver lives on the server. It is a paid tool, and for a billing desk that prints two hundred invoices a day, most offices judge the name stability alone worth it. Judge your own volume honestly - occasional printing survives the manual habit fine.
Many Tally desks still use dot-matrix printers for continuous stationery, and some print cheques. These devices are the least happy travellers through Easy Print redirection - page lengths and alignment can drift. Test thoroughly on the actual printer and paper before trusting a batch, keep expectations modest, and treat consistent misalignment as a sign to use the driver-matching route or a stable-name tool rather than endless margin adjustments inside Tally.
The video's TSPrint setup is exactly the stable-name fix described here - watch it done live on a real server and client.
▶️ Watch Full VideoThe printer Tally had remembered - yesterday's redirected name - no longer exists, so it fell back to a PDF printer. Open the print dialog, select today's redirected printer explicitly, and it will print normally.
Usually paper size: Tally is set to one size and the client printer's default is another. Match the size in Tally's print configuration and in the printer's own preferences on your PC, then test with one page.
Yes. Each session redirects its own client's printer, and each user sees their own redirected copy. The discipline needed is only human - each person must select their own printer name at print time.