EXE. However, if you have large IIS server farms and need to make changes to multiple
servers and multiple sites, it might make sense to script the changes using APPCMD.EXE.
The following example shows how to lock and unlock the defaultDocument feature in
the default configuration using APPCMD.EXE:
APPCMD.EXE lock config /section:defaultDocument
APPCMD.EXE unlock config /section:defaultDocument
You can also lock or unlock a feature for a specific Web site. For example, to lock and
unlock the defaultDocument feature on a site called IT Homepage, you can run this:
APPCMD.EXE lock config "IT Homepage/" /section:defaultDocument
APPCMD.EXE unlock config "IT Homepage/" /section:defaultDocument
The biggest question you must have now is ???How do I find out the section names????
The section names used as parameters to APPCMD.EXE are the names of the various
features as they are used within the application.config XML file. It would be nice if you
could use the more user-friendly version of these names, as displayed in the IIS Manager,
but you can??™t. The easiest way to get the names is to look them up in the ???IIS Manager
Feature to Configuration Mapping??? article on IIS.NET (www.iis.net/default.aspx?tabid
=2&subtabid=25&i=1032). You can also open the application.config XML file and look
up the section name there, although you may have to do a bit of searching and scrolling
to identify the right section name.
Pages:
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253