At this time running the Symantec Endpoint Manager (SEPM) is considered an alternative configuration and will be handled with "Best Effort Support".
Customers have reported problems with Symantec AntiVirus Server and Symantec Endpoint Protection Manager with VMware VMotion ESX server. These problems may or may not be related to the presence of VMware VMotion or the presence of the Symantec Endpoint Protection Manager.
…
Symantec is investigating each support case and will update Symantec products where necessary.
SRE, VMware Virtualization, vSphere, vCD, ESX, Configuration Management, Microsoft AD, Security, Networking, and about anything else..
Tuesday, November 25, 2008
Can't Log into 2008 Server with network account
The error is: The User Profile Service failed the logon. User profile cannot be loaded.
I had added this 2008 Server to the domain, and I can still login with a local admin, but not my domain account. The fix was to disable UAC, then it worked.
I had added this 2008 Server to the domain, and I can still login with a local admin, but not my domain account. The fix was to disable UAC, then it worked.
Wednesday, November 19, 2008
Symantec doesn't support SAV OR SEP on VM's..awesome
Question/Issue: Is ESX server Vmotion supported with SAV and SEP?
Symptoms: There have been many issues reported a few examples are, Client communication problems Symantec Endpoint Protection Manager (SEPM) communication issues Content update failures Policy update failures Client data does not get entered in to the database Replication failures
Solution:Symantec does not support ESX server Vmotion at this time.
http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2008101607465248?Open&seg=ent
Symptoms: There have been many issues reported a few examples are, Client communication problems Symantec Endpoint Protection Manager (SEPM) communication issues Content update failures Policy update failures Client data does not get entered in to the database Replication failures
Solution:Symantec does not support ESX server Vmotion at this time.
http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2008101607465248?Open&seg=ent
Tuesday, November 18, 2008
Some Good Alternative Apps
Instead of notepad or wordpad, try Textpad or Ultraedit
http://www.textpad.com/download/index.html
http://www.ultraedit.com/downloads/ultraedit_download.html
Instead of Adobe Reader, try Foxit
http://www.foxitsoftware.com/pdf/rd_intro.php
Instead of Adobe Elements, try Primo PDF
http://www.primopdf.com/
http://www.textpad.com/download/index.html
http://www.ultraedit.com/downloads/ultraedit_download.html
Instead of Adobe Reader, try Foxit
http://www.foxitsoftware.com/pdf/rd_intro.php
Instead of Adobe Elements, try Primo PDF
http://www.primopdf.com/
Friday, November 14, 2008
Exchange 2007 Can't Receive Large(er) Attachments = 20mb
Ok, this was a really hard one to solve. I tried everything you can think of to get this to work. I found a great manual online, good work to the author here:
http://exchangepedia.com/blog/2007/09/exchange-server-2007-setting-message_10.html
I also found some good troubleshooting steps here as well:
http://forums.msexchange.org/m_1800436085/mpage_1/key_/tm.htm#1800436085
However, that still didn't help me, this was an upgrade from 2003 exchange, I modifed the ADSIEDIT stuff, the send/receive connectors, the transport connectors, the global settings, the mailbox settings, etc..etc... I still got the #550 5.3.4 SMTPSEND.OverAdvertisedSize; message size exceeds fixed maximum size ## error.
Now exchange 2007 out of the box has a 10mb email size limit. I could send 13mb attachments, just not 15+. This is odd for several reasons, but let me explain the eventual fix. I was trying to "double" the size to 20mb from 10mb, so I went from 10240 to 20480 in the "size" settings.
We enabled verbose logging on the Edge SMTP machine, it showed the 18mb test email I was sending was actually 25xxx in size, so my 18mb attachment, the "SMTP" size of the email was 25 megs-ish. We increased the sizes up to 30000 and blamo..20mb email attachments now work. I tried sending from gmail and another exchange server, both significantly increased the size of these emails with the 18mb attachment. I'm not sure why, but that is a problem for another day.
http://exchangepedia.com/blog/2007/09/exchange-server-2007-setting-message_10.html
I also found some good troubleshooting steps here as well:
http://forums.msexchange.org/m_1800436085/mpage_1/key_/tm.htm#1800436085
However, that still didn't help me, this was an upgrade from 2003 exchange, I modifed the ADSIEDIT stuff, the send/receive connectors, the transport connectors, the global settings, the mailbox settings, etc..etc... I still got the #550 5.3.4 SMTPSEND.OverAdvertisedSize; message size exceeds fixed maximum size ## error.
Now exchange 2007 out of the box has a 10mb email size limit. I could send 13mb attachments, just not 15+. This is odd for several reasons, but let me explain the eventual fix. I was trying to "double" the size to 20mb from 10mb, so I went from 10240 to 20480 in the "size" settings.
We enabled verbose logging on the Edge SMTP machine, it showed the 18mb test email I was sending was actually 25xxx in size, so my 18mb attachment, the "SMTP" size of the email was 25 megs-ish. We increased the sizes up to 30000 and blamo..20mb email attachments now work. I tried sending from gmail and another exchange server, both significantly increased the size of these emails with the 18mb attachment. I'm not sure why, but that is a problem for another day.
Wednesday, November 5, 2008
Another Acrobat 8 Vulnerability
http://www.adobe.com/support/security/bulletins/apsb08-19.html , another one of those, you view the web page with a malicous PDF document and you get a Virus or Trojan types.
In order to get ourselfs up to date, you need to push this out to alot of machines. Since 8.1.2 isn't good enough anymore, you probably need the 8.1.3.msi file. Since I can't get it to extract using the "approved Adobe methods" http://www.adobe.com/go/kb400540, I had to resort to going straight to the ftp site for adobe
ftp://ftp.adobe.com/pub/adobe/reader/win/8.x/8.1.3/enu/AdbeRdr813_en_US.msi
Now that i've got the MSI, it'll be cake to push out.
In order to get ourselfs up to date, you need to push this out to alot of machines. Since 8.1.2 isn't good enough anymore, you probably need the 8.1.3.msi file. Since I can't get it to extract using the "approved Adobe methods" http://www.adobe.com/go/kb400540, I had to resort to going straight to the ftp site for adobe
ftp://ftp.adobe.com/pub/adobe/reader/win/8.x/8.1.3/enu/AdbeRdr813_en_US.msi
Now that i've got the MSI, it'll be cake to push out.
Subscribe to:
Posts (Atom)