Yip, I'm a bit squeamish about screenshots disclosing domain names etc. I did try blanking out the necessary details but then there wasn't much info left! ;)
But it is something like this...
Account Name User Name Default Type Owner
domain\administrator domain\administrator Common domain\kev-admin
domain\kevadmin domain\kevadmin yes Common domain\kev-admin
previousit previousit Common domain\previousit
System Logon Account domain\previousit2 Common domain\administrator
So the previous IT company had 2 accounts.
The kevadmin account is the same AD account as kev-admin (it was renamed in AD after BE configured).
All backup jobs are configured with the kevadmin account except for 2 jobs running as administrator (these 2 jobs never fail).
I want to remove all accounts except for kevadmin (and it would be nice to have the BE owner match the AD account).
Whilst logged on to the windows server as domain\administrator I cannot delete/replace the System Logon Account - Unable to replace old Logon Account. The server received inccorrect data.
I cannot delete the 'previousit' account - The account 'previousit' cannot be deleted because the following users have selected it as their default logon account and one or more of them are currently logged on to the media server - domain\previousit. They aren't logged on, there are no services running under this account and no jobs use this account for credentials.
I try deleting domain\administrator in the Manage Logon Accounts, replace with domain\kevadmin first as the domain\administrator account is in use by 2 jobs - Unable to replace old Logon Account. The server received inccorrect data.
Thanks to DarthBilly, logging on the the Windows server as domain\administrator gets me past the errors when trying to edit logon accounts and prompyed me to enter the administrator (or owner) credentials before they were rejected (the AD password for this account has been changed since. However, I am now being presented with invalid data errors :(
So, something is definitely not working as it should and its a mess so a clean slate sounds like a good idea to me.
PS. I'm not actually repsonsible for this mess but I've certainly learnt that BE should have logon accounts edited before amending AD credentials.