DS 7.1 Plug-in for Windows Package missing
Updated: 12 Jul 2010 | 9 comments
This issue has been solved. See solution.
I recently upgraded from CMS/SMS 7 to ITMS (formerly Total Management Suite) 7, which also has DS 7.1. After installation, when I go to the Deployment Plug-in installation policy, I get the message "No package could be found for the selected Agent installation policy". I have run a repair on DS 7.1 and even tried removing it and reinstalling it, but the Altiris Deployment Solution Complete Suite still shows up in SIM after 'successfully' uninstalling it.
Any ideas?
discussion Filed Under:
Comments
are you able to see other
are you able to see other packages like Deployment Site Server component policy or Deployment Automation Folder.
Thanks
~SysPanacea - Remedy for PC problems.
If a forum post solves your problem, please flag it as a solution. If you like an article or blog post vote for it.
The Automation Folder package
The Automation Folder package shows up, but the Site Server package does not...
I Also get this problem, its
I Also get this problem,
its similar to these KB's but they havn't worked for me
49518, 50805
I have a job loged with Symantec Support to see what they say.
I got this problem to last time i did an update via SIM, and the
AeXConfig.exe" /configureall was able to fix it...
Affter installin SP4 I get this error just for the "Software Management Solution Agent for Windows - Install" job,
After installing DS7.1 I also get it for all of the deployment agent installs (Deployment Automation Folder, Deployment Plug-in, Deployment Site Server Components )
I'll let you know once support get back to me.
After looking again, I'm also
After looking again, I'm also getting this with the Software Management Solution Agent jobs. I'll try the aexconfig.exe /configureall command...
That did not work. No
That did not work. No change.
I also tried the solutions in
I also tried the solutions in the above knowledgebase articles. No change.
Solution
I had to open a ticket with Symantec so they could remote in and fix the issue.
I had this same problem. I
I had this same problem. I fixed it by finding the conflicting GUIDs deleting the packages then using AEXCONFIG to reconfigure the solution. Like the article says you might have to do it multiple times.
Thanks
Thanks. I believe that is how they fixed it finally (I just forgot before updating the thread). In my case, I think there may have been an issue with Dell Client Manager also, so we had to get past that first.
Would you like to reply?
Login or Register to post your comment.