Terminal Server client printing

[AJP69]

I am having a problem getting terminal server clients (win98/W2K) to print.

My understanding is that if you install the drivers on the server, then the clients printers should be automatically created.

This is not happening, the clients default printer is on a network share on a W2k/WinNT server at the client site.

Any ideas?

AJ

 

[ReddLefty]

Terminal Server profiles act like any new profile on a computer at first login and the printers will not be there unless they are installed.

Here is something that one of my co-workers did, I'm not sure of the exact procedure:

- Log in Local Administrator, install printer(s).
- Log in with another user that has admin rights and copy the Administrator profile into the Default User profile.

This way, every time a user logs on for the first time, the default user profile is used to create the users profile, hence, the printer(s) comes with it. Of course, the default printer still may need to be chosen manually, but at least you can install all the printers needed.

Also, this is only good for users that log on for the first time. If you do the modifications now, the printers won't "appear" on the currently existing profiles. You could delete the existing profiles to force a new one or you can install the printers manually... this depends on how many users you may have already on the terminal server.




"In space, nobody can hear you click..."

 

[BWilson77080]

terminal services only automatically puts local printers (local to the client machine connecting) inside the printers container. Your best bet would be to use the above mentioned idea, or you could just implement a mandatory profile by making a new profile, configuring it as needed, log out of that new profile and log in as an admin, rename the ntuser.dat file in the new profile to ntuser.man, and then copy it over....this will force all users to have the same desktop when loggin onto the terminal server though.

Is printer redirection on for the terminal server? I seem to remember an option in user accounts to enable printer redirection on the terminal services tab....but this could be for only local printers...dont remember...try and see

lemme know

 

[AJP69]

Thanks for the replies:

Red, there is nothing wrong with the profile, I created a "perfect" profile and use it as default.


BWilson77080, yes it is set to map all client printers.

The normal behaviour for TS is to dynamically create ports for client printers, but only for printer drivers which have been installed on the server.

On the W2kPro PC's I installed the new RDC client and it works, so the problem is fixed for them. But when I installed the RDC client on the W98 boxes it would not allow be to save/embedd the password.

So now that has become the problem, how to make Windows98 embed the password.

I like it when the solution to one problem creates another!

Any idea on what is causing this problem would be appreciated.

AJ

 

[devastator]

If you are running SP3 on your TS that is your problem. SP3 caused mapping problems and is posted on Microsoft's web site. SP4 is suppose to fix those issues. Win98 stations have to be set up manually.


Dev

 

[AJP69]

Thanks devastator, We do have Sp3 and I saw that report from MS but we were not getting the error mentioned in the event log. I do plan to install SP4 but I need to take an image before and make sure I do not fix one problem but create another.

I did manage to sort the problem by installing the RDC client, this worked fine on the W2k clients, but the W98 clients will not let me save a password in the RDC settings. The effect of this is that user have to enter yet another password which drives them nuts.

If you have any ideas on why the Win98 client will not let me save a password, I am all ears!

Thanks for your response

AJ

 

[BWilson77080]

maybe system policies???