<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments for Allen Stalker</title>
	<atom:link href="http://astalkerdesign.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://astalkerdesign.com</link>
	<description>Self proclaimed computer guru, IT and Virtulazation enthusiast.</description>
	<lastBuildDate>Mon, 14 May 2012 20:20:44 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>Comment on Symantec Endpoint Protection &#8212; Mass Uninstall by Allen Paul</title>
		<link>http://astalkerdesign.com/2012/02/symantec-endpoint-protection-mass-uninstall/comment-page-1/#comment-213</link>
		<dc:creator>Allen Paul</dc:creator>
		<pubDate>Mon, 14 May 2012 20:20:44 +0000</pubDate>
		<guid isPermaLink="false">http://astalkerdesign.com/?p=84#comment-213</guid>
		<description>Awesome! Thanks for all of this feedback. Really great of you to reach out to me. I truly do appreciate it. This looks like a much easier method compared to the MSI commands.</description>
		<content:encoded><![CDATA[<p>Awesome! Thanks for all of this feedback. Really great of you to reach out to me. I truly do appreciate it. This looks like a much easier method compared to the MSI commands.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on About Me by Raymond Keske</title>
		<link>http://astalkerdesign.com/about/comment-page-1/#comment-206</link>
		<dc:creator>Raymond Keske</dc:creator>
		<pubDate>Tue, 01 May 2012 20:15:17 +0000</pubDate>
		<guid isPermaLink="false">http://astalkerdesign.com/?page_id=2#comment-206</guid>
		<description>This is the right blog for anyone who wants to find out about this topic. You realize so much its almost hard to argue with you (not that I actually would want…HaHa). You definitely put a new spin on a topic thats been written about for years. Great stuff, just great!</description>
		<content:encoded><![CDATA[<p>This is the right blog for anyone who wants to find out about this topic. You realize so much its almost hard to argue with you (not that I actually would want…HaHa). You definitely put a new spin on a topic thats been written about for years. Great stuff, just great!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Symantec Endpoint Protection &#8212; Mass Uninstall by Paul Murgatroyd</title>
		<link>http://astalkerdesign.com/2012/02/symantec-endpoint-protection-mass-uninstall/comment-page-1/#comment-135</link>
		<dc:creator>Paul Murgatroyd</dc:creator>
		<pubDate>Fri, 24 Feb 2012 14:07:24 +0000</pubDate>
		<guid isPermaLink="false">http://astalkerdesign.com/?p=84#comment-135</guid>
		<description>Hi Allen, great blog you have here!  I work for the Symantec Endpoint Protection Product Management team and wanted to reach out to you with respect to your experiences.

Firstly, with respect to the removal of the product, the MSI commands will work well, but obviously they require admin rights in order to execute, which you may or may not have at the time of execution.  You may or may not have seen SEPprep on our DVD - while it is primarily used for competitive uninstall, it can also be used to remove SEP too.

1. Copy the SEP folder from the SEP 12.1 DVD onto your system.

2. Delete all files from this folder (including subfolders) except:
   a. setAid.ini
   b. Setup.ini
   c. smcinst.exe
   d. SyLink.xml

3. Copy the SEPprep.exe file (from the SEP 12.1 DVD) into this folder and rename it to “Setup.exe”.

4. Create a file called SEPprep.ini from the entry below.  So then you should have six files in this folder:
   a. SEPprep.ini
   b. setAid.ini
   c. Setup.exe
   d. Setup.ini
   e. smcinst.exe
   f. SyLink.xml

5. Edit the Setup.ini file and change the line that says “ProductVersion=” to some larger value.  Example: ProductVersion=12.1.9000.9000
   a. Note only the first three numbers are used, so if you only change the last number it will not allow you to add it into SEPM.

6. Import this package into SEPM and call it something like “Package to remove SEP 12.1 clients”.
7. Assign this package to a group in SEPM and all clients in that group will uninstall the SEP 12.1 client.


-------------SEPprep.ini----------------
[Settings]
ShowGUI=N
ShowMessageBox=N
MessageBoxText=Prepairing your system for Symantec Endpoint Protection 12.1.  During this process other antivirus products will be removed.\n\nIf you are prompted please fully remove these products.
AutoRunAfterUILoads=N
AskBeforeRemoval=N
SilentMSIInstaller=Y
RemoveSymantec=Y
CheckDiskSpace=N
ResumeAfterReboot=N
EnableLogging=N
LogPath=
RunBeforeRemoval=
RunAfterRemoval=

[UninstallPaths]
SOFTWARE\McAfee\ePolicy Orchestrator\Application Plugins

[ProductNames]
;Programs that must be removed
Symantec Endpoint Protection

-------------SEPprep.ini----------------

If you dont have a DVD handy, you can download SEPprep from here too: 
http://www.symantec.com/docs/TECH148513

I hope that helps.  If you have further details on some of the issues you have seen prior to removal (such as case numbers, etc.), please let me know via email as we would like to follow these up further.

Many thanks

Paul Murgatroyd
Principal Product Manager, Symantec Endpoint Protection</description>
		<content:encoded><![CDATA[<p>Hi Allen, great blog you have here!  I work for the Symantec Endpoint Protection Product Management team and wanted to reach out to you with respect to your experiences.</p>
<p>Firstly, with respect to the removal of the product, the MSI commands will work well, but obviously they require admin rights in order to execute, which you may or may not have at the time of execution.  You may or may not have seen SEPprep on our DVD &#8211; while it is primarily used for competitive uninstall, it can also be used to remove SEP too.</p>
<p>1. Copy the SEP folder from the SEP 12.1 DVD onto your system.</p>
<p>2. Delete all files from this folder (including subfolders) except:<br />
   a. setAid.ini<br />
   b. Setup.ini<br />
   c. smcinst.exe<br />
   d. SyLink.xml</p>
<p>3. Copy the SEPprep.exe file (from the SEP 12.1 DVD) into this folder and rename it to “Setup.exe”.</p>
<p>4. Create a file called SEPprep.ini from the entry below.  So then you should have six files in this folder:<br />
   a. SEPprep.ini<br />
   b. setAid.ini<br />
   c. Setup.exe<br />
   d. Setup.ini<br />
   e. smcinst.exe<br />
   f. SyLink.xml</p>
<p>5. Edit the Setup.ini file and change the line that says “ProductVersion=” to some larger value.  Example: ProductVersion=12.1.9000.9000<br />
   a. Note only the first three numbers are used, so if you only change the last number it will not allow you to add it into SEPM.</p>
<p>6. Import this package into SEPM and call it something like “Package to remove SEP 12.1 clients”.<br />
7. Assign this package to a group in SEPM and all clients in that group will uninstall the SEP 12.1 client.</p>
<p>&#8212;&#8212;&#8212;&#8212;-SEPprep.ini&#8212;&#8212;&#8212;&#8212;&#8212;-<br />
[Settings]<br />
ShowGUI=N<br />
ShowMessageBox=N<br />
MessageBoxText=Prepairing your system for Symantec Endpoint Protection 12.1.  During this process other antivirus products will be removed.\n\nIf you are prompted please fully remove these products.<br />
AutoRunAfterUILoads=N<br />
AskBeforeRemoval=N<br />
SilentMSIInstaller=Y<br />
RemoveSymantec=Y<br />
CheckDiskSpace=N<br />
ResumeAfterReboot=N<br />
EnableLogging=N<br />
LogPath=<br />
RunBeforeRemoval=<br />
RunAfterRemoval=</p>
<p>[UninstallPaths]<br />
SOFTWARE\McAfee\ePolicy Orchestrator\Application Plugins</p>
<p>[ProductNames]<br />
;Programs that must be removed<br />
Symantec Endpoint Protection</p>
<p>&#8212;&#8212;&#8212;&#8212;-SEPprep.ini&#8212;&#8212;&#8212;&#8212;&#8212;-</p>
<p>If you dont have a DVD handy, you can download SEPprep from here too:<br />
<a href="http://www.symantec.com/docs/TECH148513" rel="nofollow">http://www.symantec.com/docs/TECH148513</a></p>
<p>I hope that helps.  If you have further details on some of the issues you have seen prior to removal (such as case numbers, etc.), please let me know via email as we would like to follow these up further.</p>
<p>Many thanks</p>
<p>Paul Murgatroyd<br />
Principal Product Manager, Symantec Endpoint Protection</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Moving VM&#8217;s from VMWare Server to ESXi/vCenter Pt. 1 by le tableau</title>
		<link>http://astalkerdesign.com/2011/08/moving-vms-from-vmware-server-to-esxivcenter-pt-1/comment-page-1/#comment-106</link>
		<dc:creator>le tableau</dc:creator>
		<pubDate>Tue, 06 Dec 2011 15:51:55 +0000</pubDate>
		<guid isPermaLink="false">http://astalkerdesign.com/?p=51#comment-106</guid>
		<description>hi, that&#039;s a pleasant spot. There is few mistakes but the principal is here.</description>
		<content:encoded><![CDATA[<p>hi, that&#8217;s a pleasant spot. There is few mistakes but the principal is here.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

