As pointed out, the script still does exist.
However, if you create a new vb.net "webforms" project?
It can (and will) build up the data base for you. And that database MUCH follows the same format as the older asp.net "webforms" authenticaiton. Older templates did use what is called FBA (forms based authentication).
However, the newer "owin" system? You not notice the difference anyway.
I suggest (assuming vs2022 - the free community edition) that you try a working template. The database will be created for you, and you don't even have to run some script. (it is automatic created for you).
So, create a new project, vb.net, asp.net, .net framework.
This project choice:
And then to have the "logon" data base created for you, then after above, choose this option:
So, above will create a database, and the database follows VERY much and close to how the previous FBA (logon database) worked.
I would suggest you find some tutorials, even perhaps you-tube ones. Or get a book. So, if it has been some time, then the efforts and "dance" to get the FBA and that aspnet_regsql "sql script" creator is not really required.
With above template, then the database created is VERY close to that older setup. You get/see this for the database, and it is created automatic for you:
So, the old FBA system had users, roles, user in roles. It really is VERY close to what you had, but you don't have to go dig around and run that aspnet_regsql thing anyway.
Now to be fair, the "moving" parts in the older system, or above? It is about the same, and the less you worry about the above user logon database , the better. In other words, just let the system create the database of logons for you.
I think about the only "possible" reason to use the older FBA system is that if you have a existing database of users and want to use a "different" table then the default table created for users. However, that table of users and how this works as noted is rather close to the older system anyway.
I currently run one site with FBA logons, and without question the roles and users etc. was created using that aspnet_regsql to create the logon tables, but I can't see it much of a issue to adopt the new default setup, since out of the box is works and is automatic setup for you. So, pick the above "individual accounts", and the result is very much like the older system and "logon database" used.
My suggestion is in fact to get/grab/move that database created in the project into SQL server express (assuming you installed and setup that on your local PC for development and testing). This will require you change the connection strings in web.config, but after doing that, then the setup is even MORE like the older FBA system anyway.
Both systems (older FBA, or newer owin) do and did require quite a bit of setup, but the template will setup all of this for you out of the box without any efforts on your part.