I have a user with no description attribute.
Anyone know why this works?
User.Invoke(put, New Object() {description, txtBxNewDescription.Text})
User.commitChanges
but this doesn't
User.Properties(Description).Add(txtBxNewDescription.Text)
User.commitChanges
I get the following error
They aren't equivalent. Try using the .Value property instead:
user.Properties(description).Value =
Description is a funny property in AD in that the schema says that it allows
multiple values, but the DS itself will only allow it to contain a single
value for backward compatibility
It worked. Thanks a million. Hopefully my hair won't take to long to grow back.
I bought your book last week from amazon. I currently reading chapter 3.
Actually took your example code. See 3.13.vb. Isn't that funny?
I thought DirectoryServices was a wrapper to ADSI? Why do you say they are not
I'm saying that those two are not equivalent functions under the hood. Add
typically does a PutEx with the append flag, while Put just does a put,
which is essentially an LDAP update operation. I think you would have the
same problem if you invoked PutEx and used the Append flag.
.Value
That is a problem only on SAM based objects (groups, users, computers).
Anything that isn't SAM based can have multiple values. :) That makes it
even more fun.
--
O'Reilly Active Directory Third Edition -
http://www.joeware.net/win/ad3e.htm
-Original Message-
From: [EMAIL
Thanks for the info, I actually understand, and please don't take my comments
as a complaint. So far I love the book, there isn't anything out there that
comes close to have so much information on directory services. I have been
programming with DSS for about 1 year now and let me tell ya,
One last comment Joe,
Do you think that is a bug with DSS? That now means depending of the attribute,
you have to use different method? Kinda makes it complicated don't you think?.
Now I have to hard code attribute names in my program.
if attribute=description do this
else
do it this way.
Anyone?
On 11/22/06, Dan DeStefano [EMAIL PROTECTED] wrote:
Is there a way to place restrictions on which rules users can create in
Outlook, like disallowing users to create an auto-forward rule? I would like
to control these settings by group membership.
Thanks in advance for any help,
Not exactly no, but you can block Auto-Forwards at the server side if
you have an Exchange server. At least for Internet mail addresses.
Ben M. Schorr
Chief Executive Officer
__
Roland Schorr Tower
www.rolandschorr.com http://www.rolandschorr.com/
I'm not sure if it is a bug or not. Generally, I always use .Value to set
a value and only use Add if I'm explicitly trying to add an additional value
to a multi-valued attribute that already has values. Same basic approach
for Remove. That helps keep me out of trouble. :)
It is
Hi guys,
A bit late to the party (I'm technically on holidays this week), but...
The best solution I have seen around the security question of new accounts
that haven't been used is to start with them disabled and then have the user
go to a kiosk machine which goes to a website where they have
11 matches
Mail list logo
