NT 4 User Accounts

[Shaun]

Anyone,

I am trying to programmatically change user accounts in
Windows NT 4. I am using Microsoft Visual Basic .NET
2003. The two things I am trying to do are as follows.

1. Set the User Cannot Change Password Checkbox.
2. Select the Account Disabled Checkbox.

Can anyone tell me how to do this?

Thanks

[Nak]

> I am trying to programmatically change user accounts in

Windows NT 4. I am using Microsoft Visual Basic .NET
2003. The two things I am trying to do are as follows.

1. Set the User Cannot Change Password Checkbox.
2. Select the Account Disabled Checkbox.

Hmm, forgive me, but one might question why?

Nick.

--
/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
"No matter. Whatever the outcome, you are changed."

Fergus - September 5th 2003
/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\

[Tom Spink]

User Admin program maybe? Automated account creation and attribute setting?
Network Administration tool for network supervisors? Network Administration
tool for computer illiterates... the list goes on and on.

In response to his question, he may need to take a look at the Net* API's.

--
HTH,
-- Tom Spink, Über Geek

Please respond to the newsgroup,
so all can benefit

"Maybe it's a game called 'Punish the User'"
"Nak" <[e-mail]> wrote in message
news:eq*************@TK2MSFTNGP11.phx.gbl...
: > I am trying to programmatically change user accounts in
: > Windows NT 4. I am using Microsoft Visual Basic .NET
: > 2003. The two things I am trying to do are as follows.
: >
: > 1. Set the User Cannot Change Password Checkbox.
: > 2. Select the Account Disabled Checkbox.
:
: Hmm, forgive me, but one might question why?
:
: Nick.
:
: --
:
/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
: "No matter. Whatever the outcome, you are changed."
:
: Fergus - September 5th 2003
:
/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
:
:

[Nak]

> User Admin program maybe? Automated account creation and attribute
setting?

Network Administration tool for network supervisors? Network Administration tool for computer illiterates... the list goes on and on.

Right, an application for fu*king accounts up too maybe? Who knows, who
knows...

Nick.

--
/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
"No matter. Whatever the outcome, you are changed."

Fergus - September 5th 2003
/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\

[Paul Clement]

On Tue, 16 Sep 2003 13:41:52 +0100, "Nak" <[e-mail]> wrote:

¤ > User Admin program maybe? Automated account creation and attribute
¤ setting?
¤ > Network Administration tool for network supervisors? Network
¤ Administration
¤ > tool for computer illiterates... the list goes on and on.
¤
¤ Right, an application for fu*king accounts up too maybe? Who knows, who
¤ knows...

No need to act ignorant.

Requirements for these types of tools is not uncommon.
Paul ~~~ pc******@ameritech.net
Microsoft MVP (Visual Basic)

[Nak]

> No need to act ignorant.

Well thanks for the advice Mr Clement, I shall take your thoughts into mind.

Requirements for these types of tools is not uncommon.

Personally I am not bothered whether people ask for code to mess other
peoples systems up or not. But just recently someone was asking for "ideas"
on what they could do to play a joke on a work associate, I gave suggestions
and everyone else thought it was "bad", though he *only* wanted ideas.

Now when someone asks how you disable accounts via code I wouldn't have
thought that there would have been an influx of answers, as this is allot
more serious than playing a simple joke on a work associate. Personally I
couldn't, nor can I still see the point in making software to do this, so
no, I was not "acting ignorant", but thanks for your concern anyway.

Nick.

--
/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
"No matter. Whatever the outcome, you are changed."

Fergus - September 5th 2003
/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\

[Paul Clement]

On Tue, 16 Sep 2003 17:39:12 +0100, "Nak" <[e-mail]> wrote:

¤ > No need to act ignorant.
¤
¤ Well thanks for the advice Mr Clement, I shall take your thoughts into mind.
¤
¤ > Requirements for these types of tools is not uncommon.
¤
¤ Personally I am not bothered whether people ask for code to mess other
¤ peoples systems up or not. But just recently someone was asking for "ideas"
¤ on what they could do to play a joke on a work associate, I gave suggestions
¤ and everyone else thought it was "bad", though he *only* wanted ideas.
¤
¤ Now when someone asks how you disable accounts via code I wouldn't have
¤ thought that there would have been an influx of answers, as this is allot
¤ more serious than playing a simple joke on a work associate. Personally I
¤ couldn't, nor can I still see the point in making software to do this, so
¤ no, I was not "acting ignorant", but thanks for your concern anyway.

Sometimes you need to provide access to your system to enable customers to manage their users that
work with your (typically web based) system. For obvious reasons you wouldn't necessarily want to
provide them with the standard set of tools. ;-)

Having an interface API (such as ADSI or System.DirectoryServices which will address the original
question) enables you to provide only those features required, thereby limiting the administrative
functionality that is actually available.
Paul ~~~ pc******@ameritech.net
Microsoft MVP (Visual Basic)

[Tom Spink]

Absolutely Agree. I've written many a network admin tool for non-technical
users to easily manage accounts and etc.

--
HTH,
-- Tom Spink, Über Geek

Please respond to the newsgroup,
so all can benefit

"Maybe it's a game called 'Punish the User'"
"Paul Clement" <Us***********************@swspectrum.com> wrote in message
news:js********************************@4ax.com...
: On Tue, 16 Sep 2003 17:39:12 +0100, "Nak" <[e-mail]> wrote:
:
: ¤ > No need to act ignorant.
: ¤
: ¤ Well thanks for the advice Mr Clement, I shall take your thoughts into
mind.
: ¤
: ¤ > Requirements for these types of tools is not uncommon.
: ¤
: ¤ Personally I am not bothered whether people ask for code to mess other
: ¤ peoples systems up or not. But just recently someone was asking for
"ideas"
: ¤ on what they could do to play a joke on a work associate, I gave
suggestions
: ¤ and everyone else thought it was "bad", though he *only* wanted ideas.
: ¤
: ¤ Now when someone asks how you disable accounts via code I wouldn't have
: ¤ thought that there would have been an influx of answers, as this is
allot
: ¤ more serious than playing a simple joke on a work associate. Personally
I
: ¤ couldn't, nor can I still see the point in making software to do this,
so
: ¤ no, I was not "acting ignorant", but thanks for your concern anyway.
:
: Sometimes you need to provide access to your system to enable customers to
manage their users that
: work with your (typically web based) system. For obvious reasons you
wouldn't necessarily want to
: provide them with the standard set of tools. ;-)
:
: Having an interface API (such as ADSI or System.DirectoryServices which
will address the original
: question) enables you to provide only those features required, thereby
limiting the administrative
: functionality that is actually available.
:
:
: Paul ~~~ pc******@ameritech.net
: Microsoft MVP (Visual Basic)

[jean3na]

I came across this thread when searching for information about how to change a user in my VB.Net code. Ideally I would like each clerk using my program to key in their user name and password and be authenticated before processing payments for a customer. The machine the clerks are using is at a front counter location and could be accessible to the general public. Assuming that I can do this then I would be able to save the clerk's user name with each payment transaction that the clerk processes.

I am hoping that there is an easy way to do this. Is the API interface (such as ADSI or System.DirectoryServices) the place for me to look?

Thanks,
Jean

[jean3na]

I forgot to mention that the users all have accounts (user names / passwords) in Windows2000. I am also hoping that changing a user sign on does not disrupt my program or any other programs that are open. The front counter PC should only allow access to programs that all of the clerks would normally be able to access.

Thanks,
Jean