Peter van der Woude

That's the execmgr.log... that means the client is already installed...

I would change the batchfile then to echo y| %~dp0usmtutils.exe /rd %systemdrive%\userstate

When you are doing a refresh you can use one Task Sequence for both actions and you don't need to make an association then.

Never heard of that software package When the package doesn't have any usefull unattended switches, then there is no other way then to (re-)package it...

I usually use a Build and Capture -Task Sequence to build our reference image (thick or thin) from the source files (Operating System Install Package).

If you are doing a migration to network location you need to have a State Migration Point and you need to create an association between the source and destination machine. When you are running a standard Task Sequence, then the default settings for the capture -part is to run in FullOS (if I'am not mistaken, don't have my testenvironment around).

I would start with looking at the ccm.log at the server.

When and how are you calling this batchfile? As the problem might just be that it can't find the usmtutils...

Did you check the distrmgr.log?

Then what is failling? What errors do you see? Also for small location you might whant to consider BranchCache, as it's now fully supported bij ConfigMgr 2012

It indeed became a long story... (I haven't tested this one) probably something like this should already give a collection with the members of the RootA and RootB collections: SELECT * FROM SMS_R_System WHERE SMS_R_System.ResourceId in (SELECT ResourceId FROM SMS_CM_RES_COLL_%ROOTA_ID%) OR ResourceId in (SELECT ResourceId FROM SMS_CM_RES_COLL_%ROOTB_ID%)

There is no BDP anymore... There is only one type of Distribution Point left.

Based on what infromation are you saying this? It would be really cool if it's possible, but all the releases until now still require an "Uninstall"-deployment.. even for App-V deployment types...

Nope, that setting doesn't exist anymore...

If you are advertising to computers you can just use a Task Sequence to install the software. Or just select Run another program first in the properties of application b.

What does your batchfile looks like then? I am doing exactly the same with a batchfile that contains a command like this: echo y| usmtutils.exe /rd <storedirectory>.

How? In a Task Sequence? If so, then what are the step, what is the error and when does it happen?

Did you refresh the Distribution Points?

What are the sub collections based on?

Did you look at the execmgr.log?

That's not normal behavior... If the setting was done initially then it should show up immediatly in the RAP when the advertisement shows up in the execmgr.log

How did you configure the advertisement?

That's defenitly gonna cause problems... For example, I think they are both trying to use the same records...

AFAIK it's normal behavior that you can't update a running application...

Why did you keep the same sitecode? That's the one thing they advise you to not reuse... Or did you restore the Site?