Lorky`s Blog - Techno ressources and general informations for everyone !

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 share that soon enformement of the PAC inside a KRB ticket will be active. (22 October 2022)

If in your enviromment you still see such error;

The KDC encounters a TGT or other evidence ticket without a PAC. This prevents the KDC from enforcing security checks on the ticket.

kdc001.png?w=536

That can have an impact if you have older domain controler, like a 2008R2 without the extended support option, as such the fix is not available for them.

A registry key exist, but after the 22 October 2022 it will no longer be checked;

To quote the registry key information;

Registry subkey HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Kdc
Value PacRequestorEnforcement
Data type REG_DWORD
Data 1: Add the new PAC to users who authenticated using an Active Directory domain controller that has the November 9, 2021 or later updates installed. When authenticating, if the user has the new PAC, the PAC is validated. If the user does not have the new PAC, no further action is taken. Active Directory domain controllers in this mode are in the Deployment phase.2: Add the new PAC to users who authenticated using an Active Directory domain controller that has the November 9, 2021 or later updates installed. When authenticating, if the user has the new PAC, the PAC is validated. If the user does not have the new PAC, the authentication is denied. Active Directory domain controllers in this mode are in the Enforcement phase.0: Disables the registry key. Not recommended. Active Directory domain controllers in this mode are in the Disabled phase. This value will not exist after the July 12, 2022 or later updates.Important Setting 0 is not compatible with setting 2. Intermittent failures might occur if both settings are used within a forest. If setting 0 is used, we recommend that you transition setting 0 (Disable) to setting 1 (Deployment) for at least a week before moving to setting 2 (Enforcement mode).
Default 1 (when registry key is not set)
Is a restart required? No
This come from KB5008380—Authentication updates (CVE-2021-42287) patch. I suggest to quickly remove those older DC if you can, else just make sure you are updated.

Continue Reading...

Today I wanted to share a small tip if you need to remove Team from autostarting when the session start for your users.

The easiest way if you have installed it to your user without the autostart at off is to remove by GPO the run command.

The path is;

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run

com.squirrel.Teams.Teams

team-autostart-remove.jpg?w=409

At the next logon your user will not see the Teams application loading, which can help on load time :)

Continue Reading...

Upgrading HP Thin Client T420

October 7, 2022, 3:59 pm technology

Hi

Today I wanted to share a tip if someday you want to upgrade the hard disk that Thin Client terminal. As by default it come with a 32 or 64 g HDD.

The terminal come with Windows 10 LTSB 2016 by default, which can be upgraded to LTSC 2019 with added licensing from HP, but it can be hard to do the update with the smaller SSD that the unit has, so the upgrade can be necessary in the end. (I didn't tried Windows 11 in it)

The interior look that way;

image.png?w=564

As you can see we have not much room for improvement, but in that specific case I would be using the WiFi pciex connector to connect the new SSD.

I remove the card;

image-1.png?w=279

The goal will be to put an adapter;

image-2.png?w=168

image-3.png?w=256

In the end it look that way;

image-4.png?w=517

I recommend to use a small SSD, to be able to close back the case.

After that we can boot, and install the OS inside the SSD :)

Continue Reading...

Hi everyone !

Today I wanted to talk a small issue that can happen if you try to join a machine to Azure AD. The issue is the Join Azure AD's option is just not displayed in the Account's windows but would work in OOBE.

That would show that way;

image-2.png?w=800

The error can come if the computer got no internet access, as it can't log into Azure at all. The error can come too if you have a Microsoft Account too into the computer, like there;

image-1.png?w=1024

For that computer I was able to log to an Microsoft Account AND an Azure AD account, but the computer was forced to stay inside a unmanaged state as the option to join the Azure AD was just not there.

To allow the computer to join the Azure AD you need in that case to remove the Microsoft's account. That will allow you to join the Azure AD, like shown there after the removal of the Microsoft's account;

image-4.png?w=606

After you can join completely;

image-5.png?w=634

Continue Reading...

Hi everyone !

Today I wanted to share a tip for creating more complex group policy.

WMI filter come handy to target the needed computer in group policy. Adding a NOT LIKE clause like in SQL can be there important.

Creating multiple query help to make a full target.

Keep in note that in multiple query EACH query must be TRUE. So if you do two query, both need to be evaluated as TRUE for the filter to apply.

I will start with the NO clause. If inside your WMI filter you need to use a NO clause please remember that it must be wrote select * ... WHERE NOT ....

An example that do a compare on the version;

select * from Win32_OperatingSystem WHERE NOT Version like "10.0.14393%"

Now time to talk on how to make multiple WMI check filter.

I would show an example of how it can be useful; if in example your GPO must target all Windows 10, except a LTSB version. That would look that way;

select * from Win32_OperatingSystem WHERE NOT Version like "10.0.14393%"

select * from Win32_OperatingSystem WHERE Version like "10.%" AND ProductType="1"

image.png?w=426

Continue Reading...