I would not recommend following the path you're taking.
First and foremost I don't ever recommend applying the default policy to anyone. I recommend making the default policy the most secure / most restrictive policy and then creating new policies for however you choose to implement IT Policy. By doing this you've gone through and explicitly set what you want and don't have any possible stragglers . you know if someone has the Default policy assigned to them that someone didn't do what they were supposed to. So, create the new policy and assign them to people. I'd do them in groups of 100 in 30 minute intervals . doing the first 10 or so prior to the group of 100 one at a time to verify that the proper settings are indeed in place. Hopefully you've done some testing already and already worked out the kinks with a pilot group, but if not, now you can. From: [email protected] [mailto:[email protected]] On Behalf Of Moller, Doreen Sent: Monday, June 28, 2010 3:12 PM To: A list for BES Admin's to discuss issues, etc. Subject: [Bes-admins] Implementing New Password Policy Tomorrow for 1300 users Hi Everyone, Can anyone make a good recommendation on the most efficient way to push down a new password policy to everyone tomorrow. I assume changing the default policy is the preferred method, and then having an exception group should that be needed. Once I update the default policy does it automatically get pushed or do I need to highlight the users names and click resent IT policy. Just want to do this is the best possible fashion to minimize problems. Thanks! Doreen Moller Global Mobility Services 908-473-3627 <http://mobility.merck.com/> mobility.merck.com Notice: This e-mail message, together with any attachments, contains information of Merck & Co., Inc. (One Merck Drive, Whitehouse Station, New Jersey, USA 08889), and/or its affiliates Direct contact information for affiliates is available at http://www.merck.com/contact/contacts.html) that may be confidential, proprietary copyrighted and/or legally privileged. It is intended solely for the use of the individual or entity named on this message. If you are not the intended recipient, and have received this message in error, please notify us immediately by reply e-mail and then delete it from your system.
_______________________________________________ Bes-Admins mailing list [email protected] http://www.dataoutages.com/mailman/listinfo/bes-admins http://www.dataoutages.com http://www.dataoutagenews.com RSS Feed: http://feeds.feedburner.com/Bes-admins --------------------------------- Bes-Admins mailing list is sponsored by Dataoutagenews.com. http://www.dataoutagenews.com
