I have had this message pop up for one of my old clients I still do support for and I am still the Admin for on their 365 system.
Microsoft enforcing MFA in 365 in 12 days message Cloud Computing & SaaS. save me countless hours of work removing your failed product from the limitless oceans of computer systems which are infected or otherwise crippled and in need of remediation and protection. though most of us have long since stopped holding our breath. Many of which, when confronted and presented with incentives to return, vehemently refuse. Altruism at its finest.Īnd there are probably those at Symantec who are still shaking their heads with astonished looks on their little faces, confused because they still can't figure out why so many of their customers have left and continue to seek alternative options to their software "offerings". And while it might be possible to create a MSI and answer file for the utility, how many of your customers are savy enough or HAVE THE TIME? How assuming of you to think that they all staff that level of talent or don't mind finishing up half-developed products for no benefit other than to have the privilege of using Symantec client removal products to learn the art of making. can't hurt to spell it out one more time). MSI (obviously, but given the length of time this issue has lingered I wonder if it's just that Symantec doesn't understand the problem. yes I'm looking at you Symantec, Cleanwipe.exe is NOT a. Now, once more, for the cheap seats all the way in the back. So, in this common scenario, unless you use CLEANWIPE.EXE to remove your SEP client I'm sorry to say, you are BONED. Password protected SEP packages cannot be removed in this manner no matter what they say to add to the registry Admins, users (and even you) cannot alter or remove the package using msiexec without this password if one was configured on the package when it was deployed. and then ONLY if you are fortunate enough to NOT have included a password with your installed SEP packages. the command looks something like msiexec /X /switches blah blah blah. However, that's only after you have queried the remote registry of each and every computer it will run on to ensure that the GUID used on each is identical (you'll need a msiexec removal lilne for each version found). To be fair, there are command strings that can be executed to remove the product via command line using msiexec in some instances. and what I mean by that is to date, they still have no tool available to their customers that can be scripted or managed via GPO (.msi) to remove SEP. 
I hate to necro a thread this old, but surprisingly it is still relevant considering Symantec still has yet to provide its customer base with a viable solution despite the cacophony of cries for one.
0 kommentar(er)
