After deploying to a IIS server could not find a way to start Web Admin Tool. Even VS2005 does not have a button/menu option to start it.

Souldn't it start directly using http://<server.com>/vdir/Webadmin.axd ?

Do I need to install/enable something?

(I'm using RTM version)

Joseas,

The ASP.NET Configuration web admin tool is only accessible on your development machine.  Instead of running through IIS, the tool uses the local ASP.NET Development Server (Cassini) to interact with your various web configuration files.  By experimenting with the tool locally, hopefully your production environment will

You should find the configuration tool under the "Website" menu.  However, it won't appear if you are editing your site live using FTP.  Let me know if you have any other questions.

- Jeff

There are functions of the Web Admin Tool are go beyond the config files though. For instance the tool can add/remove user and put them into roles. It appears as though this functionality will not be accessible remotely without rolling our own UI?

I have sucessfully uploaded and configured the Club starter kit onto my web server.  I have no problems adding roles and users on my dev server... how do I do these tasks on my production server?  I hook up via ftp and your right.. there is no configuration tool on the menu.  That option is only available when you work locally.
Thanks...
-Rob in Tampa

I have been able installed WebAdminTool for Production Servers using the following steps:

Create a virtual directory ASP.NETWebAdminFiles in IIS that point to C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\ASP.NETWebAdminFiles

Open properties windows of the new virtual directory, make sure that it is configured to run with ASP.NET 2.0, and in Security tab, uncheck Anonymous Access, check Integrated Windows Authentication.

After that, you will be able to connect to WebAdminTools using the following syntax
http://localhost/ASP.NETWebAdminFiles/default.aspx?applicationPhysicalPath=XXX&applicationUrl=/YYY
in my case, it is:
http://localhost/ASP.NETWebAdminFiles/default.aspx?applicationPhysicalPath=D:\Tasks\Libranyon\Photonyon\&applicationUrl=/Photonyon

Although I don't recommend to do it, if you want to access WebAdminTool from other computer, open WebAdminPage.cs from (C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\ASP.NETWebAdminFiles\App_Code) and comment the following code block
            if (!application.Context.Request.IsLocal) {
                SecurityException securityException = new SecurityException((string)HttpContext.GetGlobalResourceObject("GlobalResources", "WebAdmin_ConfigurationIsLocalOnly"));
                WebAdminPage.SetCurrentException(application.Context, securityException);
                application.Server.Transfer("~/error.aspx");
            }
WebAdminTool still be protected by Intergrated Windows Authentication, so you still some have some defense here.

Finally,

Somebody posted completed answer.

 

Thank you very much.

 

Alex

This looks great, but I do not understand how I determine the applicationUrl.  I have tried everything and I am not understanding what it should be.  Is it something I can copy/paste from IIS?

Thanks, Mike

this access url http://localhost/ASP.NETWebAdminFiles/default.aspx?applicationPhysicalPath=D:\Tasks\Libranyon\Photonyon\&applicationUrl=/Photonyon

means you copied your file to D:\Tasks\Libranyon\Photonyon\

and this folder is "web shared" using Photonyon so the published url is http://localhost/Photonyo

Please forgive me, I really want this to work, but I do not understand what is going on.  I have a Windows 2000 Server.  I have a folder under the C drive named TTETranscriptsIntranet2.  When you check the web sharing for this, it simply states it is web shared as '/'.  When I try to go to http://localhost/TTETranscriptsIntranet2, I just get a page not found error.  Since I setup a virtual folder for the ASP.NETWebAdminFiles directory I also tried http://localhost/ASP.NETWebAdminfiles and got nothing from that either.  I threw a 'default.aspx' on the end and received a " 'Could not load type 'Email_Excel.Global' " error.  It is just a new Windows 2000 server with the standard IIS running.  Nothing special or configured differently.  If anyone knows what my problem is, besides not being a Windows Admin, I could really use some help.  Appreciate it.

Hi ,

Need help.

Is it possible read web.config file of V1.1 in an application from V2.0 ?

or Read the configuration file located outside the application root.

using webAdmin Tool in any  way,

Thanks,

Sasi

Hi,

One more cool tip for streamlining the webadmin - you can set the application path and application physical path programmatically by putting these lines:

Session["WebAdminPhysicalPath"] = @"C:\Inetput\wwwroot_yourwebsitepath";

Session["WebAdminApplicationPath"] = @"http://youwebsiteaddress.com";

in the OnInit() function inside default.aspx. 

Or alternatively, you can create another form that authenticates the users, and sets these session values accordingly, and redirects.  You can impersonate a privileged windows user account for this application that has all the windows rights you need, and voila, you have forms based authentication.  Theres a few more things you should change to secure things properly going this route, but that should give you a good start.

khaivq:

I have been able installed WebAdminTool for Production Servers using the following steps:

Create a virtual directory ASP.NETWebAdminFiles in IIS that point to C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\ASP.NETWebAdminFiles

Open properties windows of the new virtual directory, make sure that it is configured to run with ASP.NET 2.0, and in Security tab, uncheck Anonymous Access, check Integrated Windows Authentication.

After that, you will be able to connect to WebAdminTools using the following syntax
http://localhost/ASP.NETWebAdminFiles/default.aspx?applicationPhysicalPath=XXX&applicationUrl=/YYY
in my case, it is:
http://localhost/ASP.NETWebAdminFiles/default.aspx?applicationPhysicalPath=D:\Tasks\Libranyon\Photonyon\&applicationUrl=/Photonyon

Although I don't recommend to do it, if you want to access WebAdminTool from other computer, open WebAdminPage.cs from (C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\ASP.NETWebAdminFiles\App_Code) and comment the following code block
            if (!application.Context.Request.IsLocal) {
                SecurityException securityException = new SecurityException((string)HttpContext.GetGlobalResourceObject("GlobalResources", "WebAdmin_ConfigurationIsLocalOnly"));
                WebAdminPage.SetCurrentException(application.Context, securityException);
                application.Server.Transfer("~/error.aspx");
            }
WebAdminTool still be protected by Intergrated Windows Authentication, so you still some have some defense here.

Hi khaivq,

Your post on http://forums.asp.net/p/932674/1155428.aspx is very useful. I got it working on a development machine (and also a virtual machine). However, when I transferred it to a production machine, I keep getting the message "This tool cannot be remotely accessed.". Very frustating! I have checked that both machines have the same setup:

1. Operating system (Windows 2000 Server SP4)

2. .NET version (2.0)

3. Directory structure: web application is installed in E:\BusinessReporting, Website Administration Tool website is in E:\BusinessReporting\ASP.NETWebAdminFiles.

4. Virtual directory set up for E:\BusinessReporting\ASP.NETWebAdminFiles, using ASP.NET 2.0, Directory Security set to Integrated Windows Authentication.

5. Link to the WSAT:
   Response.Redirect("http://" & Server.MachineName() & "/asp.netwebadminfiles/default.aspx?applicationPhysicalPath=E:\BusinessReporting\&applicationUrl=/BusinessReporting")

I wasn't sure about whether Integrated Windows Authentication was working on the development and production machines but for both machines, from my workstation:

User.Identity.AuthenticationType = Negotiate
User.Identity.IsAuthenticated = True

The impersonated account is an Administrator so there shouldn't be any permissions issue.

I think that if I reinstall everything on the production server, it will probably work but I'm hoping to avoid this.

Is there something I've missed?

Thanks in advance for any help.

Kui Meng Ng.

Help me.

My problem is user credential is not validating on published path.

development machine and production machine is same.

development path e:\webproject    

published path e:\webonline

first page is login page. User created and through web->asp.net configuration menu of vs. now all is working fine in development. but after publishing when i m accessing through internet browser i.e http://localhost/webonline , login page is coming but user credential is not validating and not allowing to log on.