Fixed 2025: Import Calendar Agenda into iCloud Calendar

I’ve come across many solutions for getting an Outlook or Exchange calendar into iCloud, but none of them worked for me. The “ICS To Calendar” option via “Shortcuts,” which many praised, unfortunately didn’t work either.

In the end, I found a relatively simple way to import an Outlook or Exchange calendar into iCloud.

Step 1

Export your Outlook, Exchange, or Office 365 calendar in .ics format. In Outlook, you can do this by selecting the correct calendar, then clicking on “File” and choosing “Save Calendar”. Make sure the following settings are configured under “More Options…”:

Step 2

Install iCloud for Windows and ensure your calendars sync with Outlook.

Step 3:

Open Outlook. You should now see both your Exchange calendars and your iCloud calendars. Drag the .ics file into the iCloud calendar where you want to import it.

A warning message will appear—click Yes to proceed.

All calendar events will now be imported.

I’ve noticed that sometimes, when clicking Yes, nothing happens. If that occurs, simply restart Outlook and try again.

[FIXED] Veeam add Hyper-V host ‘Failed to connect to host’

When you want to add a non-domain joined Hyper-V host to Veeam, you get the following error:

Failed to connect to host 10.40.58.11

Server '10.40.58.11' does not exist or access denied.
Check firewall settings.

Possible reasons:
1. Invalid credentials.
2. Specified host is not a Hyper-V server.

Most likely is that you will have to add the hostname of the Hyper-V host to the username, like so:

HYPERVHOSTNAME\Administrator

Or else you can try:
KB1914: “Invalid Credentials” Error Adding a Hyper-V Host Using a Local Account

System ROM Flash Binary – HPE ProLiant DL380 Gen9/DL360 Gen9 P89_3.40_08_29_2024

Here you can download the following ROM:

P89_3.40_08_29_2024.signed.flash

Version: 3.40_08-29-2024
Upgrade Requirement: Recommended
Release Date: Sep 12, 2024
Reboot Requirement: Required
Type: BIOS – System ROM

System ROM Flash Binary – HPE ProLiant DL380 Gen9/DL360 Gen9 (P89)
To ensure the integrity of your download, HPE recommends verifying your results with the following SHA-256 Checksum values:

P89_3.40_08_29_2024.signed.flash
907f09f86840c8524c140a5c4bf66c14987a697993a610cd64dba5e3f105e050

P89_3.40_08_29_2024
b4ae815efdf1c1b85cc158187d71afd4aa7b2c4bb83dd8e6af5e01d8a3df5f6b

https://support.hpe.com/connect/s/softwaredetails?collectionId=MTX-ce0053f84e284a99&tab=Installation+Instructions&softwareId=MTX_881e8158b27342eeb2ed133b97

CMMVC5970E The Remote Copy relationship was not created because there is not enough memory

You can get the following error when adding Remote Copy volumes on a IBM Storwize or IBM Flashsystem:

CMMVC5970E The Remote Copy relationship was not created because there is not enough memory

The fix is to increase the memory on both storage devices.

Login to both Storwize / Flash system devices and check the remote_copy_total_memory with the following command:

lsiogrp 0

In this output you will find the remote_copy_total_memory:

IBM_FlashSystem:MB-SAN02:superuser>lsiogrp 0
id 0
name io_grp0
node_count 2
vdisk_count 8
host_count 0
flash_copy_total_memory 20.0MB
flash_copy_free_memory 20.0MB
remote_copy_total_memory 20.0MB
remote_copy_free_memory 0.0MB
mirroring_total_memory 45.0MB
mirroring_free_memory 5.0MB
raid_total_memory 52.2MB
raid_free_memory 0.0MB
maintenance no
compression_active no
accessible_vdisk_count 8
compression_supported yes
max_enclosures 20
encryption_supported yes
flash_copy_maximum_memory 2048.0MB
site_id
site_name
fctargetportmode enabled
compression_total_memory 0.0MB
deduplication_supported yes
deduplication_active no
nqn nqn.1986-03.com.ibm:nvme:2145.00000204A0408348
flash_copy_max_legacy_memory 2048.0MB
flash_copy_used_legacy_memory 0.0MB
remote_copy_maximum_memory 512.0MB
mirroring_maximum_memory 512.0MB
raid_maximum_memory 512.0MB

With the following command you can change the remote_copy_total_memory to – for example – 40MB:

chiogrp -feature remote -size 40 io_grp0

Then check if the setting has changed:

IBM_FlashSystem:MB-SAN02:superuser>lsiogrp 0
id 0
name io_grp0
node_count 2
vdisk_count 8
host_count 0
flash_copy_total_memory 20.0MB
flash_copy_free_memory 20.0MB
remote_copy_total_memory 40.0MB
remote_copy_free_memory 0.0MB
mirroring_total_memory 45.0MB
mirroring_free_memory 5.0MB
raid_total_memory 52.2MB
raid_free_memory 0.0MB
maintenance no
compression_active no
accessible_vdisk_count 8
compression_supported yes
max_enclosures 20
encryption_supported yes
flash_copy_maximum_memory 2048.0MB
site_id
site_name
fctargetportmode enabled
compression_total_memory 0.0MB
deduplication_supported yes
deduplication_active no
nqn nqn.1986-03.com.ibm:nvme:2145.00000204A0408348
flash_copy_max_legacy_memory 2048.0MB
flash_copy_used_legacy_memory 0.0MB
remote_copy_maximum_memory 512.0MB
mirroring_maximum_memory 512.0MB
raid_maximum_memory 512.0MB

That’s it!