El conocimiento al alcance de todos.

Thanks to: https://activedirectorypro.com A user calls the helpdesk, you unlock their account, 5 minutes later they call again with another lockout. At this point, everyone is frustrated and no one knows what the heck is causing the lockouts. I’ve got good news. There are account lockout tools that can assist and quickly tracking down the source of the issue. In this post, I’ll walk you through the exact step by step process I use for tracking down the source of random account lockouts. Recommended Tool:   SolarWinds Admin Bundle for Active Directory 3 Free tools, find inactive user or computer accounts  and quickly bulk import new user accounts. Download your free copy of Admin Bundle for Active Directory There are many  Active Directory Tools  that can assist with troubleshooting account lockouts, but my favorite is the Microsoft Account Lockout and Management Tool. It’s free, simple, easy to use and comes bundled with several tools. Common caus

Thank to: https://www.itprotoday.com/ Q: Why am I receiving an error when trying to protect a SQL Server 2012 server using System Center 2012 Data Protection Manager? A:  If you have performed a fresh SQL Server installation and are trying to protect it with System Center 2012 Data Protection Manager (DPM), you might get an error in DPM that the server can't be protected. If you open Event Viewer and look in the Application log, you might see an error similar to the following: Log Name: DPM Alerts Source: DPM-EM Date: 5/6/2013 3:53:08 PM Event ID: 3170 Task Category: None Level: Error Keywords: Classic User: N/A Computer: savdaldpm12.savilltech.net Description: DPM could not start a recovery, consistency check, or initial replica creation job for SAVDALSQL01\AppController on savdalsql01.savilltech.net for following reason: (ID: 3170) The DPM job failed for SAVDALSQL01\AppController on savdalsql01.savilltech.net because the protection agent did not have sysadmin privi