WSUS: Unable to Find Resource

Situation: The client is running WSUS on their Windows 2012 R2. Many computers have failure with this message: Unable to Find Resource

Troubleshooting: 1. Try add MIME Type:

•Check that the KB3159706 for decryption of ESD content is installed

•Checked that the prerequisites for KB3095113 are all installed

•Checked that the KB3095113 for WSUS support for Windows 10 feature upgrades.

•Set the MIME type on the IIS Server for the .esd file and .msu file types(which the above update should have sorted).

•Removed the Windows Update cache from the machines, stopped the BITS/Windows Update services and restarted.

•Restarted IIS Website

•Rebooted WSUS server

•Checked Windows Firewall status (disabled on Server)

•Asked the Windows 10 machine to get updates from Windows Updates rather than WSUS (this appeared to download and install OK) so this makes me think it’s an issue with our WSUS server.

•Installed the Windows 10 ADMX templates and set the “Download Mode” in GPO to both “Bypass” and “HTTP only”.

•Set WSUS to download express installation files

2. If the 1703 upgrade is synced into WSUS before KB3159706 was installed, then after performing the necessary update of KB3159706 and its post-installing servicing (link), we still need to follow the instructions here:https://social.technet.microsoft.com/Forums/en-US/b1165b9d-bad3-4ce3-9fc1-0fe3876df5c6/0xc1800118-with-1506301703171834rs2esd-after-kb3159706-manual-steps-the-decryptionkey-in?forum=winserverwsus.

There are basically 4 steps to be performed:

1 – Remove packages synced before KB3159706 is installed. Via WSUS server’s powershell:Get-WsusClassification | Where-Object -FilterScript {$_.Classification.Title -Eq “Upgrades”} | Set-WsusClassification -Disable$s = Get-WsusServer$1703Updates = $s.SearchUpdates(“version 1703”)$1703Updates | foreach { $_.Decline() }$1703Updates | foreach { $s.DeleteUpdate($_.Id.UpdateId) }Get-WsusClassification | Where-Object -FilterScript {$_.Classification.Title -Eq “Upgrades”} | Set-WsusClassification.

2 – Delete from WSUS databse the bad contents about upgrade 1703, run from database. Mind: remove the trailing semi-colon from the SQL script in the post. They might result in the error of “table variable not declared”declare @NotNeededFiles table (FileDigest binary(20) UNIQUE)insert into @NotNeededFiles(FileDigest) (select FileDigest from tbFile where FileName like ‘%15063%.esd’ except select FileDigest from tbFileForRevision)delete from tbFileOnServer where FileDigest in (select FileDigest from @NotNeededFiles)delete from tbFile where FileDigest in (select FileDigest from @NotNeededFiles)`

3 – Restart syncing by WSUS GUI or powershell command, on WSUS server.$s = Get-WsusServer$sub = $s.GetSubscription()$sub.StartSynchronization().

4 – Repair client computers that has the error, on client computer: Control Panel->Troubleshooting->Windows Update->Try troubleshooting as an administratorDuring all these activities, no reboot is required. Then, retry and good-luck!

•Build a different Windows Server 2012 R2 machine, updated Windows Update GPO policy and got machines checking in, but download of this one update does still not happen.

3. Modify Group Policy

It sounds like you need to change Group Policy settings; that’s usually how clients are pointed at the WSUS server in the first place, instead of Microsoft for updates.Edit GP and look in Comp Config -> Admin Temp -> Win Comp -> Win Update. Start by making sure Specify Intranet… is disabled. Disabled == clients will look to MS for updates.If GP isn’t specifying an intranet updates server, then perhaps someone manually configured the clients’ reg keys. Check a client’s HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\WindowsUpdate to confirm.

4. Add .esd

1. In Products/Classifications, make sure to check off the Upgrades box or Windows 10 will not be available to deploy. 2. You also will need to add a MIME type for *.esd as application/octet-stream at the top level in IIS. To do this: Open IIS Manager > Select the server name > From the “IIS” section in the centre of IIS Manager, open “MIME Types” > Click “Add…” > File Mame Extention: = .esd MIME type: application/octet-stream

What’s different Windows black screen and blue screen

Q: What’s different Windows black screen and blue screen?

A: In most cases, Windows blue screen is hardware, drivers and system files issues. The resolutions could be 1) unplug the hardware; 2) upgrade the drivers; 3) Restore system files.

Windows black screen could be registry issue, for example the registry files or setting has been damaged and modified. please refer to this article to troubleshoot it.

Windows OS goes to black screen after Windows update

Can ping any websites but can’t access them

Situation: After a new windows update, I can’t access any websites. However, I can ping them such as google.com and yahoo.com. I just can’t access them with page can’t be displayed message.

Troubleshooting: 1. If you have any anti virus or security software, disable it for a test.

2. Reinstall Drivers.

3. ipconfig /release /renew.

4. Change the DNS server, for example use 8.8.8.8.

5. Flush DNS by running these commands: ipconfig /flushdns and ipconfig /registerdns.

6. Run netsh winsock reset command.

7. Make sure no proxies set -> all default obtain automatically.

8. Make sure it is multihomed computer or the computer with multiple Network connections..

Windows OS goes to black screen after Windows update

Symptom: The client has a windows 7 PC. Windows OS goes to black screen after Windows update. It boots, but it goes to black screen after Windows popup.

Troubleshooting: 1. Safe mode and last known good configuration don’t fix the problem. Refer to this psot:

How to boot into Windows 10 Safe Mode in black screen

2. Run Windows repair locally, but can’t access because incorrect password.

3. Run Windows bootable DVD and run repair. But it doesn’t fix the problem.

4. Run Windows repair and select System restore. Select early system point, but that doesn’t fix the problem.

5. Run Windows repair and select command. The restore backup registry files. That fixes the problem. The step by step procedure can be find here:

How to recover a Windows system that does not start because of corruption in the registry

Note: 1. The registry backup files have been remove from \windows\repair in Windows XP to \windows\system32\config\regback in Windows 7 and 10.

2. OS may install on differnet drive instead of C drive.

windows 10 Critical_service_failed BSOD loop

Situation: The client has booting issue on his laptop running windows 10. It shows a BSOD with a “CRITICAL_SERVICE_FAILED” error, then restarts, goes back to the BSOD with the same error 3 seconds later, resets, and so on.

Troubleshooting: 1. This error is usually caused by a missing or corrupted device driver, or incompatibility issues with a newly installed hardware or driver. So as an initial recommendation, I would suggest you to disconnect any peripheral devices except for the mouse and keyboard and check if it helps.

2. Automatic Repair is a Windows recovery tool that can fix certain system problems that might prevent Windows from starting. Automatic Repair scans your computer for the problem and then tries to fix it so your computer can start correctly. Run Automatic repair and check the issue status.

Create Windows 10 ISO: http://www.microsoft.com/en-us/software-download/windows10

Please follow the below steps to perform the repair for the computer.

a) Insert the Installation Disk into the disk drive of the computer. Press any key from the keyboard when prompted to.

b) Follow the instructions till the Install Now screen and then Click Repair your computer.

c) Click Advanced Options.

d) Click Troubleshoot.

e) Click Automatic Repair.

f) Follow the on screen instructions.

3. Try safe mode or last known good. Then boot Windows was by booting with the option “Disable drivers signature enforcement“.

4. Perform a System Restore from Safe Mode

1) After your computer restarts for a few times, you should see Boot Options screen. From that screen choose Troubleshoot.

2) Next click on Advanced Options > Startup Settings.Click the restart button and wait for your computer to restart.

3) When your computer restarts you’ll be presented with the list of options. Press F4, F5 or F6 to enter into Safe Mode.

4) When Safe Mode starts type system restore into the search bar and run System Restore tool.

Please view the step by step video:

Run Windows System Restore to restore your system to an earlier state

5. Run Windows repair and select command. The restore backup registry files. That fixes the problem. The step by step procedure can be find here:

How to recover a Windows system that does not start because of corruption in the registry

Active Directory on this domain controller does not contain Windows Server 2016 ADOREP /FORESTPREP update

Situation: When upgrading Windows Server 2016 in a Windows 2012 R2 domain Controller, you may receive this message:

Active Directory on this domain controller does not contain Windows Server 2-16 ADOREP /FORESTPREP update


Resolution: Load Windows Server 2016 DVD. run these two commands on \support\adprep folder: Adprep /forestprep and Adprep /domainprep

D:\support\adprep>Adprep /forestprep

ADPREP WARNING:

Before running adprep, all Windows Active Directory Domain Controllers in the fo
rest must run Windows Server 2003 or later.

You are about to upgrade the schema for the Active Directory forest named ‘test.
local’, using the Active Directory domain controller (schema master) ‘TestSvr.te
st.local’.
This operation cannot be reversed after it completes.

[User Action]
If all domain controllers in the forest run Windows Server 2003 or later and you
want to upgrade the schema, confirm by typing ‘C’ and then press ENTER to conti
nue. Otherwise, type any other key and press ENTER to quit.

c

Current Schema Version is 69

Upgrading schema to version 87

Verifying file signature
Connecting to “TestSvr.test.local”
Logging in as current user using SSPI
Importing directory from file “D:\support\adprep\sch70.ldf”
Loading entries……
5 entries modified successfully.

The command has completed successfully
Verifying file signature
Connecting to “TestSvr.test.local”
Logging in as current user using SSPI
Importing directory from file “D:\support\adprep\sch71.ldf”
Loading entries……..
12 entries modified successfully.

The command has completed successfully
Verifying file signature
Connecting to “TestSvr.test.local”
Logging in as current user using SSPI
Importing directory from file “D:\support\adprep\sch72.ldf”
Loading entries……
17 entries modified successfully.

The command has completed successfully
Verifying file signature
Connecting to “TestSvr.test.local”
Logging in as current user using SSPI
Importing directory from file “D:\support\adprep\sch73.ldf”
Loading entries……
22 entries modified successfully.

The command has completed successfully
Verifying file signature
Connecting to “TestSvr.test.local”
Logging in as current user using SSPI
Importing directory from file “D:\support\adprep\sch74.ldf”
Loading entries……………
36 entries modified successfully.

The command has completed successfully
Verifying file signature
Connecting to “TestSvr.test.local”
Logging in as current user using SSPI
Importing directory from file “D:\support\adprep\sch75.ldf”
Loading entries…….
42 entries modified successfully.

The command has completed successfully
Verifying file signature
Connecting to “TestSvr.test.local”
Logging in as current user using SSPI
Importing directory from file “D:\support\adprep\sch76.ldf”
Loading entries……….
51 entries modified successfully.

The command has completed successfully
Verifying file signature
Connecting to “TestSvr.test.local”
Logging in as current user using SSPI
Importing directory from file “D:\support\adprep\sch77.ldf”
Loading entries………….
63 entries modified successfully.

The command has completed successfully
Verifying file signature
Connecting to “TestSvr.test.local”
Logging in as current user using SSPI
Importing directory from file “D:\support\adprep\sch78.ldf”
Loading entries……..
70 entries modified successfully.

The command has completed successfully
Verifying file signature
Connecting to “TestSvr.test.local”
Logging in as current user using SSPI
Importing directory from file “D:\support\adprep\sch79.ldf”
Loading entries….
73 entries modified successfully.

The command has completed successfully
Verifying file signature
Connecting to “TestSvr.test.local”
Logging in as current user using SSPI
Importing directory from file “D:\support\adprep\sch80.ldf”
Loading entries……..
80 entries modified successfully.

The command has completed successfully
Verifying file signature
Connecting to “TestSvr.test.local”
Logging in as current user using SSPI
Importing directory from file “D:\support\adprep\sch81.ldf”
Loading entries…..
84 entries modified successfully.

The command has completed successfully
Verifying file signature
Connecting to “TestSvr.test.local”
Logging in as current user using SSPI
Importing directory from file “D:\support\adprep\sch82.ldf”
Loading entries……..
91 entries modified successfully.

The command has completed successfully
Verifying file signature
Connecting to “TestSvr.test.local”
Logging in as current user using SSPI
Importing directory from file “D:\support\adprep\sch83.ldf”
Loading entries……
96 entries modified successfully.

The command has completed successfully
Verifying file signature
Connecting to “TestSvr.test.local”
Logging in as current user using SSPI
Importing directory from file “D:\support\adprep\sch84.ldf”
Loading entries……..
103 entries modified successfully.

The command has completed successfully
Verifying file signature
Connecting to “TestSvr.test.local”
Logging in as current user using SSPI
Importing directory from file “D:\support\adprep\sch85.ldf”
Loading entries…….
109 entries modified successfully.

The command has completed successfully
Verifying file signature
Connecting to “TestSvr.test.local”
Logging in as current user using SSPI
Importing directory from file “D:\support\adprep\sch86.ldf”
Loading entries……
114 entries modified successfully.

The command has completed successfully
Verifying file signature
Connecting to “TestSvr.test.local”
Logging in as current user using SSPI
Importing directory from file “D:\support\adprep\sch87.ldf”
Loading entries……….
123 entries modified successfully.

The command has completed successfully
Connecting to “TestSvr.test.local”
Logging in as current user using SSPI
Importing directory from file “D:\support\adprep\PAS.ldf”
Loading entries………………..
142 entries modified successfully.

The command has completed successfully
Adprep successfully updated the forest-wide information.

D:\support\adprep>Adprep /domainprep
Adprep successfully updated the domain-wide information.

D:\support\adprep>

AadSyncService Health service data is not up to date

Situation: The client is use Microsoft azure AadSyncService. They get this warning: The Health Agent(s) running on one or more servers is not connected to the Health Service and the Health Service is not receiving the latest data from this server. The last data processed by the Health Service is older than 2 Hours.

Troubleshooting:

Ensure that the health agents have outbound connectivity to the following service end points. It is possible that your firewall rules are blocking this connectivity.

  1. *.servicebus.windows.net(Port 5671)
  2. https://*.blob.core.windows.net
  3. https://*.queue.core.windows.net
  4. https://*.adhybridhealth.azure.com/
  5. https://*.table.core.windows.net/
  6. https://policykeyservice.dc.ad.msft.net/
  7. https://login.windows.net
  8. https://login.microsoftonline.com
  9. https://secure.aadcdn.microsoftonline-p.com

If you use HTTP Proxy servers for outbound traffic, you can configure Azure AD Connect Health agents to use HTTP Proxy settings.

If outbound connectivity is not blocked, restart the following services on each server:

  1. Azure AD Connect Health Sync Monitoring Service
  2. Azure AD Connect Health Sync Insights Service