Swing Migrations – We luv ‘em! I guess we’ve done 6 or 7 so far and they really work. I’m not saying they are without problems, but the point is it takes the pressure off as well as making the whole migration experience much easier on the client. If you don’t know what a swing migration is then take a look here:
http://www.sbsmigration.com/One issue we have seen on several of the swings we’ve done is that ISA 2004 will install but then the ICW will fail the next time it is run. This has happened to us when swinging from SBS 2000 with ISA 2000 over to SBS 2003 with SP1 media. If we uninstall ISA 2004 all is well again. We passed the issue to Microsoft PSS who were as always incredibly helpful and came up with the following fix:
Under Domain Controller Security Policy > User Rights Assignment, add the Network Service & Local Service to the following:
Adjust memory quotas for processGenerate Security AuditsLog on as serviceReplace a process Level tokenLog on as batch jobOnce done, reboot and re-install ISA 2004 – voila - issue fixed!