What kind of object are you trying to create??
...is the 'usermanager' a separate/third party component.
why not just use ADSI to create your NT account??
Create NT account code snippet..
at its most basic form..
replace machine name with local server name and make sure you have the necessary rights to run the script
good luck!
- -- -
Set oDomain = GetObject("WinNT://WinntMachine")
Set oUser = oDomain.Create ("user", "NewUSerName")
oUser.SetPassword "password"
oUser.SetInfo
----
at its most simplest form...
the basic code..u still need to work on this (i.e error checking, etc). Try looking up the ADSI section at http://www.15seconds.com for more help and code snippets.
Also the originial *.vbs files can be easily modifed to work with ASP.
*ps: if you're interested in taking this further i.e. developing a custom NT panel professionally kindly contact me offline
- - - -
NextInst = server next instance number (you can also script a procedure to automatically get the next server instance number)
Ipadd = ip address
portnum = 80
hostheader = if any host header it goes in here
sTruepath = foldpaer path .. ie. c:\inetpub\xxx
Response.Write "Creating the New Site.."
Set IIsNewObj = WebServerObj.Create ("IIsWebServer", NextInst)
IIsNewObj.ServerComment = "ServerComment"
IIsNewObj.ServerBindings = IpAdd&":"&PortNum&":"&HostHeader
IIsNewObj.SetInfo
Response.Write "Creating Site Root..."
set IIsNewRootObj = IIsNewObj.Create("IIsWebVirtualDir", "Root")
IIsNewRootObj.Path = sTruePath
IIsNewRootObj.SetInfo
..only learning as I go along..
..I havent tried binding the IP to the NIc yet..ASDI probably wouldnt be a good candidate for stuff like that.
you could off course use a *.vbs sript which called the wscript command to do something similiar.
also..try looking up WMI
There is definitely market for such products..
..at this point of time.
I also know of local dedicated companies who are very interested in such products... and will be demoing it to them soon.
The only reason I can't put mine up for public demo yet is because mine is built on a 90% ASP based solution (with 1-2 odd dlls), therefore protecting the source will be an issue. I know of one method which is to use the VBscript Encoder which works to some extent, but the better alternative would be to encapsulate the those into COM objects (dlls)
..... like someone mentioned before..it will be awhile till we see any GPL products :-)
but feel free to post any odds questions which you might have regarding the coding... If I know the answer I'll help out
happy coding !