not_rich_yet Posted November 5, 2012 Posted November 5, 2012 Hi all, We've been using SCCM 2012 since July of this year. The only issue we have outstanding now is that rebuilding a computer (OS failure for example) to the same name doesn't pick up in SCCM 2012. We have tried deleting the computer from the AD and SCCM before a rebuild of the OS, but it still isn't getting picked up. We do a manual install of the SCCM client and Forefront yet it still doesn't install any allocated applications. AD GPO's etc. all work fine, it is just the SCCM apps/updates etc. that don't ever show up. Has anyone got any suggestions? Thanks, Chris
eejit Posted November 21, 2013 Posted November 21, 2013 Did you ever get a solution to this? I'm experiencing a similar problem to yours, but not quite as bad. If we rebuild a machine with the same name, then SCCM only sees the old machine, and "last activity" remains at the day we wiped it. If I delete the machine from SCCM and then do an "Active Directory System Discovery" then the new machine is found and the SCCM client and Endpoint get rolled out automatically as expected. There must be a way for SCCM to recognise a new build with the same name.
not_rich_yet Posted November 21, 2013 Author Posted November 21, 2013 No, not directly - it no longer happens, I can happily rebuild to the same name without a problem. I have got a few cumulative updates installed since, but nothing else.
Debbie99 Posted November 22, 2013 Posted November 22, 2013 same as eejit, just delete from SCCM after a rebuild and run a full discovery. I think it is a "feature" 1
not_rich_yet Posted November 25, 2013 Author Posted November 25, 2013 Not a feature, it works fine for me....what I did recall is that I had Maintenance Windows set on all collections - when I rebuilt a PC I was building it within the Maintenance Window so no apps were ever installed. To that end, I created a Device Collection called 'Temporary Build Area' where I put computers I rebuild and set no Maintenance Window on this collection so apps can be installed at any time of day. Solved things for me - I remembered I did this on the way home from work this afternoon. There is no need nor reason nor design in SCCM 2012 to have to delete a computer from SCCM before rebuilding it. 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now