After Upgrading to Microsoft Config Manager 1806, PXE Booting Failures Were Encountered

Issue:

After upgrading to Microsoft Config Manager 1806, PXE booting failures were encountered.

Machines fail to PXE boot or machines PXE boot and then reboot at Loading Network Settings

Review of smsts.log file on the SCCM Distribution Point found error "Task Sequence environment is not initialized"


Resolution:

Complete every task it the following list in exact order:

Remove Boot images from Distribution Point by unchecking "distribute from PXE DP" under the dp roles properties in Config Manager Console. Wait for the removal to complete by monitoring distmgr.log

Delete boot images from the console. Confirm they are gone using the content library explorer tool in the 2012r2 toolkit.

Remove the PXE service by unchecking the PXE options under the Distribution Point properties in Config Manager Console. WDS should uninstall automatically. Monitor distmgr.log for completion. Confirm WDS uninstalled via Add/remove server rules wizard on each Distribution Point, it will be available for install if it was removed properly.

If the remote install folder still exists on the Distribution Point, delete it and empty C:\Windows\Temp folder 

Reboot each Distribution Point

Uninstall all versions of ADK from the Site Server

Reboot the Site Server

Download and install the ADK version 1809

Reboot Site Server

Add PXE service in the Distribution Point properties in Config Manager Console. Wait for WDS to install, monitor distmgr.log.

Log on to each Distribution Point and verify the remote install folder/share successfully rebuilt automatically.

Reboot each Distribution Point

Run the ADK command line tool on the Site Server, CopyPE, to export new boot image media for both x64 & x86.

In the Config Manager console, create new boot images from the media you just exported. Enable F8 support and a background if desired. Do not add any drivers.

Distribute the new boot images to the Distribution Point, make sure the "distribute from the pxe dp" box is checked under the data source tab in the boot image properties. Review other boxes in that tab.

Note and then delete the deployments for the imaging task sequence.

Add the new boot images to the imaging task sequence – right click the Task Sequence and check the box “use a boot image” and specify name and location of boot image.

Redeploy your task sequences as noted above. (NOTE: under deployment settings, select make available to only media and PXE)

Test PXE. Most machine models should boot and execute the Task Sequence now. Some models may need additional drivers.

If additional drivers are needed to be added to the boot images add one at a time to each boot image, redistribute & test each driver. Some drivers may cause PXE to hang or reboot as soon as the boot image loaded.

SCCM Microsoft Configuration Manager Deployments not Updating and Clients Not Showing Recent Hardware and Software Scans

Issue: Application deployments not showing updated statistics but Task Sequences are. Clients not showing recent hardware scans and software scans.


Resolution:
On site server, In IIS,  Open IIS Manager > Sites > Default Web Site > CCM_Incoming. On the right side, click on "BITS Uploads" verify "Allow Clients to upload files" is checked

If BITS Uploads section is not listed, add the feature through Server Manager

Windows 10 version 1803 Fails to Install Cumulative Update

Windows Update fails to install 2018-07 Cumulative Update for Windows 10 version 1803 for x64-based Systems.

Windows Update fails to install 2018-08 Cumulative Update for Windows 10 version 1803 for x64-based Systems.

Windows Update fails to install 2018-09 Cumulative Update for Windows 10 version 1803 for x64-based Systems.

Update downloads, installs, when system reboots it progresses to 8% or 9% complete, fails and uninstalls update.

Review of log files revealed errors updating crdom.inf. Systems did not have CD-ROM drives.

Resolution:

add a REG_DWORD named Start with a value of 1 to this key:


HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\cdrom


Restart the computer and install updates.

Outlook 2016 Slow, Crashing, Sluggish

Click File



Click Slow and Disabled COM Add-ins



Outlook will display and Add-ins that have caused a crash or causing slowness

Inspect any add-in with a red status bar (under 1 second is acceptable)



Disable any Add-in with a red status bar (over a second) by clicking Disable this add-in

Click Close


Outlook normally disables slow add-ins unless they are marked “Always enable this add-in”

RSA SECURID: THE TOKEN DATABASE ON YOUR HARD DRIVE IS PROTECTED BY A PASSWORD

Encountering a message similar to “The token database on your hard drive is protected by a password” when opening the RSA Software Token:

  • Select the Options menu on the top right
  • Select Token Storage Device
  • Select Change Device Password
  • Click the Reset Device button at the bottom of the window
  • Click OK at the Warning
  • The password will be reset and all RSA tokens will be removed.
  • Re-import the user's Token

Office Applications prompting for credentials for proxy store.office.com

Office Applications prompting for credentials for proxy store.office.com



Open regedit

Navigate to:
HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Common\Internet\useOnlineContent
Or
HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\Internet\useOnlineContent

Change Dword value from 1 to 0

Error Installing Cisco AnyConnect VPN Client: “The file ‘Manifest Tool.exe’ is not marked for installation”

Click Start and type “regedit” in the box.

A dialogue box will pop up with the following text: Do you want to allow the following program to make changes to this computer?
Click Yes.

Browse to the following location: HKEY_CLASSES_ROOT\Installer\Products\

Within the Products folder, locate and delete the registry key which contains product information for Cisco AnyConnect. (We recommend making a backup of this registry key before deleting it.)

Each registry key within Products is an alphanumeric string. Select the first key and look on the right side for ProductName REG_SZ Cisco AnyConnect. Go through each key in the Products folder until you find the one for Cisco AnyConnect.

For example,

the registry key for Cisco AnyConnect v4.4 is named 31D43F43B3678C84490E6DDCF38F2486

the registry key for Cisco AnyConnect v4.5 is named 89A926BE96E58E04ABE93C3998F959D9

Each version of Cisco AnyConnect will have a different name for this registry key.

Close the registry editor.

Install the latest version Cisco AnyConnect.