Hi all,

I feel like I'm missing something obvious here, but I've been trying to find out where this information is stored.  Say I have package "PE123456" - is there an easy way to locate where this is stored within the ccmcache directory? 

I've come across some logs that occasionally, but not always, store this information (I believe cas.log lists it, but not consistently - I'm not sure of when it does/doesn't). I've been playing with the Roger Zander's smsclictr.automation.dll within Powershell to try to retrieve this information, but have had no luck so far (although I have managed to query and retrieve all the machine's advertisements, it does not return the path to the package themselves).

Assume I do not have access to the configmgr console for this task.

Thanks

 

For a package you can look at the execmgr.log file. (on the client)

C:\windows\ccm\logs

If it's a recent package then listing the cache folder by date modified can often give you a good shot at guessing the right folder, if a lot of packages were deployed at the same time then another option would be to search the cache folder for a specific file within the package.

• Edited by Richard.Knight 14 hours 16 minutes ago

Thanks.  Yeah, these are the things I typically do, but I just wish there was a more direct query or  programmatic way to grab the info. 

I don't have ConfigMgr next to me right now but the ccmcache object should tell you that.

Torsten is correct, the CacheInfo (https://msdn.microsoft.com/en-us/library/cc142966.aspx ) COM class enables you to retrieve all details about the cache. You can retrieve an instance of this class by class the GetCacheInfo method on the IUIResourceMgr interface of a UIResource object.

Here's some sample PowerShell code: http://cm12sdk.net/?p=1517

Why do you want this info though?

For a package you can look at the execmgr.log file. (on the client)

C:\windows\ccm\logs

If it's a recent package then listing the cache folder by date modified can often give you a good shot at guessing the right folder, if a lot of packages were deployed at the same time then another option would be to search the cache folder for a specific file within the package.

• Edited by Richard.Knight Thursday, April 23, 2015 5:31 PM

For a package you can look at the execmgr.log file. (on the client)

C:\windows\ccm\logs

If it's a recent package then listing the cache folder by date modified can often give you a good shot at guessing the right folder, if a lot of packages were deployed at the same time then another option would be to search the cache folder for a specific file within the package.

• Edited by Richard.Knight Thursday, April 23, 2015 5:31 PM

I just noticed this,

With the right click tools from Now Micro it's built in.

It's listed under client tools - client information.

You can also right click each and open explorer here. Pretty cool.

• Edited by Richard.Knight 16 hours 6 minutes ago

I just noticed this,

With the right click tools from Now Micro it's built in.

It's listed under client tools - client information.

You can also right click each and open explorer here. Pretty cool.

• Edited by Richard.Knight Friday, April 24, 2015 3:39 PM

I just noticed this,

With the right click tools from Now Micro it's built in.

It's listed under client tools - client information.

You can also right click each and open explorer here. Pretty cool.

• Edited by Richard.Knight Friday, April 24, 2015 3:39 PM
• Marked as answer by SeanRMiller 13 hours 53 minutes ago

I just noticed this,

With the right click tools from Now Micro it's built in.

It's listed under client tools - client information.

You can also right click each and open explorer here. Pretty cool.

• Edited by Richard.Knight Friday, April 24, 2015 3:39 PM
• Marked as answer by SeanRMiller Friday, May 01, 2015 5:50 PM

Thanks Jason.  The examples there are great.  As for why I need this?  Well we are transitioning from 2007, and occasionally I need to manually run installs, or check to see their caching status, etc during troubleshooting.  I also have a thought to create a tool that would show the caching (% downloaded) status of packages on remote machines. 

I appreciate the links, thanks.

Sean