Successfully Implementing Shadow Folders in Windows 2003

Post by **jclausius** » Sat Dec 11, 2004 2:05 pm

Yes. I'm going to review the KB article to make sure it is up to date for configuring Shadow Folders on the latest & greatest Win2003 server w/ latest patches as well as .Net 1.1 SP1.

Post by **jclausius** » Mon Dec 13, 2004 9:36 pm

I've updated the KB articles, so they should make sense for Vault 2.0.x as well as the up and coming Vault 3.0.1.

A big thank you to all who have reported the issue and helped us track down the problem. You can look for Vault 3.0.1 in the next couple of days.

Imar Spaanjaars · Post by **Imar Spaanjaars** » Tue Dec 14, 2004 2:17 am

That's great news!

Thanks for fixing this so quick.

Imar

Post by **jclausius** » Tue Dec 14, 2004 1:28 pm

Vault 3.0.1 is now available for download from the SourceGear Vault site ( http://www.sourcegear.com/vault/downloads.html )

ldudex · Post by **ldudex** » Tue Dec 14, 2004 1:32 pm

Can you confirm this release fixes the problems with Win2k3 Server and shadow folders (e.g. IIS 5 Isolation Mode is no longer required to get it to work)? Also, is Identity Impersonation in the Web.Config file supported?

Thanks in advance for feedback on this =)

Post by **jclausius** » Tue Dec 14, 2004 1:59 pm

ldudex wrote:Can you confirm this release fixes the problems with Win2k3 Server and shadow folders (e.g. IIS 5 Isolation Mode is no longer required to get it to work)?

Yes, I can personally confirm this works following the directions found in:
Shadow Folders on Windows 2003 Server
FAQ: Shadow Folders with UNC Paths / Windows 2003 Server

ldudex wrote:Also, is Identity Impersonation in the Web.Config file supported?

This response applies to Windows 2003 server only...

Sorry, but I could not get the Shadow Folder service to give the correct output with the following code example:

Code: Select all

[WebMethod]
public string TestPath()
{
	// should return something like - 
	// c:\Documents and Settings\user\Application Data
	return System.Environment.GetFolderPath( Environment.SpecialFolder.ApplicationData );
}

As far as I can tell, the above code only works w/ IIS 6 in native mode using a custom .Net Windows account for the Application Pool identity

OR

IIS 6 running in IIS 5.0 isolation mode with the changes made to Vault's web.config for identity impersonation.