Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SEP11?

Status
Not open for further replies.

jkupski

MIS
Jul 29, 2003
698
US
Is anyone else planning a migration to SEP11 yet?

So far my testing shows that this is a significant improvement over SAV10 (smaller memory footprint, less CPU usage, more reliable communication with the client, etc) but I'm hoping to get some feedback from others before I deploy this network-wide.

Anyone have an opinion, yet?
 
Just attempted to install this week. My current version is 9.x

I initially installed on a DC (which also ran WSUS, file and print sharing). Installation went well, but after required reboot no one on the network could print or browse the domain.

After several hours of attempting to resolve problem I contacted Symantec support. Spent the next few hours going through a 'manual' uninstall. Lots of registry keys to delete.

Symantec tech support stated the following:
Do not install on a DC.
Do not install on a server running WSUS.
Do not install on a file or print server.
Do not install on an Exchange server.
Do not install on a server running other significant applications.

In other words (mine, not theirs) you should probably install on a separate server.

Here is a link that may assist you in your determination

 
Since you uninstalled, I'm guessing that you did not successfully troubleshoot the problem?

Was this JUST the server install, or did you install the client on the server as well? I ask this because, based on your description, it would appear that the SEP firewall was probably the culprit. That would be useful information, if it is the case--I actually have the firewall disabled in my test deployment (I was VERY hesitant about using it and decided against it. The XP SP2 firewall appears to be "good enough" for my purposes, anyway.)

I do not intend to deploy the SEP client on any of my servers because the chance of unintended consequences seems fairly high. I do plan my production deployment to be on one of my file servers. While I won't use a DC or an Exchange server in that role (too many things that could go wrong) I don't have a box that I can dedicate to being the SEP server. Maybe if I had 500+ clients this would be a different story, but with my low seat count (80) this seems to be too much of an investment.

Anyone else have anything to contribute?
 
Status
Not open for further replies.

Similar threads

Part and Inventory Search

Sponsor

Back
Top