Dis you create new policies or simply using the originals? I would make new policies to ensure a clean deployment.
On Mon, Feb 29, 2016, 12:42 PM Ortega, Clint < [email protected]> wrote: > Hello, > > I recently migrated my company’s MBAM from 1.0 to 2.5 SP1. However, the > following key has appeared somehow in the new policy. Before I migrate > over the remaining 10K devices to the new policy, I’m hesitant if this key > is still necessary for 2.5 agents. Googling online, it appears to be > related to the initial 1.0 rollout, but no longer available in the policy > for 2.5. If it’s still necessary, is there another key or set of keys that > I need to configure to match these settings? Has anyone come across an > issue like this? > > > > > > Thanks, > > *Clint Ortega* > > Systems Administrator II > > CHRISTUS Health > > Information Management > > 469-282-0295 > > [email protected] > > > > *The two basic principles of Windows system administration:* > > - *For minor problems, reboot* > - *For major problems, reinstall* > > > > *CONFIDENTIALITY NOTICE: Confidential information, such as identifiable > patient health information or business information, is subject to > protection under state and federal law. If you are not the intended > recipient of this message, you may not disclose, print, copy or disseminate > this information.  If you have received this in error, please reply and > notify the sender (only) and delete the message. Unauthorized interception > of this e-mail is a violation of federal criminal law. * >
