true...I knew that, I think I meant more that nearly every month MS has at least one patch that requiresa reboot, rarely do I go through a patch tuesday without some critical fix...
I saw a timeline somewhere where there are far more patches that require rebooting on the MS side - which is only to be expected as it's a full blown OS running there...as opposed to a stripped down kernel, just running what needs to be run for the one function. >> biggest problem with hyper-v is that service packs and >> critical fixes that require a reboot of the underlying >> OS means you have to reboot however many VM's are >> running on your box too). > >I use ESXi myself, and to be fair to Microsoft, when a critical patch for >ESXi is release it requires the same process (shut down the VMs and reboot >the hypervisor). Since I deployed ESXi there has been one patch I needed to >install and that was four months ago. Most of the patches that come out are >related to the CLI which ESXi doesn't ship with, so they're not relevant. > > >-Justin ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology-Michael-Dinowitz/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:337217 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
