Windows NT batch file to change windows XP registry

  • Thread starter Thread starter xiaomei
  • Start date Start date
X

xiaomei

Hi, There,
In the old time, the network printer installed on the XP machine could not
be mapped on the Terminal server (TS), finally we got document from Ms site
told need change the client machine registry to make it works, however, we
have hundreds of client, it will be very tedious and boring if we change one
by one, is anyone have some suggestion of bactch file scrip to change the
registry, that will save a lot of time.

Thanks for any suggestion!
Shermaine
 
I've not heard of XP not being able to map printers in terminal
services. Where did that information come from? Which document are you
referring to that requires a change on the workstations to get printers
to map?

Jeff Pitsch
Microsoft MVP - Terminal Server
Citrix Technology Professional
Provision Networks VIP

Forums not enough?
Get support from the experts at your business
http://jeffpitschconsulting.com

xiaomei wrote:
> Hi, There,
> In the old time, the network printer installed on the XP machine could not
> be mapped on the Terminal server (TS), finally we got document from Ms site
> told need change the client machine registry to make it works, however, we
> have hundreds of client, it will be very tedious and boring if we change one
> by one, is anyone have some suggestion of bactch file scrip to change the
> registry, that will save a lot of time.
>
> Thanks for any suggestion!
> Shermaine
 
xiaomei <xiaomei@discussions.microsoft.com> wrote:
> Hi, There,
> In the old time, the network printer installed on the XP machine
> could not be mapped on the Terminal server (TS), finally we got
> document from Ms site told need change the client machine registry to
> make it works, however, we have hundreds of client, it will be very
> tedious and boring if we change one by one, is anyone have some
> suggestion of bactch file scrip to change the registry, that will
> save a lot of time.
>
> Thanks for any suggestion!
> Shermaine

If you're talking about KB 302361 (Printers That Use Ports That Do Not Begin
With COM, LPT, or USB Are Not Redirected in a Remote Desktop or Terminal
Services Session), I believe this registry change will be uneccessary if you
upgrade everyone's RD client to the latest version.
 
Ah now that makes sense. I read it as the OP was saying no printers at
all can be mapped using WinXP which had me all confused.



Lanwench [MVP - Exchange] wrote:
> xiaomei <xiaomei@discussions.microsoft.com> wrote:
>> Hi, There,
>> In the old time, the network printer installed on the XP machine
>> could not be mapped on the Terminal server (TS), finally we got
>> document from Ms site told need change the client machine registry to
>> make it works, however, we have hundreds of client, it will be very
>> tedious and boring if we change one by one, is anyone have some
>> suggestion of bactch file scrip to change the registry, that will
>> save a lot of time.
>>
>> Thanks for any suggestion!
>> Shermaine
>
> If you're talking about KB 302361 (Printers That Use Ports That Do Not Begin
> With COM, LPT, or USB Are Not Redirected in a Remote Desktop or Terminal
> Services Session), I believe this registry change will be uneccessary if you
> upgrade everyone's RD client to the latest version.
>
>
 
Jeff Pitsch <Jeff@Jeffpitschconsulting.com> wrote:
> Ah now that makes sense. I read it as the OP was saying no printers
> at all can be mapped using WinXP which had me all confused.

Ah, yes. I just remembered the registry thing because it used to drive me
bonkers!

>
>
>
> Lanwench [MVP - Exchange] wrote:
>> xiaomei <xiaomei@discussions.microsoft.com> wrote:
>>> Hi, There,
>>> In the old time, the network printer installed on the XP machine
>>> could not be mapped on the Terminal server (TS), finally we got
>>> document from Ms site told need change the client machine registry
>>> to make it works, however, we have hundreds of client, it will be
>>> very tedious and boring if we change one by one, is anyone have some
>>> suggestion of bactch file scrip to change the registry, that will
>>> save a lot of time.
>>>
>>> Thanks for any suggestion!
>>> Shermaine
>>
>> If you're talking about KB 302361 (Printers That Use Ports That Do
>> Not Begin With COM, LPT, or USB Are Not Redirected in a Remote
>> Desktop or Terminal Services Session), I believe this registry
>> change will be uneccessary if you upgrade everyone's RD client to
>> the latest version.
 
Dear All,
Many thanks for all of you!

Regards
Shermaine

"Lanwench [MVP - Exchange]" wrote:

> Jeff Pitsch <Jeff@Jeffpitschconsulting.com> wrote:
> > Ah now that makes sense. I read it as the OP was saying no printers
> > at all can be mapped using WinXP which had me all confused.
>
> Ah, yes. I just remembered the registry thing because it used to drive me
> bonkers!
>
> >
> >
> >
> > Lanwench [MVP - Exchange] wrote:
> >> xiaomei <xiaomei@discussions.microsoft.com> wrote:
> >>> Hi, There,
> >>> In the old time, the network printer installed on the XP machine
> >>> could not be mapped on the Terminal server (TS), finally we got
> >>> document from Ms site told need change the client machine registry
> >>> to make it works, however, we have hundreds of client, it will be
> >>> very tedious and boring if we change one by one, is anyone have some
> >>> suggestion of bactch file scrip to change the registry, that will
> >>> save a lot of time.
> >>>
> >>> Thanks for any suggestion!
> >>> Shermaine
> >>
> >> If you're talking about KB 302361 (Printers That Use Ports That Do
> >> Not Begin With COM, LPT, or USB Are Not Redirected in a Remote
> >> Desktop or Terminal Services Session), I believe this registry
> >> change will be uneccessary if you upgrade everyone's RD client to
> >> the latest version.
>
>
>
>
 
Hi, Lanwench, Jeff,
Thanks for your time and valuable suggestion!
May I know is there any Ms Windows update should be installed together with
update to latest RDC client software?
Because I update my XP SP2 machine RDC software from 5.1 to 6.0, but still
can not see the printer on Terminal server, however another Vista machine
which also running 6.0 RDC software can see the mapped printers. ( The same
office printer)

Or what is the difference between Vista and XP in terms of RDC parts.
Many thanks again!
Have a good weekend!

Shermaine



"xiaomei" wrote:

> Dear All,
> Many thanks for all of you!
>
> Regards
> Shermaine
>
> "Lanwench [MVP - Exchange]" wrote:
>
> > Jeff Pitsch <Jeff@Jeffpitschconsulting.com> wrote:
> > > Ah now that makes sense. I read it as the OP was saying no printers
> > > at all can be mapped using WinXP which had me all confused.
> >
> > Ah, yes. I just remembered the registry thing because it used to drive me
> > bonkers!
> >
> > >
> > >
> > >
> > > Lanwench [MVP - Exchange] wrote:
> > >> xiaomei <xiaomei@discussions.microsoft.com> wrote:
> > >>> Hi, There,
> > >>> In the old time, the network printer installed on the XP machine
> > >>> could not be mapped on the Terminal server (TS), finally we got
> > >>> document from Ms site told need change the client machine registry
> > >>> to make it works, however, we have hundreds of client, it will be
> > >>> very tedious and boring if we change one by one, is anyone have some
> > >>> suggestion of bactch file scrip to change the registry, that will
> > >>> save a lot of time.
> > >>>
> > >>> Thanks for any suggestion!
> > >>> Shermaine
> > >>
> > >> If you're talking about KB 302361 (Printers That Use Ports That Do
> > >> Not Begin With COM, LPT, or USB Are Not Redirected in a Remote
> > >> Desktop or Terminal Services Session), I believe this registry
> > >> change will be uneccessary if you upgrade everyone's RD client to
> > >> the latest version.
> >
> >
> >
> >
 
Hi, Lanwench, Jeff,
I found the reason, after updated to version 6.0, the default setting of
Enable the printers on the RDC was unchecked, I just enable this from
Options-----Local sources----Printers, then it works fine.

Any how, thanks a lot for your help!
Enjoy ur good weekend!

Shermaine

"xiaomei" wrote:

> Hi, Lanwench, Jeff,
> Thanks for your time and valuable suggestion!
> May I know is there any Ms Windows update should be installed together with
> update to latest RDC client software?
> Because I update my XP SP2 machine RDC software from 5.1 to 6.0, but still
> can not see the printer on Terminal server, however another Vista machine
> which also running 6.0 RDC software can see the mapped printers. ( The same
> office printer)
>
> Or what is the difference between Vista and XP in terms of RDC parts.
> Many thanks again!
> Have a good weekend!
>
> Shermaine
>
>
>
> "xiaomei" wrote:
>
> > Dear All,
> > Many thanks for all of you!
> >
> > Regards
> > Shermaine
> >
> > "Lanwench [MVP - Exchange]" wrote:
> >
> > > Jeff Pitsch <Jeff@Jeffpitschconsulting.com> wrote:
> > > > Ah now that makes sense. I read it as the OP was saying no printers
> > > > at all can be mapped using WinXP which had me all confused.
> > >
> > > Ah, yes. I just remembered the registry thing because it used to drive me
> > > bonkers!
> > >
> > > >
> > > >
> > > >
> > > > Lanwench [MVP - Exchange] wrote:
> > > >> xiaomei <xiaomei@discussions.microsoft.com> wrote:
> > > >>> Hi, There,
> > > >>> In the old time, the network printer installed on the XP machine
> > > >>> could not be mapped on the Terminal server (TS), finally we got
> > > >>> document from Ms site told need change the client machine registry
> > > >>> to make it works, however, we have hundreds of client, it will be
> > > >>> very tedious and boring if we change one by one, is anyone have some
> > > >>> suggestion of bactch file scrip to change the registry, that will
> > > >>> save a lot of time.
> > > >>>
> > > >>> Thanks for any suggestion!
> > > >>> Shermaine
> > > >>
> > > >> If you're talking about KB 302361 (Printers That Use Ports That Do
> > > >> Not Begin With COM, LPT, or USB Are Not Redirected in a Remote
> > > >> Desktop or Terminal Services Session), I believe this registry
> > > >> change will be uneccessary if you upgrade everyone's RD client to
> > > >> the latest version.
> > >
> > >
> > >
> > >
 
xiaomei <xiaomei@discussions.microsoft.com> wrote:
> Hi, Lanwench, Jeff,
> I found the reason, after updated to version 6.0, the default setting
> of Enable the printers on the RDC was unchecked, I just enable this
> from Options-----Local sources----Printers, then it works fine.
>
> Any how, thanks a lot for your help!
> Enjoy ur good weekend!

Glad you got it resolved thanks for letting us know.
>
> Shermaine
>
> "xiaomei" wrote:
>
>> Hi, Lanwench, Jeff,
>> Thanks for your time and valuable suggestion!
>> May I know is there any Ms Windows update should be installed
>> together with update to latest RDC client software?
>> Because I update my XP SP2 machine RDC software from 5.1 to 6.0, but
>> still can not see the printer on Terminal server, however another
>> Vista machine which also running 6.0 RDC software can see the mapped
>> printers. ( The same office printer)
>>
>> Or what is the difference between Vista and XP in terms of RDC parts.
>> Many thanks again!
>> Have a good weekend!
>>
>> Shermaine
>>
>>
>>
>> "xiaomei" wrote:
>>
>>> Dear All,
>>> Many thanks for all of you!
>>>
>>> Regards
>>> Shermaine
>>>
>>> "Lanwench [MVP - Exchange]" wrote:
>>>
>>>> Jeff Pitsch <Jeff@Jeffpitschconsulting.com> wrote:
>>>>> Ah now that makes sense. I read it as the OP was saying no
>>>>> printers at all can be mapped using WinXP which had me all
>>>>> confused.
>>>>
>>>> Ah, yes. I just remembered the registry thing because it used to
>>>> drive me bonkers!
>>>>
>>>>>
>>>>>
>>>>>
>>>>> Lanwench [MVP - Exchange] wrote:
>>>>>> xiaomei <xiaomei@discussions.microsoft.com> wrote:
>>>>>>> Hi, There,
>>>>>>> In the old time, the network printer installed on the XP machine
>>>>>>> could not be mapped on the Terminal server (TS), finally we got
>>>>>>> document from Ms site told need change the client machine
>>>>>>> registry to make it works, however, we have hundreds of client,
>>>>>>> it will be very tedious and boring if we change one by one, is
>>>>>>> anyone have some suggestion of bactch file scrip to change the
>>>>>>> registry, that will save a lot of time.
>>>>>>>
>>>>>>> Thanks for any suggestion!
>>>>>>> Shermaine
>>>>>>
>>>>>> If you're talking about KB 302361 (Printers That Use Ports That
>>>>>> Do Not Begin With COM, LPT, or USB Are Not Redirected in a Remote
>>>>>> Desktop or Terminal Services Session), I believe this registry
>>>>>> change will be uneccessary if you upgrade everyone's RD client to
>>>>>> the latest version.
 
Back
Top