I posted earlier about how to remotely administer an IIS 6.0 machine from Windows XP, which works great until you need to remotely configure an ASP.NET 2.0 application (from the ASP.NET tab that’s added by the installer). One of the great things about IIS 6.0 is that we now have a gui front end to most of the <processModel> elements from the old 1.x machine.config file via application pools; now with ASP.NET 2.0 we have a gui front end for most of the elements in web.config…but it doesn’t really do much good if you either have to RDP into the remote machine, or go physically sit at the terminal to get any of that done (from a remote machine the “edit configuration” button is grayed out).
So after a little research/trial and error, I discovered a simple switch you can throw to enable remote configuration of your ASP.NET 2.0 applications:
- Navigate to your .Net 2.0.x installation folder in your command shell of choice.
- Run aspnet_regiis -i -enable (note that this will in effect issue an iisreset during the process, so take care on production machines not to do this at peak hours).
Voila…you can now remotely configure your 2.0 apps. This may be old news to some, but it’s definitely news to me and simplifies remote configuration as you don’t have to RDP into the box itself.