Peter van der Woude

A share on DFS should be no problem.

Erhm.. you want to use a SQL query to add a machine to a collection? You should do that through the console, or WMI. Never directly on the database.

Did you look at the collection evaluation log files? Also, do you have the reindexing enabled in the maintenance tasks?

The version gets updated with the next heartbeat discovery.

It simply triggers the next command after successfully starting the first command. If you want it to wait until it's finished you've got to use some start / wait construction.

Yes, that will only work when a task sequence environment exists, because that specific object can only be created in a task sequence.

In most cases it's related to the SMSTSMPListRequestTimeout variable. See for more information: https://technet.microsoft.com/en-us/library/hh273375.aspx

Not really, you can open a command prompt and run it from there and see the error messages.

If it's migrated, its specifically specified during the migration. For more information see: https://technet.microsoft.com/en-us/library/hh825093.aspx

AFAIK something like that doesn't exist.

Running the cleanup wizard should not harm your software update point.

See the correct replies here: https://social.technet.microsoft.com/Forums/en-US/a83bea72-3c25-44c2-bd0a-44be9a9a4502/task-sequence-hangs-when-running-a-powershell-script?forum=configmanagersdk

I would do something like that via a Status Filter Rule. That saves a lot of problems with permissions and task sequences.

What does the script do and a what time in the task sequence are you using it?

You mean setting the firewall exceptions? If so, use GPO's.

What's in the config file that you specify in the command line?

That's probably the easiest, as it's the easiest to simply reinstall the client to assign it to a different site.

Never had the need to remove a service pack of Office, but I can imagine that it's not as straight forward as a normal update. A quick search gave the tool below, have you looked at that: https://technet.microsoft.com/en-us/library/dd723551%28v=office.14%29.aspx?f=255&MSPPError=-2147217396

You're correct. You've can use the PATCH parameter to update the client during the task sequence.

Well, that matches with the log files you've posted...

Yes, but what products did you select? You need to make the filter in the ADR more specific to prevent it from going over a 1000 updates.

Yeah, I'm seeing similar behavior with customers, which is usually "easy" to explain. Especially the inexpensive low-end devices have very-very-very slow "disks" (if you can even call it a disk), which usually cause the extreme slow write actions. Sometimes a newer-better driver might help a little tiny bit, but in general you just get what you paid for... Based on the deployment time of the desktops and laptops I would assume that there is little to nothing to be tuned about your task sequence.

To add-on, make sure that Deploy the boot image from the PXE-enabled distribution point is selected in the Data Source tab of the boot image.

I can't match the log files with the screenshot. Based on the log file I would say that it already stops before starting the task sequence...

This is too little information, please find the smsts.log file and post provide it for more details.