> maybe a stupid question but to change my current script from winnt to ldap
> its not as simple as replacing winnt:// with ldap:// right?
>
>
> "nobody" <nobody[ at ]nobody.com> wrote in message
> news:%23VuoCkxwHHA.1208[ at ]TK2MSFTNGP05.phx.gbl...
>> Hi there
>>
>> I am reading this on your site but says winnt can reveal nested groups?
>>
>>
http://www.rlmueller.net/Nested%20Groups.htm>>
>>
>> I am using Ismember function and Winnt
>>
>> "Richard Mueller [MVP]" <rlmueller-nospam[ at ]ameritech.nospam.net> wrote in
>> message news:u5TnYPxwHHA.1852[ at ]TK2MSFTNGP04.phx.gbl...
>>>
>>> "nobody" <nobody[ at ]nobody.com> wrote in message
>>> news:%23UJg1JxwHHA.3588[ at ]TK2MSFTNGP06.phx.gbl...
>>>>I have a script that basically maps drives and printers based on domain
>>>>local groups. Its using the winnt provider which I think should support
>>>>nested groups.
>>>>
>>>> SO I created one group with some users in it. The script maps drivers
>>>> and printers based on this group. Then I greated another group and put
>>>> it into the first group. Now the users in the second group are not
>>>> getting mapped drives.
>>>>
>>>> Any idea?
>>>>
>>>
>>> The WinNT provider is blind to the hierarchy of AD, including nested
>>> domain Global and Universal security groups. It does recognize nested
>>> local groups. You cannot use the WinNT provider to reveal membership in
>>> nested domain groups. You must use the LDAP provider. I have an example
>>> VBScript logon script that maps drives and printers according to group
>>> membership linked here:
>>>
>>>
http://www.rlmueller.net/Logon3.htm>>>
>>> --
>>> Richard Mueller
>>> Microsoft MVP Scripting and ADSI
>>> Hilltop Lab -
http://www.rlmueller.net>>> --
>>>
>>>
>>
>>
>
>