Reimaging Computers and SCCM sending duplicate updates

Question

We image computers with Ghost and use the same computer name they originally had on the network once they are imaged.
The intent of the latest image is to be fully updated to this point before it is pushed (Via Ghost) to the computers.
We fully updated the image and pushed it out to a few test PC's and we are using computer names that are already on the Domain and in SCCM.
The problem is SCCM thinks that our imaged computers need updates.
I believe these updates are ones that the computers didnt get before they were imaged, as like I said the image should have all the updates.
We want to assure that the images are updated and SCCM isnt pushing duplicates to the boxes.
My guess is that SCCM believes it is talking to the old system vs the new one with the updates.
Does anyone have any insight on how to fix this.
Thank you in advance.
MILADMIN

Answer 1

The problem is SCCM thinks that our imaged computers need updates.
This is really a question for the Configuration Manager Software Updates forum..
but why do YOU think that a NEWLY IMAGED system would not need updates?
I believe these updates are ones that the computers didnt get before they were imaged
I'm intensely inclined to concur. Unless you made that image since Tuesday, August 13th, it's *impossible* that the image would be fully patched! Ergo any system built from that image is, by definition, NOT fully patched and WILL need more patches.
We want to assure that the images are updated and SCCM isnt pushing duplicates to the boxes.
Whether the images are updated or not has absolutely nothing to do with Software Updates.
As for duplicate patches.. for almost 20 years Windows Update and it's associated enterprise products, all based on the Windows Update Agent, have successfully patched systems without sending duplicate updates to a client -- not ONCE! Why would you be concerned
that an architecture that's existed for over a dozen years might suddenly screw your environment up when it hasn't done so in the previous dozen years? :-)
My guess is that SCCM believes it is talking to the old system vs the new one with the updates.
I think you're overthinking the situation. Your guess is totally inaccurate. A *NEW* system has a *NEW* identifier (GUID), and it's impossible to confuse a newly imaged system with a previously existing system.
The *OLD* system, at worse, is orphaned in Configuration Manager and needs to be deleted.
Does anyone have any insight on how to fix this.
So your assumption is that it's broken???
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.