Posts

Surface Slim 2 Pen not writing on Surface PRO

 It is an nightmare to solve this issue, put with a lot of patience you can solve it. Uninstall and reinstall everything on driver and firmware related to PEN and TOUCH . Procedue: 1. Surface Pen is paired on your Surface Pro open Device Manager 2. Click View on top and check Show hidden devices. 3. Expand Human Interface Devices category. Right click drivers and select Uninstall.  HID-compliant pen > Uninstall device Surface pen settings > Uninstall device Surface pen integration > Uninstall device HID-Compliant touch screen > Uninstall device Intel (R) Precise Touch Device > Uninstall device Surface Touch Pen Processor > Uninstall device Some have different names, but AGIAN uninstall EVERYTHING with PEN and TOUCH ! Note: If prompted with a checkbox stating, "Delete the driver software for this device", leave it uncheck then hit Uninstall. 4. Expand Firmware > Surface touch > Uninstall device Note: If prompted with a checkbox stating, "Delete the

Cross-Tenant Migration Legal-Hold or Encrypted Mail or File Data

 This is a quick note and IMPORTNANT : Within a Cross-Tenant Migration project, you can experience data encryption. Note the following statement and plan accordingly. Legal-Hold: There is no possibility to migrate data (EXO, SPO, OneDrive) if the source is set on legal-hold Encrypted Data: It depends on the encryption method. Either AIP or user based. If it user based user@dnsdomain.com, the migration can work and with the resignment of the user@dnsdomain.com the encryption/decryption might work again. But while the DNS domain is with the source tenant, encrypted mails become unusable. With AIP, the only way is to decrypt in source, than migrate and encrypt in target again. Migrating a tenant AIP key is NOT possible

Teams new and MTO (Multi Tenant Organization)

Image
Microsoft is moving towards a new optimized collaboration and administration for organizations operating multiple M365 tenants. New Teams client is supporting this feature. Nevertheless, there are (today in public preview) limitations to MTO, which might be removed over time. Self-service of multitenant organization functionality is limited to a maximum of five tenants and 100,000 internal users per tenant. To request a raise in these limits, submit a Microsoft Entra ID or Microsoft 365 admin center support request. Further to me, it is NOT a real multi-tenant organization, as we know from earlier days in AD, where we had "SubDomains", it is based on automated B2B identities, which are provisioned as B2B users automatically. This is the sync feature in MTO. Below the extract from Microsoft blog release: Using shared channels for seamless cross-tenant collaboration and communication In a  recent blog , we shared how Microsoft Teams Connect enables seamless and secure collabora

Faster Search with new Slash commands in Teams (Tips & Tricks)

Image
 Faster Search with new Slash commands in Teams (Tips & Tricks)

Teams Call Queue Cross-Tenant Migration

  Handling Call Queues and Auto Attendant during Cross-Tenant Migration   Note: Call queues can’t be externally chatted with. This is an important information and is the main problem you will have to deal with. Nevertheless, there is a feature, where a call is assigned to a Teams Channel. This allows at least the functionality of Guest User Access. Steps for handling Call Queues: Identify all Call Queues and Groups/ Channel(Teams) Identify all User assigned to Call Queues Identify Users assigned to multiple Call Queues Identify the purpose of the each Call Queue Identify Call Queue used internal, external (phone), internal and external, channel used For all Call Queues used internally, discuss and consider changing them to a Channel based Call queue and build a solution for revers Guest Access. Meaning, make sure you have a process included where migrated users, using the call queue have access via Guess Access from Target to Source. It is advised, that users in a Call Q

Free & Busy Sync during Cross-Tenant Migration (Exchange Online)

Image
  Free & Busy Sync during Cross-Tenant Migration You have two options “migrating” mailboxes cross-tenant: -           Microsoft Cross-Tenant Migration this will move, reconnect a user’s mailbox in target and removes the source mailbox entirely -           Using a 3 rd party tool, copying the mailbox content and syncing calendars this will leave the source mailbox intact and can confuse users in the source environment, which user is now active (see the user adoption story)   Organization relationship in Exchange Online If you migrate the User Mailbox entirely, meaning, nothing is left behind in the source, you can use Organizational Free/Busy Lookup: This feature is named: Organization relationship in Exchange Online   This allows: -           Set up an organization relationship to share calendar information with an external business partner. -           Set up an organization relationship with another Microsoft 365 or Office 365 organization or with an Exc

Exchange Hybrid Wizard Error 1603

Image
How to fix Exchange Hybrid Wizard Error 1603 This issue is related to TLS 1.2 Some links for you: Microsoft Entra Connect: TLS 1.2 enforcement for Microsoft Entra Connect - Microsoft Entra ID | Microsoft Learn The following scripts, you need to copy and same as CheckTls.ps1 and EnableTls.ps1 Frist if you run any of the following scripts, make sure UAC is disable :) Start with checking TLS Settings: FunctionGet-ADSyncToolsTls12RegValue {[CmdletBinding()]Param(# Registry Path[Parameter(Mandatory=$true,                    Position=0)][string]$RegPath,# Registry Name[Parameter(Mandatory=$true,                    Position=1)][string]$RegName)$regItem= Get-ItemProperty-Path $RegPath-Name $RegName-ErrorAction Ignore     $output= ""|selectPath,Name,Value     $output.Path = $RegPath$output.Name = $RegNameIf($regItem-eq$null){$output.Value = "Not Found"}Else{$output.Value = $regItem.$RegName}$output}$regSettings= @()$regKey= 'HKLM:\SOFTWARE\WOW6432Node\Microsoft\.NETFrame