Endpoint Protection

I had to do a clean re-install of SBS 2008 due to a problem in Exchange.

Will the packages for Server and Client created earlier work or new packages will have to be created?

The package for clients can be created as per the link
http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2007110513361348
However I am unable to find the link for creation of the Server package. Will someone be kind enough to provide the link and the resources?

Thanks,

there is no differeence client package forclient and server, however the package with required modules that needs to be installed differs for server and client then you need to create the package based on the above URL and use package for deployment on client and server.

cheers
Pete

The same Article http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2007110513361348 should help in creating the package.

Secondly, as rightly mentioned by pete_4u2002 there is no difference in the package usually unless:

 - You would want to exclude features like PTP, NTP , etc... on the server


Thanks :-)

It will definitely work.Go ahead

One of the Symantec executives worked me around in creating the packets. He created one for the client and one for the server. However, the one for the server is not being accepted. Hence the query raised by me.

Thanks for your advice.

 Could you let us know what excatly is happening.. Is it not getting installed if yes then what error are you getting. Or is it rolling back ?

Duh Uh - Please read the topic first before posting just for the heck of it.....

Hey,

I agree to what Kedar said.

To summarize :
As you have installed Fresh SEPM on the clean re-install of SBS 2008, you will need to create new install Packages for Servers and Clients ( Only if there are seperate groups for Servers and Clients or difference in Feature sets).

Reason for new package :

The package created from the old SEPM would have the Old SEPM information for reporting:

1.  Old server certificate
2.  Old SEPM ID
   
   All this information is in Sylink.xml file.

If you already have clients deployed and you just want to reset the communication of the SEP clients with the new SEPM then please refer to the following link :
Using the "SylinkReplacer" Utility
http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2008062412271448?Open&seg=ent

Create a list of computers in a Notepad with either IP addresses or host names. This is to be used while you are running Sylink Replacer.

How to pickup the correct Sylink.xml

1. In SEPM - go to Clients tab
2. Right Click the Group where you want the clients to be reporting
3. Take a note of 1st 4 alpha numeric ID of Policy Serial Number
   
4. Go to C:\Program Files\Symantec\Symantec Endpoint Protection Manager\Data\Outbox\Agent\
5. Open the folder name that has similar ist 4 alpha numeric IDs
6. Copy Sylink.xml to Desktop. This is the one that you can select.

OR

1. Right Click the Group where you want the clients to be reporting
2. Export Communication Settings
3. Save it to Desktop
4. Rename the file as Sylink.xml

Now Run Sylink Replacer Utilty and follow the Wizard.

Please revert if it helped.....

Thanks,

Thanks Sanosh for the detailed post.

I thought so that a new package shall have to be created and shall give it a try in the weekend.

There is no mention of the server package anywhere and I do not understand why that was created when the Symantec Executive walked me in creating one the last time.

Thanks,

Hi,

The difference in Server and Client Package :
It is a good practice to have two different groups SERVERS and CLIENTS to organize the structure :

Server Group : On servers it is better to exclude PTP(Not supported) and NTP
Clients : Select any feature set as per your requirement

If 64 bit platform Servers/Clients :
Make different groups for each, do not mix with 32 bit systems
Do not include PTP feature as it is not supported on 64 bit platform
------------------------------------------------------------------------------------------------------------------------------------------------------------------
Note : For more information on Symantec Endpoint Protection 11.0 compatibility with 64-bit platform please refer : http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2007022310384648
------------------------------------------------------------------------------------------------------------------------------------------------------------------
Separate groups will help in setting up Auto upgrades for the clients by attaching a 32/64 bit package to the respective groups.

How to Create custom install packages

1. Once you have the group structure in place in SEPM you can create custom Feature set templates in Admin- Install Packages – Client Install Features. [Eg. :1. Server Feature set; 2. Client Feature set]
2. Then select the appropriate package (32/64 bit) from Client Install packages and Export
3. Browse to the location you want to save this package.
4. In the drop down where you see Client install features select the one you created (Features for Server incase it is a package is to be made for Servers)
5. Put a check in front of the group where you want the servers to be reporting (Server Group)
6. Leave the other settings to default and Export
7. Once this is created, you can use this package to Servers(as we took an eg. of Server package) using Migration and Deployment Wizard.

Please revert if this answers your query….

Thanks 

Server packages are created for Best Practises so that the they will be in diffrent groups and  diffrent policies can be applied on them.
And as per the best practises Support also ensures that the client package contains all the the features sometimes without NTP on customers request.
and for the Server Package only Antivirus and Antispyware is selected so that any issue wont impact the whole network.

You mentioned that the server is not accepting the package..is it a 64 bit server ??

Hi Vikram,

I agree to you on that. Thats a very valid point.

If NTP needs to be installed it is good to go with, however rules are to be configured as per the requirement.
The above explaination is just to give an idea on how to create a organized structure so as to ease the deployment process and help in further product upgrades if required.
The reason behind making a seperate group for 64 bit is for the ''Upgrade Group with package' option wherein we need to select either 64 or 32 bit Install Package.

Thanks Vikram :)

Thanks to you all for the detailed clarifications.

SBS 2008 is 64 bit but the nodes are Windows XP 32 bit.

While creating the install packages, I do not remember seeing the 32/64 bit mentioned anywhere.

Created the Server package as per advice. However i am unable to install the package on the server as getting the message Logon failure while deploying the same on the server.

The same logon failure is coming while deploying to one of the clients.

Is it a 64 bit package that you have created ?
No need to deploy it to the server..since you are local to the server just execute the setup.exe for the install package. 

Hi rkkhandelwal_54,

Please follow the checks as under :

1. Verify you have entered the correct username and password.
2. Set the Windows Firewall to disabled or create an exception to allow UDP Ports 137, 138 and TCP ports 139 and 445
3. Disable Simple File Sharing on the target system
4. Start the Remote Registry Service if it is not already started.
5. Enable the built in Administrator account and set a password for it.

Hope this should help.

Please revert is it gives the solution.

Thanks :)

Hello rkkhandelwal_54,


You can also do a local installation of the package on thise systems if it only for one or 2 systems.

Thanks to you all for your support.

:)