Windows Update date and time error
Windows (Windows Update) Monday, 10 August 2020 by paul

When using Windows Update the following error is displayed: "We couldn't install updates because there's a problem with the date and time information on your device. Make sure your date, time, and time zone settings are correct and we'll try again later."

Checking machine time and date settings shows no issues.

The machines are configured to get their updates from an internal Windows Update server. Connecting to the WSUS Console does not work either and gives a SSL error.

Checking the WSUS site in IIS Admin show the SSL Certificate bound to the site has expired.

Renew the certificate and restart the IIS site.

Now the machines connect and windows update as normal.

Raspberry PI not connecting to network on boot
Raspberry Pi (Config) Wednesday, 05 August 2020 by paul

Recently saw an issue with a Rasperry Pi not connecting to the network on boot or reboot. Needed a hard reset to get it to connect to the network.

Running command: dmesg | grep "Link is Up"

Returned: [   13.353678] bcmgenet fd580000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx

This shows the Pi has connect to the network using it's ethernet port, speed 1Gb and flow control on. It is actually connected to a 100Mb switch so has not negotiated the correct speed for the port. This results in the Pi being unable to access the network.

It is possible to disable auto negotiation and set the correct speed manually using the command below:

ethtool -s eth0 autoneg off speed 100 duplex full

Now the Pi can access the network fine. It is possible to add this to the Pi startup using the process below:

    1. Enter command: sudo nano /etc/init.d/autoneg

    2. Enter script text:

#!/bin/bash
/sbin/ethtool -s eth0 autoneg off speed 100 duplex full
exit

    3. Save and exit Nano (ctrl+x)

    4. Enter command: sudo chmod a+x /etc/init.d/autoneg

Then the script will be automatically executed whenever the Pi is started.

PowerShell 101: Open in same folder every time
PowerShell (Profile) Tuesday, 04 August 2020 by paul

You can use a PowerShell profile to open the window to the same folder every time.

  1. Check if a profile already exists with command "Test-Path $profile"
  2. If it is false then create the profile file with the command "New-Item -path $profile -type file –force"
  3. Edit the file (usually created by default as filename c:\Users\username\Documents\WindowsPowerShell\Microsoft.Powershell_profile.ps1)
  4. Add the text "cd c:\foldername" and save changes

Or add more of a startup script:

$Shell = $Host.UI.RawUI
$Shell.WindowTitle="Windows PowerShell for Me"
Write-Host "Username:"$($env:username) -foreground gray
Write-Host "Hostname:"$($env:computername) -foreground gray
Write-Host "PS Version:"$Host.Version.ToString() -foreground gray
Write-Host ""
cd "$($env:onedrive)\Scripts"

Now when you start a PowerShell session it will always execute the profile file automatically and change you to the specified folder. You can also add commands to configure the size, location, title, prompts, create aliases and set colours of your PowerShell window.

New Microsoft Team meeting experience
Office 365 (Teams) Friday, 31 July 2020 by paul

If you are on the latest greatest version of Teams then you can enable the new features:

  • Meetings open in a separate window (allowing you to continue using Teams client for other stuff)
  • Together mode (rather than video like celebrity squares it puts everyone in a virtual conference room)
  • Large Gallery Mode (up to 49 videos, must have at least 10 users with video to see)
  • Focus mode (for when presentations – removes video and mutes you)
  • New Meeting Notes view (separate tab for notes rather than just side panel)
  • Owner can “End Meeting” rather than leaving and allowing it to continue

The new features need to be enabled manually in settings. Under General tick box “Turn on new meeting experience”. Then exit Teams (right clock icon in system tray and select “Quit”) and restart client to see changes.

The new meeting experience will become the default at some point and then everyone will see it.

 

Issue with ManageEngine Password Manager Pro v10.5.0 (10500) upgrade
ManageEngine (Upgrade Issue) Thursday, 16 July 2020 by paul

After upgrade ManageEngine Password Manager Pro to the latest release 10.5.0 the postgres database would not start.

Below is an excerpt from PMP Support on the issue:

From version 10402 we have done some security enhancements. Earlier, PostgreSQL data directories in Windows installations were entirely accessible to all locally authenticated users. Now, as a security practice, we have exerted the following measures, applicable for installations under the 'Program Files' directory:

No inherited permissions are allowed for data and configurations directories.
1.    "Authenticated Users" permission has been excluded entirely.
2.    Only the CREATOR OWNER, SYSTEM, Installation User, NT AUTHORITY\Network Service, and Administrators groups will have the Full Control over the directories and also can start PostgreSQL.
You can also refer to our release notes here under the 10402 (7th January 2020). 

So after upgrading to 10500 version the service might not start due to permission issues. You need to reapply the permissions to get the service up and running.
•    Start the Task Manager and kill all Postgres process(make sure show process from all users is selected - For PMP). 
•    Run the PMP service with a privileged account or a Local Admin account. 
•    If it's already running with a privileged account, right-click on the PMP folder ---> Properties ---> Security and provide the PMP service account with full permissions (even if the account is a member of the local admin group). 
•    Rename the logs folder present inside the <PMP_Installation_Directory> as logs.old 
•    Navigate to <PMP_Installation_Directory>/bin directory and look for files names .lock or lockfile. If present, move both these files to any other directory. 
•    Go to <PMP_Installation_Directory>/pgsql/data directory and look for a file named recovery.conf, postmaster.pid. If present, move this file to any other directory. 
•    In case if it still fails, please open the command prompt with the Admin right and then execute the below commands. 
•    icacls "(PMP installation directory)" /grant PMPserviceaccountname:(OI)(CI)F /T
•    icacls "PMP installation directory" /grant currently logged in account to the server:(OI)(CI)F /T
•    service account= mention the account name used for running the PMP service.
•    Currently logged in account to the server= mention the account name currently logged into the PMP server

 

After following their steps the database did start and the application was working again.

Page 1 of 83 (418 Articles) << 1 2 3 4 5  Next >>