since I posted here. I have been busy preparing for and delivering the forefront security training. I am having a great time. for this I installed Forefront on my laptop as well, it rocks for me, but it does strange things ( as I found out yesterday.) I thought it had to do with hyper-V for I upgraded that one to RC. and I got problems, it still is related to Hyper-V, but the cause is not RC vs. Beta,but Forefront Client Security..
It seems that Forefront wants a Filelock when scanning a file, the on access scan when starting a VM will create the lock and this may cause the Virtual Machine Manager for Hyper-V to crash. So if you have both Hyper-V and FCS running on the same machine, you might want to consider either of the following three options:
- switch off Forefront when starting machines, reverting machines or any vhd related actions.
- exclude VHD files altogether in FCS,
- Exclude files accessed through c:windowssystem32vmms.exe and c:windowssystem32vmwp.exe.
For me the last does the trick (up till now) I might want my VHD’s scanned, but not when the Virtual Machine management service is accessing those files.
please let me know if you have similar problems, and what kind of thing you did to solve the problem.