Break/Fix

Repair guides for common error messages, problems we have seen before, or obscure fixes that need to be documented before Microsoft reformats their knowledgebases and deletes all the old articles... again.

Adobe

Adobe

License Migration

If you are attempting this process on a terminal server and it fails, then an administrator will need to employ this supplementary guide.

If you are currently logged into Adobe, you simply sign out of your account and sign back in. Again, this will occur on or after August 7th and an email will be sent that morning the work has been completed.  

Please note: Depending on the application you are using the sign-out process may be slightly different.

image.png

Choose Sign out if asked.

image.png

Enter your Adobe username as normal.

image.png

Enter your Adobe password as normal.

image.png

You should get prompted to join the new Team, click Join team of “Local Media – Gazette”

image.png

Select “Local Media – Gazette” to use the new license within the new Team.

image.png

Stock Account Users (FYI)

If you use https://stock.adobe.com for Stock photos, you may need to manually change your account by clicking your profile image at the top and then choosing “Change Profile”. As previously noted, there will be no licensed image history in the new account.

image.png

image.png

Cloud Libraries (FYI)

For anyone using cloud libraries, you may want to keep this link handy for exporting these from your old account and then importing them into your new account. It may behoove you to export ahead of August 7th to avoid going back and forth between accounts to save steps. You will still have access to items until September 1st, but something to note if you use this functionality.

https://helpx.adobe.com/creative-cloud/help/import-export-creative-cloud-libraries.html

Adobe

License Migration on Terminal Servers

The steps for the Adobe License Migration are sometimes successful on a terminal server without incident. But, they may instead produce an error message that the subscription status cannot be verified:

Are you connected to the internet? We can't verify your subscription status. We can't reach the adobe servers. This may be because you're not connected to the internet. Check your connection and try again below. If you're still having issues, please see our connectivity troubleshooting guide.

In these cases, Adobe's recommendation is to disable "Acrobat Protected Mode". This change is made in the HKEY Current User registry hive, meaning it is per user, not per computer, so the same change may need to be made for multiple users of the same terminal server. These are the steps.

  1. Quit all Adobe software.
  2. Double click AdobeAcrobat_PMOff.reg as the user to copy the values in the file to the user's registry hive.
  3. Run the Adobe software, and verify successful login.
  4. Double click AdobeAcrobat_PMOn.reg as the user to re-enable Acrobat Protected Mode for their userstate. Now that the license is verified, this should not be necessary a second time unless the license changes again.

Crowdstrike

Crowdstrike

Channel File 291 Bootloop

To reboot a machine into safe mode (workstation or server) follow these steps..

At the recovery screen hit "see advanced.."

image.png

Troubleshoot

image.png

Advanced Options

Startup Settings

image.png

Hit reboot

image.png

Once the server reboots you'll see this recovery option screen. I've been selecting "safe mode with networking" since there's a chance you'll still be able to auth using your normal elevated creds (if not cached).

image.png

Once you've logged into the server you need to open up cmd or powershell.

C:\Windows\System32\drivers\CrowdStrike
dir

(to list all files)

image.png

Copy this filename ( C-00000291-etc) and then run this:

del <filename you copied>

Reboot the machine.

Procedures for Machines Requiring Added Storage Drivers

Machines like the ProBook 650 G8 may not have the "Startup Settings" option above. Instead, follow these steps.

  1. Load the correct driver for the machine to an external drive.
  2. Use the Command Prompt option in the recovery mode which will open a command prompt into the Windows Recovery Environment, mapped as X:\
  3. Type DISKPART to enter disk partition mode.

    This screenshot is for illustrative purposes only. Your disk and partition numbers will vary.

    image.png

  4. Type List Disk and identify the disk number, based on its size, that contains the driver
  5. Type Select Disk #  based on the size and hit enter - the selected disk is now active
  6. Type List Partition and identify the primary partition
  7. Type Select Partition # and hit enter - the selected partition is now active
  8. Type assign letter=[drive letter] where drive letter is any available drive letter (at this point, any except x)
  9. Type EXIT to leave disk partitioning mode
  10. Change drive letter to the drive letter you just assigned.
  11. Change directories to the directory containing the .inf file for the storage driver - in the example included and attached to this document, that is the *:\src\driver\ directory but this may be different for other drivers.
  12. Type pnputil -i -a drivername.inf to load the driver into active memory.
  13. Repeat steps 3 through 9 above, but this time select the new, larger drive that you should now be able to see. Select its primary partition and mount it to a different drive letter than the one you chose in step 8.
  14. Once out of disk partitioning mode again, select your new drive letter.
  15. Change directory to *:\Windows\System32\drivers\CrowdStrike
  16. Rename any files beginning with "C-00000291" to end with ".old" instead of ".sys" and then restart the system.
  17. You're done!

Printers

Printers

Printers Need Driver Or Fail To Install

After installing software meant to enable cross-tenant cloud printing, which monopolized the print queues on the print server, re-establishing the relationship with the printers was necessary on some devices at LLEV.

  1. Open Settings and navigate to Bluetooth & Devices > Printers & scanners
  2. For any printer that says "New driver required" click the printer and then click "Remove"
  3. Open terminal - as the user works just fine
  4. Do a gpupdate: gpupdate /force
  5. When the printers are re-added from the print server, they work properly again

Additional Issues

If you see any of the following errors...

...this can be overcome by adding the printer as an admin. Open a terminal as admin and run this command:

rundll32 printui.dll,PrintUIEntry /il

This allows the printer to be installed as an admin, which downloads the driver. After this, the printer can be removed and a gpupdate run again to install the printer properly.