I have priority call for a tech we cannot make any changes to. My initial research points to the fact the account is being accessed by another user/machine and therefore locked out. "unable to change user's access mode"
Been reading restarting the db service or sb server can resolve this. Any implications on doing this in the middle of day?
Yes, you may create orphans if you do so. Do you have multiple instances of EEM active (possibly from various computers)?
yes we do. 6700 users, 5200 laptops. many many admins. support said it wont let me stop the service if any critical syncs are going on. i would rather do this off hours myself.
Then you have got an answer. Do you have service window established when you restart database services (beside other things)? We call it a "maintenance time" and everyone knows when it occurs.
Would local recovery bypass this issue since its PBA? We could always do an emergency boot for the time being. Just curious on what you thought.
I hear ya but we have 220 techs and only 13 of us have full access. Happens all the time. Daily. Wondering if pushing the local recovery would alleviate the calls.
Shouldn't be getting that many locks in a day, are you assigning a huge number of users to each machine?
How many connections does the server recieve during peak hours? What are you synchronization parameters for your machines? Does your helpdesk technicians connect remotely through a mini-admin console? Sounds like network connections to the server are dropped frenquently.
I suggest you change the TCP/IP KeepAliveTime in the server's registry to 5 minutes (default is 2 hours). It will requires a server reboot. The object lock will clear in this time period and you will be able to work with the account. This is suggested in the EEPC Best Practices guide that you can obtain through the McAfee Service Portal.