Configmgr 2012 Available After date in Software Center changes to 4/10/1998

Update: This post is updated after the Configmgr 2012 R2 CU1 hotfix released as this fix will resolve the subject line Issue.

I recently had interesting issue with Configmgr 2012 SP1 CU3 client.Many Optional applications in Software Center changes to 4/10/1998 for  ‘Available After

This issue was posted on several forums but there is no solution yet why is this happening.

After working with Microsoft,found the root cause but no permanent solution ,instead we have temporary workaround to fix this issue.

Issue:

Applications appear as Old date(1998) in Software Center for ‘Available After’ which is unclear to end users about the application availability and they tend to ignore it.

Take a look at the picture below,for Microsoft office project professional 2007 application,the available after date shows as 4/10/1998.Why is this ? and for test project professional application,it show correct date .why ?

image

This is not application issue nor client issue nor Server issue then where is the problem,

Basic Troubleshooting:

The first thing that comes in mind is,check the Scheduled date for the Deployment ,what date it is specified ? You are wrong.The scheduled date is correct but it will not display here.

2nd is to look at wmi ,application information is stored in “root\ccm\clientsdk” namespace.Startdate for the specific application show wrong Date.

3rd to look is,run the policy spy and check the properties for the problem package using the application assignment ID,you will see correct date which was scheduled in application deployment but why is this showing as 1998 ?

4th to look at all the logs(expecially policyagent.log,DCMagent.log,ccmstatestore.log) but they don't reveal much information.

After doing lot of troubleshooting on the client,found the issue is causing because of Task Sequence .Confused ?

Root Cause:

Applications which are deployed to clients are also part of Task Sequence as referenced packages ,the two deployments causing the clients to go back to old Date.

This problem occurs for applications that are made available through task sequences.

More explanation:

Assume Task sequence(TS1) which is used to deploy OS is targeted to Collection(coll1) as Optional (not mandatory).This task sequence has many actions for applications For Ex: MS project professional (app1)

So the clients which are part of Collection coll1 (considering the cm12 client is installed) will have information about App1 which used in the Task sequence(ts1).

I also created deployment for App1 and targeted to ms office project collection(coll2) with available option(not Required).

So far,No confusions.One TS to coll1 and one application(App1) to coll2.

after the deployment is done ,if you look at the software center,if it will show wrong date(1998),then client is not synced correctly and this is happening because of 2 deployments, one from Task Sequence and other from Application Deployment.

To Confirm this,I tested by creating few deployments for the applications used in Task sequence and deployed to test collection(for the clients who are part of TS),i see the same behavior.

 Temporary Workaround: Do not use the same application which is referenced in Task sequence for the application deployment.Recreate the application used in Task sequence and deploy to clients that will show the right information for ‘available after’.

Solution: Microsoft released Configmgr R2 CU1 hotfix that resolves several issues among which,this is one of the fix.

After you deploy the HotFix(Cu1) onto R2 Clients,you will have re-deploy the Task sequences (delete the existing TS deployments and Create again) to collection to purge the old entries in client wmi else you will see these entries persist in software center.

Leave a Reply