Peter van der Woude

No that setting is only for updates that are superceded and not all older updates are superceded. Make sure that the view you are looking at is not filtering your updates, because you should be able to see all applicable updates.

If your device doesn;t have a IP address, then yes it's a driver issue. Make sure to add the network driver to the boot image (the driver has to match the operating system of the boot image).

Check if the file replication routes still exists.

I would create a simple application that just copies the executable to the location you want and you that location as your detection method.

Is it by any change happening on the first application after a reboot?

Sorry, I completely missed your reply. You're getting close. Your task sequence setup looks correct, but the folder part is wrong. The container that should be added as input should be a container holding your application collections. Based on that container the search for collection memberships of the user will be narowed from the start.

By defining a slow boundary you also need to specify the site system that it uses for content. That will be the location the client will look for content.

I use firefox only for this forum, so I can paste URLs here This is the link Garth is refering to: http://be.enhansoft.com/post/2013/10/03/Slow-Software-Inventory-Cycle-in-SCCM-2012.aspx

Haven't really noticed that behavior, but I always like to preach to keep everything (like deployments and packages) clean. So every month clean them up...

What do you mean exactly with unknown computers? The unknown computer objects (the two defaults), or just computer objects without client.

The nice thing is that the client will only download the files that it really needs. So are you sure that some updates don't require multiple folders/ files?

Is your software update point still having problems (as you mentioned a succesfull synchronization)?

That shouldn't matter unless your requirement(s) are not good enough. The thing you should keep in mind is that the first deployment type will be used of which the requirements are met.

I see a few MSI 1642 error codes, which means that the update is not applicable.. You might want to check if all the updates are for the version you are using.

Yes, you are making sense. By differentiating in the requirements you should be able to make one deployment type work for Korea and one for the rest.

Even though I like your screenshot, you do need to show some log files with information about this issue..

It should indeed also check if the client is installed and install it when it's not detected.

You have to start looking for a log file if you want more help on this... Based on the log file we can see what errors you are running into.

This is not really easy reading... What I did see in your WindowsUpdate log file is that it's scanning for updates and finding them. The errors in there are only about the self update of the client... Did you check all the abvious things, like if the targeted updates are available in packages?

Removing a Management Point because of problems with a boot image?!?! Those two things are not related at all. About your error message, your Management Point does a health check once every hour (I thought). Make sure your certificates are configured and you should be fine.

I would always be a bit carefull with deploying task sequences to, basically all, your clients. In most situation I have a specific collection for OS deployment and target them with available task sequences.

Can you provide the solution for your problem for future reference?

It shouldn't be a problem.

The thing with this system is that it's not as dynamic (at least how I read it) as you might think. You're using the task sequence to add the device to a collection (via a group), that's basically the same as directly installing the application during the task sequence. Either find a way to add your device (or user) already to a group before the task sequence starts, or just install the applications during the task sequence.

Did you add the dynamic RPC ports?