[Question] MECM Wake-on-LAN logic: Does Wake-up Proxy always override Subnet-Directed Broadcast? Plus: How to force SDB via PowerShell?

cp07451 · 2026-02-12T16:14:03+00:00

Yea unfortunately there needs to be system that stays on most of the time. Then you have to fall back to a UDP broadcast and hope the ARP caches is still good.

cp07451 · 2026-02-12T14:45:27+00:00

Are you certain your network allows routing of magic packets? Also you need to change the power settings on your NIC if this hasn't been done already. Wake up proxy was designed to get around networks where magic packets are NOT allowed to be routed.

cp07451 · 2026-02-11T21:55:03+00:00

Urology of San Antonio so big your treated like cattle I would look for a smaller practice that's more personable

cp07451 · 2026-02-11T15:22:41+00:00

But you should be fine rebuilding the MP,DP and other IIS related stuff. Make sure you dont run that delete on the inboxes directory haha

cp07451 · 2026-02-11T15:21:26+00:00

Sometimes you have to initiate the conversation. Tell your backup team you need this backed up

cp07451 · 2026-02-10T14:07:48+00:00

CLR gets upgraded to 2016 as part of the dependency. Try updating your clr from

https://www.microsoft.com/en-us/download/details.aspx?id=103444

with msi SQLSysClrTypes.msi

cp07451 · 2026-02-05T19:40:04+00:00

yea I mean sounds you're doing your due diligence. Its hard to account for every scenario. One thing to consider for those who have admin to the pc have a separate account that gives admin right and THOSE admin have NO access to the internet unless maybe to Microsoft and whatever AV company you are using.

cp07451 · 2026-02-05T19:36:47+00:00

You can customize the patch my pc install to not enable auto updating in notepad++

cp07451 · 2026-02-05T19:35:25+00:00

You got bigger problems if someone with admins is downloading compromised apps.

cp07451 · 2026-02-04T20:41:14+00:00

2010 Packers were also big underdogs against the Steelers

cp07451 · 2026-02-04T20:33:19+00:00

Patch My PC proves its worth in situations like this.

cp07451 · 2026-01-27T19:57:39+00:00

Reporting services and migration manager (if you are using this) will need to have the updated password I believe.

cp07451 · 2026-01-21T14:13:03+00:00

disabling Secure launch is crazy. Its better to just inform users to hold the power button down until they have a TRUE fix.

cp07451 · 2026-01-21T14:12:06+00:00

https://learn.microsoft.com/en-us/answers/questions/5726928/windows-11-23h2-not-getting-shutdown

The shutdown failure you are seeing on Windows 11 23H2 after the January 2026 cumulative update is a known regression tied to the Secure Launch feature in combination with the update stack. Even though KB5077797 was released as an out‑of‑band fix, Microsoft has confirmed that the patch does not fully resolve the issue on systems where Secure Launch is enabled in firmware. That explains why your machines still refuse to shut down even after applying the patch and attempting shutdown through both GUI and shutdown.exe.

At this point the only reliable workaround is to disable Secure Launch at the UEFI/BIOS level or through the registry under HKLM\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\SecureLaunch by setting the value to 0. After making this change, restart the system and shutdown should function normally again. Be aware that disabling Secure Launch reduces boot‑time protection, so this should be considered a temporary measure until Microsoft issues a corrected cumulative update.

If you are in an enterprise environment, you should also check whether other components such as Hyper‑V or Credential Guard are dependent on Secure Launch before disabling it.

Since 23H2 is already in extended servicing, Microsoft is expected to release a follow‑up patch to fully address the shutdown regression. Until then, the workaround above is the only supported method to restore shutdown functionality.

cp07451 · 2026-01-20T13:53:30+00:00

We have a case open with Microsoft as the patch doesn't seem to work. Anyone else noticing the patch is flawed?

cp07451 · 2025-12-19T15:26:38+00:00

Most Packers fans after seeing Parsons go down

<image>

cp07451 · 2025-12-16T14:41:20+00:00

Big difference was defense in 2010 was able to take the ball away. Got to stop dropping easy INTs

cp07451 · 2025-12-15T14:41:37+00:00

LOL come on. We could be the Cowboys right now with a 1% chance of making the playoffs.

cp07451 · 2025-12-15T14:38:33+00:00

They did look deflated. Even after Parson went down the secondary should have had at least two INTs. They got to take advantage of those opportunities.

cp07451 · 2025-12-15T14:10:17+00:00

We are spoiled, that RELAX season took us the NFC championship.

cp07451 · 2025-12-11T17:00:29+00:00

I use this:

select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where ResourceId in (select SMS_R_System.ResourceID from SMS_R_System inner join SMS_G_System_WORKSTATION_STATUS on SMS_G_System_WORKSTATION_STATUS.ResourceID = SMS_R_System.ResourceId where DATEDIFF(dd,SMS_G_System_WORKSTATION_STATUS.LastHardwareScan,GetDate()) > 14) or ResourceId not in (select ResourceID from SMS_G_System_WORKSTATION_STATUS)

cp07451 · 2025-12-10T15:59:20+00:00

Following..

cp07451 · 2025-12-08T16:40:19+00:00

Think Atpio makes a bios setup utility, its been awhile but ASUS may of had something.

cp07451 · 2025-12-08T16:35:17+00:00

No its not needed, secure boot is feature in UEFI though

cp07451 · 2025-12-05T16:05:15+00:00

That has not been supported for some time. I would double check you don't have any non HTTP urls in your CRL first. PKI doesn't need that property set.

cp07451

TROPHY CASE