[THIN] Re: Autocreated printers fail to work normally after schema upgrade domain to W2K3
- From: Michel Roth <mrdizzz@xxxxxxxxx>
- To: thin@xxxxxxxxxxxxx
- Date: Thu, 20 Oct 2005 07:39:43 +0200
I meant that a forgotten client printer policy might overrule the AD printer
properties. No events being logged in eventvwr when a client printer isn't
being created?
2005/10/19, Matthew Shrewsbury <MShrewsbury@xxxxxxxxxxxxxxx>:
>
> I can use the client printer policy. However I need to control this
> setting on a per user bases and when I set it in the policy everyone gets
> the setting.
>
> *Matthew** Shrewsbury**, *MCSE+Internet MCSE 2000 CCA Server+
>
> Senior Network Administrator
>
> -----Original Message-----
> *From:* thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] *On
> Behalf Of *Michel Roth
> *Sent:* Wednesday, October 19, 2005 2:43 AM
> *To:* thin@xxxxxxxxxxxxx
> *Subject:* [THIN] Re: Autocreated printers fail to work normally after
> schema upgrade domain to W2K3
>
> Client printer policy?
>
> 2005/10/18, Matthew Shrewsbury <MShrewsbury@xxxxxxxxxxxxxxx>:
>
> Autocreated printers are no longer working based on how the AD account is
> configured. In the users account under the "environment tab" in AD I
> normally specify weather to "Connnect client printers at logon" and "Default
> to main client printer". Some users I don't check these options because I
> use logon scripts to map their printers.
>
> Currently no matter what setting I set in AD it has no effect on the user
> when they logon to Citrix. However the "Connect client drives at logon" does
> work correctly.
>
> I don't know when this problem first started but my guess is it started
> when I upgraded the AD schema for our first W2K3 domain controller. The only
> other change I made is a few months back I installed Citrix FR3 SP4.
>
> Any idea why these AD settings don't take effect in Citrix?
>
> *Matthew Shrewsbury, *MCSE+Internet MCSE 2000 CCA Server+
>
> Senior Network Administrator
>
>
Other related posts:
