You saying that this only happens in certain cases? Do you have the installation logs from those instances? You're correct - the only solution is to remove/reinstall, since the installation path is used all over the code and in services properties. From: isapros-bounce@xxxxxxxxxxxxx [mailto:isapros-bounce@xxxxxxxxxxxxx] On Behalf Of Jason Jones Sent: Friday, June 15, 2007 2:13 AM To: isapros@xxxxxxxxxxxxx Subject: [isapros] Re: Install Path ISA2k=>ISA2k6 In Place Upgrade Anyone??? From: isapros-bounce@xxxxxxxxxxxxx [mailto:isapros-bounce@xxxxxxxxxxxxx] On Behalf Of Jason Jones Sent: 01 June 2007 14:08 To: isapros@xxxxxxxxxxxxx Subject: [isapros] Install Path ISA2k=>ISA2k6 In Place Upgrade Hi, In line with general best practice of placing server applications on a separate partition than the OS. I have always installed ISA to D:\Program Files\Microsoft ISA Server\ as opposed to the standard C: drive. However, I have noticed from a few recent ISA2k4=ISA2k6 upgrades that the in place upgrade process doesn't prompt for a new path and rather dumbly places the new version back into C:\Program Files\Microsoft ISA Server\ rather than replacing the binaries into the existing directories. Is this a "feature"? Anyone know how to fix it without full remove and reinstall? Cheers JJ All mail to and from this domain is GFI-scanned.