I didnt bother reading through your debug files. I came across the
same thing the other day. My problem was that the policy i created was
for WinNT/2k/XP. Make sure that you drop down the tab and select
Terminal Server policies either 2k or XP and create a DLU policie in
there.
Let me know how it goes
+-------------------------------------------------------------------+
|Filename: Capture.jpg |
|Download: http://www.ndsengineers.com/attachment.php?attachmentid=30|
+-------------------------------------------------------------------+
--
archieZA
>>> On 2007-02-15 at 04:41, in message <45D4710B.F...@nospam.com>,
Dale
Bentley<da...@nospam.com> wrote:
> Hi,
>
> Yes the policy is for Terminal server 2000 or 2003 and yet it does not
> apply.
>
> The debug information must be able to be interpreted by someone who
> could shed light on why it does not apply. Strangely quiet on the
> suggestion front from anyone else. Has anyone had a similar that they can
> suggest what could be the workaround?
>
> Cheers,
> Dale.
>
>>>> archieZA<archieZ...@no-mx.nds_engineer.com> 15/02/2007 8:39 am
>>>
> Hi,
>
> I didnt bother reading through your debug files. I came across thesame
> thing the other day. My problem was that the policy i created wasfor
> WinNT/2k/XP. Make sure that you drop down the tab and selectTerminal
> Server policies either 2k or XP and create a DLU policie inthere.
>
> Let me know how it
goes+-------------------------------------------------------------------+|Fi
lename: Capture.jpg
The issue you could get with Windows password restrictions and DLU
is that you can not have a Windows password policy that is more
restrictive than the eDirectory password policy. If the Windows
policy is more restrictive, then the DLU account will not be created.
Regards
Rolf Lidvall
Swedish Radio (Ltd)
--
archieZA
For example, in my New York container, I have user account objects that
have no problem logging into Citrix and creating the DLU account. Also
in my New York container, I have alias user accounts that point to user
accounts in other partitioned containers. When a user tries to log into
Citrix with an alias user account the DLU account is not created on the
Citrix server.
The Citrix Server (MPS3.0) is located on the same subnet as the Novell
server (6.5sp5), Zenworks 6.5sp2 server and Edirectory server. The alias
user accounts in the New York Container point to user accounts located in
partitioned containers where the master replica for the container exist
on different subnets. (don't know if that makes a difference)
This being said, are the novell accounts being used to login referencing
alias user objects?
You may have already tried this, but check CTX737605
Like I said before, we have several containers with users who log into
Citrix. Only the NY user accounts were working with the DLU account
being automatically created. No alias' accounts were getting thier
respective DLU account.
In the Container Package (for each container), there is a Search Policy
which I had misconfigured. I stumbled accross this when I checked the
Zenworks Effective Policies on the user accounts. The results of
Effective Policies on a user account should include the DLU Policy. If
not, then the DLU will not be created. I adjusted the Search policy (by
setting it to "Associated Container" and "Search Level" 0) and verified
that the container associated User Package had the proper settings to
create the DLU and it worked.
Hope this helps.