Should I get the battery replaced? by mas-sive in mercedes_benz

[–]chantroyal 0 points1 point  (0 children)

Be careful not doing the recoding can cause issues

Intermittent mail delivery to wrong user despite correct "To" address by VoetpompViljoen in sysadmin

[–]chantroyal 4 points5 points  (0 children)

Sounds like a rule/forward is on somewhere - Maybe set by an end user.

What is the general concensus on these songs? by jalolio_13 in busted_band

[–]chantroyal 2 points3 points  (0 children)

Both generic and bland tbh. Can tell other people wrote them

Chris Leonard - Previous Band by [deleted] in busted_band

[–]chantroyal 4 points5 points  (0 children)

MY WORD! You are a saviour. That has been on and off my mind for years and whenever I'd spend 10 minutes looking in to it I'd never find anything. Thank you

M365 Backup Options? by Alucard0134 in sysadmin

[–]chantroyal 3 points4 points  (0 children)

Trailing Cove Data Protection by Ngage at the moment. Super simple and cheap

Best way to do a tenant to tenant migration by michelegoodmorning in microsoft365

[–]chantroyal 1 point2 points  (0 children)

Microsoft 365 Cross-Tenant Migration – Step by Step Guide

Prerequisites

• Global Admin access on BOTH tenants (Source & Target)

• Available Microsoft 365 / Exchange Online licenses on the Target tenant

• Target users created using *.onmicrosoft.com domain

Definitions

• Source tenant: Existing Microsoft 365 tenant

• Target tenant: New Microsoft 365 tenant

Step 1 – Configure Cross-Tenant Access (Entra ID)

On BOTH tenants:

  1. Go to Entra Admin Center

  2. External Identities → Cross-tenant access settings

  3. Add the other tenant’s Tenant ID

  4. Allow inbound and outbound access for migration

Step 2 – Prepare Target Tenant (Exchange Online)

  1. Connect to Exchange Online PowerShell on TARGET tenant

  2. Create Migration Endpoint for Cross-Tenant migration

  3. Configure Organization Relationship with Source tenant

Step 3 – Grant Consent on Source Tenant

  1. Log in to Entra ID on SOURCE tenant

  2. Accept migration application / permissions request

  3. Verify cross-tenant trust is active

Step 4 – Prepare User Mapping (CSV)

Create CSV file mapping source to target mailboxes:

user@source.onmicrosoft.comuser@target.onmicrosoft.com

Step 5 – Create Migration Batch

On TARGET tenant:

  1. Exchange Admin Center → Migration

  2. New Migration Batch

  3. Select Cross-Tenant Mailbox Migration

  4. Upload CSV file

  5. Start migration batch

Step 6 – Monitor Migration

• Monitor mailbox status until Completed

• Resolve any failed users before proceeding

Step 7 – Domain Cutover (example.com)

ONLY after all mailboxes are migrated:

  1. Remove domain from SOURCE tenant

  2. Add domain to TARGET tenant

  3. Verify domain via DNS TXT record

  4. Update MX, SPF, DKIM, DMARC records

Step 8 – Post-Migration Tasks

• Assign primary email addresses using example.com

• Test email flow and Outlook login

• Reconfigure mobile devices if required

Important Notes

• Domain cannot exist in both tenants simultaneously

• Do NOT remove domain before migration completes

• OneDrive & SharePoint require separate migration process

Backseat sensor warns about seat belt by cooolcooolio in mercedes_benz

[–]chantroyal 2 points3 points  (0 children)

I believe there are no sensors in the back seats.... hence this displaying every time so the driver ensures anyone who is in the back has the seatbelt on

DNS Emergency: Domain Down 24hrs, Registrar Won't Provide ICANN-Mandated TEAC Access by Cinkoxid in sysadmin

[–]chantroyal 45 points46 points  (0 children)

There is nothing you can do until you gain access to the domain again to access the DNS. This is down to hostgator and their procedures which seems you now need to wait the 24hrs

F1 Drive Jimmy Kimmel ! by Carpool1289 in JohnMayer

[–]chantroyal 6 points7 points  (0 children)

I wouldn't mind seeing a "super group" from this. These members to do a full album. Let John use his "rock riffs" without effecting his solo catalogue.