TrustedLogon on desktop clients & domains

jman

Hi,

Suppose I have a Windows domain called “abc” and in their AD it’s “abc.net”, WSMP trustee are sync from AD so the domain of the trustees are “abc.net”. In a client PC, the Windows login will be in the format like “abc/peter” and their Trusted Logon on desktop clients are working fine.

Here’s the question, how come the desktop client can map “abc/peter” to the WSMP trustee “abc.net/peter”? Looks like there’s some “magic” to handle this. For web component, we have to use the “ADS Domain Extension” to make Trusted Logon works.

Any idea on the “magic”?

Thanks,

John

sphan_xell

Trusted logon for desktop clients pick up what's called the "Workstation Domain DNS Name". You can see what this is by typing "net config workstation" from the command line. The webapp, on the other hand, picks up only the "Logon Domain" (e.g. "abc") so a domain extension (e.g. ".net") will need to be configured OR provide a "Fully Qualified Domain".