STEVE: Can you open another thread with the rights of a built-in account to an UNC share? This thread here gets too complicated if I answer it here.
I'm setting up a VM with the Longhorn CTP and see if I can reproduce the error. The way the accounts are defined are different in IIS7. It is nice the login is reduced to just use the application pool user id vs. having it defined in the anonymous section, then the application pool settings.
Just the option of using a setup like I described using domain accounts seems different in IIS7. I didn't realize the username and password are not validated. I guess this is the same in IIS6, so the behavior is consistant, maybe it is the UI changes that make it seem different. All the press and articles cover the new built-in users, which is cool. When I ran into an issue, I probably should have posted. I'll have some results from my testing.
Here are the steps I'm going to test. The IIS_WPG is of course the IIS_USERS group on IIS7.
I haven't tried on the latest CTP yet, however I ran into issues on previous builds of Longhorn. The way you did this in IIS6 would be to
1) create a domain account
2) add the domain account to the IIS_WPG group
3) adjust the anonyous user and application pool user to use this domain account. When using IIS manager, it would allow you to browse and add the user.
or you could
1) create a domain account
2) create a global group
3) put the domain account in the global group
4) then put the global group in the IIS_WPG group.
Steve Schofield
Windows Server MVP - IIS
http://weblogs.asp.net/steveschofield
http://www.IISLogs.comLog archival solution
Install, Configure, Forget