Hi there

Hoping someone can shed some light on an issue I am struggling to find indepth information about:

1) Application revisions and Deployment Type revisions.

The revision number of an Application is easy to view in the SCCM 2012 console, in the summary area. 

The revision number of a Deployment Type only seems to be visible in certain CCM logs when an application is being deployed.

Based on what I've read, any changes to an Application or its Deployment Type which is updated to the Distribution Points results in the revision number of the APPLICATION being incremented.

That being so, where does the Deployment Type revision get updated? What activity results in the Deployment Type revision being incremented?

The Application revision and Deployment revision on the same app I have looked at are different - how does this come to be?

Do both revisions start out the same number, 1, then if a change ONLY to the Application is made, the Application revision is incremented, and likewise if the Deployment Type is changed ONLY does that objects revision get incremented? That doesn't sound plausible.

I have tried to find an indepth explanation of the differences between Application and Deployment Type revision numbers but haven't been able to do so.

If anyone can link to a detailed explanation I'd appreciate it.

2) We had an OSD outage some time ago, whereby one application in a task sequence failed to install and crashed the task sequence. After looking into it, the task sequence was trying to download an older Application revision i.e. not the latest revision. Why would this happen? There are various sites which cover this issue out there but although all are helpful they frankly admit they know what happens and how to fix it, but not WHY it happens. Why would a task sequence try to download an older revision of an application and not automatically try to download the latest revision? Is it the case that any changes to applications which are referenced in a task sequence should result in the application being removed and re-added to the task sequence?

Right now I'm more interested in a detailed explanation of the differences between Application revisions and Deployment Type revisions - if anyone can shed some light I'd appreciate it.

Thanks

John

Glasgow

The Application revision and Deployment revision on the same app I have looked at are different - how does this come to be?

Can you share a screenshot of shis?

Did you check the information in the database?

when you make changes to either application or deployment type,configmgr will creates a new revision of the application  which you can see from the console ,Revision number.so client always look for this revision during the application discovery .I doubt if there is any revision number for deployment type which client uses to perform the detection method in application deployment. If you look at appdiscovery.log on the client,it always says,revision for the application but not the deployment type revision. take a look at steve's blog explaining about application model http://blogs.msdn.com/b/steverac/archive/2012/07/08/configmgr-2012-application-model-internals-part-i.aspx might help you to understand about internal of it.

Eswar

Thanks for replying. I have previously read through those blogs but didn't find the information I was hoping to find.

Daniel

If you run the SCCM 2012 console in debug mode, you get access to the Tools area.

Within the Tools area if you select an application you will see futher information about that application. You will see an an item named CI_UniqueID, which shows:

ScopeID_*UniqueIdentifier*/Application_*UniqueIdentifier*/Revision number

This Revision number is the same Application revision number viewed in the SCCM console in the Summary area.

If you now look at the Deployment Type for the SAME application, again you see a CI_UniqueID object, which will have this information:

ScopeID_*UniqueIdentifier*/DeploymentType_*UniqueIdentifier*/Revision number

You can see the Deployment Type also has a Revision number, and in the application I have been looking at, these are different: The Application revision is 24, whereas the Deployment Type revision is 21.

If you look at the AppEnforce.log after an application has been installed, you will see the Deployment Type revision number being referenced.

So I'm still in the same place I was when I logged the post, I can't find out what action/s causes the Deployment Type revision number to increment, nor can I find any information on what causes a task sequence, for example, to target an older application revision number (and so fail to download the application).

It may be the case that Application and Deployment Type revisions are meant to be the same, though I'm not too sure about that and I still don't know what causes Deployment Type revisions to be incremented.

I'll keep looking to see if I can find a good explanation, thanks for replying.

John

Glasgow

• Edited by John T. Chance 8 minutes ago Spelling correction

Eswar

Thanks for replying. I have previously read through those blogs but didn't find the information I was hoping to find.

Daniel

If you run the SCCM 2012 console in debug mode, you get access to the Tools area.

Within the Tools area if you select an application you will see futher information about that application. You will see an an item named CI_UniqueID, which shows:

ScopeID_*UniqueIdentifier*/Application_*UniqueIdentifier*/Revision number

This Revision number is the same Application revision number viewed in the SCCM console in the Summary area.

If you now look at the Deployment Type for the SAME application, again you see a CI_UniqueID object, which will have this information:

ScopeID_*UniqueIdentifier*/DeploymentType_*UniqueIdentifier*/Revision number

You can see the Deployment Type also has a Revision number, and in the application I have been looking at, these are different: The Application revision is 24, whereas the Deployment Type revision is 21.

If you look at the AppEnforce.log after an application has been installed, you will see the Deployment Type revision number being referenced.

So I'm still in the same place I was when I logged the post, I can't find out what action/s causes the Deployment Type revision number to increment, nor can I find any information on what causes a task sequence, for example, to target an older application revision number (and so fail to download the application).

It may be the case that Application and Deployment Type revisions are meant to be the same, though I'm not too sure about that and I still don't know what causes Deployment Type revisions to be incremented.

I'll keep looking to see if I can find a good explanation, thanks for replying.

John

Glasgow

• Edited by John T. Chance 10 minutes ago Spelling correction

Eswar

Thanks for replying. I have previously read through those blogs but didn't find the information I was hoping to find.

Daniel

If you run the SCCM 2012 console in debug mode, you get access to the Tools area.

Within the Tools area if you select an application you will see futher information about that application. You will see an an item named CI_UniqueID, which shows:

ScopeID_*UniqueIdentifier*/Application_*UniqueIdentifier*/Revision number

This Revision number is the same Application revision number viewed in the SCCM console in the Summary area.

If you now look at the Deployment Type for the SAME application, again you see a CI_UniqueID object, which will have this information:

ScopeID_*UniqueIdentifier*/DeploymentType_*UniqueIdentifier*/Revision number

You can see the Deployment Type also has a Revision number, and in the application I have been looking at, these are different: The Application revision is 24, whereas the Deployment Type revision is 21.

If you look at the AppEnforce.log after an application has been installed, you will see the Deployment Type revision number being referenced.

So I'm still in the same place I was when I logged the post, I can't find out what action/s causes the Deployment Type revision number to increment, nor can I find any information on what causes a task sequence, for example, to target an older application revision number (and so fail to download the application).

It may be the case that Application and Deployment Type revisions are meant to be the same, though I'm not too sure about that and I still don't know what causes Deployment Type revisions to be incremented.

I'll keep looking to see if I can find a good explanation, thanks for replying.

John

Glasgow

• Edited by John T. Chance Tuesday, May 26, 2015 7:38 AM Spelling correction

John,

I am also experiencing the issue where applications fail during OSD because the client is looking for an old revision. The workaround is to delete any application install steps in your task sequence, close/save the task sequence, and then add the steps back. This seems to work for most people, but it doesn't always work for me. I suspect that sometimes I might perform the workaround before all the CI changes have propagated through the database or whatever it does in the background.

Have you noticed if when an application install fails, is it looking for the revision number that matches the deployment type revision number instead of the application revision number? I am going to do some tests to see if the revisions match or if they seem random.