If you are going to be using scopes for your collections, get your scopes worked out on the front end and then apply the scope(s) during migration
Jimmy Martin | ENGINEER-SYSTEMS II | BMHCC - CORPORATE | (901) 227-8209 | [email protected] <mailto:[email protected]> The opinions expressed above are not necessarily those of Baptist.<mailto:[email protected]> From: [email protected] [mailto:[email protected]] On Behalf Of Krueger, Jeff Sent: Tuesday, September 24, 2013 12:34 PM To: [email protected] Subject: RE: [mssms] Migration and Required Deployments If you do a collection migration it should take all associated items over (packages, advertisements, etc) including clients and execution history. The execution history should prevent those previously deployed packages redeploying on machines that already ran it. It was mentioned in another thread to be wary of having the always rerun setting set, as someone else found that because of that machines started rerunning the advertisement after the migration. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Jeff Poling Sent: Tuesday, September 24, 2013 11:49 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] Migration and Required Deployments I am migrating an environment from CM07 to CM12. There are a number of mandatory advertisements in CM07 that I migrated to CM12. When migrating, the deployment IDs are new in CM12, so the required deployments re-run when the CM12 client is installed. We do not want the required deployments to re-run on existing machines; however, they need to run on new machines that are built and introduced into the environment. Is there any way to prevent required deployments from running on existing machines but keep them required for new PCs? All I have come up with so far is remove the required deployments and re-create them on a separate collection that users are made members of when a new PC is built for them. Thanks, Jeff ________________________________ CONFIDENTIALITY NOTICE: This email contains information from the sender that may be CONFIDENTIAL, LEGALLY PRIVILEGED, PROPRIETARY or otherwise protected from disclosure. This email is intended for use only by the person or entity to whom it is addressed. If you are not the intended recipient, any use, disclosure, copying, distribution, printing, or any action taken in reliance on the contents of this email, is strictly prohibited. If you received this email in error, please contact the sending party by reply email, delete the email from your computer system and shred any paper copies. Note to Patients: There are a number of risks you should consider before using e-mail to communicate with us. See our Privacy & Security page on www.henryford.com<http://www.henryford.com> for more detailed information as well as information concerning MyChart, our new patient portal. If you do not believe that our policy gives you the privacy and security protection you need, do not send e-mail or Internet communications to us. This message and any files transmitted with it may contain legally privileged, confidential, or proprietary information. If you are not the intended recipient of this message, you are not permitted to use, copy, or forward it, in whole or in part without the express consent of the sender. Please notify the sender of the error by reply email, disregard the foregoing messages, and delete it immediately. P Please consider the environment before printing this email...
