We'd love to hear about it! Click here to go to the product suggestion community
Can Anyone help us to providing the below information:
1.Required ports to be open for Safeguard Server,Safeguard Center,Client & Database
2.Required antivirus(SYmantec/Mcafee) exclusion list for SGN8.2 both (Client & Server Side)
3. Can anyone help where TAC(Technical Support help for partners) for client side installation
In reply to paresh palav:
4.Migration Process from 6.1 to SGN 8.2
OR SGN 8.0 to New differnet SGN 8.2 Server.
(Note here 2 seperate server are built like SGN8.0 & SGN 8.2).
Need urgent help.
Hi paresh palav
Please find the answers for your queries below:
1. Required ports to be open for Safeguard Server, Safeguard Center, Client & Database - Please refer this document which has all port numbers used by different Sophos applications.
2. Required antivirus(Symantec/Mcafee) exclusion list for SGN8.2 both (Client & Server Side) - Please refer to this document which suggests what needs to be taken care when installing Safeguard on the machine.
3. Can anyone help where TAC(Technical Support help for partners) for client-side installation - Sophos technical support will help you when you face any issues while Safeguard client installation.
4. Migration Process from 6.1 to SGN 8.2 OR SGN 8.0 to New different SGN 8.2 Server. - Please refer to this document which has information regarding the upgrade path. Please refer to this document which suggests a generalized pattern and way to upgrade your SGN server to latest version. The version number will differ in the implementation from the document as per your from and to version number.
In reply to Jasmin:
Can you please share the support tac help for partners to raise any technical or installation related issue
For customers and partners, we have a same support portal where they can create a support case. Please refer to this site to open a support case.
Thanks for the reply.
We have other concern as below:
1.One of client is having already built SGN6. 1& SGN 8.1 console.
Now client is wants to built the new SGN8. 2 server console on the remote location, also they wants to migrate the SGN8. 1&Sgn6.1 server to the SGN8. 2.
The SGN8. 1 & SGN 6.1 server is already sync with one AD users and computers and full Decryption policy is applied to the here at domain level.
In new SGN8.2 SERVER, the client establish another AD users & computers is separated by other domain but this other new domain is communicated with other old AD USERS& Computers.
The main concern here, if we built the sgn 8. 2 server and sync new AD then will it applied the other console policies to the new 8. 2 console.
Note :1.From SGN 8.2 & 6.1 console, some of users are migrated to the new AD but this new AD Is connected to the Old Ad.
2.Here for the old users, we understand, we need to decrypt the old instance ie SGN8 1&sgn6 1users then we able to install SGN8. 2new client with policies.
2.how we can create the new CCO at sgn 8.2?
3.If we sync the users and computers, which is present in the newly created AD then whatis the impact of policies as this new and old connected to the network of company.
Would you please suggest what do you mean by new AD server? Do you mean a new domain and trust relationship to another domain? If you have the same domain on both the AD servers and the clients are also the same in both the ADs, you can only install a single Client configuration package on the client. The client will communicate to the Safeguard enterprise console whose client configuration package is installed on the client.
Please refer to this article to know about CCO.
You are correct Jasmin.
As here 2 AD are created and connected via trust relainshoip.
In here, we need to migrate the user from one console to another.
Thank you for the information but your above two statements are contradictory as you have mentioned that there are two different domains and they have a trust relationship between them and after that, you said that you are going to migrate the users from 1st domain to another one.
The 2nd statement can't be true if there are two different domains as users for both the domain will be different, however, the users of the older domain might get authenticated on the machine of the new domain through trust relationship between two domains.
I haven't tested above scenario ever in the lab, so I am not sure how exactly it will work when you have a trust relationship between two domain and you are doing cross authentication using it. It may complicate Safeguard Enterprise deployment and other software deployments which are also dependent on the AD users.
I'd recommend you to don't use trust relationship for users who are in different domain.