As a result of a query – I wanted to advise how to check if you are having specific issues with cached credentials – and why you don’t get notified like you did before … here is some MS info that shows the mechanism for getting alerted – which will certainly help you pin down the problem.
User is not alerted when logging on with domain cached credentials
SYMPTOMS
When you attempt to log on to a domain from a Windows-based workstation or member server and a domain controller cannot be located, no error message is displayed. Instead, you are logged on to the local computer using cached credentials.
Back to the top
RESOLUTION
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
To configure Windows to display a message when a user is logged on using cached credentials, follow these steps on each computer on which you want to display a message: 1. Start Registry Editor (Regedt32.exe).
2. Select the following registry key:
HKEY_LOCAL_MACHINESOFTWAREMicrosoft Windows NTCurrentVersionWinlogon
3. On the Edit menu, click Add Value, and then add the following value:
Value Name: ReportControllerMissing
Data Type: REG_SZ
Data Value: TRUE (must be all uppercase)
4. Quit Registry Editor.
For each user for whom you want to display a message, follow these steps:
1. Start Registry Editor (Regedt32.exe).
2. Select the following registry key:
HKEY_CURRENT_USERSoftwareMicrosoftWindowsNTCurrentVersionWinlogon
3. On the Edit menu, click Add Value, and then add the following value:
Value Name: ReportDC
Data Type: REG_DWORD
Data Value: 1
4. Quit Registry Editor.
MORE INFORMATION
To verify that you are logged on to the domain, check the System log. If you were logged on using cached credentials, you see the following event:
Event ID 5719
No Windows domain controller is available for domain domain_name the following error occurred: There are currently no logon servers available to service the logon request.
When you are using cached credentials, you may not see evidence of that immediately. Evidence is that you do not have access to items such as group policies, roaming profiles, home folders, or logon scripts.
As per the article on other issues with credentials – once you know its happening its easier to fix – it’s when you are not aware that the user is not “really” logging in that these problems can lead you up the garden path.