Discovery is using incorrect credentials for Linux and windows server

[reddy122]

Some Linux servers are getting discovered using 'x' credentials which is created long back.

But now network team is highlighted that are not managing this 'x' account instead they have created 'y' account and managing this account as a unique one for all Linux servers and provided required access to get data.

So, we have created new credentials(y account) given by network team and most of them are getting discovered using newly created 'y' account , however some Linux servers are still getting discovered using the old credentials('x' account).i have tried to validate the credentials for these server with newly credentials and these are getting validated but unable to pick up the same credential while getting discovered.

I didn't turned turn off the old credentials ,because we are not sure how many will use newly created credentials

I have tried by giving order 90 to new credentials(y account) and 100 to old credentials(x account) but this also failed as still using old credentials.

only method is by made active false to old credentials ,so that we can force discovery to use new credentials.

Can anyone suggested any alternative methods to force discovery use new credentials?

[Pratiksha]

You need to delete the credential affinity. Then the new order will work. 

[reddy122]

Hi @Pratiksha ,

Is it the best practice?

[reddy122]

I have tried it by deleting record in the affinity table ,but still it is using the same by creating new record in the affinity table

[Pratiksha]

You can give a specific mid server on the schedule and on credentials mention the same mid server.