I did see a script somewhere (sorry I don’t have a link) that searched for the computer objects group membership and created TS variable from them. You could then use those variables to have variable driven installs in the TS.
It shouldn’t be too difficult to do in PowerShell if you have the time etc. From: [email protected] [mailto:[email protected]] On Behalf Of CESAR.ABREG0 Sent: 05 February 2015 05:08 To: [email protected] Subject: Re: [mssms] RE: App Deployment after Reimage The GUI in SCCM is dynamic but does not matter. If you have the computer name in the AD group, SCCM will evaluate it and add it to the correct collection that you have setup which should be based in the AD group membership. Cesar A. Meaning is NOT in words, but inside people! Dr. Myles Munroe. On Feb 4, 2015, at 8:57 PM, Chad Beard <[email protected]<mailto:[email protected]>> wrote: Ok. I know the helpdesk do delete the object out of SCCM before imaging again. Is there a script or something that can keep the GUID the same? From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Jeffrey Hunt Sent: Thursday, 5 February 2015 2:45 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: App Deployment after Reimage Unless you have gone and deleted SCCM or AD objects relating to that asset before the refresh/reimage, all should be ok. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Chad Beard Sent: Thursday, 5 February 2015 12:56 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: App Deployment after Reimage Thanks for the response. So it has nothing to do with the machine GUID. It should basically reinstall provided the machine has the same name? From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Jeffrey Hunt Sent: Thursday, 5 February 2015 10:53 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: App Deployment after Reimage the machine will evaluate the collections it is in and then determine any appropriate advertisements before kicking off required tasks. if you have an app deployment deadline that has passed and is not set to expire (unless it’s a time [still] in the future), it will reinstall after these two cycles happen: · Machine Policy Retrieval & Evaluation Cycle · Application Deployment Evaluation Cycle If an application deployment is with a deadline and no expiration, then if the software is uninstalled, on the next Application Deployment Evaluation Cycle, it will reinstall (within a 2 hour built-in SCCM time variance set to reduce the load on the DP), though generally I have seen it happen pretty quickly. In addition, there are VBscripts available to force the evaluation cycles. A quick google search led me to this one: http://heineborn.com/tech/actions-in-configuration-manager-client/ You can execute these at the end of your task sequence From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Chad Beard Sent: Thursday, 5 February 2015 10:56 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] App Deployment after Reimage Hi All, I have a query regarding the reimaging of a PC. We have software being deployed via AD Security Groups. If I re-image the machine with the same name will it detect the AD Groups that it is in and update the collection again to push the applications back out? If not does anybody know of a way that we can make this happen? Thanks Chad Beard Infrastructure Support Officer - Adelaide Enterprise Services <image001.png> P. 0882305155 M. +61 434 076 370 E. [email protected]<mailto:[email protected]> Australian Rail Track Corporation 11 Sir Donald Bradman Drive Keswick Terminal SA 5035 artc.com.au<http://www.artc.com.au> The information in this email and any attachments to it is confidential to the intended recipient and may be privileged. Receipt by a person other than the intended recipient does not waive confidentiality or privilege. Unless you are the intended recipient, you are not authorised to disseminate, copy, retain or rely on the whole or any part of this communication. If you have received this communication in error please notify ARTC on +61 8 8217 4366. While we have taken various steps to alert us to the presence of computer viruses we do not guarantee that this communication is virus free. This email, including any attachments, is confidential. If you are not the intended recipient, you must not disclose, distribute or use the information in this email in any way. If you received this email in error, please notify the sender immediately by return email and delete the message. Unless expressly stated otherwise, the information in this email should not be regarded as an offer to sell or as a solicitation of an offer to buy any financial product or service, an official confirmation of any transaction, or as an official statement of the entity sending this message. Neither Macquarie Group Limited, nor any of its subsidiaries, guarantee the integrity of any emails or attached files and are not responsible for any changes made to them by any other person. --------------------------------------------------------------------------------------- Information in this message is sent in confidence and is intended only for the use of the individual or entity to whom it is addressed. If you are not the intended recipient, any use, distribution or copying of the information is strictly forbidden. Please notify the sender immediately by return email or telephone 01823 721400. If you received this email in error please delete it and any copies of it from your system. Viridor Waste Management Limited Registered Office: Peninsula House, Rydon Lane, Exeter EX2 7HR Registered in England No. 575069 ---------------------------------------------------------------------------------------
