Author: Bob Lin

Situation: the user can’t download and install Office 365.

Troubleshooting: 1. try to add www.office.com to Internet Option>Security. That doesn’t fix the problem.

2. Try different Internet Browser. The same problem.

3. Go to Internet Browser settings to clean the cooks and history. That fix the problem.

Situation: the client has Palo Alto firewall and use their VPN for remote access. The problem is they can’t copy big files from the network resources to the VPN client.

Troubleshooting: We don’t know the reason for that. However, if we copy the file through RDP, that works fine. This is the temporary resolution.

Situation: The client is running Exchange 2010 on Windows 2012 R2 Domain Controller. After they demoted one of DCs, they can’t login the Exchange server.

Troubleshooting: 1. Make sure you have correct DNS settings on Exchange serve.

2. The problem could be a result of the Exchange Management Console caching the domain controller details in the MMC temp files. It caches the data but it’s not smart enough to update the data or locate another DC. To fix the issue you have to remove the MMC cache file from the users profile.

Use the following steps to clear the EMC MMC cache file:

1) Close the EMC if you have it open
2) Go to the User’s profile directory and delete the Exchange Management Console file.
3) File location can be found here:

• C:\users\<specific user>\AppData\Roaming\Microsoft\MMC\Exchange Management Console

4) Reopen the EMC

Situation: The user has a new PC running Office 365 latest version. It worked for a couple days. Now, when she opens the Outlook, it disappears. The Task Manager doesn’t show the Outlook running.

Troubleshooting:

1. Run Office 365 repair, that doesn’t fix the problem.
2. Installing Office 365 update, that doesn’t fix the problem.
3. Disabling all Add-ins, that doesn’t fix the problem.
4. Run Microsoft Support and Recovery Assistant for Office 365, that doesn’t fix the problem.
5. Try different Outlook profile. it is the same problem.
6. It could be bad PST problem. Run ScanPST.exe to Repair PST files. In Office 365/Office 2016, ScanPST.exe is located in C:\Program Files (x86)\Microsoft Office\root\Office16. That fixes the problem.

1. Install the proper operating system and name the new server with the same name as the lost server.
2. Reset or rejoin the computer account for the lost server.
3. Install the necessary prerequisites and operating system components on the target server. For details, see Exchange Server system requirements.
4. On the target server, open File Explorer, right-click on the Exchange ISO image file that you downloaded, and then select Mount. Note the virtual DVD drive letter that’s assigned.
5. Open a Windows Command Prompt window. For example:
6. In the Command Prompt window, use the following syntax:

Copy

<Virtual DVD drive letter>:\Setup.exe /IAcceptExchangeServerLicenseTerms /Mode:RecoverServer [/TargetDir:<Path>] [/DomainController:<ServerNameOrFQDN>] [/DoNotStartTransport] [/EnableErrorReporting]

This example uses the Exchange installation files on drive E: to install Exchange in the default location (%ProgramFiles%\Microsoft\Exchange Server\V15) and recover the Exchange server.

Copy

E:\Setup.exe /IAcceptExchangeServerLicenseTerms /Mode:RecoverServer

This is the same example, but a custom location for the Exchange program files is required to match the location on the lost server.

Copy

E:\Setup.exe /IAcceptExchangeServerLicenseTerms /Mode:RecoverServer /TargetDir:”D:\Program Files\Exchange”

7. After Setup has completed, but before you put the recovered server into production, reconfigure any custom settings that were previously present on the server, and then restart the server.

Situation: The client has WSUS. The WSUS synchonization works fine.

The Last Status Report shows Installed is 100%.

However, the workstations don’t install the update and shows “Your device is at risk because it’s out of date and missing important security and quality fixes”

Cases 1:

I uninstalled this update (KB4058043) and did a manual cumulative update (KB4073290) which fixed the issue for me. Since then the error is gone from the Windows update.

Case 2: Install the latest cumulative update manually.

Case 3: Uninstall the KB4058043 Update.

Case 4: Make sure you have correct DNS settings.

Case 5: Have you been maintaining the wsus server in regard to using the server cleanup wizard? We were having issues at one time, and that fixed our issues.

Situation: Recently, One of the users keeps having a problem to login her domain computer because the account is locked.

Troubleshooting: The company uses Office 365 and has 90 password expiration policy. After check Microsoft Azure sign-ins status of this user, we find it is her mobile phone failed login. The problem is she changed the domain account password but did do so in the mobile phone. To check Azure sign-ins status, login Azure and go to Users>Sign-ins. Here you can check Basic info and Device info.

Other suggestion: 1. Check Event Viewer for ID 4740.

2. Use Microsoft Account Lockout and Management tools.

3. Check out the freeware Netwrix Lockout Examiner as it can be used to track it down if you can’t find it in the security logs on the DC.

https://www.netwrix.com/account_lockout_examiner.html

4. Check your network drive mappings.  You may have an old one created when you had a different password.  Your computer is sending the old information when it checks items on those drives.

5. Scheduled tasks.  Clear any not in use.  You may have created an item using your login and a former password.  When the schedule attempts to execute, it will create a failed login.

6. Service accounts.  Check any services that you may have set up under your login that may contain a former password.  This could be on ANY workstation or server that you have used.

7. Go to Control Panel > Credentials Management to clean the password.

Situation: The client use Mitel phone system. After they restarted the appliance, no one can make the phone call and it shows: the server required for this operation is not available the users can’t change the phone from DND to Active.

Resolution: Reset Turn the ShoreTel Switch TS100DA by turning it off and then on.

Situation: the client has been using Mitel/ShoreTel phone system. Some users compliant ” Internally I do not have any troubles, but all outside callers complain about static and breaking up regardless if it is inbound and outbound calls”.

Troubleshooting: 1. Check the switch port and make sure the QoS is configured on the network to prioritize voice traffic.

2. If the user has softphone, replace it with deskphone for a test.

3. Make sure the Mitel phone settings is Softphoone also.

4. Try to reset the softphone or restart the Mitel Connect or even restart the computer.

Please view this step by step video:

1. Ensure your device is paired with your audio or navigation system. For help pairing your device, visit HyundaiBluetooth.com.
2. Open a music player or podcast app on your device and begin playing.
3. Press the MEDIA button on your audio or navigation system to listen to the audio from your device in your vehicle
4. Use steering wheel or on-screen buttons to control the audio playback