Web Services - ASP.NET

[RockLobster]

Has anyone used them?

I'm going to be developing a web page in ASP.NET so users can register their own accounts. This is the process: -

Create the user in Active Directory.
Create a folder on our file server for the user.
Create a share for the folder.
Set a quota on the folder (20mb each).
Create an exchange mailbox and set the mailbox to 10mb.

What I'm going to do is create a page where they have to verify it is actually them and if it is they can create their own account. I will be invoking a web service to do the above steps. Does anyone think this could be problematic?

 

[oldbag]

Won't they need an account on the machine first before they can create their own account? And what stops them from creating more than one account? What makes them not follow the company standard login naming convention? What stops them not putting in offensive user names?

 

[RockLobster]

We will have a standard account purely for this purpose. They will only be able to create one account because they will be issued with a security code. With the login naming convention I will be pulling that from our MIS system so it will be read only.