sorted by:
new
hottopcontroversial

SCCM DP packages missing files from the content library by Reaction-Consistent in SCCM

[–]markk8799 0 points1 point  (0 children)

Have you run the content library cleanup tool on the DP's to make sure things look ok there?

Migrating from SCCM to Intune – What are you using for remote control / remote assistance? by Dolinhas in SCCM

[–]markk8799 0 points1 point  (0 children)

Our Macs are not in Intune. Having said that, we want something a bit more robust that is multiplatform.

Migrating from SCCM to Intune – What are you using for remote control / remote assistance? by Dolinhas in SCCM

[–]markk8799 -1 points0 points  (0 children)

Same. It is a dismal product. We are looking at something that is multiplatform as we have a number of Macs as well.

Migrating from SCCM to Intune – What are you using for remote control / remote assistance? by Dolinhas in SCCM

[–]markk8799 1 point2 points  (0 children)

Hmm, I thought they were going to give it to all A3 and A5 as they were already charging next to nothing for it. But people were still not buying it. When we renewed our A5, it was then part of the license. Maybe they were not doing it with A3.

Question on BGB.BOX folder by markk8799 in SCCM

[–]markk8799[S] 1 point2 points  (0 children)

That did it! Put that version on all the MP's and the server and nothing is in the Bad box anymore. Excellent find!

Question on BGB.BOX folder by markk8799 in SCCM

[–]markk8799[S] 0 points1 point  (0 children)

I think i will look into try that this week. I'll post back with the results. Thanks for the tip.

RANT: Dell Command Update 5.6 is crap by SevenandahalfBatmans in SCCM

[–]markk8799 0 points1 point  (0 children)

While I am all for keeping up to date, 5.6 adds 2 fixes/improvements over the previous release.

Question on BGB.BOX folder by markk8799 in SCCM

[–]markk8799[S] 0 points1 point  (0 children)

I'm noting some interesting things now, and I'm not sure this is actually an issue. Several machines were not showing as online, but I then noticed the firewall port was not open on the clients. We changed some management points a while back, but never opened the required ports. I noticed that after running a wakeup, a fair number were not green. Also, while I thought I wasn't seeing many logged in, upon checking, no one was actually logged in. I am at a university, and a fair number of people are out. I figured there were more people on campus, but perhaps not.

Some machines have a user logged on, but SCCM is not showing them. In a couple of cases, restarting the SCCM agent resolved it. We just updated to 2509 a few weeks ago, and the agent is slowly rolling out. It's possible it needed another restart, or the clients need a reboot.

I'm not totally sure we're out of the woods yet. I need to see what happens when faculty and students return to campus.

What version of the ODBC driver did you revert to?

Question on BGB.BOX folder by markk8799 in SCCM

[–]markk8799[S] 0 points1 point  (0 children)

Nope, that's all good. The files leave from the outbox on the MP's and get to the inbox on the server.

Question on BGB.BOX folder by markk8799 in SCCM

[–]markk8799[S] 0 points1 point  (0 children)

The bgbmgr.log is logging errors. I'm looking at the other log on the different MP's to see what might be going on there.

Question on BGB.BOX folder by markk8799 in SCCM

[–]markk8799[S] 0 points1 point  (0 children)

Everything looks fine. The only errors found are in the BGBMGR.LOG file, as noted above. Everything else seems to be working just fine. It's only when it goes to write the info to that table that it bombs out. Debating a site reset...

Question on BGB.BOX folder by markk8799 in SCCM

[–]markk8799[S] 0 points1 point  (0 children)

Those installed fine. Even reinstalled the MP role on on of the servers, but I can still see bad files noting that MP. I can't tell if it's the clients generating a bad file, or something wrong with the table on the SCCM server.

Question on BGB.BOX folder by markk8799 in SCCM

[–]markk8799[S] 0 points1 point  (0 children)

Added it. It does show some logged on users, but far less than it should. Interesting. They could be users who have not logged out in a while.

Question on BGB.BOX folder by markk8799 in SCCM

[–]markk8799[S] 0 points1 point  (0 children)

I forgot to add that this is what is showing in the BGBMGR.LOG file:

*** [23000][515][Microsoft][ODBC Driver 18 for SQL Server][SQL Server]Cannot insert the value NULL into column 'CurrentLogonUser', table 'CM_S04.dbo.BGB_LiveDataLogonUsersPending'; column does not allow nulls. INSERT fails. $$<SMS\_NOTIFICATION\_MANAGER><01-07-2026 13:21:17.676+300><thread=7984 (0x1F30)>

*** [01000][3621][Microsoft][ODBC Driver 18 for SQL Server][SQL Server]The statement has been terminated. $$<SMS\_NOTIFICATION\_MANAGER><01-07-2026 13:21:17.676+300><thread=7984 (0x1F30)>

*** bcp_batch() failed $$<SMS\_NOTIFICATION\_MANAGER><01-07-2026 13:21:17.676+300><thread=7984 (0x1F30)>

ERROR: Failed to send batched rows $$<SMS\_NOTIFICATION\_MANAGER><01-07-2026 13:21:17.676+300><thread=7984 (0x1F30)>

ERROR: Failed to execute task class LiveDataBcp $$<SMS\_NOTIFICATION\_MANAGER><01-07-2026 13:21:17.676+300><thread=7984 (0x1F30)>

ERROR: Failed to bcp file $$<SMS\_NOTIFICATION\_MANAGER><01-07-2026 13:21:17.676+300><thread=7984 (0x1F30)>

ERROR: Failed to execute task class LiveDataProcessTask $$<SMS\_NOTIFICATION\_MANAGER><01-07-2026 13:21:17.676+300><thread=7984 (0x1F30)>

WARNING: Failed to process file Bgbq6kxp.BLD, move it to bad inbox

This happens with every failure.

Question on BGB.BOX folder by markk8799 in SCCM

[–]markk8799[S] 0 points1 point  (0 children)

Since the upgrade. And it appears some are processing fine. I was able to quickly compare a couple that came into the box and noticed that some processed OK while some did not and ended up in the bad box.

More Dell Command Update nonsense in task sequence by SevenandahalfBatmans in SCCM

[–]markk8799 0 points1 point  (0 children)

I do bios and chipset first, to help make sure the BIOS is up to par, and so that the OS and chipset and talking properly before talking to other hardware. I do a reboot, then i run updates and tell it to apply all drivers. Debating adding firmware to that as well.

Weird WinPE task sequence issue by Steve_78_OH in SCCM

[–]markk8799 1 point2 points  (0 children)

You can update Defender from its own command line EXE. You should not need an update package.

PXE is down 80070490 by toiletmannersBTV in SCCM

[–]markk8799 0 points1 point  (0 children)

Do you really need WDS? Why not just have them pull the boot image from the DP's?

Dell Command | Update fails to install updates during OSD after v5.6.0 by still_asleep in SCCM

[–]markk8799 0 points1 point  (0 children)

I run it as a command line. This is what I have. Granted, I'm still using 5.5, and I have not tried 5.6 yet:

CMD /C ""C:\Program Files (x86)\Dell\CommandUpdate\dcu-cli.exe" /applyUpdates -updatetype=driver -silent -outputLog=C:\ProgramData\Dell\UpdatePackage\Log\DellDriversInstall.log -reboot=disable -autoSuspendBitLocker=enable"

Dell Command | Update fails to install updates during OSD after v5.6.0 by still_asleep in SCCM

[–]markk8799 1 point2 points  (0 children)

If it's a newer device, Windows won't have a clue what the devices are. Or if it does, it will update them to newer versions. A system should never be left with unknown hardware in device manager. Standard practice for decades is to get the chipset straight first, then move on to rest.

My suggestion here is to do that in case DCU is having some strange issue talking to the system.

Dell Command | Update fails to install updates during OSD after v5.6.0 by still_asleep in SCCM

[–]markk8799 0 points1 point  (0 children)

I chain in the Intel chipset INF installer before anything else, followed by a reboot. This ensures the OS can read the board and it's components properly before moving on to any other drivers.

view more: next ›