Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MMAgent - updated product ID #11

Open
janegilring opened this issue Jun 27, 2016 · 4 comments
Open

MMAgent - updated product ID #11

janegilring opened this issue Jun 27, 2016 · 4 comments

Comments

@janegilring
Copy link

janegilring commented Jun 27, 2016

It seems like the MM Agent has gotten a new product ID. At least the one I'm using got a different ID than the one in the DSC Resource:
8A7F2C51-4C7D-4BFD-9014-91D11F24AAE2

The error when applying a DSC configuration using the resource:
PowerShell DSC resource MSFT_PackageResource failed to execute Set-TargetResource functionality with error message: Package from C:\Windows\Temp\MMASetup-AM
D64.exe was installed, but the specified ProductId and/or Name does not match package details

@janegilring
Copy link
Author

janegilring commented Jun 27, 2016

Turns out there are multiple versions in play here:

Version: 7.2.10375.0
ID: E854571C-3C01-4128-99B8-52512F44E5E9

Version: 8.0.10879.0
ID: 8A7F2C51-4C7D-4BFD-9014-91D11F24AAE2

Version: Unknown (the one in cMMAgentInstall)
ID: E854571C-3C01-4128-99B8-52512F44E5E9

@rchaganti
Copy link
Owner

I am pushing an update very soon! The existing composite resource will always have a problem when they change the product ID. I will create a separate resource for this.

@janegilring
Copy link
Author

Maybe consider to add the product ID as a parameter (with a default value)?
Or accept a -Version parameter and have a mapping table between versions and product IDs which will make the resource automatically use the correct ID for the specified version?
Although it might be a challenge to maintain, as I`m not sure how often the product ID is changed.

@rchaganti
Copy link
Owner

Certainly. But, I am thinking of avoiding Package resource completely.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants