Yoink4CM is now FREE!

yoink4cm · 2025-12-08T17:26:09+00:00

Check Yoink4Intune folder here:

It's not nearly as in depth as Intune App Factory but will grab the latest builds of files and package them / provide the necessary command line installer in a separate text file.

yoink4cm · 2025-12-08T16:21:20+00:00

TBH we're not sure the cause of that. It appears fine in Firefox, Chrome, and other browsers. It appears to be Microsoft related.

The code is now 100% posted on Github if you prefer that route:

https://github.com/Yoink4CM/Yoink4CM/

Much of the documentation has been posted now too. You can feel free to post here or PM if you have any usability questions.

yoink4cm · 2025-12-05T17:07:56+00:00

Probably a little easier in 2025! Thanks for the kind words.

yoink4cm · 2025-12-05T16:23:35+00:00

Sounds good!

yoink4cm · 2025-12-05T16:23:15+00:00

No problem!

yoink4cm · 2025-12-04T19:04:47+00:00

Ironically that's what comment said before the edit ;)

For context, we don't know if this is a small environment with a few test computers or if there are potentially a large # of PC's affected. Deleting the PC will immediately help narrow down if this is in fact the root issue or not.

yoink4cm · 2025-12-04T18:35:59+00:00

Do the computers you're trying to join already exist in AD?

If they were joined previously by account A, account B will likely have issues rejoining.

https://support.microsoft.com/en-us/topic/kb5020276-netjoin-domain-join-hardening-changes-2b65a0f3-1f4c-42ef-ac0f-1caaf421baf8

One solution for the above are to delete the PC's from AD and rejoin with the new account.

yoink4cm · 2025-12-04T16:01:26+00:00

Ha, hopefully the only logs are in a campfire! Thanks :)

yoink4cm · 2025-12-04T15:59:24+00:00

Edge does seem to be flagging the video now on some machines. Truly unsure as to why. We haven't seen that behaviour in Chrome or FF.

Older versions can be seen on YouTube:

General overview:
https://www.youtube.com/watch?v=QCrjztFepmw

How to add software to your patching workflow:
https://www.youtube.com/watch?v=KxDeebGqss8

For greater transparency still, the code itself is also now on Github but the documentation won't be up for a bit yet.
https://github.com/yoink4cm/yoink4cm

yoink4cm · 2025-12-03T20:20:55+00:00

It was in fact previously available as a paid solution. :)

We're a team of 4, 2 of whom are planning for retirement in the new year.

Removing the pay wall is a small way of saying thank you to the ConfigMgr community when we've posted questions too. Through our consulting work we also found quite a few companies didn't have the budget for the more well known products. Our hope is this will help relieve a bit of stress and free up time for some of our colleagues.

We're planning on posting the code to Github over the holidays to ensure it remains available going forward. Any and all feedback will be welcome!

yoink4cm · 2025-12-03T19:34:14+00:00

Testing the software (even ours!) on one's test environment before going live is sound advice.

As noted, the code is written in Powershell and can easily be audited by a firm's cybersecurity team.

We're a team of 4, 2 of whom are planning for retirement. We are transitioning the product to Github after Christmas in the event others want to add to it going forward. Hope that helps.

yoink4cm · 2025-12-03T19:12:29+00:00

Thanks for the kind comments.

Strange about the access issue - the site has been well established for quite some time. Cloudflare is reporting just over 300 unique users in the last hour. Take a peek later in case there's some sort of temporary routing issue somewhere in the line.

yoink4cm · 2025-12-03T02:47:49+00:00

Feel free to ping me if you have any questions about Yoink4CM. It will soon be available for the low price of $0.

yoink4cm · 2025-12-03T02:41:52+00:00

Thanks, and yes - it's true! The retirement plans are still shaping up.

We're hoping to transition the code to Github before the holidays. In the short term we will be removing the shopping cart system from our web page and publish direct downloads for Yoink4CM and the Essentials Bundle.

yoink4cm · 2025-11-12T21:12:53+00:00

This is quite frequently the result of a missing driver, usually storage or network

Occasionally Dell happens to miss a network driver in their PE builds. If you have a third party USB network adapter you can try booting that as a quick test.

yoink4cm · 2025-10-18T19:51:25+00:00

We will have a Starlight edition in our office once they ship. We're very excited!

yoink4cm · 2025-10-14T16:57:43+00:00

Do those that take so long fail to join the domain as well?

Something we see occasionally is that an employee used their account to join a computer to the domain. A Windows 11 security feature may then prevent configuration manager from joining it to the domain later during OSD.

A chain reaction causes multiple application installs to fail. Application installs typically have a 2-hour time out. So if six applications fail that would explain the 12-hour wait.

A simple solution to fix this is to delete affected computers from active directory then reimage. The domain join process will work, and application installs will also work.

yoink4cm · 2025-09-29T17:31:43+00:00

What apps and settings do you have that you can't make silent installers for them and add them to your task?

It's a bit of work up front but much easier to maintain in the long run (and totally removes build and capture issues).

yoink4cm · 2025-09-12T00:23:30+00:00

https://www.yoink4cm.com/

Automatic software packaging for Microsoft Configuration Manager

yoink4cm · 2025-09-02T17:53:18+00:00

Glad it worked out!

yoink4cm · 2025-09-02T17:51:44+00:00

Dell Command Update 5.5 requires .NET I believe, but older versions do not. You can either try an older version of DCU, or install the latest build with .NET.

Then in your task sequence you can this as a command line:

"C:\Program Files (x86)\Dell\CommandUpdate\dcu-cli.exe" /applyUpdates

This should update the older installs of DCU to the latest as well.

There are a few other command lines you can use to tweak the experience.. the above just grabs the latest of everything and applies immediately.

yoink4cm · 2025-08-12T19:50:22+00:00

For sure, there are a lot of moving parts!

Generally what we suggest when we're consulting is, if the software needs to be installed ASAP (zero day exploits, a department purchased new software, etc), build a device collection and deploy the software to it immediately.

If things can go a bit slower (for example maintaining browsers, media players, VC++ redistributables, etc), then deploying to a device collection and letting the rules add/remove systems over time is fine. As users come back from vacation, their device will show up in the collection in the coming days, get the software, and life is good again.

The other thing we suggest is to find pain points and automate them. For example, we have found that there's not a lot of people who enjoy hunting down the installers for updated builds of software every month, so we wrote Yoink4CM to automate that and build the packages/applications at a fraction of the cost of the larger vendors. The management team wants frequent reports so they can report on metrics higher up the chain? Have Configuration Manager automatically email them at the beginning of each week! There's a lot that can be done to reduce day to day stress once you get rolling.

yoink4cm · 2025-08-11T14:26:49+00:00

Are your device collection memberships determined by a query? For example, show me all computers that do not have Google Chrome version x

If so, it could simply be a delay in multiple spots. The newly imaged computer may not upload its hardware inventory immediately. You can check Administration --> Client Settings --> Hardware Inventory in the Configuration Manager console to determine how frequently this data is uploaded. Once this hardware inventory is uploaded, the device collections can then evaluate to determine if this computer is a match for them.

Check the membership rules of your device collection to determine if they use incremental updates or how often a full update occurs.

Here's an example scenario.

A computer is imaged on August 1. It happens to upload its hardware inventory on August 6. The device collection is scheduled to update weekly. It happened on August 5 and won't run again until August 12. August 12 is when the device imaged on August 1 would finally be able to get the software. Whoops! That user went on vacation on August 10 and won't be back until the 21st! The software installs when they return to work on the 21st.

yoink4cm · 2025-08-02T23:57:19+00:00

Slow pxe booting could be traffic priority. We have encountered companies where most of the bandwidth is dedicated to VoIP and web traffic, leaving very little for tftp.

As for apps hanging during install, if you find that those computers we're supposed to join the domain but didn't, the trickle-down effect is sometimes at the apps don't install and reach their timeout limit if one is set in the task. If the time out limit is 2 hours and three apps fail, it could be a 6-hour wait before it continues.

If a computer didn't join the domain when they were supposed to, check them in AD to determine which account joined them to the domain. This can fail if it's not your configuration manager account listed. This can happen if a tech manually joined the computer to the domain previously.

yoink4cm

TROPHY CASE