Argument 'picture' must be a picture that can be used as a Icon
Hi
I'm trying to add an APP-V Application into SCCM and I get the following error message when it tries to read the manifest.xml.
Error : Argument 'picture' must be a picture that can be used as a Icon
Has anyone come across this at all and if so how did you get around it.
Jo
I'm trying to add an APP-V Application into SCCM and I get the following error message when it tries to read the manifest.xml.
Error : Argument 'picture' must be a picture that can be used as a Icon
Has anyone come across this at all and if so how did you get around it.
Jo
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
JMWebster
14 years ago
Posted by:
jnojr
13 years ago
Posted by:
Rheuvel
13 years ago
The sequencer extracts icons for every OSD from the source where the original shortcuts/executables point to. However, once in a while some formats are missing, especially with older (legacy/16-bit) apps. Not such a big deal.
There is 1 format however (I forgot which one it was) that makes SCCM go mad if it's missing.
Whenever I encouter this I found that the easiest solution was to use IcoFX (free tool) which has a button to generate all the missing icon formats that Windows might be using. So you're done with 1 click, save/replace the icon and you'll have a working SCCM import again.
There is 1 format however (I forgot which one it was) that makes SCCM go mad if it's missing.
Whenever I encouter this I found that the easiest solution was to use IcoFX (free tool) which has a button to generate all the missing icon formats that Windows might be using. So you're done with 1 click, save/replace the icon and you'll have a working SCCM import again.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.