It takes a long time to login TS

[chicagotech]

We're using Group policy preferences to deploy shared printers for Terminal users. He TS is windows 2003 SP2. When TS users login, it takes between 15 to 20 minutes to login. The Event Viewer has this message (note: it takes 2 more minutes to map one shared printer as shown in the Event):

Event Type: Warning

Event Source: Group Policy Printers

Event Category: (2)

Event ID: 4098

Date: 3/15/2012

Time: 2:28:18 PM

User: NT AUTHORITY\SYSTEM

Computer: TERMINALSERVER

Description:

The user 'Lansing-400' preference item in the 'Map Printers (Chicago) {A504EAFA-587F-439E-8EFD-D75E0A72D903}' Group Policy object did not apply because it failed with error code '0x8007007b The filename, directory name, or volume label syntax is incorrect.' This error was suppressed.

Event Type: Warning

Event Source: Group Policy Printers

Event Category: (2)

Event ID: 4098

Date: 3/15/2012

Time: 2:25:35 PM

User: NT AUTHORITY\SYSTEM

Computer: TERMINALSERVER

Description:

The user 'Cicero-200' preference item in the 'Map Printers (Chicago) {A504EAFA-587F-439E-8EFD-D75E0A72D903}' Group Policy object did not apply because it failed with error code '0x800706bb The RPC server is too busy to complete this operation.' This error was suppressed.

However, administrator doesn’t have this problem. Any help?


--------------------------------------------------------------------------------

[chicagotech]

When you apply printer mapping via GP you get 4098 warning but policy apply successfully.

The connection will be stored in the user's profile (HKCU\Network) and reapplied at next login. Which means the OS is mapping the printers already. That might lead to the GPP event log error.

Please try to disable printer redirection to test to see if the same issue still exists.

[chicagotech]

Check if the AV is scanning HTTP traffic as was the earlier case I had.

If not I recommend you work with the AV vendor to identify the AV options that might be interfering with RDWeb.

[chicagotech]

By default, the windows 2008 will use the easy print to redirect the default print which is installed on the client side. So would you mind having a try to connect this server via a clean system client without installing any print? Does this issue happen as usual?



Meanwhile, there are some requirements to use the easy print on the Windows Server 2008:



1. Clients are running Remote Desktop Connection (RDC) 6.1 client.

2. The .NET Framework 3.0 Service Pack 1.



And the order for looking for Printer driver on windows 2008 R2 is: Built-in printer driver -> Custom Printer Mapping File -> Easy Print .