Independent ASP

NOT as a high availability solution, but as a possible solution to reduce 
downtime it has been suggested to us that we investigate using an 
independent ASP.  That way when we bring down MACHINE1 we can switch that 
stuff over to MACHINE2.  This way downtime due to ptf's, upgrades, etc, 
should be kept at a minimum.  My concerns would be:
- User profiles.
- All the PC's.  I suppose at that time we could switch the DNS to route 
them to the new machine (another reason why host tables are the root of 
all evil).
- BPCS keys.  I suppose we could explain this to SSA and they'd give us 
keys.  However we might probably keep the static libraries holding each 
key out of the IASP.

Any other considerations?

Rob Berendt
-- 
"They that can give up essential liberty to obtain a little temporary 
safety deserve neither liberty nor safety." 
Benjamin Franklin