Endpoint Protection 11.0.5 managed package won't install on Windows 7 Pro x64
I don't understand why I am being directed here, but Symantec Support has assured me this is the forum to use in order to get the developers to fix an installation bug. The problem is discussed in Case 320-233-740, but a brief overview follows.
I have created a managed installation package for SEP 11.0.5 by using the export feature in SEP manger. However, when I run setup.exe on a Win7 Pro x64 workstation, the install stops and rolls back. Based on some internet research, I tried installing LiveUpdate off the SEP cd, and then running the managed package install; sure enough, this method works. Symantec support found some internal documents indicating a problem with Windows Scripting Host, but no solution.
I verified the behavior on 3 Win7 computers, all built fresh from the Microsoft dvd with current updates installed. I also verified that SEP installs fine (as an unmanaged client) from the cd without needing to install LU first.
Rich
Comments
This would actually be more
This would actually be more appropriate for suggesting ideas for enhancements to the products.
Though if there is aproblem and development is aware the more customers calling in to report it will only to increase the priorty of defect/problem be fixed.
Thanks, Rich - by posting
Thanks, Rich - by posting here you let other users comment on this bug so we can see how prevalent it is, which helps the development team assign priorities when fixing it.
concerning whether to post here or not...
As I said originally, I did not think this was an appropriate place to post either, Symantec support sent me here. They sent me a link, so I know I went where they expected me to. After I saw this site, I went back to support and questioned their reasoning, but they assured me it was the right place.
Frankly, I see it as a cop out, because support is going to 'close' the ticket even though my problem has not been resolved. Yet this site does not assign tickets nor offer accountability since it is not a support site, so I have no reason to expect any response. So in the end, have I been 'supported'? If Symantec employees, such as yourself, see this post and agree it isn't the logical place for it, I hope someone will take the initiative to inform support to stop telling customers to use the enhancement forums for technical support.
The support system should have a mechanism for the support staff to make the developers aware how many calls are being placed for a particular issue without polluting the enhancement forums. Additionally, tickets that are pending future fixes should be not closed with the same status as an issue that has actually been resolved.
Rich
Posting suggestions/closing cases
Symantec used to have a no-visibility enhancement request system...you went to a web page, you entered what you'd like to see, and the email was sent to somewhere in development. People didn't have any way to know if their idea was unique, or if every other administrator out there wanted the same changes. There was also (as I understood it), little to no communication...people wouldn't know if their idea was even being considered.
Symantec decided to implement the Ideas board as a way to help deal with these issues. People can see what others are suggesting and add their voice (or their dissention) to ideas. Development can see "hey, this issue has 350 votes...let's look at what it would take to implement it". It helps to improve visibility for issues.
Some issues aren't "issues" per se...that is, the code of the SEP software isn't broken or defective...it is working exactly as designed. However, the design itself could use changing. In that case, if a person calls into support, the support person would direct the end user to the Ideas page here where he or she can post the requested change. In this case, the ticket would be closed as, again, there's nothing broken in the software.
However, if the software is actually broken, the ticket should remain open until a solution has been delivered (cases can also be closed if the customer isn't responding...but even that takes time, it's not like "well, customer didn't answer my one call back, close the case"). If you feel that your ticket was closed before the issue was resolved, call back into support and speak with the technican about it. If needs be, speak with their supervisor. However, if the issue has been determined to be working as designed, you really do need to come here and post the suggestion(s) that you'd like to see changed.
We really do value your feedback and suggestions.
There has been a thread
There has been a thread opened about this issue in the support area
https://www-secure.symantec.com/connect/forums/win...
Some one else with
Some one else with information on this in the ideas section has posted the following.
https://www-secure.symantec.com/connect/idea/insta...
Fix soon...
Symantec called me back to confirm the bug has been acknowledged and a fix is currently being built. They're estimating a new release of Enpoint Protection by the first week in December which will resolve this.
Rich
Would you like to reply?
Login or Register to post your comment.