03-16-06 12:49 PM
http://blogs.msdn.com/david.wang/ar...Permission.aspx
Write permission in IIS has no bearing on FileSystemObject being able to
Write a file. As the blog describes, they are two separate concepts that
users frequently mix up.
So, all you did was enable WebDAV. Fortunately, WebDAV is disabled by
default in Web Service Extensions. Whew; IIS6's defense in depth just saved
you from your mistake.
As for "missing IUSR" -- IIS never gives NTFS WRITE permission to IUSR, so
you are basically asking why a custom configuration on your old server was
not present on the new server. I can only point at the man in the mirror for
this misconfiguration.
There are no ACL differences between Windows Server 2003 Standard and
Windows Server 2003 Web. It's the same IIS6 binaries. Any difference you
observe is either user-initiated or inherited from an upgrade. Maybe your
Windows Server 2003 Standard server was an upgrade from NT4 or Windows
2000 -- upgrades will preserve old crusty ACLs. I always clean install and
then migrate sites for the best possible experience. IIS6 security settings
are different between Upgrade and Clean install, with Clean install the most
secure.
--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Joey Martin" <joey@kytechs.com> wrote in message
news:uuZ%23o4GSGHA.4792@TK2MSFTNGP14.phx.gbl...
>I moved web server (from Server 2003 Standard to Server 2003 Web
> Edition).
>
> I noticed that permissions hasve changed some under IIS. My asp page
> uses FileSystemObject to write file. My old server, this worked fine.
>
> I have verified that WRITE permission is enabled under IIS. But, Under
> PERMISSIONS, I noticed that I_USR is missing. When I add it, my WRITE
> command works. On my old server, the I_USR shows that it's inheriting
> rights from the parent. What would be the parent directory under IIS? I
> looked under Windows Explorer and the main directory does not have
> I_USR. Ideas??
>
>
>
> *** Sent via Developersdex http://www.codecomments.com ***
[ Post a follow-up to this message ]
|