Enabling Edge Enterprise Copilot
Microsoft (Edge) Thursday, 09 November 2023 by paul

To enable the Edge Copilot in the Enterprise it may be necessary to set a few group policy settings.

Enable sidebar in the group policy options below: Computer Configuration -> Policies -> Administrative Templates -> Microsoft Edge

  • Show Hubs Sidebar (set to Enabled)
  • Search in Sidebar enabled (set to Enable search in sidebar)

If you are using extension whitelisting the add the extension Ids below to "Allow specific extensions to be installed" in: Computer Configuration -> Policies -> Administrative Templates -> Microsoft Edge -> Extensions

  • Bing Chat - ofefcgjbeghpigppfmkologfjadafddi
  • Search - jbleckejnaboogigodiafflhkajdmpcl
  • Discover - nkbndigcebkoaejohleckhekfmcecfja
  • Microsoft Office 365 - gecfnmoodchdkebjjffmdcmeghkflpib
  • Outlook - kfihiegbjaloebkmglnjnljoljgkkchm (optional)
  • OneNote Feed - gbihlnbpmfkodghomcinpblknjhneknc (optional)
  • Teams Chat - piilhopgoheagglmepbmkpodfceclmab (optional)

Checking the sidebar config in Edge itself can be done using the url: edge://settings/sidebar and also edge://sidebar-internals/

Ensure that Edge has access to the URL: https://edgeservices.bing.com to allow the extension to load data.

Remote Access VPN not working after Cisco ASA Upgrade
Cisco (VPN) Wednesday, 23 August 2023 by paul

After upgrading ASA IOS to version 9.14.x the Remote Access VPN Connection failed.

After checking debug logs and config the cause was located as Authorisation server LDAP over SSL connections failing.

Before the upgrade LDAP over SSL connections were working fine. The new version of the software was failing as the certificate used by the LDAP server (AD CA) was not trusted by the ASA.

This was fixed by exporting the AD CA certificate from the Windows server and importing it into the ASA (under Configuration -> Remote Access VPN -> Certificate Management -> CA Certificates).

Cisco ASDM does not launch after upgrade
Cisco (ASDM) Wednesday, 23 August 2023 by paul

After upgrading Cisco ASDM it does not load when the created shortcut launched.

To get the new ASDM to work I had to do the following:

  1. Install Java JRE
  2. In Control Panel -> Java -> Network Settings -> Set to Direct Connection
  3. Created batch file pointing to the newly installed JRE with command: 
    "C:\Program Files (x86)\Java\jre-1.8\bin\javaw.exe" -Xms64m -Xmx512m -Dsun.swing.enableImprovedDragGesture=true -classpath lzma.jar;jploader.jar;asdm-launcher.jar;retroweaver-rt-2.0.jar com.cisco.launcher.Launcher cert.PEM
  4. Use the batch file to launch ASDM instead of the created shortcuts

Hopefully ASDM will not require Java at some point.

Turning on the Lenovo Thinkpad Keyboard backlight with a script
Lenovo (Backlight) Friday, 02 June 2023 by paul

On my new Lenovo Thinkpad the backlight cannot be turned on automatically and required the keyboard shortcut (Fn + Spacebar) used every time it is started or resumed. This is a pain as my previous laptop allowed the backlight to be enabled permanently.

After not finding any Lenovo method of enabling the backlight permanently I found it can be done via a PowerShell script. The script is based on Cariffo1994’s work at: https://www.reddit.com/r/thinkpad/comments/odqwsl/keyboard_backlight_enabled_on_startup_or_wake/

# Turn on lenovo thinkpad keyboard backlight 

[string]$path = 'C:\ProgramData\Lenovo\ImController\Plugins\ThinkKeyboardPlugin\x86\';
[int]$level = 2; # Backlight level: 0 - Off, 1 - Dim, 2 - On

[string]$core = $path + 'Keyboard_Core.dll';
[string]$contract = $path + 'Contract_Keyboard.dll';

Add-Type -Path $core;
Add-Type -Path $contract;

[Keyboard_Core.KeyboardControl]$control = New-Object -TypeName 'Keyboard_Core.KeyboardControl';
$control.SetKeyboardBackLightStatus($level, $null);

The script needs to be executed using x86 PowerShell (does not work in 64-bit PowerShell). Test from command line (set-execution policy may have to be run to allow the script to execute).

Create a scheduled task. Triggered on events startup and workstation unlock.

Command line: %SystemRoot%\SysWOW64\WindowsPowerShell\v1.0\powershell.exe

Arguments: -File path\scriptname

Conditions: Disable option start only when on AC power



Kace K1000 v13 Script Issue
Kace (v13) Wednesday, 24 May 2023 by paul

After upgrading to v13 of the Kace agent machines experienced an issue with scripts looping continuously. This resulted in high CPU usage.

This only affected scripts set to offline and scheduled to run on a specific day. If scheduled to run every day then not affected.

Quest developers are looking at the issue (ref K1A-4002). Currently affects all latest versions of Kace.

Workaround is to change scripts to online or schedule to run every day.

Page 1 of 96 (482 Articles) << 1 2 3 4 5  Next >>