Apple #Iphone Management Software (FonTool)

Today I would like to mention FoneTool (https://www.fonetool.com/) 

This software permits to backup, manage and transfer files/data from/to PC versus  several  kind Apple devices.

An alternative feature is transfer data between Iphone and Android through wireless connection.

There is a free and Pro edition comparing link

https://www.fonetool.com/download.html

https://www.fonetool.com/iphone-transfer.html

Here they are some key features:

1. Phone Backup & Restore (full or granuraly)
2. HEIC Converter
3. WhatsApp Backup
4. iOS System repair
5. iCloud Manager
6. Ringtone Maker
7. Data eraser & Wipe feature
8. One-click to Transfer All Data from iPhone to iPhone
9. Transfer WhatsApp Messages to New iPhone
10. Downgrade & Upgrade iOS/iPadOS
11. Erase Private Data
12. deleting duplicate files
13. and more advanced tools

Vmware Cloud Director &Microsoft Failover Cluster & Named Disks

To setting up Microsoft Failover Cluster there are some specifics requirements. (in our case related to SQL)
First of all allow all cluster nodes must access shared disk sending iSCSI commands.
Here they are complete requirements.

https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/setup-for-windows-server-failover-clustering/getting-started-with-wsfc/clustering-configuration.html

To allow this configuration on Vmware Cloud Director it is necessary to create Named Disk.
Here it is official documentation that confirm that this configuration is feasible

https://techdocs.broadcom.com/us/en/vmware-cis/cloud-director/vmware-cloud-director/10-5/map-for-vmware-cloud-director-tenant-portal-guide-10-5/using-named-disks-reviewing-storage-policies-and-migrating-storage-policy-entities-tenant.html

https://www.bdrsuite.com/blog/vmware-cloud-director-named-disks/

Finally here they are some screenshots:

Security #February 2025 Deadline related KB5014754 and Certificate-based authentication changes on Windows domain controllers

Microsoft released, several months ago this important bulletin.

The key point is that, after February 2025 patch installation Windows domain controller certificate-based authentication will change (due to security reasons) to Full Enforcement mode. However, you can move back to Compatibility mode until September 2025.

There are several CA checks to be done to be sure that no problem will affect your organization.

One compatibility doubt that it might arise it could be related to organization that have no longer supported O.S. (like 2008 or older)

I think that working in compatibility mode might help to check, on internet, after February 2025 if any customer had some issues and find relative fixes/workarounds

In any case here they are essential checks that you should consider before enable “full enforcement mode”:

1. Common Name (CN) and Subject Alternative Name (SAN): Must match the users or devices in Active Directory.
2. Certificate Authority (CA): Certificates must be issued by a trusted and recognized CA.
3. Certificate Chain: The certificate chain (including intermediate and root CA certificates) must be complete and valid.
4. Revocation: It is necessary to check that the certificates have not been revoked.
5. Time Validity: It must be verified that the certificates have not expired

KB5014754: Certificate-based authentication changes on Windows domain controllers

https://support.microsoft.com/en-us/topic/kb5014754-certificate-based-authentication-changes-on-windows-domain-controllers-ad2c23b0-15d8-4340-a468-4d4f3b188f16 

https://admin.microsoft.com/AdminPortal/home?#/MessageCenter/:/messages/MC894351

ExtraIT #Cashback Widilo WebSite

I would like to mention https://www.widilo.it/ website which allows you to make purchases, with interesting discounts, using the Cashback concept

Vmware #vCenter emergency mode

You might face that, during vCenter reboot phase might appear below screenshot.

To fix problem you should:

1. Take vCenter snapshot
2. Press E immediately upon boot until Grub boot startup appear
3. Add systemd.unit=emergency.target (that tells the OS to boot into emergency mode)

F10 to continue boot

 Utilize these commands to find mounted devices, you need to fix only sda devices with ext4 file system

About all of them you need to launch these commands

e2fsck -y /dev/sda1

Finally, you need to reboot

[original article]

https://www.tech-e.co.uk/vcenter-boots-into-emergency-mode-on-startup/