Page 1 of 1

Re-starting conflict

PostPosted: Mon Mar 28, 2011 10:13 am
by uniceftacro
So far Alloy Discovery 6 connector has been updating our Navigator database quite good.
However, one computer appears in discovery but not in navigator, most likely because it was originally detected as a computer name conflict and was manually resolved to update instead of create.
Is there a way to force the conflict again so that navigatior creates the computer/asset records properly?

Re: Re-starting conflict

PostPosted: Wed Mar 30, 2011 10:15 am
by eliaslynch
uniceftacro computer appears in discovery but not in navigator...

Not sure how this might have happened, but sounds like there must have been some conflict in AN6 on import and it was handled in the wrong way. Otherwise AN6 computers are linked to AD6 computers by their ID in AD6 so it's hard to have this happen I think.

I guess deleting the computer in AD6 will cause it to generate a new ID and then the ID won't match a computer in AN6 and it will cause a conflict or create a new computer.

Again just a guess, but probably a good one.