Duplicate name in all system collection...........
Hi,In myAll Systems Collectiona lot of systems are appearing twice.But only one of them having client.Please suggest how duplicate entries are coming with no client? if that systemhave reimaged, then why they r not going to mark as obsoleted?Ihave make an sql query for find dulicate systems, andit is working fine. i have also created report based on same query.select name0 , count (*) from v_r_system GROUP BY name0 having count (*) > 1;but i am not able to make collection using same sql/wql query.Please tell me ,how can i create collection for those non client duplicate name systems,so i can delete them?and why that duplicate name systems is coming?Waitng for suggestion.
June 10th, 2009 5:56am
This must have something to do with the strange issue you already described here: http://social.technet.microsoft.com/Forums/en-US/configmgrgeneral/thread/73f04833-e12b-49ee-86dc-81177ec575b6
June 10th, 2009 6:21am
NO Torsten,thats the different issue.These are my own site client.few client appearing twice but one of them having client,other one is non client.Is it a issue with reimaging ofsystem with same name.
June 10th, 2009 6:40am
Im not anSCCM master but from what i've seen you canbuild a query based collection.
June 10th, 2009 12:05pm
thats the SQl query for finding duplicate name systems,select name0 , count (*) from v_r_system GROUP BY name0 having count (*) > 1;But i am not able to convert it into WQL for making collection.
June 11th, 2009 3:33am
Also having this problem. It causes the new machine to not get a client. This is a serious problem that affects system compliance. Will someone please advise on 'best practice' for sites that often reimage machines and maintain the same hostname? Is there a more efficient method than staggering heartbeat discovery and delete obsolete records by 1-2 weeks? I need machines to acquire a functional client within minutes, not weeks! I expected much snappier performance from SCCM than what I'm seeing.
June 22nd, 2009 8:36pm
Also having this problem. It causes the new machine to not get a client. Which problem? You should add some details (for example: how do you install the client? etc)
June 23rd, 2009 2:30am
The problem is that after reimaging a box and preserving the hostname the new system is not manageable. The solution seems to be manually deleting the original computer record from SCCM and pushing a new client. I've got AD System Discovery and Client Push Installation enabled. If there's a better practice that will not cause these conflicts please share.
June 23rd, 2009 7:40am
So it seems as if you don't install the ConfigMgr client during the OSD process? Why not?
June 23rd, 2009 8:04am
Hi Torsten, Here's my story: I work in a university where IT is compartmentalized. I'm not a domain admin or network engineer - just the application administrator (I don't have admin rights on the SCCM box, which makes things interesting at times.) Setting up OSD has been a high priority for me but other projects keep bumping it down. Configuring OSD will take a test lab (which we haven't yet purchased licenses for) so I can simulate the steps, so I can provide docs and screenshots to the domain admins and network engineers for the necessary tweaks. Basically, I am responsible for teaching them how to make the necessary changes, and they click the buttons. Right now we're deploying 600 boxes, and I was unable to convince my director that it would have been the perfect opportunity for SCCM to prove its value. Unfortunately the powers that be decided to outsource the job, so now a small team of desktop admins and me are helping the Dell contractors to use DAD to bring these 600 boxes into the environment. For these boxes I have pre-installed the SCCM client and all is working fine. It's the other 800 computers in the field that are symptomatic. Three other departments roll out an assortment of images with a smorgasbord of applications and drivers, at various levels of MS updates, and without the SCCM client preinstalled. So that's why I've enabled AD discovery and client push to assimilate them. But when machines get reimaged or repurposed, the client doesn't reinstall as expected and the computers are unmanaged.
June 23rd, 2009 10:20am
Hi torsten,I install the client with OSD TS.But the reimaged computer come twice in sccm .one with client and other without client.Don't know whyprevious record is notcoming as obsolete. ___________________________________________________________ Shimbesh
June 24th, 2009 3:32am
Have you checkd this thread ?http://social.technet.microsoft.com/forums/en-US/configmgrosd/thread/53a3b1a4-6262-4091-b9eb-c672ae3cec7b/
June 24th, 2009 5:16am
I have the similar issue, the only difference that the duplicate records are not from reimaged machines, it simple duplicate records from old machines, one with agent one without.
June 30th, 2009 6:00am
This script by kungcocos is interesting, but I'm not clear on where it runs. Do I run it from each client? It seems like there's got to be a better way. Has anyone used this method?
July 1st, 2009 7:25am
First you need to check why they are duplicate,check the discovery agent for both account for client and non client system.In my case they are twice because we are adding system account in AD.so one is coming by AD disacovery with no client.and second one is coming after prestage and by MP client regsitration.___________________________________________________________ Shimbesh
July 1st, 2009 8:12am
hi Nidhi_123, I'm having exactly the same issue as yours. So how did you solve the problem? It's true that they both are from different discovery - so is this normal? How do we get it to remove the duplicate/old entries? I'd imagine this would be a normal scenario where people have AD discovery set up and re-image PCs etc etc. Cheers, Xm
April 30th, 2012 10:22pm