\Inetpub\wwwroot\ directory
While you can do that, I question why one would
want to do that. I prefer to set a new otherwise
unused partition to have Adminsitrators Full at the
root, then build a directory structure such as
x:\
x:\site1name
x:\site1name\root
x:\site2name
x:\site2name\root
and some others for mgmt sake under each
x:\siteNname
Then, redefine where the website has its root
as x:\siteNname\root
following which, examine how permissions were
tweaked by doing this on the parent chain upwards
starting at x:\siteNname\root (and take into account
the principal to be used in place of IUSR_ / IWAM_
for that website)
If you just move all of inetpub
1. you may be moving things you do not want to have at all
2. you are moving your ftproot (if used) and your smtp all
too the same place, which may be (is) ill-advised
(Actually, at the partition root I also set a couple
other things, like an audit ACL for any failure from
any account, and deny of writes for the anonymous
users and web applications groups IIS lockdown
creates. These last cause the need to micro-manage
allowing write where, but only where, desired.
Also, you may need to loosen things a small amount
partially up the parent chain for FPSE authoring or
Asp.Net, both if in use and depending on version)
|