iammi Absent Member.
Absent Member.
398 views

ADSI calls from AD Driver to handle "userParameters" attr


Hello every one,

I have to set Terminal Server Informations for my created users on
Active Directory , this data is stored in "userParameters" attributes a
little special, we can not set it via LDAP operations , and
out-of-the-box NIM does not allow operations on this attribut

The only way to edit this attribut is via ADSI Calls, is there any way
to perform ADSI calls from NIM Active Directory Driver ? any
documentation ?

Thanks in advance.


--
iammi
------------------------------------------------------------------------
iammi's Profile: http://forums.novell.com/member.php?userid=71308
View this thread: http://forums.novell.com/showthread.php?t=450052

Labels (1)
0 Likes
3 Replies
Anonymous_User Absent Member.
Absent Member.

Re: ADSI calls from AD Driver to handle "userParameters" attr

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Aside from the ones mentioned in the docs via some pseudo-attributes
that the driver can handle, this would probably be best-accomplished via
a scripting driver that can make arbitrary calls as you would like it to.

Good luck.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.15 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJO+08RAAoJEF+XTK08PnB5hN0P/05xrpzWj+YP2Ukw91p/wYm/
ZdnXrGbdNCeT62VOqhv1igZYIoPOmlAuNcgVeGv3aqESNIaeFQlNjZ1o7O1Rb30T
p0CgOswG1gnHJcd8gVr+dPZZza+/BfS9ESuUu3BAPgCBcSdehJyZHsR1psYy2tIl
BGk4y6pYHmNAgFhIonz8rumwxOTQtpa3XFPboR5zIG0m/C84n+q2s/exljeTirpT
338B2WVqy0SR6ZJfdrxLk3zsXstjDiBK2EgPaG0LhbE5lKFaD9+4fqQXi101/6ez
mywZ0TEsKhXkA41YNSZkC2A0zb1QiAwAjuREbNvYemj8o5cUKkEOEzTKaFOXVvHg
xNmlh6tjwh8+wS5oAZxUQeii5KalFx3MTRYcr2/5r/rZyULQf+blTvTnloyg3rhI
DttPUq47BZMzPWJRdomWw8PZyN9nhl7dMtaHfHkVXcmLPPNWNuWFfx6M/LbfUhb4
6ZAfXOYad2QnFydyns6/wWxNYmK39qLdKuqXDHGiOB57zkSBMateXmHDT5ZveiQ3
Sw+JPM/Xvh74FdG93Qytofmmr2hkkYkCYctFCoc361Jkhp1ZktEvg/L8ds+oDEPQ
3zPR092eukOCXOEb9ueBIOB2nAcDcz+R1XFI7XuWZPltYXKJFExQ1duJc4IqDBTW
Zkfuolz0oHA7Qw6GOFxD
=7wQi
-----END PGP SIGNATURE-----
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: ADSI calls from AD Driver to handle "userParameters" attr

The other way Ihave handled this before is to set an unused attribute as a 'trigger' value in AD, then have an AD side script that runs on the
accounts with the trigger value set, sets the terminal server bits, and then clears the trigger value.

We should probably enter an enhancement request to add support for these into the driver.

On 12/28/2011 11:17 AM, ab wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Aside from the ones mentioned in the docs via some pseudo-attributes
> that the driver can handle, this would probably be best-accomplished via
> a scripting driver that can make arbitrary calls as you would like it to.
>
> Good luck.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.15 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iQIcBAEBAgAGBQJO+08RAAoJEF+XTK08PnB5hN0P/05xrpzWj+YP2Ukw91p/wYm/
> ZdnXrGbdNCeT62VOqhv1igZYIoPOmlAuNcgVeGv3aqESNIaeFQlNjZ1o7O1Rb30T
> p0CgOswG1gnHJcd8gVr+dPZZza+/BfS9ESuUu3BAPgCBcSdehJyZHsR1psYy2tIl
> BGk4y6pYHmNAgFhIonz8rumwxOTQtpa3XFPboR5zIG0m/C84n+q2s/exljeTirpT
> 338B2WVqy0SR6ZJfdrxLk3zsXstjDiBK2EgPaG0LhbE5lKFaD9+4fqQXi101/6ez
> mywZ0TEsKhXkA41YNSZkC2A0zb1QiAwAjuREbNvYemj8o5cUKkEOEzTKaFOXVvHg
> xNmlh6tjwh8+wS5oAZxUQeii5KalFx3MTRYcr2/5r/rZyULQf+blTvTnloyg3rhI
> DttPUq47BZMzPWJRdomWw8PZyN9nhl7dMtaHfHkVXcmLPPNWNuWFfx6M/LbfUhb4
> 6ZAfXOYad2QnFydyns6/wWxNYmK39qLdKuqXDHGiOB57zkSBMateXmHDT5ZveiQ3
> Sw+JPM/Xvh74FdG93Qytofmmr2hkkYkCYctFCoc361Jkhp1ZktEvg/L8ds+oDEPQ
> 3zPR092eukOCXOEb9ueBIOB2nAcDcz+R1XFI7XuWZPltYXKJFExQ1duJc4IqDBTW
> Zkfuolz0oHA7Qw6GOFxD
> =7wQi
> -----END PGP SIGNATURE-----


0 Likes
Knowledge Partner
Knowledge Partner

Re: ADSI calls from AD Driver to handle "userParameters" attr

On 1/3/2012 11:49 AM, Will Schneider wrote:
> The other way Ihave handled this before is to set an unused attribute as
> a 'trigger' value in AD, then have an AD side script that runs on the
> accounts with the trigger value set, sets the terminal server bits, and
> then clears the trigger value.
>
> We should probably enter an enhancement request to add support for these
> into the driver.


For those who do not quite understand it, the RMS system
(www.novell.com/rms) is designed to let the customers tell novell how
important stuff is.

So the more requests for the same feature makes it seem more desirable.

So I would recommend everyone who wants this, or cares, to open an RMS
enhancement request.

If you can specify how large your license is, larger the better, that is
even better. Seats, users, etc...

It takes about two minutes to do, and the more they see, the more likely
the product manager is to consider it.




> On 12/28/2011 11:17 AM, ab wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Aside from the ones mentioned in the docs via some pseudo-attributes
>> that the driver can handle, this would probably be best-accomplished via
>> a scripting driver that can make arbitrary calls as you would like it to.
>>
>> Good luck.
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v2.0.15 (GNU/Linux)
>> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>>
>> iQIcBAEBAgAGBQJO+08RAAoJEF+XTK08PnB5hN0P/05xrpzWj+YP2Ukw91p/wYm/
>> ZdnXrGbdNCeT62VOqhv1igZYIoPOmlAuNcgVeGv3aqESNIaeFQlNjZ1o7O1Rb30T
>> p0CgOswG1gnHJcd8gVr+dPZZza+/BfS9ESuUu3BAPgCBcSdehJyZHsR1psYy2tIl
>> BGk4y6pYHmNAgFhIonz8rumwxOTQtpa3XFPboR5zIG0m/C84n+q2s/exljeTirpT
>> 338B2WVqy0SR6ZJfdrxLk3zsXstjDiBK2EgPaG0LhbE5lKFaD9+4fqQXi101/6ez
>> mywZ0TEsKhXkA41YNSZkC2A0zb1QiAwAjuREbNvYemj8o5cUKkEOEzTKaFOXVvHg
>> xNmlh6tjwh8+wS5oAZxUQeii5KalFx3MTRYcr2/5r/rZyULQf+blTvTnloyg3rhI
>> DttPUq47BZMzPWJRdomWw8PZyN9nhl7dMtaHfHkVXcmLPPNWNuWFfx6M/LbfUhb4
>> 6ZAfXOYad2QnFydyns6/wWxNYmK39qLdKuqXDHGiOB57zkSBMateXmHDT5ZveiQ3
>> Sw+JPM/Xvh74FdG93Qytofmmr2hkkYkCYctFCoc361Jkhp1ZktEvg/L8ds+oDEPQ
>> 3zPR092eukOCXOEb9ueBIOB2nAcDcz+R1XFI7XuWZPltYXKJFExQ1duJc4IqDBTW
>> Zkfuolz0oHA7Qw6GOFxD
>> =7wQi
>> -----END PGP SIGNATURE-----

>


0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.