Situation: After configuring LAPS, the client finds some computers’ local administrator password generated by LAPS doesn’t work. They have multiple IT people to try it. LAPS UI and Get-AdmPwdPassword -ComputerName pco1 shows the same password. But the PC doesn’t take it. They also run gpupdate /force on the PC.
Troubleshooting: we find the problem. Some apps and services use administrator account with original password to login. That locked the administrator account.
Situation: The client just configured Microsoft Local Administrator Password Solution in their domain environment. After that, some computers getting thee errors:
Event ID: 7
The computer does not have the necessary permission to write the local administrator password to its object in Active Directory. Please submit an AD Request to have permissions set on your Department OU.
Event ID: 101
The assignment of application Local Administrator Password Solution from policy LAPS GPO failed. The error was : %%1274
Event ID: 103
The removal of the assignment of application Local Administrator Password Solution from policy LAPS GPO failed. The error was : %%2
Event ID: 108
Failed to apply changes to software installation settings. The installation of software deployed through Group Policy for this user has been delayed until the next logon because the changes must be applied before the user logon. The error was : %%1274
Troubleshooting: 1. It doesn’t has LAPS UI.
2. We find the LAPS is not installed correctly. LAPS folder under C:\Program Files doesn’t shows AdmPwd.UI.
3. LAPS UI on Manage Computer doesn’t show the computer local administrator’s password.
Troubleshooting: They didn’t move computers into LAPS OU so that failed to apply changes to software installation settings. Move the computers into the LAPS OU and Re-install LASP UI.
Situation: After configuring LAPS, the client gets this Event 12294: The SAM database was unable to lockout the account of Administrator due to a resource error, such as a hard disk write failure (the specific error code is in the error data) . Accounts are locked after a certain number of bad passwords are provided so please consider resetting the password of the account mentioned above.
Troubleshooting:
Error ID 12294 means there are numerous failure authentication events in security log due to incorrect credentials or could be a virus issue.
As you have changed the built-in domain Administrator password then ensure that the credentials are updated everywhere. e.g. for service account, IIS application pool, account tied to a scheduled task, virtual machine, mapped drice, etc…
If you have already verified the the old Administrator credentials are updatetd everywhere then the reason for event 12294 is worm virus and you need to full virus scan and Malicious Software Removal tool Virus to remove the Win32/Conficker malware family.
Event ID: 12294 Woes
http://blogs.technet.com/b/mempson/archive/2012/01/13/event-id-12294-woes.aspx
Malicious Software Removal tool Virus to remove the Win32/Conficker malware family.
http://support.microsoft.com/kb/962007
Situation: The user is member of IT group. His home computer Outlook shows the group. The office computer doesn’t show it.
Troubleshooting: In the most cases, the office computer Exchange cache mode is unchecked. Checking should fix the problem.
Situation: When working on Outlook, you may receive this message “The operation cannot be performed because the message has been changed” randomly.
Resolution 1: Run Outlook repair. Go to File>Account Settings>Repair.
You can use the Inbox Repair tool (SCANPST.EXE) to diagnose and repair errors in your Outlook data file.
Resolution 2: Run office online repair.
Resolution 3: Try running the SARA Tool: https://diagnostics.outlook.com/#/
Resolution 4: It could be add-ins issue. Go to Outlook add-in Adobe Send & Track for Microsoft Outlook – Acrobat. Disabling it.
Resolution 5: Enable Exchange cached mode.
Resolution 6: That happens because you may have a large email size so that you must wait a moment for the sync completed.
Resolution 7: This seems to be a problem only with IMAP accounts.
I fixed my problem on the IMAP account (which, ahem, started after a Microsoft update) by using Outlook’s “repair” tool:
– In Outlook, right click on the mailbox in the left-side navigation bar.
– Choose “Account Properties.”
– In a blue toolbar about 1/3 of the way down the window, “Repair” is one of the choices.
– Click Repair. It only took about 5 seconds.
If you move the emails and receive this popup,
2. If above doesn’t work, uncheck all options under Conversation Clean Up
3. Account Settings > Open your account > More settings > Under Advanced tab, put INBOX in Root Folder Path. (If your all folders disappear, simply remove INBOX from here). Note: Do NOT use option # 3 above. With an IMAP account this will empty an entire folder! Really, REALLY dumb suggestion that cost me a ton of data!
4. Select Cleaned up items will go to this folder.
This is a known issue with IMAP accounts. The change (read state) needs to sync with the server before you can move it, which only takes a split second, but outlook keeps a hold on the message until you switch messages.
Situation: The client uses Veeam backup to back up their Hyper-v VMs. The backup doesn’t work and rescan Backup Repositories takes forever.
Troubleshooting: We find the client just configured Microsoft Local Administrator Password Solution (LAPS). All local and domain administrators’ passwords have been managed by LAPS. So, administrator save in the Veeam don’t work. There are some places need to check the credentials.
4. Select Properties
5. Navigate to Credentials.
6. Edit credentials
If you have multiple Backup Repositories, check them by going to Property.
Check the Share Credentials.
Situation： When starting or restarting a Windows service, you may receive this message: This user can’t sign in because this account is currently disabled.
Troubleshooting: In most cases, the Logon account password is expired or disable.
Situation: The client uses Veeam backup to back up their Hyper-v VMs. The backup doesn’t work on multiple Hyper-V hosts. Source host requires Veeam integration components to be upgraded.
Troubleshooting: We find the client just configured Microsoft Local Administrator Password Solution (LAPS). All local and domain administrators’ passwords have been managed by LAPS. So, administrator save in the Veeam don’t work. There are some places need to check the credentials.
4. Select Properties
5. Navigate to Credentials.
6. Edit credentials
If you have multiple Backup Repositories, check them by going to Property.
Check the Share Credentials.
Situation: Whenever the suer click on New Email, the Outlook closes.
Resolution 1: Go to Control Panel>Programs and Features>Uninstall. Highlight the Microsoft 365>Change>Repair>Online repair.
Resolution 2: Create a new email. profile. Go to Control Panel>Mail. Create a new email profile. Restart the Outlook using the new profile.
Resolution 3: If you see an event viewer error with Add-ins, you may want to disable the add-ins. Or disable all add-ins for a test.
Situation: The client has a general accounting email address. Accounting mailbox doesn’t show any emails. Message trace shows the status of all emails is Resolved.
Troubleshooting: 1. If status shows Resolved, it could be the email address could be forwarded to someone else. By the way, If the mailbox receives emails, trace message should show Delivered.
2. It may be removed to guaranty.