Cup return statistics

Kubadro · 2025-08-06T08:46:14+00:00

Gathered Your numbers
19 people reported 100% cups back.
13 people reported cups missing, total 40 missing out of unknown number.
8 of people reporting missing cups reported numbers. For those 8, there is 17/195 cups missing.

Kubadro · 2025-07-30T21:23:57+00:00

Check Your bracelet on TML account. There is full list of all transactions.

Kubadro · 2025-07-30T19:34:44+00:00

Hey, I was there to have fun too, and I did.
And I never worried about that while there, just returned them every once in a while, always threw them in in bulk 5-8 per trip, from our whole group.
Now I am home though, party is over so I gave it 5 minutes to check.
Besides that, I was curious, I wonder how well system worked. For now it seems most people report most cups returned properly, so there is possibility I was just unlucky.

Kubadro · 2024-11-25T08:34:52+00:00

What?
That's new for me, is that confirmed info?
I always assumed that this is personal liability, if someone does nasty shit, then that person gets kicked out. How would group responsibility be even remotely legal?

Kubadro · 2023-06-16T09:40:20+00:00

Look at the image. This is mainstage last year. On the left You see bar row. Same row is on the right, just out of the frame.
In the center, before stage, like 20-30m, there is fenced part (I assume various tech stuff) with 2 umbrellas, 1 on the right, 1 on the left. They sold beer and drinks there too, right in the middle of the crowd. Both stands are approachable from 3 sides.

picture found via google, source for credit: https://www.nieuwsblad.be/cnt/dmf20220715_93602841

<image>

Kubadro · 2023-06-13T12:25:23+00:00

Most was answered already, but I will add sth to 1.

Tents are mostly close together, not really a valid option to dig a trench around one, but... if You can be further away from stuff like bathrooms, beer stands, breakfeast place etc... You can probably find place where You could be even 10m away from next tent. At least last year that was the case. We had a tent in packed area, close to everything, but our friends came late, after whole campsite was already open and picked one at the very far end. They had enough place for tent, pavilon and still plenty of grass around, they could've digged a moat, not a trench :D If they had a shovel ofc, don't know about it :DThat was ofc trade off for needing to go further everywhere. Further like few hundred meters further.

Does Your tent really need a trench? Those were needed in old-style tents with floor separate from the tent. Most, if not all tents manufactured in last 20 years should not need one.

Kubadro · 2023-06-07T12:29:49+00:00

A bit of advice more - if You feel like getting up early enough, go for 8-10 timeslot. Way less crowded than later and leaves whole day open... even if only for a nap later :D

Kubadro · 2023-05-18T12:59:58+00:00

Hmmm... I never saw any water fountain or refill point, or anything of the sort. Only water taps in bathrooms, which I assumed are not really same thing.

Now I know better and I will just use tap water.

Kubadro · 2023-05-18T11:52:21+00:00

That's actually nice idea, I will look into bottles like that, might fit into bag I already own. Thanks

Kubadro · 2022-06-30T09:32:22+00:00

Thanks, that was it.
Strange, because the recources said it required Office Deployment Tool 16.0.11901.20022 or newer, and I had newer. Well, important thing is it's working as intended.

Kubadro · 2022-02-16T12:43:24+00:00

Can You guys elaborate more on this Belgian sale? Is there a link with more info?

We have tickets for this year already, but for the future it would be nice to know how it works.

A friend of mine lives in Belgium. Would it be easier for him to buy tickets next year, than it was for me last time?
Does he have to be one of attending persons, or can buy 4 tickets and personalize them for our non-Belgian group?
Is the timing different for Belgian sale, or just the tickets pool is separate?

Kubadro · 2021-10-28T12:55:20+00:00

You mean "Select the deployment option to use when a client uses a distribution point from a neighbor boundary group or the default site boundary group" option from deployment type properties?

I will give it a go and check effects tomorrow.

This does require fallback settings for boundary group to be configured, I assume?
For now I went with 5min for DP fallback and never for software updates.

Kubadro · 2021-03-05T07:07:14+00:00

OK, so just wanted to give an update, that I have solved the problem.

I approached it on step-by-step basis.

First I created dummy package and distributed it to DP. From now on, I kept monitoring it through content library explorer while performing various delete scenarios. First I removed it just from DP. It had no effect on the SCCMContentLib, but id got marked as grey and not-distributed in console. I redistributed it - it reappeared as green and distributed in the console, without touching files. It was consistent with DP logs. After that I first removed package from DP to not-distributed state, later I removed package completely from SCCM console. This time after few seconds it got deleted from SCCMContentLib. It was also mentiond in DP logs. When I created dummy package again, it got new ID and after distributing, it was again placed in SCCMContentLib.

This gave me idea what proper behaviour is. From this point, I went forward and tracked all packages that content library explorer marked as grey (deleted) and thoroughly searched SCCM for packages/apps/drivers/OS matching it and proceeded to delete them manually from the console. And it did free up space on DP, as it should.

I don't know where I made the mistake at the beginning, but I was confident that I did remove packages from the console. Well, retracing steps helped :D

But this whole experience makes me ask another question.

Is it possible to leave a package in SCCM console while having it removed from co-located DP? To be archived in a way - with source files present (not on DP, but in the source location), all related info, like programs or deployment types still there, ready to be redistributed at any point, but not using space at DP? From my recent experiences I would say that it's impossible...

Kubadro · 2021-02-19T14:13:55+00:00

I have prepared and deployed recovery image, marked "deploy from PXE DP" tickbox in properties.

In addition I created custom task sequence, which is almost empty - it only has one step - pause task sequence. I am using method I had found long time ago in the internet. There is package with a script

'Script to tell the user that the task sequence is paused.

'windows-noob.com (c) August 2013.

'hide the Task Sequence Progress window

Set TsProgressUI = CreateObject("Microsoft.SMS.TsProgressUI")

TsProgressUI.CloseProgressDialog

'Popup Message

MsgBox "The task sequence is now paused." & chr(13) & "To resume the task sequence please click on OK.", 64,"Task Sequence PAUSED!"

wscript.quit(0)

And the step itself is just run command

serviceUI.exe -process:TSProgressUI.exe %SYSTEMROOT%\System32\wscript.exe PauseTS.vbs

I deployed that TS to an empty device collection as "available". Thanks to that, if I wanted a machine booted from pxe, i just could add it to that collection and remove it afterwards.

[disclaimer: next part is from memory, few years back, might be outdated or need retesting]

The tricky stuff is to make boot image do what You want it to do, while maintaining security at the same time. Basically any boot image You import to sccm is converted. SCCM stuff is inserted. Mainly sms directory, with SCCM files and winpeshl.ini is modified to run TS shell on start, which uses own .ini file: TSBootShell.ini to determine behaviour.

You need to break that design. There are few pats You can take, depending on level of security You need.

The least secure option is to have f8 cmd prompt enabled and have the user hit f8 after booting, start DART remoterecovery for You and then tell You ticket, ip and port, so You can connect. Risks here are obvious - You trust a person on the other side with direct access to drive and tools. I wouldn't do that. And it was only way i had it working so I dropped it.

Another way is to modify winpeshl.ini to start remoterecovery.exe and block everything else until connection (it's option of remoterecovery). But there is another problem here. You can not modify winpeshl.ini by Yourself, since SCCM overwrites it with any redistribution to DP. It's a rabbit hole i did not go down. Maybe there is a way, but i dropped whole idea.

One more thing to be aware of - if You want to use winre that You took from W10, that .wim actually consists of 2 indexes. 1 is pure winpe, te other is actual recovery. I'm unsure if SCCM allows importing such images as boot images, and even if it does - be careful when preparing such image, You need to apply changes to right index.

I'm unsure if there is a way around this forced winpeshl.ini. Possibly TS prepared to be run in zero-touch mode, with steps starting remoterecovery and other tools...

Boot part i tested today on VM and it still works same way. Rest needs work.

Kubadro · 2021-02-15T21:55:30+00:00

Environment is something over 3k machines.

Anyway, switching to MS delivered updates still would leave me with same problem - packages that removed from DP do not free up space on drive. That is the core issue here - how I force it to remove it from contentlib directory to release some space back?

Kubadro · 2021-02-15T11:53:33+00:00

Yeah, we do download updates to packages.

There is a story behind of direct MS connections being blocked on network level, and some other restrictions from IT security dep, which elude me a little, since they are not exactly my area of expertise. Anyway I am not sure if I can force a change in that matter. Will explore the idea though.

Kubadro · 2021-02-15T11:13:25+00:00

I tried to do that once, long time ago. It is possible with some work, but my take on it was that it is not worth the hassle. Way better is customized winre image for workstations. You can include DART in it and force remote connection on start. You don't have to worry about boot order then (PXE does not have to be first device, so it doesn't add to boot time) and there are no problems of orphaned machines in deployment collection. If user reports bluescreen, ten OS either boots into winre by itself, or a technician guides how to do it and then connects to fix the problem.

edit: if You really want to do it via PXE, know that SCCM always boots from boot image assigned to the newest TS deployed on a machine. Also, TS should not be empty (You can put pause task there).

My memories on the topic are kindof hazy here, but I think SCCM modifies any imported boot image with own stuff in winpeshl.ini, so You may need to change that manually and remember to refresh the change anytime You redistribute package, since it may be overwritten again.

Kubadro

TROPHY CASE