"Setup has detected that FrontPage server extensions is installed on this
computer. To upgrade your server, uninstall this component."
Not only are FrontPage server extensions not installed but IIS isn't even
installed. No sign of any uninstall for FrontPage server extensions either.
Anyone any idea what the W2008 server is looking at to think they are
installed so I can delete it to allow the upgrade to continue
Thanks
Peter Lawton
1) Removed the frontpage ISAPI filter from all web sites and the top level
"Web Sites" in IIS manager
2) Searched the registry for all entries containing "FrontPage" and "web
server extensions" and deleted as many of the keys as possible
3) Used a delete on boot utility to remove the directory "C:\Program
Files\Common Files\Microsoft Shared\web server extensions"
I can't see why they insist on not installing W2008 if FrontPage extensions
are installed, why don't they just remove the extensions during the install
process, or at least publish a "completely remove frontpage extensions" tool
Peter Lawton
"Michael Wehle" <Michael We...@discussions.microsoft.com> wrote in message
news:5971B455-BB93-46F2...@microsoft.com...
It really isn't good enough though for MS to insist FrontPage extensions
aren't installed before an upgrade and then not to provide any way to remove
them.
MS even supply a cut down version of FrontPage extensions for W2008 now, why
on earth not just ship that with W2008 and be done with it.
I don't think this problem is isolated either, I've had to do the same on
every W2003 server I've upgraded, that had FrontPage installed at any time.
Peter Lawton
<webde...@gmail.com> wrote in message
news:0cc54266-0a3c-403d...@i12g2000prf.googlegroups.com...
Just a shame MS forces us to go to these lengths, I bet this is going to
happen to a lot of people, I've had it on 4 servers already.
Peter Lawton
"Michael Wehle" <Michae...@discussions.microsoft.com> wrote in message
news:CB7C81ED-CF74-4D34...@microsoft.com...
1) Removed the frontpage ISAPI filter from all web sites and the top
level
"Web Sites" in IIS manager
2) Searched the registry for all entries containing "FrontPage" and
"web
server extensions" and deleted as many of the keys as possible
3) Used a delete on boot utility to remove the directory "C:\Program
Files\Common Files\Microsoft Shared\web server extensions"
--
bigbcreations
------------------------------------------------------------------------
bigbcreations's Profile: http://forums.techarena.in/members/bigbcreations.htm
View this thread: http://forums.techarena.in/server-deployment/918672.htm
> On Thursday, February 21, 2008 3:00 PM Peter Lawton wrote:
> Trying to upgrade a W2003 server to W2008 and the upgrade is disabled with
> the message:-
>
> "Setup has detected that FrontPage server extensions is installed on this
> computer. To upgrade your server, uninstall this component."
>
> Not only are FrontPage server extensions not installed but IIS isn't even
> installed. No sign of any uninstall for FrontPage server extensions either.
>
> Anyone any idea what the W2008 server is looking at to think they are
> installed so I can delete it to allow the upgrade to continue
>
> Thanks
>
> Peter Lawton
>> On Thursday, February 28, 2008 11:51 PM Michael Wehl wrote:
>> I am having the same issue on two different 2003 machines. I uninstalled
>> FrontPage 2002 Extensions using Add/Remove Programs, but see no way to
>> uninstall FPSE. What is the W2008 install looking for?
>>
>>
>> "Peter Lawton" wrote:
>>> On Friday, February 29, 2008 3:22 AM Peter Lawton wrote:
>>> As there seemed no MS tool to remove them I got brutal in the end.
>>>
>>> 1) Removed the frontpage ISAPI filter from all web sites and the top level
>>> "Web Sites" in IIS manager
>>> 2) Searched the registry for all entries containing "FrontPage" and "web
>>> server extensions" and deleted as many of the keys as possible
>>> 3) Used a delete on boot utility to remove the directory "C:\Program
>>> Files\Common Files\Microsoft Shared\web server extensions"
>>>
>>> I can't see why they insist on not installing W2008 if FrontPage extensions
>>> are installed, why don't they just remove the extensions during the install
>>> process, or at least publish a "completely remove frontpage extensions" tool
>>>
>>> Peter Lawton
>>>
>>> "Michael Wehle" <Michael We...@discussions.microsoft.com> wrote in message
>>> news:5971B455-BB93-46F2...@microsoft.com...
>>>> On Saturday, March 01, 2008 4:56 AM webdezchri wrote:
>>>> Did getting brutal work? Did you get 2008 installed? I have the same
>>>> problem and and am up the creek.
>>>>> On Saturday, March 01, 2008 5:02 AM Peter Lawton wrote:
>>>>> Oh yes, I got the upgrade to run OK in the end after ripping everything
>>>>> related I could find out of the registry, IIS even works still after the
>>>>> upgrade.
>>>>>
>>>>> It really isn't good enough though for MS to insist FrontPage extensions
>>>>> aren't installed before an upgrade and then not to provide any way to remove
>>>>> them.
>>>>>
>>>>> MS even supply a cut down version of FrontPage extensions for W2008 now, why
>>>>> on earth not just ship that with W2008 and be done with it.
>>>>>
>>>>> I don't think this problem is isolated either, I've had to do the same on
>>>>> every W2003 server I've upgraded, that had FrontPage installed at any time.
>>>>>
>>>>> Peter Lawton
>>>>>
>>>>> <webde...@gmail.com> wrote in message
>>>>> news:0cc54266-0a3c-403d...@i12g2000prf.googlegroups.com...
>>>>>> On Saturday, March 01, 2008 9:22 PM MichaelWehl wrote:
>>>>>> Peter, thanks so much for passing on your solution! This works for me too.
>>>>>>
>>>>>> "Peter Lawton" wrote:
>>>>>>> On Sunday, March 02, 2008 4:18 AM Peter Lawton wrote:
>>>>>>> Great, glad it worked for you too :)
>>>>>>>
>>>>>>> Just a shame MS forces us to go to these lengths, I bet this is going to
>>>>>>> happen to a lot of people, I have had it on 4 servers already.
>>>>>>>
>>>>>>> Peter Lawton
>>>>>>>> Submitted via EggHeadCafe - Software Developer Portal of Choice
>>>>>>>> A Comparison of Managed Compression Algorithms
>>>>>>>> http://www.eggheadcafe.com/tutorials/aspnet/71485ecc-2d2d-435a-9c35-3d12b279f9ae/a-comparison-of-managed-compression-algorithms.aspx