Console not reporting compliance, "Software Center" on client shows applications installed.

April 24, 2013, 2:20 pm

≫ Next: SCCM 2012: failed to connect to distribution point

≪ Previous: Application Catalog - Application installation not started

SCM 2012 sp1 running on 2008R2

I've deployed several MSI "Applications"

If I look at the client machines and open the "Software Center" it shows that the applications are installed and I verify this both by looking in "programs and features" and by runnning the application. But the console still shows as unknown. I don't think it's the client not getting policy because the installs occured.

1.) Why wouldn't the console update?

I've tried running the Summarizations again but nothing changes.

2.) What exactly does running a summarization do?

↧

SCCM 2012: failed to connect to distribution point

June 28, 2012, 12:53 am

≫ Next: Certain packages not downloading to new distribution point

≪ Previous: Console not reporting compliance, "Software Center" on client shows applications installed.

Hi folks,

I have an intermittent issue and can't figure out the reason so far.

I have a primary server and multiple distribution points. The primary does not have a DP configured. When I deploy a new distribution point, I have the following messages:

Distribution Manager failed to connect to the distribution point. Check your network and firewall settings.

and

Distribution Manager failed to find or create the defined share or volume on distribution point.

DistMgr.log shows the following:

CWmi::Connect() failed to connect to \\AMB-SCCM-E.domain.name\root\CIMv2. Error = 0x800706BA

STATMSG: ID=2391 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=BBD-SCCM-E.domain.name SITE=IDC PID=2120 TID=3376 GMTDATE=do jun 28 07:24:17.463 2012 ISTR0="["Display=\\AMB-SCCM-E.domain.name\"]MSWNET:["SMS_SITE=IDC"]\\AMB-SCCM-E.domain.name\" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=404 AVAL0="["Display=\\AMB-SCCM-E.domain.name\"]MSWNET:["SMS_SITE=IDC"]\\AMB-SCCM-E.domain.name\"

ERROR DPConnection::ConnectWMI() - Failed to connect to AMB-SCCM-E.domain.name. error = 0x800706ba

Failed to find a valid drive on the distribution point ["Display=\\AMB-SCCM-E.domain.name\"]MSWNET:["SMS_SITE=IDC"]\\AMB-SCCM-E.domain.name\

Cannot find or create the package share.

Error occurred. Performing error cleanup prior to returning.

However, after a while (couple of hours), it looks like everything is distributed on the DP. But this message keeps on coming back during the course of the day and every time a new DP is deployed.

I checked permissions, IIS, WMI, but I can't find out the cause of this behavior. I have events about WMI (id 5605) but I can connect to the WMI workspace (root\MicrosoftIISv2) with no issues.

Can anyone shed some light on this please? It would be greatly appreciated.

Cheers,

Safdar.

↧

Certain packages not downloading to new distribution point

April 24, 2013, 11:46 am

≫ Next: Invalid executable file AdbeArCleaner.exe

≪ Previous: SCCM 2012: failed to connect to distribution point

I have setup a new distribution point and have started to deploy software packages, driver packages and windows image files to it. Most packages deployed without an issue to this new DP, but certain packages are not getting deployed correct. The status is stuck in "pending" when I look at the console. I have found the following error in the DataTransferService.log on the new DP, which appears to be telling me why the package is failing to copy but I'm not sure how to resolve the issue. I did review WebDav settings and I have reviewed the instructions listed here http://technet.microsoft.com/en-us/library/cc431377.aspx (even though they are for SCCM 2007). I don't see anything in the applicationhost.config file that would be restricting the transfer of this file. I have also confirmed that my NTFS permissions on the source share include full access for the computer account of the new DP.

Here is a snippet from the log:

DTSJob {9F845677-CD64-4B3B-8753-FE2764F7F079} in state 'DownloadingData'.	DataTransferService	4/24/2013 11:43:24 AM	4428 (0x114C)
CDTSJob::JobError: DTS Job ID='{9F845677-CD64-4B3B-8753-FE2764F7F079}' BITS Job ID='{5FA55DC2-C3C0-41BD-8226-05D172FD974C}' ErrorCode=0x80190194	DataTransferService	4/24/2013 11:43:31 AM	2352 (0x0930)
CDTSJob::JobError: DTS Job ID='{9F845677-CD64-4B3B-8753-FE2764F7F079}' URL='http://SCCM2.domain.local:80/SMS_DP_SMSPKG$/SR10002C' ProtType=1	DataTransferService	4/24/2013 11:43:31 AM	2352 (0x0930)
DTS job {9F845677-CD64-4B3B-8753-FE2764F7F079} BITS job {5FA55DC2-C3C0-41BD-8226-05D172FD974C} failed to download source file http://SCCM2.domain.local:80/SMS_DP_SMSPKG$/SR10002C/sccm?/ArcGIS_Mobile_10.1/ArcGISMobile/Documentation/install_guides/ArcGIS_Mobile/include/l10n/main-rsrc.js3/swfaddress.js to destination C:\SMS_DP$\SR10002C\SR10002C.44\ArcGIS_Mobile_10.1\ArcGISMobile\Documentation\install_guides\ArcGIS_Mobile\include\l10n\main-rsrc.js3\swfaddress.js with error 0x80190194	DataTransferService	4/24/2013 11:43:31 AM	2352 (0x0930)
DTSJob {9F845677-CD64-4B3B-8753-FE2764F7F079} in state 'Error'.	DataTransferService	4/24/2013 11:43:31 AM	2352 (0x0930)
DTSJob {9F845677-CD64-4B3B-8753-FE2764F7F079} in state 'NotifiedComplete'.	DataTransferService	4/24/2013 11:43:31 AM	4428 (0x114C)
DTS job {9F845677-CD64-4B3B-8753-FE2764F7F079} has completed:
	Status : ERROR (0x80070002),
	Start time : 04/24/2013 11:43:23,
	Completion time : 04/24/2013 11:43:31,
	Elapsed time : 8 seconds	DataTransferService	4/24/2013 11:43:31 AM	4428 (0x114C)

↧

Invalid executable file AdbeArCleaner.exe

April 24, 2013, 3:05 pm

≫ Next: How to work with dependencies that superseed

≪ Previous: Certain packages not downloading to new distribution point

I have created an application to run the Adobe reader Cleanup tool, and have set it as a dependency for the Adobe Reader install application. when I run the Reader install application the Cleanup tool does not run. The AppEnforce.log file shows the following information:

+++ Starting Install enforcement for App DT "Adobe Reader uninstaller for Virtualized Apps" ApplicationDeliveryType - ScopeId_B4003F77-CAD1-44A1-B035-0EEBD86CA67F/DeploymentType_bd1d9e99-31c5-4703-8694-f68af835908d, Revision - 6, ContentPath - , Execution Context - System	AppEnforce	4/24/2013 9:47:17 AM	11064 (0x2B38)
    The content path is not specified for DeploymentType ScopeId_B4003F77-CAD1-44A1-B035-0EEBD86CA67F/DeploymentType_bd1d9e99-31c5-4703-8694-f68af835908d.  Content is assumed to be locally available.	AppEnforce	4/24/2013 9:47:17 AM	11064 (0x2B38)
    A user is logged on to the system.	AppEnforce	4/24/2013 9:47:17 AM	11064 (0x2B38)+++ Application not discovered with script detection. [AppDT Id: ScopeId_B4003F77-CAD1-44A1-B035-0EEBD86CA67F/DeploymentType_bd1d9e99-31c5-4703-8694-f68af835908d, Revision: 6]	AppEnforce	4/24/2013 9:47:29 AM	11064 (0x2B38)
    Performing detection of app deployment type Adobe Reader uninstaller for Virtualized Apps(ScopeId_B4003F77-CAD1-44A1-B035-0EEBD86CA67F/DeploymentType_bd1d9e99-31c5-4703-8694-f68af835908d, revision 6) for system.	AppEnforce	4/24/2013 9:47:17 AM	11064 (0x2B38)
    App enforcement environment: 
	Context: Machine
	Command line: "AdbeArCleaner.exe" /Silent /product=1
	Allow user interaction: No
	UI mode: 1
	User token: null
	Session Id: 4294967295
	Content path: 
	Working directory: 	AppEnforce	4/24/2013 9:47:29 AM	11064 (0x2B38)
    Prepared working directory: C:\Windows\system32	AppEnforce	4/24/2013 9:47:29 AM	11064 (0x2B38)
Invalid executable file AdbeArCleaner.exe	AppEnforce	4/24/2013 9:47:29 AM	11064 (0x2B38)
ScriptHandler::EnforceApp failed (0x87d01106).	AppEnforce	4/24/2013 9:47:29 AM	11064 (0x2B38)
AppProvider::EnforceApp - Failed to invoke EnforceApp on Application handler(0x87d01106).	AppEnforce	4/24/2013 9:47:29 AM	11064 (0x2B38)
CommenceEnforcement failed with error 0x87d01106.	AppEnforce	4/24/2013 9:47:29 AM	11064 (0x2B38)
Method CommenceEnforcement failed with error code 87D01106	AppEnforce	4/24/2013 9:47:29 AM	11064 (0x2B38)++++++ Failed to enforce app. Error 0x87d01106. ++++++	AppEnforce	4/24/2013 9:47:29 AM	11064 (0x2B38)
Method EnforceApp failed with error 87D01106	AppDiscovery	4/24/2013 9:47:29 AM	11064 (0x2B38)
CAppProvider::ExecMethodAsync failed. Error 87d01106	AppDiscovery	4/24/2013 9:47:29 AM	11064 (0x2B38)

From what I can tell, it appears that a file can not be found. The Deployment Status states "Failed to verify the executable file is valid or to construct the associated command line". I have run the "AdbeArcleaner.exe /Silent /product:1" command on a test computer using the System account and it works fine.

Does anyone know if there should be something placed in the Content path, or what might be causing this error?

↧

How to work with dependencies that superseed

April 23, 2013, 5:09 am

≫ Next: What is different between available and required deployments to machines?

≪ Previous: Invalid executable file AdbeArCleaner.exe

We have an application that has a prerequirement to install another application first. We point the dependency to the right application/deployment type.

Now the application in the dependency gets a new version. We superseed that application.

Now, if we look at the dependency, it is still pointing to the old version. Do we have to fix that manually by pointing to the newer dependency?

I hope not, because we have a lot of applications like this one.

Regards, Bob

↧

What is different between available and required deployments to machines?

April 24, 2013, 2:36 pm

≫ Next: Problems in Application management

≪ Previous: How to work with dependencies that superseed

Ok, I am looking at a strange problem and to me it makes no sense at this point. From how I understand things if I do a required or available deployment of a MSI to a machine where the deployment type is set to install for system the installation environment should be the same. What we are noticing with one application is that it fails when it is installed as an available application but not as a required application to a device. Does anyone have some potential ideas as to why the two scenarios would matter to a MSI?

www.bighatgroup.com

↧

Problems in Application management

April 25, 2013, 12:01 am

≫ Next: SCCM 2012 SP1 App-V not showing up / installing

≪ Previous: What is different between available and required deployments to machines?

I had two problems in Application management:

1, After a application is deployed, any renaming won't take effect on the client side. The client will always see the first (old) name unless I delete the whole Application and recreate a new one with new (2nd) name. I tried removing deployment but no luck either.

2, Application retirement. This feature is really confusing. After refer to this link (http://social.technet.microsoft.com/Forums/en-US/configmanagerapps/thread/c9a19cdc-7733-450c-9ef5-55cb2981117d/) and my tests, my understanding is the application is inoperable after been retired, which means no new deployment types and no new deployments but before the existing deployment is removed, users can install it as long as they want to.

Any help is appreciated.

Regards,

Sean

↧

SCCM 2012 SP1 App-V not showing up / installing

April 25, 2013, 3:02 am

≫ Next: applcations don't install via OSD but install fine through normal deployment

≪ Previous: Problems in Application management

Hi Guys.

I have a SCCM 2012 environment which was installed and software deployment tested and all good. I have upgraded to SP1 so that i can start to look at App-V. Again software deployment and all other tasks within SCCM are working fine. I have setup the App-V client and sent this out via SCCM to my test workstation and all good.

I have setup a App-V app but this never gets to the client. Again a normal software install arrives fine and installs.

Anything you think i should check or have missed?

↧

applcations don't install via OSD but install fine through normal deployment

April 25, 2013, 4:07 am

≫ Next: DistMgr flooded with DMD files for deleted package

≪ Previous: SCCM 2012 SP1 App-V not showing up / installing

I am using SCCM 2012 SP1.

Dear all, everything was fine untill I added requirements in applications to be installed only on system which are part of specific OU. The applications in which I added the requirements now don't get installed during OSD. These applications install just fine after OSD if I install them on specific collections user or system. Am I missing something?

And also, I have set "allow application to be installed via task sequence" option. I actually was installing applications during osd just fine. But the applications are now not installed after adding the requirement.

I see the following in appintenteval.log -

the Applicability is always set to NotApplicable.

Evaluating Application policies for Machine AppIntentEval4/25/2013 10:35:21 AM

2564 (0x0A04)ScopeId_6622B5DC-1C2D-4C47-A08C-5B6D8E18F38E/DeploymentType_7f8e9d67-d81c-41a8-baaa-fb022ea93ca9/21 :- Current State = NotInstalled, Applicability = NotApplicable, ResolvedState = None, ConfigureState = NotNeeded, Title = 7-Zip 9.20 (x64 edition)