Napomene za djelatnike 4D i distributere

Setiranje Terminal Services

•Setiranje mrežnog printera na klijentu

•Setiranje servera za udaljene POS kase

•Setiranje printera čiji driver ne postoji na Windows 2000

•Dodavanje nove privremene licence

•Keep Alive parametar

Windows 2000 Terminal Services Does Not Redirect Network Printers

The information in this article applies to:

•Microsoft Windows 2000 Server

•Microsoft Windows 2000 Advanced Server

Summary

In Windows 2000 Terminal Services you can redirect clients' local printers when they log on to a Terminal Services session with the Microsoft RDP 5 Terminal Services client. The redirection of local printers is a default behavior.
When clients connect to a Terminal Services session and the clients have network printers configured, the clients' network printers are not redirected. This behavior is by design. If users need to print to a network printer, it is logical to set up the network printer on the Terminal Services computer normally, through the Add Printer Wizard, and allow users to select and print to that printer. If Terminal Services also redirected network printers, a single server could easily end up with 30 instances of the same printer configured.

More Information

If there is a special circumstance where the user needs to redirect a network printer, you can use the net use command to map a network printer to a local port. For example:

net use lpt3 \\servername\printer /persistent:yes

This command maps the network printer to the local port LPT3. The user can then install the correct drivers for that printer as though the printer was installed on LPT3. If this is done, the printer on LPT3 is redirected when the user connects to the Terminal Services session. This also works with LPT1 and LPT2, as long as there is not a local device on either of these ports.

This workaround is useful in environments when a user opens a session to a Terminal Services computer on a remote network (for example, across the Internet) and wants to print back to a printer shared on the local area network (LAN).

Terminal Services: Setiranje remote printera

Dakle, problem je u tome da terminal klijent ne moze štampati na lokalni printer. Zašto? Zato što se na klijentu printer zove npr. "HP Deskjet 720c" a na serveru "HP Deskjet 720b" (razlika u nazivu pa Windowsi ne vide da je riječ o istom printeru).

Greške

Problem se dijagnosticira sa stopostotnom preciznošću zato što server logira greške 1111, 1105 i 1106 (a tamo piše i nemam driver x za printer y).
System event log na serveru:

Type: Error
Event ID: 1111
Opis: Driver <drivername> required for printer <printertype> is unknown. Contact the administrator to install the driver before you log in again.

Type: Error
Event ID: 1105
Opis: Printer security information for the <printername>/<clientcomputername>/Session <number> could not be set.

Type: Error
Event ID: 1106
Opis: The printer could not be installed.

Rješenje

Jedno od mogućih rješenja je instalirati isti driver na server i na klijent ali to nekad nije moguće zato što je klijent Win98 ili Win95. Dakle rješenje bi bilo serveru reći "HP Deskjet 720c"="HP Deskjet 720b" (što mu pomaže da shvati da je isti printer). Nekada se to radilo tako da se u datoteci ntprint.inf (u c:\winnt\inf folderu) pod sekcijom [Previous names] upise "720c"="720b". Taj način nije dobar jer Microsoft brani modificiranje datoteke ntprint.inf. Zato je nakon instalacije service packa 2 (bez njega postupak ne radi) predloženi postupak slijedeći (izvadak iz dokumentacije):

You must add two new values to the registry key HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\Wds\rdpwd.
The new values are as follows:

Name: "PrinterMappingINFName"
Type: REG_SZ
Data: Name of the .inf file to which you want to redirect lookups.

Name: "PrinterMappingINFSection"
Type: REG_SZ
Data: Name of the section in the .inf file to which you want to redirect
lookups.

After adding the new registry values above, an .inf file must be created (step 2) or modified (step 3) to include the user-defined mappings from the client-side to server-side drivers. This is explained below.
Example of the format for creating a new inf file:

[Version]
Signature="$CHICAGO$"

[Printers]
OEM Printer Driver Name = Windows 2000 Printer Driver Name

This file can be created with Notepad and needs to be saved with a .inf file extension. In this example, you would specify the .inf filename that you just created in the "PrinterMappingINFName" registry value and "Printers" in the "PrinterMappingINFSection" registry value.

You can also modify the existing Printupg.inf file in the Winnt\Inf folder (using Notepad) by adding the new mapping to the [Printer Driver Mapping] section. Use the format: OEM Printer Driver Name = Windows 2000 Printer Driver Name

The top section of the Printupg.inf file explains this format. If you modify the Printupg.inf file in this example, you would specify "Path to inf file\Printupg.inf" in the PrinterMappingINFName registry value and "Printer Driver Mapping" in the PrinterMappingINFSection registry value.

NOTE : Do not modify the original Ntprint.inf file. Doing so may break the file signing of the Ntprint.inf file.

Staro rješenje

Slijedi tekst starog rješenja problema, koje je ostavljeno samo da bi se ukoliko je neophodno, imale informacije o tome kako je to radilo.

The following resolution breaks the digital signing on Ntprint.inf. If you make the following changes, the changes may allow a workaround on a specific driver mismatch, however, any additional printer driver installs can invoke a file signing error for every printer action and redirection on the server. Making changes to this file are not supported, this information is supplied as is.

NOTE: The following resolution will cause the digital signing on the Ntprint.inf file not to work. Making the changes below may allow you to work around the issue on a specific driver mismatch, but any additional printer driver installs may invoke a file signing error message for every printer action and redirection on the server. Making changes to this file is not supported.

To add support for the redirection of a client printer that uses a driver with an unknown name (such as a third-party driver or a driver from an earlier version of Windows), you can add a line to the [Previous Names] section of the Ntprint.inf file on the Terminal Services-based server. This line associates the name of a Windows 2000 driver with the unknown name. Many entries already exist in this list. The following text is an excerpt from this section of the Winnt\Inf\Ntprint.inf file:

[Previous Names]
"Apple LaserWriter v23.0" = "Apple LaserWriter"
"Apple LaserWriter II NT v47.0" = "Apple LaserWriter II NT"
"Apple LaserWriter II NTX v47.0" = "Apple LaserWriter II NTX"

The left column contains the name of the Windows 2000 driver. The right column contains the name of the driver that the client is using.

You can add additional entries anywhere in this list. For example, Hewlett-Packard (HP) supplies Windows 98 and Microsoft Windows NT 4.0 drivers for the DeskJet 722C printer. This driver is called "HP DeskJet 720C Series v10.3." The Windows 2000 version of this driver is called "HP DeskJet 722C." You can find the Windows 2000 driver name by checking the list of printer driver names in the [HP] section of the Ntprint.inf file. For Windows 2000 to recognize the HP driver name, add the follow entry to the [Previous Names] section:
"HP DeskJet 722C" = "HP DeskJet 720C Series v10.3"

This instructs Windows 2000 to use the HP DeskJet 722C driver when a client with Hewlett-Packard's HP DeskJet 720C Series v10.3 driver connects. These names must match exactly, with identical spacing; the names are also case sensitive.

Setiranje udaljenih POS kasa za Terminal Services

Direktoriji za razmjenu podataka i INI datoteke

U 4D direktoriju na Terminal Serveru napraviti direktorij "Transfer". U "Transfer" direktoriju za svaku lokaciju (grad) napraviti poddirektorij. U njima napraviti dva direktorija: npt: "Zagreb-Split" i "Split-Zagreb". Na ta dva direktorija treba staviti WebShare.
U 2002.INI (ili koji već treba iz direktorija w:\4d\wand\1_firma\ini) treba u sekciju sa šifrom skladiša staviti pathove za import i export: "\" na kraju obavezan.

[0000103]
POSImport=C:\4D\Transfer\Split\Split-Zagreb\
POSExport=C:\4D\Transfer\Split\Zagreb-Split\

Direktoriji se ovako postavljaju, jer se gleda sa POS strane: POS "importira" iz direktorija Zagreb-Split, tako da je u Zagrebu taj direktorij "POSExport". Pos šalje ("exportira") promet u direktorij Split-Zagreb, ali je to iz Zagreba "import" direktorij.

Privremene Terminal client licence

Privremene licence za terminal cliente se nalaze u ključu: HKEY_LOCAL_MACHINE\Software\Microsoft\MSLicensing\Store\LICENSE00x

Keep Alive parametar na Terminal servisima

Knowledge Base

You cannot completely disconnect a Terminal Server connection
PSS ID Number: 216783
Article Last Modified on 8/3/2004
________________________________
The information in this article applies to:
* Microsoft Windows NT Server 4.0 Terminal Server Edition
* Microsoft Windows 2000 Server
________________________________

This article was previously published under Q216783
Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry

SYMPTOMS
After a Terminal Server client loses the connection to a Terminal Server, the session on the Terminal Server may not transition to a disconnected state, instead, it may remain active even though the client is physically disconnected from the Terminal Server. If the client logs back in to the same Terminal Server, a totally new session may be established, and the original session may still remain active.

CAUSE
This issue can occur because Terminal Server implements a Keep Alive mechanism.

RESOLUTION
Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

For Windows NT 4.0 Terminal Server Edition

To work around this issue:
1. Apply the latest service pack for Windows NT 4.0, Terminal Server Edition.
2. Use Registry Editor to add a DWORD value, KeepAliveEnable, with a Positive numeric value of 1 (which represents 1 minute) to the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server
3. In the Terminal Server Connection Configuration tool, double-click rdp-tcp, and then click Advanced.
4. On the On a broken or timed-out connection, <connect action> the session line, click to clear the inherit user config option. Click Disconnect on On a broken or timed-out connection, <connect action> the session, and then click OK.

For Windows 2000 Server

1. Use Registry Editor to add a DWORD value, KeepAliveEnable, with a positive numeric value of 1 (which represents Enable) to the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server
2. Open Terminal Services Configuration in Administrative Tools, double-click RDP-Tcp in the Connections folder, and then click the Sessions tab.
3. Click to select Override user settings and make sure that Disconnect from session is selected and then click OK.
Additional query words: terminalsvr terminal KeepAliveEnable KeepAliveInterval session disconnect session alive