How to restore the People Pane in Outlook 365

Microsoft has retired the People Pane, but you can still get it back … albeit not in the Outlook desktop app itself.

  1. Log in to the corresponding Outlook web app. You can find this via File -> Info -> Account Information -> Account Settings -> below Access this account on the web. If you do not have a corresponding Outlook web app, this method will not work
  2. In the Outlook web app, find the message you want to see people details for
  3. Mouseover the name of the person of interest in the email header
  4. To the right of the Call icon, mouseover the V icon

The ensuing dropdown menu provides much of the People Pane’s functionality, including finding previous emails, attachments, and more.

from DEV Community: jdrch https://dev.to/jdrch/how-to-restore-the-people-pane-in-outlook-365-35be
via IFTTT

How to get around Outlook 365 automatically encrypting emails you save to your computer

If the Microsoft Outlook 365 desktop app is encrypting emails you manually save to disk, here’s how to get around that.

  1. Log in to the corresponding Outlook web app. You can find this via File -> Info -> Account Information -> Account Settings -> below Access this account on the web. If you do not have a corresponding Outlook web app, this method will not work
  2. In the Outlook web app, find the message you want to download
  3. Click the ... icon at the top right of the message
  4. Click Other reply options >
  5. Click Forward as attachment
  6. Forward the email to yourself
  7. Open the above email in the Outlook 365 desktop app. You’ll notice the attached email is unencrypted
  8. Save the attached email as a .msg file

You should now be able to attach the saved .msg file above without it being encrypted.

The above worked on Outlook 2016 365 on Windows 10.

from DEV Community: jdrch https://dev.to/jdrch/how-to-get-around-outlook-365-automatically-encrypting-emails-you-save-to-your-computer-4530
via IFTTT

How to connect to the NETGEAR BR500 router using OpenVPN-GUI on Windows

Assuming you’ve already installed OpenVPN and renamed the corresponding network adapter as the user manual‘s instructs, here are a few additional details:

  1. The config files downloaded from the router must all be located at C:\Program Files\OpenVPN\config or C:\Users\$USERNAME\OpenVPN\config and must all have unique names. If you need only 1 connection and manually place files in 1 of those 2 locations, delete files with the same names in the other location
  2. Once the above is satisfied, start OpenVPN GUI
  3. Right-click on the tray icon
  4. Mouseover Import
  5. Click Import from file...
  6. Import the client.opvn file downloaded from the router
  7. Once the import is complete, right-click on the tray icon again
  8. Click Connect

Your OpenVPN connection should now work perfectly.

The above works on Windows 11 and should also work on Windows 10.

Source: https://community.openvpn.net/openvpn/wiki/OpenVPN-GUI-New

from DEV Community: jdrch https://dev.to/jdrch/how-to-connect-to-the-netgear-br500-router-using-openvpn-gui-41ld
via IFTTT

How to fix the HDHomeRun app getting stuck on the Recorded screen or being unable to find any tuners

If you find the above is happening, do this:

  1. If not already installed, install the HDHomeRun Software for your desktop OS. Please note that this is not the same as the app
  2. Run the HDHomeRun Setup app on your desktop. If a firmware update is available, it will execute and reboot the network tuner automatically. Once this happens, check your client apps again; they should be working now. If no firmware update occurs, then continue
  3. Download the latest beta HDHomeRun Software from here
  4. Repeat Step 2. All your client apps should work now

from jdrch https://dev.to/jdrch/how-to-fix-the-hdhomerun-app-getting-stuck-on-the-recorded-screen-or-being-unable-to-find-any-tuners-1p2j
via IFTTT

How to convert a Workday job listing login redirect to the actual job listing

You just tried to apply directly to a job on the employer website from a job board link, but are greeted with a Workday login redirect that looks like this:

Workday login redirect

To get to the original actual job listing:

  1. Click on the login page URL
  2. Delete login?redirect=%2FCompanyString
  3. Delete %2Fapply
  4. Replace remaining %2F strings with /
  5. Click Enter or tap the browser Go icon

The original actual job listing should now load properly.

from jdrch https://dev.to/jdrch/how-to-convert-a-workday-job-listing-login-redirect-to-the-actual-job-listing-1d37
via IFTTT

How to fix Windows Hello facial recognition locking your screen while the PC is use

If this is happening to you, you may have Personify ChromaCam installed. Stop the matching service in Serices.msc, then uninstall all Personify apps (as well as Logitech Capture).

Fixed the problem for me with the Logitech BRIO 4K webcam on Windows 10.

from jdrch https://dev.to/jdrch/how-to-fix-windows-hello-facial-recognition-locking-your-screen-while-the-pc-is-use-59ac
via IFTTT

How to resolve the Resilio Sync service “Error 1069: The service did not start due to a logon failure.” on Windows

So you restarted your PC and Resilio Sync isn’t running. When you try to manually start the service, you get the Could not start the Resilio Sync Service service on Local Computer. Error 1069: The service did not start due to a logon failure. message.

Here’s how to fix it:

  1. In Services.msc (which I assume you’re already in to have seen the error message), right click Resilio Sync Service -> Properties -> Log On
  2. (You may be able to skip Steps 2) to 6). I’m just regurgitating what worked for me) Enable the Local System account radio button
  3. Click Apply
  4. Click OK
  5. Click Start the service
  6. After the service has started, click Stop the service
  7. Repeat Step 1)
  8. Click This account:
  9. Click Browse...
  10. In the Select User windows, click Object Types...
  11. Uncheck Built-in security principals
  12. Click OK
  13. Enter your username in the Enter the object name to select (examples) field
  14. Click Check Names
  15. Select your username
  16. Click OK
  17. Enter your user password in the Password: and Confirm password: fields
  18. Click Apply
  19. Click OK
  20. Repeat Step 5)

Resilio Sync should now start normally.

from jdrch https://dev.to/jdrch/how-to-resolve-the-resilio-sync-service-error-1069-the-service-did-not-start-due-to-a-logon-failure-on-windows-5dfd
via IFTTT

How to reset a default app preference in Samsung One UI 3.1 (Android 11)

Couldn’t find any writeup for this specifically elsewhere, so here’s how:

  1. Go to Settings -> Apps -> Choose default apps -> Opening links
  2. In the Installed apps list, tap the app you no longer want to be the default for something
  3. In the ensuing dialog, tap Clear defaults

The above worked on a Samsung Galaxy Tab S7 Wi-Fi.

from jdrch https://dev.to/jdrch/how-to-reset-a-default-app-preference-in-samsung-one-ui-3-1-android-11-3bfd
via IFTTT

How to resolve the “Could not create MokListXRT: Out of Resources” Debian boot error on Dell computers

Uh oh, you just rebooted your Debian Dell machine to effect a system update, only to get the following error message:

Debian error message reading "Could not create MokListXRT: Out of Resources"

Could not create MokListXRT: Out of Resources
Something has gone seriously wrong: import_mok_state() failed: Out of Resources

You can resolve the above by doing this.

from jdrch https://dev.to/jdrch/how-to-resolve-the-could-not-create-moklistxrt-out-of-resources-debian-boot-error-on-dell-computers-504o
via IFTTT

How to fix the nfsfind “find: cannot open /path/to/directory: No such file or directory” error on OpenIndiana/Illumos

My OpenIndiana machine recently emailed me the following error message, with the subject line Cron <root@DellOptiPlex390MT> [ -x /usr/lib/fs/nfs/nfsfind ] && /usr/lib/fs/nfs/nfsfind:

find: cannot open /znapzend/DellOptiPlex390MT/ROOT/openindiana: No such file or directory
find: cannot open /znapzend/DellOptiPlex390MT/export/home/judah: No such file or directory
find: cannot open /znapzend/DellOptiPlex390MT/export: No such file or directory
find: cannot open /znapzend/DellOptiPlex390MT/export/home: No such file or directory
find: cannot open /znapzend/DellOptiPlex390MT/ROOT: No such file or directory



Here’s how I fixed it

1st, let’s interpret the error message. Each line is saying that the find command cannot open a certain path, because there is no file or directory at that path. Both those paths exist, so how can find not locate them? More on that later.

The Cron <root@DellOptiPlex390MT>email subject line tells us that this error message is coming from the root crontab (or, more accurately, the cron daemon running as root), and that it’s occurring at the -x /usr/lib/fs/nfs/nfsfind ] && /usr/lib/fs/nfs/nfsfind line.

Let’s look at the root crontab to see if we can find a matching line. Sure enough, there it is:

15 3 * * 0 [ -x /usr/lib/fs/nfs/nfsfind ] && /usr/lib/fs/nfs/nfsfind

The above line means “at 0315 every Sunday, run -x /usr/lib/fs/nfs/nfsfind ] && /usr/lib/fs/nfs/nfsfind.” So what is nfsfind? You can find the full description in the Solaris docs. nfsfind cleans stale temporary files out of your NFS shares once a week, presumably to prevent the shared filesystems from running out of space.

Now that we know what nfsfind does, let’s take a look at it using our editor of choice. I prefer nano, invoked here under my own user account as I do not want to accidentally edit a system script:

$ nano /usr/lib/fs/nfs/nfsfind
if [ ! -s /etc/dfs/sharetab ]; then exit ; fi

# Get all NFS filesystems exported with read-write permission.

DIRS=`/usr/bin/nawk '($3 != "nfs") { next }
        ($4 ~ /^rw$|^rw,|^rw=|,rw,|,rw=|,rw$/) { print $1; next }
        ($4 !~ /^ro$|^ro,|^ro=|,ro,|,ro=|,ro$/) { print $1 }' /etc/dfs/sharetab`

for dir in $DIRS
do
        find $dir -type f -name .nfs\* -mtime +7 -mount -exec rm -f {} \;
done

The penultimate line of the nfsfind script has the script’s only find command. By process of elimination, this would be where the error message is coming from. It’s safe to assume find isn’t malfunctioning and its options are syntactically correct, so the error message is probably showing up because it’s being fed the wrong input ($dir).

find $dir tells us the find command is operating on a variable $dir, which from the for dir in $DIRS line is each successive value in $DIRS. From the DIRS= line we see that DIRS comes from whatever is found in /etc/dfs/sharetab.

Let’s look at /etc/dfs/sharetab, invoking nano with the same privileges as before:

$ nano /etc/dfs/sharetab
/znapzend/DellOptiPlex390MT/ROOT/openindiana    -       nfs     sec=sys,rw=@192.168.0.107/32,root=@192.168.0.107/32
/znapzend/DellOptiPlex390MT/export/home/judah   -       nfs     sec=sys,rw=@192.168.0.107/32,root=@192.168.0.107/32
/znapzend/DellOptiPlex390MT     -       nfs     sec=sys,rw=@192.168.0.107/32,root=@192.168.0.107/32
/rpool1 -       nfs     sec=sys,rw=@192.168.0.107/32,root=@192.168.0.107/32
/znapzend       -       nfs     sec=sys,rw=@192.168.0.107/32,root=@192.168.0.107/32
/znapzend/DellOptiPlex390MT/export      -       nfs     sec=sys,rw=@192.168.0.107/32,root=@192.168.0.107/32
/znapzend/DellOptiPlex390MT/export/home -       nfs     sec=sys,rw=@192.168.0.107/32,root=@192.168.0.107/32
/znapzend/DellOptiPlex390MT/ROOT        -       nfs     sec=sys,rw=@192.168.0.107/32,root=@192.168.0.107/32

Now, some background:

  • /znapzend is the mountpoint for rpool1/znapzend/, a ZFS fiesystem I created as a destination for znapzend
  • rpool1 itself is mounted at /rpool1. I shared it via NFS using # zfs set sharenfs=on long before I created rpool1/znapzend

Clearly, all of rpool1‘s child datasets inherited its sharenfs=on property upon their creation. Moreover, the child datasets are also mounted:

$ mount | grep znapzend
/znapzend on rpool1/znapzend read/write/setuid/devices/nonbmand/exec/xattr/atime/dev=4c10008 on Fri Apr 30 21:59:04 2021
/znapzend/DellOptiPlex390MT on rpool1/znapzend/DellOptiPlex390MT read/write/setuid/devices/nonbmand/exec/xattr/atime/dev=4c10034 on Sat May  1 10:00:03 2021
/znapzend/DellOptiPlex390MT/ROOT on rpool1/znapzend/DellOptiPlex390MT/ROOT read/write/setuid/devices/nonbmand/exec/xattr/atime/dev=4c1003a on Sat May  1 10:00:04 2021
/znapzend/DellOptiPlex390MT/ROOT/openindiana on rpool1/znapzend/DellOptiPlex390MT/ROOT/openindiana read/write/setuid/devices/nonbmand/exec/xattr/atime/dev=4c1003c on Sat May  1 10:03:00 2021
/znapzend/DellOptiPlex390MT/export on rpool1/znapzend/DellOptiPlex390MT/export read/write/setuid/devices/nonbmand/exec/xattr/atime/dev=4c1003d on Sat May  1 10:03:22 2021
/znapzend/DellOptiPlex390MT/export/home on rpool1/znapzend/DellOptiPlex390MT/export/home read/write/setuid/devices/nonbmand/exec/xattr/atime/dev=4c10040 on Sat May  1 10:03:33 2021
/znapzend/DellOptiPlex390MT/export/home/judah on rpool1/znapzend/DellOptiPlex390MT/export/home/judah read/write/setuid/devices/nonbmand/exec/xattr/atime/dev=4c10042 on Sat May  1 10:03:48 2021

It seems I made 2 mistakes here:

  1. I forgot to # zfs set sharenfs=on the child datasets
  2. I probably unnecessarily mounted the child datasets. As you can see from my znapzend tutorial link, znapzend uses ZFS zpool/dataset paths, not filesystem paths (created by mount operations)

(As a corollary, this is probably why ZFS uses the term dataset and not filesystem. All ZFS filesystems are datasets, but not all ZFS datasets are filesystems. A dataset becomes a filesystem only when it is mounted.)

But that still doesn’t explain why find chokes on those paths. Let’s try to navigate to them ourselves using cd:

# cd /znapzend/DellOptiPlex390MT/ROOT/openindiana
-bash: cd: /znapzend/DellOptiPlex390MT/ROOT/openindiana: No such file or directory

Wait, what? How can there be no file or directory at that path? The answer lies in the sequence of sequence of events that led to that location being considered a filesystem (note the emphasis) path to begin with. 1st, rpool1 was created with sharenfs=on. Much later rpool1/znapzend and rpool1/znapzend/DellOptiPlex390MT were created. Both those datasets inherited the sharenfs=on.

rpool1/znapzend was then mounted at /znapzend, which also mounted all of its current and future datasets. All of the above became filesystems by virtue of being mounted and NFS shares by virtue of inheriting their parent dataset(s)’ sharenfs=on setting.

The future datasets came into being when znapzend created them recursively as zfs receive destinations. However, because each dataset is actually a family of snapshots, each has no actual corresponding filesystem, despite the apparent path! This is why # cd fails to find anything.

We can fix this problem by 1st unsharing the “problematic” dataset (actually this along is sufficient to solve the problem):

# zfs set sharenfs=off rpool1/znapzend

and then also unmounting it (good practice, since the location isn’t intended to be generally accessible to non-ZFS operations anyway):

# zfs unmount rpool1/znapzend

For those who may be confused about the continued accessibility of the destination dataset to znapzend after unmount, remember that all datasets on a zpool are accessible via ZFS (note the emphasis) operations as long as that zpool has not been exported.

Checking the contents of /etc/dfs/sharetab again:

$ nano /etc/dfs/sharetab

gives:

/rpool1 -       nfs     sec=sys,rw=@192.168.0.107/32,root=@192.168.0.107/32

Both find and ‘cdwork on/rpool1`, so we can be sure there will be no further errors of the kind detailed at the outset.

from jdrch https://dev.to/jdrch/how-to-fix-the-nfsfind-find-cannot-open-path-to-directory-no-such-file-or-directory-error-on-openindiana-illumos-7dj
via IFTTT

%d bloggers like this: