You don't have to delete ANYTHING in order to do an OSD refresh on a machine.
*-----------------------------------------------* *Adam Juelich* Pulaski Community School District <http://www.pulaskischools.org> Client Management Specialist 920-822-6075 On Thu, Apr 2, 2015 at 11:16 AM, ccollins9 <[email protected]> wrote: > Unless I missed where someone mentioned otherwise, I don't think it's > possible to re-image without deleting from at least AD. If you just simply > rename a computer, SCCM will pick up that change and rename the object > within SCCM because the GUIDs are the same. Same with AD, a rename is fine > because the SID remains the same. But when you re-image a computer, the AD > SID and SCCM GUID are now different and it's treated as a new object. SCCM > will allow duplicate names with different GUIDs, but AD won't allow > duplicate names at all. > > On Thu, Apr 2, 2015 at 12:07 PM, Chris Carbone < > [email protected]> wrote: > >> The problem is we do not want these objects getting deleted at all. Our >> ticketing system pulls from SCCM so when you start deleting objects and >> adding new objects, our ticketing system is becoming littered with old >> computer names. >> >> >> >> We want to reimage a computer, and if the name is different, we need it >> to stay associated with the same object in SCCM. We want the object for a >> computer entered one time, and it always lives in AD/SCCM even if renamed. >> >> >> >> Hopefully this makes sense. >> >> >> >> >> >> >> >> *From:* [email protected] [mailto: >> [email protected]] *On Behalf Of *Juelich, Adam >> *Sent:* Thursday, April 02, 2015 11:45 AM >> *To:* [email protected] >> *Subject:* Re: [mssms] RE: Re-imaging computers without deleting sccm >> object >> >> >> >> What Steve said... >> >> >> >> You should have a naming convention and then stick to it to prevent the >> issues you are creating. Rename the machines at the end or after the >> fact. Your TS should be zero-touch unless you're dealing with bare-metal. >> Otherwise, delete the object and handle it that way. If the machines are >> being re-purposed for a different area you'll most likely want to delete >> the object anyways depending on how you're doing Application deployment. >> You don't want the machine to automatically get deployed applications it >> may no longer need (again, depending on how you're deploying and how you're >> creating your collections). >> >> >> *-----------------------------------------------* >> >> *Adam Juelich* >> >> Pulaski Community School District <http://www.pulaskischools.org> >> >> Client Management Specialist >> >> 920-822-6075 >> >> >> >> On Thu, Apr 2, 2015 at 10:27 AM, ccollins9 <[email protected]> wrote: >> >> How are you all dealing with the object in AD? AD doesn't allow >> duplicate names, so AFAIK the only way to make sure the newly imaged >> computer gets in AD properly is to either first delete the old object in >> AD, or go into AD, find the computer, right-click and select and click >> "reset account" before the TS joins the computer to the domain. >> >> >> >> This whole thread may lead me to also fully automating this, as we >> currently have helpdesk members delete the old computer from SCCM and AD >> first, and if I do automate it, I think my first attempt would be to use >> the PowerShell commands Remove-CMDevice and Remove-ADComputer. If I >> venture down that path, ill share my results. >> >> >> >> On Thu, Apr 2, 2015 at 10:55 AM, Chris Carbone < >> [email protected]> wrote: >> >> Currently I have UDI popping up so helpdesk can change name, date, >> time, and choose software etc. >> >> >> >> That is good to know if the name stays the same, no new object is >> created. But need to also figure out how we can keep that same object even >> if the name changes. >> >> >> >> >> >> >> >> *From:* [email protected] [mailto: >> [email protected]] *On Behalf Of *Steve Whitcher >> *Sent:* Thursday, April 02, 2015 10:52 AM >> *To:* [email protected] >> *Subject:* Re: [mssms] RE: Re-imaging computers without deleting sccm >> object >> >> >> >> How are you changing the computer name? Are you entering the computer >> name manually at the start of the task sequence? >> >> >> >> In my environment, we use a standard naming convention for workstations, >> so the names never change. Our OSD task sequence is fully automated, so >> that after initiating the pxe boot there is no user interaction required. >> SCCM already knows the computer, by MAC and GUID, so the task sequence >> assigns the computer the same name that it had before. No duplicate >> computers are created in SCCM or AD. >> >> >> >> On Thu, Apr 2, 2015 at 9:41 AM, Chris Carbone < >> [email protected]> wrote: >> >> So this is great, now we can reimage without dealing with deleting >> computers in SCCM first. >> >> >> >> But there is still a problem. When I reimage a computer now, and change >> the name of it. Both entries appear in AD and SCCM. What I would like to >> happen is the name changes the existing object, and doesn’t create a new >> object. Maybe I can add a couple steps to my TS that deletes the old >> computer name/object before it starts imaging? Just throwing ideas out >> there. >> >> >> >> I’m currently testing this out also. If I leave the computer name the >> same, what happens when you reimage. >> >> >> >> Thanks again for everyones help! >> >> >> >> >> >> >> >> >> >> *From:* [email protected] [mailto: >> [email protected]] *On Behalf Of *Steve Whitcher >> *Sent:* Thursday, April 02, 2015 9:52 AM >> >> >> *To:* [email protected] >> *Subject:* Re: [mssms] RE: Re-imaging computers without deleting sccm >> object >> >> >> >> I know it's one of those things that people will argue about until the >> end of time, but I'm in the "Never deploy anything to the 'All Systems' >> collection" camp. ESPECIALLY an OSD task sequence... >> >> >> >> On Thu, Apr 2, 2015 at 8:38 AM, Ryan <[email protected]> wrote: >> >> Think of it this way, if you deploy it correctly to All Systems then no >> one can accidentally deploy it there! You can't deploy a task sequence >> twice to the same collection. >> >> Just make sure you have the song Danger Zone playing in the background >> when you make the deployment. >> >> >> >> On Thu, Apr 2, 2015 at 2:26 AM, Andreas Hammarskjöld < >> [email protected]> wrote: >> >> If you are on 2012, deply to a collection of your liking, ”All systems” >> being mentioned and could be safe/unsafe. Just make sure nobody has right >> to change the PXE/USB/MEDIA flag to “Clients”, and use “Available” rather >> than “Required”. >> >> >> >> My 2 swedish kroners! >> >> >> >> //A >> >> >> >> *From:* [email protected] [mailto: >> [email protected]] *On Behalf Of *ccollins9 >> *Sent:* den 1 april 2015 23:49 >> *To:* mssms >> >> >> *Subject:* Re: [mssms] RE: Re-imaging computers without deleting sccm >> object >> >> >> >> "You can't change a deployment from available to required without doing >> some very unsupported things in the database. >> Can it be done in SCCM 2007? If so, maybe a deployment to All Systems is >> just what you need to get that upgrade started!" >> >> >> >> Yes, you're right, I was thinking SCCM 2007 and the idea of it used to >> terrify me haha. >> >> >> >> >> >> >> >> On Wed, Apr 1, 2015 at 12:14 PM, Ryan <[email protected]> wrote: >> >> You can't change a deployment from available to required without doing >> some very unsupported things in the database. >> >> Can it be done in SCCM 2007? If so, maybe a deployment to All Systems is >> just what you need to get that upgrade started! >> >> >> >> On Wed, Apr 1, 2015 at 6:45 AM, ccollins9 <[email protected]> wrote: >> >> "Advertise the task sequence to All Systems, boot media/pxe only. >> That’s how we’re doing it in the 2012 system we’re setting up now, seems to >> work like a charm." >> >> >> >> I wouldn't ever recommend anyone do this unless you have reallllllly >> tight control (permissions) over SCCM and ALL the techs working it know it >> well. All it takes is someone setting that advertisement to "required" and >> then all the computers in your domain will be re-imaged. Granted there is >> a safety net there with PXE/Boot Media option, but if a computer reboots >> and has PXE enabled, wouldn't it boot to PXE and begin the image >> installation? >> >> >> >> >> >> My recommendation is to give the lower level technicians access to delete >> machines in certain collections. SCCM is designed to be used by everyone >> from end-user to the highest tiers of support. You can lock many things >> down with permissions. We package the SCCM console and push it to all our >> techs in the IT department. They have the console, but can only do what >> they have permissions for. >> >> >> >> Another method and maybe a safer one if the above scares you---SCCM 2012 >> supports PowerShell commands. Create a service account with permissions to >> delete objects using the Remove-CMDevice command and script it. >> >> >> >> >> >> >> >> On Wed, Apr 1, 2015 at 7:26 AM, Jessie Twaddle <[email protected]> >> wrote: >> >> The unknown systems works great for unknown systems, but what do you do >> when SCCM already knows about the computer and the staff who deploy the >> images have no access to SCCM? Rather then have them contact Sccm admin >> every time they need to reimage, I just use wds to deploy the base image. >> It would be great to use SCCM always. If anyone has an automated way >> around this issue, please let me know. >> >> Jessie >> >> On Apr 1, 2015 4:33 AM, "Trond Karstensen" <[email protected]> >> wrote: >> >> I always advertise to «all systems» pxe & media only, and to all >> unknown computers. >> >> And password protect the TS. >> >> >> >> >> >> *From:* [email protected] [mailto: >> [email protected]] *On Behalf Of *Jeff Gilbert >> *Sent:* tirsdag 31. mars 2015 22.29 >> *To:* [email protected] >> *Subject:* RE: [mssms] RE: Re-imaging computers without deleting sccm >> object >> >> >> >> Available to all unknown systems is the ticket: >> https://technet.microsoft.com/en-us/library/dn818437.aspx >> >> >> >> *From:* [email protected] [ >> mailto:[email protected] <[email protected]>] *On >> Behalf Of *Juelich, Adam >> *Sent:* Tuesday, March 31, 2015 4:23 PM >> *To:* [email protected] >> *Subject:* Re: [mssms] RE: Re-imaging computers without deleting sccm >> object >> >> >> >> Rule of thumb is to never deploy anything to 'All Systems.' Unless >> you're into extreme sports or something.... >> >> >> *-----------------------------------------------* >> >> *Adam Juelich* >> >> Pulaski Community School District <http://www.pulaskischools.org> >> >> Client Management Specialist >> >> 920-822-6075 >> >> >> >> On Tue, Mar 31, 2015 at 3:20 PM, Rob Glodt <[email protected]> wrote: >> >> Advertise the task sequence to All Systems, boot media/pxe only. >> That’s how we’re doing it in the 2012 system we’re setting up now, seems to >> work like a charm. >> >> >> >> Rob Glodt >> >> >> >> *From:* [email protected] [mailto: >> [email protected]] *On Behalf Of *Chris Carbone >> *Sent:* Tuesday, March 31, 2015 1:15 PM >> *To:* [email protected] >> *Subject:* [mssms] Re-imaging computers without deleting sccm object >> >> >> >> We currently need to delete the computer out of SCCM each time we want to >> image a computer. Is there a way where we can image a computer without >> doing this? We want it to stay in SCCM for asset management from another >> system that is pulling from SCCM. >> >> This electronic mail transmission may contain confidential information >> intended only for the use of the individual(s) identified as addressee(s). >> If you are not the intended recipient, you are hereby notified that any >> disclosure, copying, distribution or the taking of any action in reliance >> on the contents of this electronic mail transmission is strictly >> prohibited. If you have received this transmission in error, please notify >> me by telephone immediately. >> >> >> >> >> ------------------------------ >> >> Confidentiality Notice: This e-mail message, including any attachments, is >> for the sole use of the intended recipient(s) and may contain confidential >> and privileged information. Any unauthorized review, use, disclosure or >> distribution is prohibited. If you are not the intended recipient, please >> contact the sender by reply e-mail and destroy all copies of the original >> message. >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> This electronic mail transmission may contain confidential information >> intended only for the use of the individual(s) identified as addressee(s). >> If you are not the intended recipient, you are hereby notified that any >> disclosure, copying, distribution or the taking of any action in reliance >> on the contents of this electronic mail transmission is strictly >> prohibited. If you have received this transmission in error, please notify >> me by telephone immediately. >> >> >> >> >> >> >> >> This electronic mail transmission may contain confidential information >> intended only for the use of the individual(s) identified as addressee(s). >> If you are not the intended recipient, you are hereby notified that any >> disclosure, copying, distribution or the taking of any action in reliance >> on the contents of this electronic mail transmission is strictly >> prohibited. If you have received this transmission in error, please notify >> me by telephone immediately. >> >> >> >> >> >> >> >> >> >> >> This electronic mail transmission may contain confidential information >> intended only for the use of the individual(s) identified as addressee(s). >> If you are not the intended recipient, you are hereby notified that any >> disclosure, copying, distribution or the taking of any action in reliance >> on the contents of this electronic mail transmission is strictly >> prohibited. If you have received this transmission in error, please notify >> me by telephone immediately. >> >> >> > >
