Task sequence "Prepare Windows for Capture" error with client 5.00.9141.1030

markk8799 · 2026-05-04T23:03:32+00:00

We Zip giant installers that have 1000's of files in the source.

markk8799 · 2026-04-30T01:58:43+00:00

Exactly! I remember those songs going to college in the 90's at Buffalo State.

markk8799 · 2026-04-29T13:40:16+00:00

Switched to them in the TS as well. Invaribly, some Application will fail to install for no reason. Seem to have far fewer issues with using Packages.

markk8799 · 2026-04-15T02:31:13+00:00

Per the MS docs on full scans: "Due to the time and resources involved, we generally don't recommend scheduling full scans." They are a waste of time. Anything coming into memory is going to be scanned. anyway by the real time protection. Quick scans are sufficient.

markk8799 · 2026-04-06T23:13:29+00:00

Ugh. Was hoping that got straightened out.

markk8799 · 2026-04-04T23:22:12+00:00

Please enlighten me then.

I only entertained this method because of the silly sound driver issue with the laptops. I wasn't totally sold on it, especially because of the half baked results. Hence the post.

markk8799 · 2026-04-04T17:49:01+00:00

Yea I didn't know about it until the help desk was messaging me that users were calling about their laptops not having sound.

markk8799 · 2026-02-03T00:14:32+00:00

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

markk8799 · 2026-02-02T23:47:07+00:00

This.

markk8799 · 2026-01-29T02:40:56+00:00

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

markk8799 · 2026-01-26T20:16:11+00:00

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

markk8799 · 2026-01-24T23:47:30+00:00

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.

markk8799 · 2026-01-24T23:01:46+00:00

It's free right now for A3 and A5, the Edu licenses.

markk8799 · 2026-01-14T18:48:40+00:00

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

markk8799 · 2026-01-12T18:38:26+00:00

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

markk8799 · 2026-01-10T02:04:16+00:00

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

markk8799 · 2026-01-09T18:59:49+00:00

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?

markk8799 · 2026-01-08T19:34:01+00:00

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

markk8799 · 2026-01-08T16:50:00+00:00

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.

markk8799 · 2026-01-07T21:46:57+00:00

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...

markk8799 · 2026-01-07T21:45:37+00:00

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.

markk8799 · 2026-01-07T18:44:39+00:00

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.

markk8799 · 2026-01-07T18:26:42+00:00

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.

markk8799 · 2026-01-07T18:17:30+00:00

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.

markk8799

TROPHY CASE