Symantec Endpoint Protection Manager won't export install package

I was getting the error message "Management server is not yet ready".

Here is how I fixed it.

I reran the Management server configuration wizard.  This time it asked for a database password.

Restarted the Symantec Endpoint Protection Manager and the Symantec Embedded Database services.

Logged back on and tried to export and it successfully exported.

SEPM Version: 11.0.7 MP2

Source:  Link

The Nightmare that they call Symantec Backup Exec

On one of my previous projects, I worked with a guy that was in charge of backups. He used Backup Exec with tapes. Smooth as can be, no headaches (or so it seemed to me). A client comes to ask me about backing up there data. First thing that I thought of was, Backup Exec. That was almost 3 years ago and to this day it works some times and other times it doesn't. No rhyme or reason. Numerous calls to Symantec and getting no where, I finally gave up. I decided to look at it again today, and so far, it looks like I may have fixed it.

I was getting error such as: E000810C, E000FE36, and others that I don't remember.

I googled something and it suggested changing that account password. I decided I was going to create a new user account and just start from scratch.

I found this article.

How to change the user name or password of the Backup Exec Services Account in Backup Exec.

So I did that and it broke some things.  So I kept looking.  I found this.

Requirements for the Backup Exec Service Account (BESA)

It had some interesting things that I have never seen before or have been told by symantec. They were:

The Backup Exec Service Account (BESA) requires the following User Rights in group policy and group memberships:

• User rights requirements: 
• Act as a part of Operating System ( Only for Windows Server 2000 ).
• Create a token object.
• Log on as a service. 
• Logon as a batch job. 
• Manage auditing and security log. 
• Backup files and directories. 
• Restore files and directories.
  
• Group Memberships or equivalent access: 
• Domain Admins or Administrators.
• Backup Operators. 

Due to security implementations in Microsoft Small Business Server, the service account must be " DomainName\Administrator " account.


Refreshes local and Active Directory-based Group Policy settings, including security settings by executing "gpupdate" command. 

I ran the "Test  Run" option on the job and it ran with no errors and actually completed in a crazy fast amount of time (25 and 36 seconds).  I guess the true test will be if this completes the full backup job scheduled to run in two days.  I don't think I have ever had a full backup work unless I started it and deleted all the previous saved data.  I don't have my hopes up but we'll see.

Other Sources:  Link Link Link Link

Symantec Endpoint Protection Mac OS X 10.6.6 Live Update annoying

Commands:

symsched -l list the jobs for current user
sudo symsched -l does it for root
su jsmith, password, symsched -l shows for jsmith

I think it runs multiple times because it is configured for each user account on computer

Solution:

Delete all with symsched -d all and do that for every local user

Now run this and change the 24hr time to whatever time you want.  This will run for all users.
sudo symsched LiveUpdate "Update All Daily" 1 0 -daily 07:17 "All Products" -quiet

As far as I have noticed this has seemed to work. It stopped the annoying pop up of live update and the antivirus was a day or 2 old.

Sources: Link Link Link

Deploying Symantec Endpoint Protection 11

First off I am going to make some assumptions...

1.  You already downloaded Symantec Endpoint Protection (SEP) from https://fileconnect.symantec.com
2.  You have already installed Symantec Endpoint Protection Manager Console (SEP Manager)

Open SEP Manager and login with your account.  Select Admin from the icons on the left.  Click Install Packages located at the bottom of the second column on the left.  Next, click "Client Install Settings". Right click in the window to the right and click "add". I am going to call my settings Custom SEP install.  You can choose different types of installations.  The choices are Interactive, Unattended and Silent.  Interactive lets the user interact with it, unattended shows the user but doesn't allow them to give input, and silent is when it runs in the background with no user interaction.  You will also have to choose if you want the computer to restart after the install or not.  Another option is if you want to install it into the default location or a special one.  The last setting is for upgrading.  If you are deploying this to a client that already has SEP installed, you have to choose if you want it to maintain all logs, policies, and client-server communication settings.

Next select "Client Install Feature Sets". Right click in the window to the right and click "add".We are going to create the features that are installed.  Pick a name and choose your features you want installed.

Next select "Client Install Packages", then select the version of SEP you are trying to install.  Select "Export Client Install Package".

Click Browse and navigate to a folder that you want the deployment package to be stored.  You will want to click the drop down box below "Pick the customized installation settings below:" and select the custom install settings you created.  Do the same for "Select the features you wanted to use:".

The next step will be different for everyone.  If you have multiple groups in side of SEP manager, then you might have to do this several times.  You can have several packages or you can select the default package and move the client to the correct group once it shows up in SEP manager.  Click ok and your package starts to be exported.

Click close and close SEP manager.  Now open "Migration and Deployment Wizard".  Click Next --> Deploy the Windows Client --> Next --> "Select an existing client install package to deploy" --> Click Browse --> Navigate to the folder you exported your package to and select the exe.  Click finish.  You will then have to choose which machines you want to push it too.  Select the machines, select add, enter administrative credentials and hit finish.  You will be able to watch the progress of each machine.

If you want Symantec's explanation here is a link to their page:  Link