![]() The agents broker the communication between OS+ESET product and Remote Administrator 6. Once Remote Administrator 6 is installed in place of v5 or else on a different server altogether, you can proceed to deploy the software agents to all network machines. The Apache portion of the setup just involves copying the era.war archive from where it is in the ERA installer folder, to inside of Tomcat's WebApps folder. When you install Remote Administrator 6 later, you'll need to give it the credentials to log in to MSSQL using either the SA account or any other manager level account that you create after installing MSSQL. ![]() Otherwise, you'll need to install and configure MSSQL 2008R2 to not only listen on a free tcp\ip port, but also to use mixed mode authentication. If you have a server in your network that isn't running MSSQL, previous versions of Remote Administrator, nor is a Domain Controller, you'll find that the setup wizard will be able to configure the MSSQL and Apache Tomcat installations for you. As you read in article SOLN3607, you will have to note your version 5 policies, notifications, and reports so that you can re-create them in version 6. Although we have a conversion utility that can convert version 5 logs, static groups, and Remote Administrator Console users to a version 6 importable format, it can't do similar for policies\notifications\reports. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |