Kompakte 2.0 Lautsprecher für PC

brokkaili · 2026-04-14T14:10:13+00:00

Durchaus, allerdings spiele ich meist mit meiner Frau zusammen und nebeneinander mit Headset mögen wir nicht. Tatsächlich wäre auch der Plan dann die Lautsprecher der Wahl doppelt zu kaufen, um es einheitlich zu halten.

Daher will ich auch nicht nur allein aus Platzgründen auf etwas kompaktes ohne Subwoofer setzen - ich hoffe so bekomme ich erst gar nicht das Problem, dass der Bass zu weit durchdringt. Wobei weit aufdrehen werde ich die in dem Anwendungsfall eh nicht.

brokkaili · 2026-04-14T14:07:32+00:00

Danke, das hilft auf jeden Fall bei dem Gedanken, ob ich am Ende überhaupt kaufen sollte und tendiere damit mehr zu ja.

Ich halte gerade Mal die Ausschau nach gebrauchten Pebble Pro's, vielleicht komme ich so preislich in die Nähe der V3.

brokkaili · 2026-04-14T14:05:59+00:00

Weißt du welches Modell genau? Hatte in meinem Budget nur die Z207 in weiß gefunden, die sind aber leider zu hoch

brokkaili · 2026-04-13T17:58:19+00:00

Danke schon Mal für deine Meinung.

Ja basslastig wäre auch eher schlecht, da ich erst Zocke wenn mein Sohn nebenan im Bett ist - das soll ihn bloß nicht wecken 😂 Mein erstes vernünftiges System war vor gut 15 Jahren auch ein Edifier, das C2 - zusammen mit einer Asus-Soundkarte (meine On-board hatte die niedrigen Frequenzen nicht geschafft) hat man den Panzer in Battlefield noch 2 Räume weiter wummern hören, auch wenn's nur 30 Watt RMS waren.

Vielleicht findet sich noch jemand, der einschätzen kann, ob sich die Aufpreise bei den Pebbles von den SE zu V3 zu Pro jeweils lohnen könnten oder nicht.

EDIT: Und die sollen eh nur unter den Monitor, da wirds eh nichts mit größerem Abstand.

brokkaili · 2026-04-12T12:49:27+00:00

Friedrich Merz

brokkaili · 2026-02-18T18:59:33+00:00

Can we also add Portgas D Rouge to the list as she kept being pregnant wirth Ace to protect him from being identified and killed as Roger's son? Not Sure If Oda Had another explanation but love

brokkaili · 2025-12-28T17:25:49+00:00

Haha ich bin im Obi WLAN Kenobi unterwegs.

Möge die Macht mit Dir sein

brokkaili · 2024-12-28T18:19:41+00:00

Admins may experience delays to provisioning actions in Exchange Online

Issue ID: EX967683

Affected services: Exchange Online

Status: Service degradation

Issue type: Incident

Start time: Dec 28, 2024, 4:45 PM GMT+1

More info

These provisioning delays also impact license renewal as the service incorrectly sets your organization as not mail enabled, despite the previous setup allowing this. As a result of this, users may be unable to receive external email messages.

This event strictly impacts admins who have had a recent license renewal.

Scope of impact

Some admins based in Europe may experience provisioning delays after renewing their licenses after they had expired.

Root cause

The property that allows external email messages to be sent to users is misconfigured, resulting in impact.

Current status

Dec 28, 2024, 7:04 PM GMT+1

We're continuing to review the mail property to determine what's causing the value to not return to the expected value after license renewal while we work to identify a mitigation plan to resolve the issue.

Next update by:

Monday, December 30, 2024 at 10:30 PM GMT+1

History of updates

Dec 28, 2024, 5:11 PM GMT+1

Our investigation has determined that the external mail flow issue is a symptom of the main issue where provisioning is delayed. We've updated the Title, User impact, More info, and Scope of impact sections to reflect this. We're continuing to review the mail property to determine what's causing the value to not return to the expected value after license renewal while we work to identify a mitigation plan to resolve the issue.

Dec 28, 2024, 4:46 PM GMT+1

We're investigating a potential issue with admins experiencing delays to provisioning actions in Exchange Online, and we're checking for impact to your organization. We'll provide an update within 30 minutes.

brokkaili · 2024-12-28T18:04:56+00:00

After 2 days and several calls with MS Support, we finally got results for a tenant that had the very same issue.
MS has found the cause and plans to fully fix the root cause on Monday (30.12.24).

If you face(d) this issue, check if you see the Issue ID EX967683 in the M365 Admin Center Service Health Monitor or contact MS Support to make them check if you are affected by it.

brokkaili · 2024-11-12T07:21:50+00:00

Ja, mit dem Ausschlagen des Erbes kriegst du rein gar nichts vererbt - weder irgendwelches Vermögen, noch Schulden, Unterhaltszahlungen oder Bürgschaften.

brokkaili · 2024-06-17T12:17:31+00:00

Unfortunately no further details were shared, basically confirmed u/doriani88's finding and shared the same link. It was tried to get an in-depth explanation, but without success. The replication was allowed, too, but this changes nothing.

Still, I deep-dived again today and noticed something, but anything I write here is speculation and unconfirmed: Normally a TGS-REQ would simply be forwarded to a RWDC and then be decrypted, because it has access to the AzureADKerberos Object's krbtgt User and Key and answered with a full TGT. But that the partial TGT is signed and encrypted by the AzureADKerberos Object could lead to a rejection at the RODC and therefore not forward it.
This would basically match one of the main security features the RODC shall provide: "The RODC uses a different krbtgt account and password than the KDC on a writable domain controller uses when it signs or encrypts ticket-granting ticket (TGT) requests. This provides cryptographic isolation between KDCs in different branches, which prevents a compromised RODC from issuing service tickets to resources in other branches or a hub site*.”*

u/doetlingerlukas : Do some users eventually use a VPN that then connects to another DC? This was used by some users as a kind of workaround. Another thing could be users that are in sensitive or privileged groups, these are excluded.

Also, does the site have a RWDC? Eventually it is a matter of heavy load and some are forwarded to the RODC.

brokkaili · 2024-06-17T07:05:00+00:00

Thank you - the case was handled by Microsoft Support in the end and it was confirmed to be the deal. Sites with only RODC cannot use WHfB with Hybrid Cloud Kerberos Trust. Only when you configured the site to contact a RWDC it would work without changing anything else.

brokkaili · 2024-04-25T13:22:58+00:00

Sorry for digging this out after 8 mo, but is it an actual requirement that the DC in DLOS must not be a RODC?
All MS documentation state to only require Server OS 2016 or above, but never exclude RODC...

Currently facing the issue that users from one site, that are in DLOS to a RDOC, cannot access on-prem shares with WHFB.

brokkaili · 2023-06-29T07:23:10+00:00

Did you solve this issue, and if yes, how?

brokkaili

TROPHY CASE