I didn't realize SEP 11 was reaching EOL on Jan 5th. I have a SEP 12 server up however I don't know if I can start migrating in the next two weeks. Initially I planned on pointing all my SEP 11 clients to the SEP 12 server and once they show up in SEPM 12, I will configure them to update them at their next reboot. If I understand correctly however, there is an engine update somewhere in the pipeline which will cause SEP 11 clients in SEP 12 to break/stop working entirely/blue screen the PC? If that is the case then I cannot just push remote communication package update to SEP 11 client installs and have them show up in SEP 12 because if the engine update gets pushed, my SEP 11 clients which haven't yet updated will break.
Is there a way around thisso called engine update? Is there someway I can block the engine update from my SEP 11 clients that will be managed in SEP 12 until they are updated to SEP 12?
I can do a remote push to update communication package and have them appear in SEP 12 this week. Then over the next few weeks I will froce desktops to reboot and get SEP 12.