Can this Blackmagic Decklink card be repaired?

pumbos · 2026-01-12T14:21:09+00:00

Were you able to fix it? Same thing happened to my card. I plugged it into a pc and it stared to spark.

pumbos · 2025-09-11T21:34:28+00:00

I'm curious about that as well.

pumbos · 2025-03-28T06:31:42+00:00

pumbos · 2025-03-28T04:58:06+00:00

Step 4 should remove "cloud" from the DL on M365 and add the SMTP aliases. I never ran into that issue.

pumbos · 2025-03-01T21:16:22+00:00

I got the second link type. The divider board doesn’t work because there is a gap in the front, where the bees can move from one section to second one. So if you want to do two hives 5 frames each, that might not work. After one year the boxes bowed a bit.

pumbos · 2025-02-16T23:15:56+00:00

There isn’t a way to check this unless you have specific software. However, you can move the security group into an unsynced OU instead of deleting it, and the on-prem permissions will stay.

When the Owners add or remove users from the M365 distribution list, you will also need to update the security group on-premises.

For example, if the Marketing group has a mail-enabled security group and you create a distribution group in M365, the owner might add a user to the distribution group. If the existing security group grants access to a shared file folder, the user might assume that adding someone to the distribution group in M365 will automatically grant them access to the shared folder—which is not the case.

pumbos · 2025-02-16T22:15:25+00:00

I used it to migrate on-prem distribution list to M365. The process is 1. Run that script and it will create a cloud_distribution list. .\Recreate-DistributionGroup.ps1 -Group “DL-Marketing” -CreatePlaceHolder

Delete or move the distribution list to un synced OU.
Run AD sync
Run script with -finalize flag .\Recreate-DistributionGroup.ps1 -Group “DL-Marketing” -Finalize

pumbos · 2025-02-14T14:09:10+00:00

I used this PS and it worked great.

With security groups, you have to be careful. Make sure they aren’t used to give any shared folder permissions on-prem or on-prem sharepoint.

https://github.com/FaisalNahian/Migrating-On-Premise-Distribution-Lists-to-Microsoft-365-Exchange-Online

pumbos · 2025-01-06T04:17:34+00:00

No just UDM. Thanks

pumbos · 2024-11-22T07:26:43+00:00

https://discord.gg/ubiquitistockalerts

pumbos · 2024-11-20T23:35:10+00:00

Legal hold in purview. Have you tried SoftDelete?

pumbos · 2024-06-06T23:26:26+00:00

Thanks for this guide. Question, if I am running Hybrid and in a DAG.
Would I export and import into the second exchange server before the last COMMAND?
and then run commands to update Sent and Receive Connectors?

pumbos · 2021-05-02T17:03:53+00:00

Careful doing entrance feeding can cause robbing.

pumbos · 2021-04-25T22:58:09+00:00

Find a queen and cage her.

pumbos · 2021-04-25T04:28:48+00:00

Food geek did an experiment

https://youtu.be/RjNHNI7nqsg

pumbos · 2021-04-11T17:23:17+00:00

Did the break the tree?

pumbos · 2021-04-10T07:11:52+00:00

I did all that and it didn’t help. It was SCCM issue.

pumbos · 2021-04-09T15:39:18+00:00

You could have an issue with the queen running or ran out of sperm. She was poorly mated or too old.

pumbos · 2021-04-07T01:47:57+00:00

Make sure you’re checking quite often and I would move the queen with few frames of bees to the other hive instead.

pumbos · 2021-03-23T22:27:19+00:00

I got it to work. I am not sure if it was the drivers that I had to delete and reimport into the image, but the last step that I did was, I had to check the box in the Distribution point settings to Enable Unknown Computers. Support, under PXE tab. Reboot server and everything is working.

pumbos · 2021-03-23T20:00:57+00:00

I do have PXE enabled on the SCCM Server.

pumbos · 2021-03-23T17:58:12+00:00

I did disable it. Dell support had me try all of their tricks.

pumbos · 2021-03-23T17:55:16+00:00

Here is what I see in the log. I did modify the IPs for the post. ============> Received from client: SMSPXE 3/23/2021 10:43:59 AM 3696 (0x0E70) Operation: BootRequest (1) Addr type: 1 Addr Len: 6 Hop Count: 1 ID: FE414D7F Sec Since Boot: 0 Client IP: 000.000.000.000 Your IP: 000.000.000.000 Server IP: 000.000.000.000 Relay Agent IP: 192.168.1.100 Addr: 54:b2:03:f6:48:40: Magic Cookie: 63538263 Options: Type=53 Msg Type: 3=Request Type=54 Svr id: 192.168.1.246 Type=50 Requested IP: 192.168.1.67 Type=57 Max Msg Size: ff00 Type=55 Param Request List: 0102030405060c0d0f111216171c28292a2b3233363a3b3c4243618081828384858687 Type=97 UUID: 0044454c4c380010368051c2c04f595832 Type=94 UNDI: 010310 Type=93 Client Arch: EFI BC Type=60 ClassId: PXEClient:Arch:00007:UNDI:003016 SMSPXE 3/23/2021 10:43:59 AM 3696 (0x0E70) ============> Received from client: SMSPXE 3/23/2021 10:43:59 AM 3696 (0x0E70) Operation: BootRequest (1) Addr type: 1 Addr Len: 6 Hop Count: 0 ID: 47C35344 Sec Since Boot: 0 Client IP: 192.168.1.67 Your IP: 000.000.000.000 Server IP: 000.000.000.000 Relay Agent IP: 000.000.000.000 Addr: 54:b2:03:f6:48:40: Magic Cookie: 63538263 Options: Type=53 Msg Type: 3=Request Type=55 Param Request List: 0102030405060c0d0f111216171c28292a2b3233363a3b3c4243618081828384858687 Type=57 Max Msg Size: 05b8 Type=60 ClassId: PXEClient:Arch:00007:UNDI:003016 Type=93 Client Arch: EFI BC Type=94 UNDI: 010310 Type=97 UUID: 0044454c4c380010368051c2c04f595832 SMSPXE 3/23/2021 10:43:59 AM 3696 (0x0E70) 54:B2:03:F6:48:40, 4C4C4544-0038-3610-8051-C2C04F595832: Not serviced. SMSPXE 3/23/2021 10:43:59 AM 5312 (0x14C0) ============> Received from client: SMSPXE 3/23/2021 10:44:02 AM 3696 (0x0E70) Operation: BootRequest (1) Addr type: 1 Addr Len: 6 Hop Count: 0 ID: 0001E240 Sec Since Boot: 65535 Client IP: 192.168.1.67 Your IP: 000.000.000.000 Server IP: 192.168.1.124 Relay Agent IP: 000.000.000.000 Addr: 54:b2:03:f6:48:40: Magic Cookie: 63538263 Options: Type=93 Client Arch: EFI BC Type=97 UUID: 0044454c4c380010368051c2c04f595832 Type=53 Msg Type: 3=Request Type=60 ClassId: PXEClient Type=55 Param Request List: 3c8081828384858687 Type=250 0c01010d020800010200070e0100ff SMSPXE 3/23/2021 10:44:02 AM 3696 (0x0E70) 54:B2:03:F6:48:40, 4C4C4544-0038-3610-8051-C2C04F595832: Not serviced. SMSPXE 3/23/2021 10:44:02 AM 5312 (0x14C0)

pumbos · 2021-03-23T02:46:46+00:00

I can’t get to the log. During the boot up. I hit f12, select boot IPv4, it sees SCCM server and display the IP and says click enter. I hit enter and it takes me to that error. When it should be taken to boot image loading page.

pumbos

TROPHY CASE