>>>>>>>>Hi,
>>>>>>>>
>>>>>>>>I am in the process of installing an ASP.NET app on the customer virtual server. When I try to run a simple (one line) test.aspx, I get this message:
>>>>>>>>
>>>>>>>>

>>>>>>>>Error message 401.2.: Unauthorized: Logon failed due to server configuration.  Verify that you have permission to
>>>>>>>> view this directory or page based on the credentials you supplied and the authentication methods enabled on the
>>>>>>>> Web server.  Contact the Web server's administrator for additional assistance.
>>>>>>>>

>>>>>>>>
>>>>>>>>What permissions should I be looking at?
>>>>>>>>
>>>>>>>>Additional information. This is Server 2008 64-bit.
>>>>>>>
>>>>>>>Can you attach the web.config you are using?
>>>>>>>
>>>>>>>Have you configured the default page for the website in IIS (you can set start page in you aspnet project, but sometimes IIS ignores that when you publish).
>>>>>>
>>>>>>You were right; it was my web.config. By mistake, I copied to the customer site "my" copy of web.config that I use for testing on my computer. And it has a million settings. Once I replaced this copy of web.config with my "light" web.config, I can see the page. Sorry for troubling you guys with my silly questions.
>>>>>>
>>>>>>Thank you.
>>>>>
>>>>>:-}
>>>>>
>>>>>Best way of avoiding a recurrence of that problem is to take the time to setup web.config transforms:
>>>>>http://msdn.microsoft.com/en-us/library/dd465318.aspx
>>>>
>>>>Thank you for the link; I will read it. My deployment is usually done via 1980s approach <g>. I copy a ZIP file to the customer site and then unzip it there.
>>>
>>>I've never used it that way but I assume it would still work when building a deployment package. It's not as difficult to set up as it sounds and the ability that it gives to fine tune the config settings depending on the deployment is well worth the effort.....
>>
>>Keep in mind, also, that during the deployment I have to make many changes to the web.config on the customer's site. There many "keys" defined in the web.config that are used to "customize" the app for each customer.
>
>That's the whole point - you have a core web.config and use a separate transform for any deployment where modifications are needed.

I see your point. Thank you.