Month: November 2022

Situation: The client just configures Local Administrator Password Solution (LAPS) on their domain. It works for a while. Now, most domain computers don’t install LAPS and LAPS doesn’t change the administrator password.

Troubleshooting: It could be the fast logon issue. Please check any Event Viewer for any issues and refer to these posts:

• 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
• Event ID: 1112 – The Group Policy Client Side Extension Software Installation was unable to apply one or more settings because the changes must be processed before system startup or user logon
• The assignment of application Local Administrator Password Solution from policy LAPS GPO failed. The error was : %%1274

 

Situation: The client just configures Local Administrator Password Solution (LAPS) on their domain. It works for a while. Now, most domain computers don’t install LAPS and LAPS doesn’t change the administrator password..

Troubleshooting: 1. gpresult /R shows the LAPS policy has been applied to the computer.

Applied Group Policy Objects
—————————–
LAPS GPO
Default Domain Policy
Local Group Policy

2. The Event Viewer shows this Event ID 103

The removal of the assignment of application Local Administrator Password Solution from policy LAPS GPO failed.  The error was : %%2

Resolution 1: Enable the Specify startup policy processing wait time

1. On the Domain Controller, run Group Policy Management

2. Right click on the policy you want to modify, for example LAPS GPO in our example, click on Edit.

3. Navigate to:

Computer Configuration > Policies > Administrative Templates > System > Group Policy.

4. Enable the Specify startup policy processing wait time or Startup policy processing wait time. Set Amount of time to wait (in seconds): = 90 or more for a test.

Resolution 2: Enable Always wait for the network at computer startup and logon

1. Repeat resolution 1 step 1 and 2.
2. In a GPO that applies to that computer, add the following setting:
   • Computer Settings
     • Administrative Templates
       • System
         • Logon
           • Always wait for the network at computer startup and logon – Enabled

3. Check Enabled

Resolution 3: Make sure the computer can access the LAPS software and have permissions. For example, you may assign everyone to access the LAPA shared folder for a test.

Resolution 4: And I just found another different cause of this error. If you have “Spanning Tree” configured on the ethernet switch connected to the problem workstation, it will delay activation of the switch port when the PC boots up. Disabling Spanning Tree for the switch port or enabling “Spanning Tree Portfast” for the switchport solved this problem on a few of my workstations.

Situation: The client just configures Local Administrator Password Solution (LAPS) on their domain. It works for a while. Now, most domain computers don’t install LAPS and LAPS doesn’t change the administrator password..

Troubleshooting: 1. gpresult /R shows the LAPS policy has been applied to the computer.

Applied Group Policy Objects
—————————–
LAPS GPO
Default Domain Policy
Local Group Policy

2. The Event Viewer shows this 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

Resolution 1: Enable the Specify startup policy processing wait time

1. On the Domain Controller, run Group Policy Management

2. Right click on the policy you want to modify, for example LAPS GPO in our example, click on Edit.

3. Navigate to:

Computer Configuration > Policies > Administrative Templates > System > Group Policy.

4. Enable the Specify startup policy processing wait time or Startup policy processing wait time. Set Amount of time to wait (in seconds): = 90 or more for a test.

Resolution 2: Enable Always wait for the network at computer startup and logon

1. Repeat resolution 1 step 1 and 2.
2. In a GPO that applies to that computer, add the following setting:
   • Computer Settings
     • Administrative Templates
       • System
         • Logon
           • Always wait for the network at computer startup and logon – Enabled

3. Check Enabled

Resolution 3: Make sure the computer can access the LAPS software and have permissions. For example, you may assign everyone to access the LAPA shared folder for a test.

Resolution 4: And I just found another different cause of this error. If you have “Spanning Tree” configured on the ethernet switch connected to the problem workstation, it will delay activation of the switch port when the PC boots up. Disabling Spanning Tree for the switch port or enabling “Spanning Tree Portfast” for the switchport solved this problem on a few of my workstations.

Situation: The client just configures Local Administrator Password Solution (LAPS) on their domain. It works for a while. Now, most domain computers don’t install LAPS and LAPS doesn’t change the administrator password.

Troubleshooting: 1. gpresult /R shows the LAPS policy has been applied to the computer.

Applied Group Policy Objects
—————————–
LAPS GPO
Default Domain Policy
Local Group Policy

2. The Event Viewer shows Event ID:      1112

The Group Policy Client Side Extension Software Installation was unable to apply one or more settings because the changes must be processed before system startup or user logon. The system will wait for Group Policy processing to finish completely before the next startup or logon for this user, and this may result in slow startup and boot performance.

Resolution 1: Enable the Specify startup policy processing wait time

1. On the Domain Controller, run Group Policy Management

2. Right click on the policy you want to modify, for example LAPS GPO in our example, click on Edit.

3. Navigate to:

Computer Configuration > Policies > Administrative Templates > System > Group Policy.

4. Enable the Specify startup policy processing wait time or Startup policy processing wait time. Set Amount of time to wait (in seconds): = 90 or more for a test.

Resolution 2: Enable Always wait for the network at computer startup and logon

1. Repeat resolution 1 step 1 and 2.
2. In a GPO that applies to that computer, add the following setting:
   • Computer Settings
     • Administrative Templates
       • System
         • Logon
           • Always wait for the network at computer startup and logon – Enabled

3. Check Enabled

Resolution 3: Make sure the computer can access the LAPS software and have permissions. For example, you may assign everyone to access the LAPA shared folder for a test.

Resolution 4: And I just found another different cause of this error. If you have “Spanning Tree” configured on the ethernet switch connected to the problem workstation, it will delay activation of the switch port when the PC boots up. Disabling Spanning Tree for the switch port or enabling “Spanning Tree Portfast” for the switchport solved this problem on a few of my workstations.

Situation: The client just configures Local Administrator Password Solution (LAPS) on their domain. It works for a while. Now, most domain computers don’t install LAPS and LAPS doesn’t change the administrator password..

Troubleshooting: 1. gpresult /R shows the LAPS policy has been applied to the computer.

Applied Group Policy Objects
—————————–
LAPS GPO
Default Domain Policy
Local Group Policy

2. The Event Viewer shows this error.

Log Name:      System

Source:        Application Management Group Policy

Event ID:      101

Level:         Warning

Description:

The assignment of application Local Administrator Password Solution from policy LAPS GPO failed.  The error was : %%1274

Resolution 1: Enable the Specify startup policy processing wait time

1. On the Domain Controller, run Group Policy Management

2. Right click on the policy you want to modify, for example LAPS GPO in our example, click on Edit.

3. Navigate to:

Computer Configuration > Policies > Administrative Templates > System > Group Policy.

4. Enable the Specify startup policy processing wait time or Startup policy processing wait time. Set Amount of time to wait (in seconds): = 90 or more for a test.

Resolution 2: Enable Always wait for the network at computer startup and logon

1. Repeat resolution 1 step 1 and 2.
2. In a GPO that applies to that computer, add the following setting:
   • Computer Settings
     • Administrative Templates
       • System
         • Logon
           • Always wait for the network at computer startup and logon – Enabled

3. Check Enabled

Resolution 3: Make sure the computer can access the LAPS software and have permissions. For example, you may assign everyone to access the LAPA shared folder for a test.

Resolution 4: And I just found another different cause of this error. If you have “Spanning Tree” configured on the ethernet switch connected to the problem workstation, it will delay activation of the switch port when the PC boots up. Disabling Spanning Tree for the switch port or enabling “Spanning Tree Portfast” for the switchport solved this problem on a few of my workstations.

 

 

 

 

Situation: The client just creates a new mailbox for group users. However, none of the users can’t see the emails with this message:

“We didn’t find anything to show here”

Resolution 1: Changing Hidden state to ‘Compact’ or ‘Preview’.

1. Click on the specific folder where you receive error ‘We didn’t find anything to show here.’

2. Select the ‘View’ tab from the Outlook toolbar.

3. Click ‘Change View’ from the ‘Current View’ group.

4. In the resulting drop-down menu, does it say that this folder has been set to a ‘Hidden state’?

5. If so, please change it to ‘Compact’ or ‘Preview’ (depending on your preference).

Resolution 2: “Reset View”

If “Reset View” was grey, click on the “reset View”. that may fix the problem.

Resolution 3:  I just turned off my message preview and all of the mail in my box showed up.

Resolution 4: It could be you reach some of Outlook limitations such as account limitation, session limitation, folder limitation, space limitation and email limitation. Googling for these limitations.