Video Screencast Help

Endpoint Small Business Protection for Windows 2000 SP4 client - not compatible?

Created: 08 Sep 2012 • Updated: 10 Sep 2012 | 13 comments
This issue has been solved. See solution.

Hello,

I recently purchased Symantec Endpoint Protection Small Business Edition 12, however appraently despite the claims that Windows Server 2000 SP4 (Advanced Server) is compatible here as a client in System Requirements:

http://www.symantec.com/business/support/index?pag...

it is not really compatible, as I get this error when installing: "This version of Windows Server 2000 OS is not compaitible.. the latest version that is supported is 12.0.1001.95." I have attached a screengrab.

Does anyone have advice? There is no distinction in 12.1 vs 12.0 on the purchasing page, which is misleading.

Symantec, please provide a way for me to download this version or another that *is* compatible, as this is what was advertised, and I have already purchased this product with multiple licenses for my employer.

(I have tried to open a case, but the page does not work and results in a jboss error: http://www.symantec.com/business/support/index?pag...)

Comments 13 CommentsJump to latest comment

Ashish-Sharma's picture

hi,

I think Currently you have use Small Business Editions SEP 12.1

Kindly check system requirement

System Requirements for Symantec Endpoint Protection, Enterprise and Small Business Editions, and Network Access Control 12.1

http://www.symantec.com/business/support/index?page=content&id=TECH163806

you can download for https://fileconnect.symantec.com/ using your licence no.

How to download Symantec Endpoint Protection (SEP) from File Connect website
http://www.symantec.com/docs/TECH95270

Thanks In Advance

Ashish Sharma

 

 

bluerosebuddha's picture

Thank you, Ashish!

The download page you gave me is indeed the same product I already have. But I still need the download for SMB Endpoint Protection for 12.0.x.x for Windows server 2000 SP4. Where can I get that then?

Thanks!

Marie

 

Ashish-Sharma's picture

hi Marie,

All product all Available below Url https://fileconnect.symantec.com/ .

you can choose your product

If you will not find that product you may contect Customer Support Assistance.

http://www.symantec.com/support/assistance_care.jsp

Thanks In Advance

Ashish Sharma

 

 

Mithun Sanghavi's picture

Hello,

Could you please verify, if you are running Symantec Endpoint Protection version 12.0 OR Symantec Endpoint Protection version 12.1.

You could check the version by Logging in to Symantec Protection Center (Symantec Endpoint Protection Manager) and clicking on "About" on the right hand top corner.

Both these versions have lot of difference.

The Article which you have provided is in reference to the Symantec Endpoint Protection version 12.0, whereas Ashish is providing you the Article for Symantec Endpoint Protection version 12.1.

The Screenshot you have provided does not reveal the version, and this error only appears if you are running the Symantec Endpoint Protection version 12.1.

Incase, if you are running the SEP 12.0.22.192 (RTM version), then I would suggest you to migrate to the Latest version of SEP 12.0.1001 (RU1)

Hope that helps!!

Mithun Sanghavi
Senior Consultant
MIM | MCSA | MCTS | STS | SSE | SSE+ | ITIL v3

Don't forget to mark your thread as 'SOLVED' with the answer that best helped you.

Chetan Savade's picture

Hi,

If you are using Small Business Edition (SBE) 12.1 then you will be having SBE 12.0 RU1 package.

This package is available at the following location

Go to the drive where SBE 12.1 console in installed.

Navigate to SEPM\Inetpub\ClientPackages, check the folder by name 'full', you will find 'setaid.ini' file.

Make sure you will see the following details in the setaid.ini file.

ShortName=sesmAvClient32en_12_0_MR1
DisplayName=Symantec Endpoint Protection Win32 12.0.1001.95 (English)

It's a SEP old version setup & would be compatible with windows 2000 SP4.

On my test machine folder is by name 1b42208a6dc8ff67b9a65370351a0457.

Copy this setup & install on the machine as an unmanaged client.

After successful install, replace Sylink.xml & make it managed SEP client.

I have just tested it on my test server & working great.

SBE 12.1 can manage SBE 12.0 RU1 client.

Screenshot is attached to the reference.

 

Check till date SEP releases:

http://bit.ly/m0vOJp

I hope these steps will help you to resolve the issue.

Chetan Savade
Sr Technical Support Engineer, Endpoint Security
Enterprise Technical Support
CCNA | CCNP | MCSE | SCTS |

Don't forget to mark your thread as 'SOLVED' with the answer that best helps you.<

bluerosebuddha's picture

Wow! Thanks Chetan, that is exactly what I was looking for. (For info purposes, I do have Symantec Endpoint Protecion version 12.1.1101.) 

I appreciate the help guys!! This should be documented somewhere. I will mark your response as a Solution.

:-)

Thanks,

Marie

SOLUTION
Chetan Savade's picture

Hi Marie,

Thanks for an update. We have an article which talks about SEP Enterprise Edition.

https://www-secure.symantec.com/connect/articles/h...

Now I am creating an article for Small Business Edition, will ping you the link once it's published.

Chetan Savade
Sr Technical Support Engineer, Endpoint Security
Enterprise Technical Support
CCNA | CCNP | MCSE | SCTS |

Don't forget to mark your thread as 'SOLVED' with the answer that best helps you.<

Chetan Savade's picture

Hi,

Please go through public kb, you can export it through client deployment wizard (CDW) as well.

How to create packages for Legacy systems from the Symantec Endpoint Protection Manager (SEPM) v.12.1 SBE?

http://www.symantec.com/docs/TECH185247

Chetan Savade
Sr Technical Support Engineer, Endpoint Security
Enterprise Technical Support
CCNA | CCNP | MCSE | SCTS |

Don't forget to mark your thread as 'SOLVED' with the answer that best helps you.<

sandra.g's picture

You accidentally marked your own answer as the solution smiley

sandra

Symantec, Senior Information Developer
Enterprise Security, Mobility, and Management - Endpoint Protection

Don't forget to mark your thread as 'solved' with the answer that best helps you!

John Cooperfield's picture

bluerosebuddha,

Please mark the reply that helped you as the solution, - Chetan's for example.

Thanks

bluerosebuddha's picture

Great, thanks! One more quick question, you said replace the Sylink.xml to make it a managed client - with what? With the Sylink.xml file that's on the Symantec Manager machine? Or do I edit it?

Regards,

Marie

Mithun Sanghavi's picture

Hello,

Check this Article:

How to change the sylink.xml file in Symantec Endpoint Protection (SEP) 12.1

http://www.symantec.com/docs/TECH157585

Hope that helps!!

Mithun Sanghavi
Senior Consultant
MIM | MCSA | MCTS | STS | SSE | SSE+ | ITIL v3

Don't forget to mark your thread as 'SOLVED' with the answer that best helped you.

Chetan Savade's picture

Hi,

There are two ways to do it.

Replace sylink.xml in the folder itself where we have an old package.(folder by name 'full')

OR

You need to export Sylink.xml file from Symantec Endpoint Protection Manager.

Select the group where you wish to report that respective client, right click on the group and select export communication settings.

Save the file as a 'Sylink.xml' only

After successful export replace it on the SEP client machine.

Now client should list under respective group.

How to change the sylink.xml file in Symantec Endpoint Protection (SEP) 12.1

http://www.symantec.com/docs/TECH157585

Chetan Savade
Sr Technical Support Engineer, Endpoint Security
Enterprise Technical Support
CCNA | CCNP | MCSE | SCTS |

Don't forget to mark your thread as 'SOLVED' with the answer that best helps you.<