Changing hardware - SCCM client behaviour
hi, I was wondering what is the correct procedure to change hardware for a user from a SCCM client respective, will the new hardware create a new SCCM GUID? what happens if i want to re-image the old hardware? some test i made: i have changed the hardware for user and it has "locked" both MAC address in SCCM and now both of them cannot be re-imaged.MCSA | MCTS - SCCM 2007
May 21st, 2011 5:26am

It will create a new computer object in the database and makr the old object as obsolete (that's the default behavior).Kent Agerlund | My blogs: http://blog.coretech.dk/author/kea/ and http://scug.dk/ | Twitter @Agerlund | Linkedin: /kentagerlund
Free Windows Admin Tool Kit Click here and download it now
May 21st, 2011 6:06am

it will create a new object by the same computer name?MCSA | MCTS - SCCM 2007
May 21st, 2011 6:11am

Yes.....Anoop C Nair - This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
May 21st, 2011 6:40am

kinda related to this, what if i want to re-image the same hardware? Advertisement is available to "unknown computers' only and it means i need to delete the old object from SCCM manually. Is there another way to re-image the same hardware (without removing it from SCCM)? Advertising to "All systems" might solve the problem, but is it safe?
May 21st, 2011 8:36am

Just add the computer object to a collection (using a membership rule) where you have the desired task sequence(s) advertised. All activity in ConfigMgr is targeted to a collection. Thus, if you want something to happen advertise or deploy the action/activity to a collection and add the system as a member of that collection. The only time ConfigMgr can do anything to a system it does not know is with OSD and the Unknown Computer resources (which hapen to be members of the Unknown Computer collection but don't have to be). Note that objects in ConfigMgr can be members of as many collections as you want them to be. Collections are not a directory; the objects do not live in a specific collection.Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys
Free Windows Admin Tool Kit Click here and download it now
May 21st, 2011 8:52am

you mean that this is a manual task anyway?
May 21st, 2011 9:01am

Which task are you talking about?Torsten Meringer | http://www.mssccmfaq.de
Free Windows Admin Tool Kit Click here and download it now
May 21st, 2011 11:03am

working with direct membership rules
May 22nd, 2011 2:32am

Hi - If you wanted to rebuild an existing machine through TS then its better to have direct membership rule collection to avoid any acidents...Anoop C Nair - This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
May 22nd, 2011 5:58am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics