If history of that machine is not important, delete machine from SCCM before re-image. That should create new record in SCCM after re-image and creation date will be also be new, so it will fall in to new machines collection.
Anand From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of sccmfun Sent: Tuesday, January 20, 2015 2:40 PM To: mssms@lists.myitforum.com Subject: RE: [mssms] Newly built machines into patching collection - Follow-up It the machine has been re-imaged, and was created a month ago it wouldn't show up in the collection since it's a re-image. From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Michael Mott Sent: Tuesday, January 20, 2015 1:46 PM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: RE: [mssms] Newly built machines into patching collection - Follow-up Also set a high coll refresh on this, maybe 30 minutes. It's not a big hit either and it works quite well. From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Michael Mott Sent: Tuesday, January 20, 2015 12:25 PM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: RE: [mssms] Newly built machines into patching collection - Follow-up select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where datediff(day,CreationDate,getdate()) < 1 From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of sccmfun Sent: Tuesday, January 20, 2015 10:37 AM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: RE: [mssms] Newly built machines into patching collection - Follow-up Follow-up on this. What if you are re-imaging a machine? If the machine was discovered when it was created a month ago by System Discovery, it won't show-up in the collection of new machines. How do you get around something like this? From: sccmfun [mailto:sccm...@hotmail.com] Sent: Monday, January 12, 2015 1:58 PM To: 'mssms@lists.myitforum.com' Subject: RE: [mssms] Newly built machines into patching collection Cool, both good suggestions. Thanks From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Gilmanov, Nile Sent: Monday, January 12, 2015 1:10 PM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: RE: [mssms] Newly built machines into patching collection Or do a query on what's NOT in a patch collection and then run stuff against that data. From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Marcum, John Sent: Monday, January 12, 2015 11:53 AM To: mssms@lists.myITforum.com<mailto:mssms@lists.myITforum.com> Subject: RE: [mssms] Newly built machines into patching collection You could do a query for creation date From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of sccmfun Sent: Monday, January 12, 2015 10:52 AM To: mssms@lists.myITforum.com<mailto:mssms@lists.myITforum.com> Subject: [mssms] Newly built machines into patching collection Just wondering what have others done to get newly built machines into patching collections. We're using MDT (not integrated yet) and have the SCCM client get installed during the MDT build. How do you ensure that the newly built machines get into the patching collections quickly so they are patched during build time? ________________________________ Confidentiality Notice: This e-mail is from a law firm and may be protected by the attorney-client or work product privileges. If you have received this message in error, please notify the sender by replying to this e-mail and then delete it from your computer. ________________________________ Confidentiality Notice: This e-mail is from a law firm and may be protected by the attorney-client or work product privileges. If you have received this message in error, please notify the sender by replying to this e-mail and then delete it from your computer. ________________________________ Legal Notice: This email is intended only for the person(s) to whom it is addressed. If you are not an intended recipient and have received this message in error, please notify the sender immediately by replying to this email or calling +44(0) 2083269015 (UK) or +1 866 592 4214 (USA). This email and any attachments may be privileged and/or confidential. The unauthorized use, disclosure, copying or printing of any information it contains is strictly prohibited. The opinions expressed in this email are those of the author and do not necessarily represent the views of 1E Ltd. Nothing in this email will operate to bind 1E to any order or other contract. ________________________________ Legal Notice: This email is intended only for the person(s) to whom it is addressed. If you are not an intended recipient and have received this message in error, please notify the sender immediately by replying to this email or calling +44(0) 2083269015 (UK) or +1 866 592 4214 (USA). This email and any attachments may be privileged and/or confidential. The unauthorized use, disclosure, copying or printing of any information it contains is strictly prohibited. The opinions expressed in this email are those of the author and do not necessarily represent the views of 1E Ltd. Nothing in this email will operate to bind 1E to any order or other contract.
