Hello, I am currently experiencing a huge problem with our SCCM. When i delete a computer object from the console, then when I want to create it, I cant. It never shows up in the console again. Not even if I just try to install the client on it with a running OS. I was suspecting that whenever i delete the object, it is not properly deleted from the SQL database. I tried to look inside the SQL and found out that the mac address allready exists inside odb.SystemResouce_MAC_Addes_ARR. In a desperate attempt i tried to manualy remove one of my buggy computers from there, and after that created it again... Now i can find it in the console... I was happy, i thought i had found a workaround until i tried to run an OS deployment on it.. It fails, and says it havent got an Task Sequence, but in console, it does. When I PXE the machines, i have also noticed that the GUID it displays on PXE boot doesnt match the on i can see in the console. Does anyone have a good idea for what i can do? What tables I should look at, or even better.. Knowing a more proper way to get the machines back without having to work directly inside the SQL? Thanks in advance, and please, its very urgent, since I allready have quite alot of PC's doing this, and counting :(/Dennis

If you delete a computer from the console by right-clicking on it and deleting it there are triggers that make that resourceID delete from every table in the database that it needs to be removed from. You should be able to add that machine right back without issue. I'm not sure why that's not happening for you. Sorry, I guess that wasn't much help. John Marcum | http://myitforum.com/cs2/blogs/jmarcum/|

It is not supported at all to modify the database directly! So what are the actual problems? (1) a client does not pick up a PXE advertisement and (2) you cannot create a new manual machine entry? Regarding (1): what does smspxe.log on the PXE service point say? (2) What smsprov.log during the import.

I thought so too, and i have been deleting computer objects before without any issues, but now, im very afraid of doing so. Thanks for your reply :)/Dennis

Hi Torsten, thanks for our comment. Yes i know that editing the database directly is a bad thing, but I was so "blank" at what was going on, and thought i would give it a try. To (2), Creating a new object works fine, as long it have'nt existed before. It only occurs when i have deleted it first. Im not at work right now, and therefore cant get access to the files. Will provide them, first thing tomorrow. /Dennis EDIT: Im sorry for the very late reply, but I have been struggling to recreate problem (2), so i can give you a log (typically i dont get the problem right now). Problem (1): i dont think i was so clear about this. Since we are having a little different setup than normal, the PXE works fine, but as soon as it is running in the boot enviroment it restarts. The smsts.log says "There is no advertisement for the specific computer". When i look at the settings for the machine console, it says it does have one.

Hi Torsten, thanks for our comment. Yes i know that editing the database directly is a bad thing, but I was so "blank" at what was going on, and thought i would give it a try. To (2), Creating a new object works fine, as long it have'nt existed before. It only occurs when i have deleted it first. Im not at work right now, and therefore cant get access to the files. Will provide them, first thing tomorrow./Dennis

Does the machine stil show in v_r_System or v_gs_system_disc (that second name may not be exactly right, I don't have a site in front of me now, it should be close enough for you to know what I mean) John Marcum | http://myitforum.com/cs2/blogs/jmarcum/|

Problem (1): i dont think i was so clear about this. Since we are having a little different setup than normal, the PXE works fine, but as soon as it is running in the boot enviroment it restarts. The smsts.log says "There is no advertisement for the specific computer". When i look at the settings for the machine console, it says it does have one. Problem (2): we don't know your "non-standard setup" ;-) Could you add details? The PXE service point won't deliver a boot image at all if there was not advertisement assigned to that client when not using unknown computer support. So that advertisement must still be present when booting in WinPE.