Yes I imaged the server and restored in on a total different hardware with acronis universal restore and it worked fine. I am sure you know re-imaging a windows machine to dissimilar hardware is very hard due to device drivers. But this tool does the magic. I changed from a dell power edge 2850 with xeon processor and scsi drive to a Pentium 4 and IDE drive and it booted fine and no blue screen. It took a while to come up for the first time and hard drive was spinning constantly (hardware detection) but it was normal on second time. It was an OEM Windows and it was dell to dell so probably under other scenarios activation might be necessary. And I don't care if PSS is laughing or not because I am not going to call them for help on this special issue and I am pretty sure they haven't done this before. :-) ________________________________ From: isalist-bounce@xxxxxxxxxxxxx [mailto:isalist-bounce@xxxxxxxxxxxxx] On Behalf Of Jim Harrison Sent: Friday, January 12, 2007 6:10 AM To: isalist@xxxxxxxxxxxxx Subject: [isalist] Re: my experience with surf control 5.5 "I did re-image the server on another machine" - not supported for ISA. You might be successful; you might not. Either way, any problems you encounter will be laughed away by PSS. Jim From: isalist-bounce@xxxxxxxxxxxxx [mailto:isalist-bounce@xxxxxxxxxxxxx] On Behalf Of Ara Avvali Sent: Thursday, January 11, 2007 11:10 AM To: undisclosed-recipients Subject: [isalist] my experience with surf control 5.5 Ok So I just want to share the story. I did re-image the server on another machine and logged in to it. Then I did an in-place upgrade from 5.1 to 5.5. It went smoothly telling me that it is going to upgrade rules and settings. Rebooted the server and registered filter for ISA was upgraded to 5.5. So I let it run for couple hours and checked on event logs and service status and everything was cool. Then I went ahead and did it on live server. This time damn thing gave me the error which is attached during installation. Then it was installed and rebooted. Upon reboot web filter service did not start automatically and I had to it manually but everything seems to be working fine and no nasty event so far. If I remember it correctly this error is related to the fact that SF can not stop the firewall service on its own so you should stop it manually before attempting the upgrade. I will post again for those who are interested. Just have to figure it out why the web filter service does not start automatically :-( All mail to and from this domain is GFI-scanned.