Important
To filter the blog, please use theses tag:
General news.
Website related post
website.
parental-control about technology.
technology post.
Note
All blog links are archived here.
Hi everyone
I wanted to warn that on 1 November 2023 a new requirement will be there for SMTP relay inside Exchange Online.
Effective from November 1, 2023, the matching condition for the SMTP P2 sender domain will be removed. This means that relaying email through Exchange Online will require meeting the following criteria:
Failure to meet either of these conditions after November 1, 2023, will result in the rejection of relay attempts from your on-premises environment to Exchange Online
Solution: It is necessary to modify your Inbound Connector of the on-premises type and switch from using IP addresses to a certificate domain. Furthermore, you need to ensure that the certificate domain is included as an accepted domain of your organization.
Hi everyone
Today I wanted to share a tip, as if I read reddit or ui's forum it seem a really complex task to change a WAN IP.
After multiple error and guess I now found the correct solution for that.
First we log locally if we can.
After we need to remove the NAT'ing definition for the public IP we will change; to set none

If we have multiple network, it's to be done for all of them, as seen below I have two to change;

If we forget that step the unifi will complaint about the IP being used in the Default network.
After we pause all Site-to-Site VPN.
If we forget that step the unifi will complain that it can't change the gateway.
After all those steps, now we can change the public IP :)

Hi everyone
Today I wanted to share a method to be able to map network drive from Intune / Endpoint Manager.
The method is useful if you are in a hybrid setup, where some ressource are in the cloud and some other on premise.
If you have azure ad sync with a domain controller and your cloud, the SSO will work out of the box with the mapping. A exception to the SSO, if your users use PIN with Windows HELLO you will have other integration to do.
To start please go download the drive mapping custom ADMX.
Download link from the author site | An alternative link from github
After that we need to import the ADMX into Intune.
Go into Device

Go into configuration profiles

Select the correct ADMX to be imported

After that we can now create our profile with the news settings
Create one here named Map Drive

There we set the settings we want;

We can see the settings the ADMX give us;

After that it should work correctly to map when the device is located inside the datacenter :)
Hi everyone
Today I wanted to share a small tip if you got HHCTRL filling your event log like crazy.


Findind the culprit can be done, but in case it's know and it dont impact anything you can disable the event log for the event that way with these registries key;
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\HTMLHelp\1.x\HHRestrictions
MaxAllowedZone = 00000001 (DWORD)
EnableNonInteractiveUser = 00000001 (DWORD)
EnableFrameNavigationInSafeMode = 00000001 (DWORD)
and
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\HTMLHelp\1.x\HHRestrictions
MaxAllowedZone = 00000001 (DWORD)
EnableNonInteractiveUser = 00000001 (DWORD)
EnableFrameNavigationInSafeMode = 00000001 (DWORD)
That should do the tip to remove those entry as it can block other good information to appear easilly.
Hi everyone !
Today I wanted to share a small tip if you migrate some file share to sharepoint online as it's a essential part to migrate full cloud.
In the migration wizard as seen here; you could hit some warning that some files use incorrect filenames.


The migration wizard got some file that it does not like, aka;
Thumb.db's file or temporary Office's file, ~\$'s file prefix.
The command issued for your file share; Get-ChildItem -Path '\\server\path' -Filter '~\$*' -Recurse would give you a good idea what it can find.
A dir /s like that would work too;

If you download the analyse's log you will get log entries with that error code;

An easy fix if you don't want to migrate those filename is to replace in batch; like that way;

Get-ChildItem -Path 'z:\' -Filter '~\$*' -Recurse | Rename-Item -NewName { \$_.Name -replace '~\$', ' ' }
The option are too cna help in the batch migration advanced's option;

Some good information for regex in case you have other files that need updating in batch;
https://megamorf.gitlab.io/cheat-sheets/powershell-regex/
Thanks everyone