why is my isa server such a dog?
We have an ISA server, which we call isa2. It has run for about 4 years in a MS virtual pc on top of our physical isa1 server. the isa 2 is our unfiltered server for slt and us.
It started going down hill a while ago, we stopped being able to tsc it directly, it got really laggy and was using 100% cpu a lot of the time.
In our infinite wisdom we decided to migrate it from its ms vpc home to a vmware esxi host, which went swimmingly, and it was up and running in no time - but despite a doubling in available memory and the addition of another cpu core it is still using 100% cpu.
We are not using SQL logging, but there is an isa instance of sql desktop consuming between 12 and 88% cpu contstantly, and the wspsrv firewall consuming pretty much whatever sql is not consuming, creating a 100% cpu condition, 100% of the time!
We've applied all the hotfixes and service packs and supportability packs to it with very little change.
WHAT IS WRONG WITH MY [DERP] ISA!
We have just decided to use TMG instead, we have read the guide, exported the info from ISA, created a new VMware host on the appropriate IP and i'm just waiting for the ISO to download.
Have I just condemned myself?