Hi there

We have a problem with the Install Dynamic Applications failing on a majority of computers - not all, some install applications exactly as expected but these are in the minority - during build (SCCM 2012 SP1 CU3 and Windows 7 SP1).

The actual 'Install Dynamic Applications' task step is not to blame, it is the task step which immediately proceeds it, 'Convert list to 2 digits' i.e. where the COALESCEAPPS variable is applied to the list of associated application groups. This step should be passing a list of applications to install to the 'Install Dynamic Application' task step, but the ZTI Coalesce log shows no such list is created, so there's nothing to install. Even so, I don't even think that THIS step is actually to blame either, I suspect the problem lies elsewhere.

We have a UDI setup which involves using a custom web service. Basically, a task step runs near the start of the task sequence, which passes the computer name and MAC address to the web service. The web service then queries AD to get a list of application groups associated with that computer name/MAC address. The web service then passes this data to the MDT Database. The Gather task step runs (customsettings.ini) which gathers this list of application groups in the MDT Database and passes them to the task sequence. That's a very high level description of the process.

I know some might say, well go and ask the guy who wrote the custom web service to fix the issue, but that's not an option right now.

Besides, my interest in this question is around the MDT Database itself; namely, is the MDT Database clearing out computer names and MAC address at the end of the task sequence?

To get to the point, what steps do I need to take to clear out the MDT Database, to make sure any duplicates or rogue entries are purged?

I'm thinking of a process that could be run once a week, which gives us a fresh MDT Database with no computer names, MAC address, application groups, etc - what do I need to do to achieve this?

Does the MDT offer a scheduled task which will clean out the database or is there a powershell script which could be run on a schedule to thoroughly clear out the MDT Database?

I just want to rule out the custom web service not clearing out the MDT Database as expected as the problem (a task step runs near the end which is supposed to achieve this but I'm not convinced).

The fact that the Install Dynamic Applications task step works perfectly on a minority of computers suggests the overall process is functional but is being impacted at a particular stage - it may well be that the MDT Database is not the problem, I just want to rule it out by ensuring it is not clogged up by rogue data which is is turn causing the Install Dynamic Applications step to fail.

Best regards

John

 namely, is the MDT Database clearing out computer names and MAC address at the end of the task sequence?

No. Adding or removing things from the database is a "manual" task.

The design ("The web service then queries AD to get a list of application groups associated with that computer name/MAC address. The web service then passes this data to the MDT Database".The Gather task step runs (customsettings.ini) which gathers this list of application groups in the MDT Database and passes them to the task sequence) seems complicated? What adding it to the database if you want to clean all records on a regular basis? You could just populate variables directly.
Why do you think that clearing the database would help? Have you already examined any logs to get an idea where it is failing exactly? You can also add a step to the task sequence that logs all task sequence variables so that you can see what's set.