Hi I was trying to use PFDAVAdmin on our Exchange 2007 SP3 but was running in to some authentication issues. After some digging around for a solution I noticed that the Exadmin site in IIS is configured with the wrong physical path BUT what is the correct path? Lasse/Lasse

ISTR it's very similar to (if not the same as) the Exchange one with a path of \\.\BackOfficeStorage\domain.com\MBX . This isn't a path you can manually enter in the IIS interface, since it's a virtual share exposed by Exchange's IFS (installable file system), which IIS can't see. If you try to browse to it, or type it in, IIS will give an error message (which may be why you think there's something wrong with it). The only way to recreate it, if you are sure that the VDir is wrecked, is with the PS command New-OWAVirtualDirectory , supplied with a -VirtualDirectoryType value of Exadmin.Outlook Web Access For PDA , OWA For WAP www.owa-pda.com email a@t leederbyshire d.0.t c.0.m

Hi Lasse, Please also post the error message here. Resource: PFDAVADMIN, Exchange 2007, and the v1.1 .NET Framework http://mostlyexchange.blogspot.com/2008/01/pfdavadmin-exchange-2007-and-v11-net.html Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi Lasse, Any updates?Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi Frank I haven't had the time to check to link regarding PFDAVADMIN and 1.1 .NET, but will hopefully get to it later today or tomorrow. I didn't know that the \\BackOfficeStorage was a virtual share that can't be access through the IIS management console. So Lee is correct in me assuming that it might have been the cause of my problem :-) I will get back to you later!/Lasse