Disappearing hosts from host list

@Wayne-Workman thx for the work. About primary. Can it be checked somehow by code that a host with no primary mac cannot be save? I think i have a guess how it came.

That host field, the mac is normally updated when new cloning starts (we regularly do few hosts in pack as company now upgrades all pc “one by one”. I will check, but i think it is done as follows: new mac copied from hw library and pasted into for host record. Since now it has primary and other field, maybe colleague did it to other field, not the primary (he only deleted primary, then by mistake copied the new mac to nonpripary field.

If possible, pls dont let it be updated if no primary mac entry exists. Maybe it prevents this. I will ask him how he does, but i fear he wont remember the exact process, as it is dont in “half robot” mode (tons of pcs are repared, etc).

As for the hostADPass field. I forgot to ask it, but inspecting the problem i saw that, too. Is that field is for entering hosts to domain? I was not even aware that they use it. As far as i remember it is dont by scripting on the host, not by fog at all.

@Tom-Elliott No, none did any manual work about that password :) Those who use fog for imaging, well, dont even care how it works. :) I will ask them, but i am totally sure they will be surprised even hearing it! (and shocked that password thing)

Also - I don’t know how you got a clear-text password into the hostADPass field inside the hosts table - that shouldn’t even be possible. I’m suspecting someone did some manual work in the database and did that.

@Foglalt I just set all my MACs hmPending field to 0, everything is fine.

I need to see your problem myself. If you would message me via the forums messaging system, I can give you my email address and if you trust me enough, you can email me a copy of your database for me to look at. I should be able to very quickly figure out what’s wrong if I had a copy of your DB.

Btw if zero means it is not pending, how can i get rid of this host? As it has mac, mac is not pending is it a legit host playing hide and seek somehow? :) Anyway i see one interesting thing. the problematic host’s mac has no primary flag. Can it be the problem? if i modify that from 0 to 1 maybe it comes back to visible? (can it be done with database browser anyway, or is it “rape” of the database integrity? :)

Additional information, until you can suggest me anything how to remove the unwanted “already registered” host i watched the database with a browser to see manually under the hood. host is actually there in hosts table. as i dont know the links of tables i wont delete it :) but it may help if u need more info on this issue.

I did upgrade, but sadly it says that “hostname exists already”. as i am not an sql pro, can you pls tell me what else can be done to find reason fo it? :)

one more thing. as it first occured the colleague who found this issue uses his own “clone hosts” and when imaging comes, he only renew MAC of the new hw, changes image if needed, but hostname or host “item” is not deleted. it sounded absolutely working, but does it any wrong? (in my logic it doesnt, but pls confirm me)

Case reopened. I still use version 1.3.0 (well, have no time to test all versions in the last few subversions were fast to come out). Last time i could not register new host cos it said mac already used. not it says hostname exists, but i cant find it. (well, the new host lister part in gui is strange for me, but other hosts it list i search for but not this particular one).

Do you maybe have another tip what is it? (i did what you suggested last time, but now it “affected zero rows” now).

I would now like to try to get a fresh start as my database began it’s life in 2009. I’ve backed up my database and exported my hosts, printers etc to csv files so I can copy paste the information back into the FOG GUI. How do I make a fresh empty FOG database but keep my settings?

@Foglalt some of the trunk versions between 1.2.0 and 1.3.0 had serious issues. We’re confident those are resolved now in 1.3.0 onwards. You probably had the issue for a long time (junk data in your database) without even noticing an issue until just now.