OM server is locking out the Windows AD service account used by snapdrive on the host servers. The problem is I can not understand WHY?
OM runs on a Windows server with DAS and does not have snapdrive installed and the OM 'windows' services do not use this account. OM connects to the filers via root or a dfm_service account so I can not understand why this is happening.
The Window's DC log files show the OM server as the cause of the wrong password attempts (every 15 minutes) and since the OM service has been turned off, we have had no more 'lock outs' on the snapdrive service account.
Any ideas why this may be happening or how to trouble shoot it?
Had a similar issues cause by an incorrect password used when installing SnapDrive 6.2 and Protection Manager Integration. RE-installing snapdrive would not update DFM with the correct password. I had to use snapdrive cli to update the password with DFM.
The account would be locked out at the very beginig of each SMSQL backup.
Wow, this saved me so much time! I tried to reinstall Snapdrive to add in the protection piece and it kept locking the account in AD. After updating using the snapdrive cli it works like a champ! Thanks for sharing!!