Also, the way we name our computers makes it easy to identify who the computer belongs to. Never liked the idea of serial number for computer name.
From: [email protected] [mailto:[email protected]] On Behalf Of Chris Carbone Sent: Saturday, April 04, 2015 12:09 PM To: '[email protected]' Subject: RE: [mssms] RE: Re-imaging computers without deleting sccm object It's important to our ticketing system that pulls from SCCM. If new objects are created when a computer is renamed, then we will have multiple records in our ticketing system for that one computer. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Joe Sestrich Sent: Friday, April 03, 2015 5:23 PM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] RE: Re-imaging computers without deleting sccm object I'll go ahead and ask a stupid question. Why would you rename the computer if that end to end pedigree is so important? Why not include the serial number or last six digits of the MAC address as part of the name? Have the Task sequence automatically generate the computer name based on that info and they'll keep the same name forever. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Chris Carbone Sent: Friday, April 03, 2015 2:01 PM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] RE: Re-imaging computers without deleting sccm object The reason we need the same sccm object to stay with the hardware is for asset management. Nightly our ticketing system pulls all of the computers and associates to the primary user of that device. If this computer comes in for repair and gets reimaged with a new name, then our ticketing system will have two separate entries for this computer. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Mote, Todd Sent: Friday, April 03, 2015 1:41 PM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] RE: Re-imaging computers without deleting sccm object I know logically it's the same computer, you're sitting in front of it re-imaging it, but how would SCCM reconcile the difference? To SCCM, it's a new OS, new client install, new name, new GUID, new everything. The only thing that's the same at that point is the MAC and the SMBIOS GUID and that's hardware. OldComputerA has a clientID of 12345, OS=win7 and a MAC of 12:34:78:56:90. NewComputerB has clientID 67889, OS=win8 and MAC 12:34:78:56:90. Your brain knows that OldComputerA=NewComputerB, but how is SCCM supposed to know which is which and that you want one to supplant the other? I would think a new object is safest, honestly. What's "in" the old one you need to keep? From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Chris Carbone Sent: Friday, April 3, 2015 9:46 AM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] RE: Re-imaging computers without deleting sccm object When you say you rename fine, you are renaming a computer with a TS that reimages the computer? Because if you do this, a new object is created. I would just think that when you are reimaging a computer, and you want to change the name, a new object doesn't get created, which is what actually happens. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Mote, Todd Sent: Friday, April 03, 2015 10:29 AM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] RE: Re-imaging computers without deleting sccm object We rename computers all the time and SCCM handles it fine, it just takes the client rerunning inventory and reporting it back to the server. No new object needed. But we don't redeploy during a rename though. At that point it's not a rename, really, you're actually installing a new client on a new OS with the same name. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Chris Carbone Sent: Friday, April 3, 2015 8:52 AM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] RE: Re-imaging computers without deleting sccm object I tried the method used in the link below and it actually seems to work nice. I'm testing again, because we need to make sure the Resource ID stays the same between computer name changes. The other thing I'm seeing is that this script does combine both objects in SCCM, but in AD I have both objects showing up. The AD thing is okay, we have rules already in place to deal with stale objects. Just wanted to share what I think is the solution for this work around. I am a bit surprised that SCCM does not handle computer renaming natively this way. When you rename a computer, why would you want a new object if you're using SCCM for asset management? From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Andreas Hammarskjöld Sent: Thursday, April 02, 2015 5:50 PM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] RE: Re-imaging computers without deleting sccm object Script a name change with status filter rule? (Can you script the name change with some good ol' API?) From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of ccollins9 Sent: den 2 april 2015 23:45 To: mssms Subject: Re: [mssms] RE: Re-imaging computers without deleting sccm object In that case you could put in the TS to rename the computer, then have the TS reboot the computer and maybe AD would pick up the change, then the TS would proceed with the re-image. And because SCCM knows that computer is an existing resource and not being deployed via Uknown computers, it would pick up the name change. On Thu, Apr 2, 2015 at 4:39 PM, Mote, Todd <[email protected]<mailto:[email protected]>> wrote: When you rename a computer normally, it doesn't actually change the object in AD until it comes up again after the reboot. To accomplish what it sounds like you want, you'd have to rename the computer, at the computer, reboot so AD picks up the change, possibly wait for SCCM to pick up the change, then run your deployment task sequence with the new name. I don't think you can do it all in the same process AND keep all of the same objects. Todd From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Chris Carbone Sent: Thursday, April 2, 2015 11:56 AM To: '[email protected]<mailto:[email protected]>' Subject: RE: [mssms] RE: Re-imaging computers without deleting sccm object Again, the problem is when we run OSD on an existing computer and change the computer name, a NEW entry is added in AD and SCCM. We don't want this to happen. We want a rename to keep the same object. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Juelich, Adam Sent: Thursday, April 02, 2015 12:53 PM To: [email protected]<mailto:[email protected]> Subject: Re: [mssms] RE: Re-imaging computers without deleting sccm object For me, when I deploy an OSD TS, if the object already exists it is then Zero-Touch. If the object doesn't exist (Bare-Metal) then I get prompted for the name at the beginning which I can choose to ignore and it'll get assigned a random name that I can then change after the fact. ----------------------------------------------- Adam Juelich Pulaski Community School District<http://www.pulaskischools.org> Client Management Specialist 920-822-6075<tel:920-822-6075> On Thu, Apr 2, 2015 at 11:42 AM, Chris Carbone <[email protected]<mailto:[email protected]>> wrote: Even if you change the computer name? From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Steve Whitcher Sent: Thursday, April 02, 2015 12:37 PM To: [email protected]<mailto:[email protected]> Subject: Re: [mssms] RE: Re-imaging computers without deleting sccm object We don't even use a refresh task sequence... our OSD task sequence is pretty much always deployed from pxe, going through the new computer ts steps. Even so, it still re-uses the same computer account in AD. On Thu, Apr 2, 2015 at 11:24 AM, Juelich, Adam <[email protected]<mailto:[email protected]>> wrote: 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<tel:920-822-6075> On Thu, Apr 2, 2015 at 11:16 AM, ccollins9 <[email protected]<mailto:[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]<mailto:[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]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Juelich, Adam Sent: Thursday, April 02, 2015 11:45 AM To: [email protected]<mailto:[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<tel:920-822-6075> On Thu, Apr 2, 2015 at 10:27 AM, ccollins9 <[email protected]<mailto:[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]<mailto:[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]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Steve Whitcher Sent: Thursday, April 02, 2015 10:52 AM To: [email protected]<mailto:[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]<mailto:[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]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Steve Whitcher Sent: Thursday, April 02, 2015 9:52 AM To: [email protected]<mailto:[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]<mailto:[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]<mailto:[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]> [mailto:[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]<mailto:[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]<mailto:[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]<mailto:[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]<mailto:[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]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Jeff Gilbert Sent: tirsdag 31. mars 2015 22.29 To: [email protected]<mailto:[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]> [mailto:[email protected]] On Behalf Of Juelich, Adam Sent: Tuesday, March 31, 2015 4:23 PM To: [email protected]<mailto:[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<tel:920-822-6075> On Tue, Mar 31, 2015 at 3:20 PM, Rob Glodt <[email protected]<mailto:[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]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Chris Carbone Sent: Tuesday, March 31, 2015 1:15 PM To: [email protected]<mailto:[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. 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. 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. 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.
