Backup Exec Exchange backups hanging

Backups hanging and never completing at random place during Exchange backups, despite having been working for a long period previously.

On the Exchange server, add the following registry entry…

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameter
Key: IRPStackSize (case sensitive).
Value: 30 (Hex)

Source: e00084f8 – The network connection to the Backup Exec Remote Agent has been lost – Check for network errors – refer to link V-79-57344-34040 (veritas.com)

Move Exchange Mailboxes

Lots of reasons for moving, often because you want to delete one of the mailbox databases.

User Mailboxes

new-moverequest "joe bloggs" -TargetDatabase "Mailbox Database"
Get-MoveRequest | Get-MoveRequestStatistics

Arbitration Mailboxes

Get-Mailbox -Arbitration | New-MoveRequest -TargetDatabase "Mailbox Database"
Get-MoveRequest | Get-MoveRequestStatistics

Remove the completed Move Requests

Get-MoveRequest -MoveStatus Completed | Remove-MoveRequest

or if you have lots to do

Get-MoveRequest -MoveStatus Completed | Remove-MoveRequest -Confirm:$false

 

Additional Moves

You may also have to:

Get-Mailbox –RecipientTypeDetails DiscoveryMailbox | Format-Table Name

Get-Mailbox -RecipientTypeDetails DiscoveryMailbox | New-MoveRequest -TargetDatabase @Mailbox Database"

Get-MoveRequest | Get-MoveRequestStatistics

Get-MoveRequest -MoveStatus Completed | Remove-MoveRequest

To get a list of all Audit mailboxes in this database, run the command

Get-Mailbox -Database <Database ID> -AuditLog

To disable a Audit mailbox so that you can delete the mailbox database, run the command

Get-Mailbox -Database "Mailbox Database 2138967441"  -Auditlog | Disable-Mailbox

 

 

Once all moved, old DB can be removed. If you have created a new mailbox database, you will need to add new AV exclusions asper MS’s recommendations.

Installing ESXi 8 on old CPUs

Boot from USB in normal way.

At the initial ESXi Boot menu, press SHIFT-O (letter o)

Type: <space>allowlegacycpu=true and hit enter

Now, although you’ll be prompted during the install that the CPU is unsupported, it will let you continue.

Note – ESXi 8.0.2 will fail to install if your CPU is from pre 2012 era.

Installing Windows 11 tips

Unsupported hardware:

In Windows 10, mount the Win11 ISO, open elevated command prompt, change to mounted ISO drive letter:

setup.exe /product server

Use local account, rather than MS account:

When prompted for MS account, just make up a random local account name such as AdminUser and it will error and default to asking for local account.

Installs after around April 2024

Use “Setup for Work and School” rather than “Personal” and pick “Domain Join”


	

Creality Print on ESXi VM

Creality Print needs OpenGL 4.1 in order to show the model view.  By default, although it slices and uploads to printer fine, you cannot see, thus modify, the model.

In VM settings, enable 3D Support, and set 3D memory to 1GB (1GB is Vmware’s recommendation for Win7 and later):

For it to work over a Remote Desktop Connection, within the VM, you need to disable WDDM.

In Local Computer Policy, go to Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Remote Session Environment and disable Use WDDM graphics display driver for Remote Desktop Connections:

Restart VM.

 

Creality Print in all its VM/RDP glory:

 

VMware: Failed to leave the domain . The user or group named ‘\esx^admins’ does not exist.

Sometimes when ESXi loses its trust relationship with Active Directory, you cannot log in with your AD account, and attempts to remove the ESXi server from AD result in an error:

Failed to leave the domain <Domain Name>. The user or group named ‘<AD>\esx^admins’ does not exist.

Solution:

Create a local group called esx^admins:

/usr/lib/vmware/busybox/bin/busybox addgroup DOMAIN\\esx^admins

(Change DOMAIN to be Netbios name of AD, and note the double \)

Repeat for any other AD based group names you have assigned permission to within the ESXi host.

Remove from the domain, either via ESXi or vCenter (preferred)

Remove the temporary local group(s):

/usr/lib/vmware/busybox/bin/busybox delgroup DOMAIN\\esx^admins

Add the ESXi Host back into the domain via ESXi or vCenter (preferred).

If it fails to rejoin after a long delay, delete the Computer object for the ESXi Host from AD.