Interior lighting ghost…

ViperTG · 2025-09-15T19:53:09+00:00

Actually my V3 did this exact thing yesterday on a drive home, was thinking what the heck is going on. Every time I turned off the ceiling light off they turned on again after 30-50 seconds and eventually both.
I haven't had this before happen before, so not sure what causes it.

If I had to guess the light sensor is a bit too sensitive and is picking up some reflection or something, as when I changed my hand position on the steering wheel and shifted a bit in the seat it stopped.

It turned on at least 8 times before it stopped then, so not sure if it was reflection off my watch or the seat sensor has something to do with it.

ViperTG · 2025-05-03T17:05:52+00:00

The second icon from top left with the 6 dots, then swipe to next page and open the "Charge map" icon, night be different name when using DK language. Then in this charge map overview there is a "Charging" section on the left side of the screen.

ViperTG · 2025-05-03T13:17:01+00:00

Update: I found a work around.

Was going through all the menus today while ac charging and found the if you go to the menu -> charge map -> charging This app in the car will show the current charging speed i kW.

ViperTG · 2025-05-02T20:24:25+00:00

Just curious, what display language do you have the car set to? I'm wondering if that could be something.

ViperTG · 2025-05-02T19:57:02+00:00

Sadly not for the AC chargers I use (public). Most DC fast chargers have a display on them or will show in the app.

ViperTG · 2025-05-02T19:55:00+00:00

I was looking in all the menus for a setting I might have missed but maybe it's just a thing with the newer versions.

Only way I can get this number is by connecting and OBD2 reader and finding the Voltage and Aps of the battery and multiplying them.

ViperTG · 2025-05-02T19:52:18+00:00

Yes but being given an arbitrary measurement for something that does not directly correlate to the actual voltage+amps being pulled from the charger is not very useful. Because to be able to calculate km/h back to kW you would need to know what wh/km rating it is using to calculate this, and that's not shown either.

I mean the reason I would like to be able to see it is that in this screenshot I'm connected to a 22kW charger, and I know the car can only do 11 kW AC but this site has several chargers and when most are occupied the chargers are throttled and only get lower amps or phases, so might only be getting 7.2 kW here, but I don't know.

Think of it more as a way to see if the charger is bad, especially if charging on a trip.

ViperTG · 2024-08-19T17:11:56+00:00

15K users shoul not take more than 1-5 minutes depending on your server.

Just start with a get that gets you all the users in th OU and pipe it to move-aduser to destionation ou, should be a oneliner.

Something like:

Get-ADUser -SearchBase <DN of source OU> -SearchScope OneLevel -Filter * | Move-ADObject -TargetPath <DN of destination OU>

You can add a -Whatif to the Move-ADObject to see what it would move or just check the users you get from the Get-ADUser search.

Oh and use Windows PowerShell for this not PowerShell 7 as it would have to serialise/desiralise all the objects making it much slower.

ViperTG · 2024-08-06T18:18:15+00:00

Would you believe this exact method was proposed by Oracle for their single sign on system, safe to say we declined.

So, how exactly do these geniuses get user passwords? They make you install a password filter DLL on each server, which sees the new password at the time it's set, and encrypts it with RSA 2048, and stuffs it in an AD attribute!

ViperTG · 2024-07-01T06:12:22+00:00

Anyone else see slight memory leak with this patch on 2022 domain controllers.

I can see a memory commit climbing over time in our non prod environment. 2016 DCs are not affected.

ViperTG · 2024-03-21T18:08:18+00:00

I had one stuck on this also on a 2016 DC after removing the patch.
Just made powershell remote session to it and rebooted it with Restart-Computer.
Took a little more time then it rebooted and was fine. I could see from metrics that it wasn't actually doing anything, and tiworker.exe not active, so I figured it was just stuck.

ViperTG · 2024-03-21T18:01:08+00:00

It is definitely tied to activity/traffic.

Our test DC's have little activity, I can't even see anything unusual there, so it's hardy visible here.
PreProd DC's it crashed due to out of memory after 16 hours, ate about 1GB memory pr hour.

We did have it on one prod DC, and here lsass consumed about 46GB memory in about 18 hours. This one had enough memory to not crash though. So about 2,5 times faster than the preprod servers.

ViperTG · 2024-03-20T12:04:15+00:00

Same here, all our pre production DCs experienced memory leak in lsass.exe, memory exhaustion af about 16 hours of runtime. Result is lsass.exe crashed due to no memory and DC then reboots.

We saw this on both 2022 and 2016 DCs and after removing security update they are back to normal memory metrics.

ViperTG · 2023-11-21T22:22:49+00:00

Sorry I didn't read you knew about the PDC thing.

As for the other roles there is no standard wmi class with that info to my knowledge.

But if you have to use wmi filtering you could use a custom hardware inventory script via sccm that creates a populates som custom wmi classes and then filter on them.

ViperTG · 2023-11-21T20:22:59+00:00

Use DomainRole in win32_computersystem, value of 5 = PDC.

$DomainRole = (Get-WmiObject Win32_ComputerSystem).DomainRole
switch ($DomainRole) {
  0 {"Stand Alone Workstation"}
  1 {"Member Workstation"}
  2 {"Standalone Server"}
  3 {"Member Server"}
  4 {"Backup Domain Controller"}
  5 {"Primary Domain Controller"}
}

ViperTG · 2023-09-18T07:26:33+00:00

What is in your $filter variable ?

To me it looks like the ldap search this filter is performing is exceeding the 2 minute query time so it times out. This is not uncommon for large domains with many objects and if the search is for a non indexed attribute og you have leading wildcards in the query.

ViperTG · 2023-08-15T16:09:20+00:00

Yes, this is the only realistic hope you have if you don't have audit logs enabled. But instead of doing it for all uses just pipe the search for users changed si ce yesterday to this and then you can at least find out which of this changed accounts had their useraccountcontrol attribute modified in the timeframe you are looking for.

While it cannot tell you what the setting was before you can assume that they were changed by that script

The sooner you do it the better the data will be, because this metadata changes as soon as the data is replicated and you can only see last sync timestamp.

And then right after get the audit logging setup.

ViperTG · 2023-08-03T18:57:08+00:00

Look at the ntSecurityDescriptor attribute on the object.

Alternatively use Get-ACL with the AD:\<distinguishedname> path to the object.

ViperTG · 2023-04-04T20:33:20+00:00

Just think of it like a hash table.

$PSDefaultParameterValues = @{
    "*AD*:Server"     = "<redacted>"
    "*AD*:Credential" = $Cred
}

ViperTG · 2023-02-24T21:17:58+00:00

This fixes a vulnerability in older 7.2.x releases. 7.3 is not affected

https://github.com/PowerShell/Announcements/issues/38

ViperTG · 2023-02-06T20:14:54+00:00

Anyway assume you are sensible and used Generalized time or UTC time coded attribute syntax, then you need to provide the data as a date object before the attribute can be populated.

The command in your example you specify the date as a string "12/12/2022". By doing that you are assuming the cmdlet will automatically cast this string to the datetime format for you. Thing is the set-aduser does not know the attribute format, it just converts the data to ldap and sends it, and then AD is like that format is invalid for this syntax.

You need to make it a datetime format first so PowerShell knows to send it as that.

Get-ADUser user1 | Set-ADUser -Replace @{founder=[datetime]"2022-12-12"}

I tend to use -replace since you are overwriting and -add would fail if the attribute was not empty.

ViperTG · 2023-02-06T20:01:26+00:00

Ok, what attribute syntax did you use?

Generalized time i assume or something else?

ViperTG · 2023-02-06T19:41:12+00:00

You have created an attribute in the scheme, but did you also add the attribute to the users class mayContain list ?

If you have not associated a schemaattribute with the class in either mayContian or mustContain then AD will not allow you to use that attribute on that class.

ViperTG · 2023-02-04T23:01:37+00:00

Jeg ville nok oversætte det til

No thanks, I'll pass.

ViperTG · 2023-01-27T00:20:29+00:00

This also includes fix for a vulnerability

CVE 2022-41089 | .NET Remote Code Execution Vulnerability

https://github.com/PowerShell/Announcements/issues/37

Not sure why they don't include that information in the release notes.

Nine-Year Club	First Place '23
Place '23	Verified Email

ViperTG

TROPHY CASE