5 Replies Latest reply on Oct 14, 2014 10:58 AM by tao

    ePO FramePkg and Port Settings

    tao

      Scenario

      1) Change the default Agent wake-up/broadcast ports

      2) Manually download a new Agent FramePkg from the ePO console

       

      Question

      Is the new Agent FramePkg suppose to have the new port settings or the default port settings?

        • 1. Re: ePO FramePkg and Port Settings
          fitchsoccer342

          Not sure but you could always install the new FramePkg after making the change, then go to C:\ProgramData\McAfee\Common Framework and open Agent.ini; the first couple lines should list the port settings. If they have not changed, then I am sure after the first asci you could re-open the Agent.ini file and it will show the port as changed..

          • 2. Re: ePO FramePkg and Port Settings
            lmcashen

            From what I've seen, the new agent will have the 8081 port set as the default, so you won't be able to do a wakeup call, but the next time it does an ASCI, it will pick up the new setting and after a few moments, the port will be changed and you'll be able to do wakeup calls.

            • 3. Re: ePO FramePkg and Port Settings
              tao

              The Agent.ini has the default ports and the next time it does an ASCI, it does change the ports to the new settings.

               

              Found it strange that you can change the ports through the ePO console put yet the FramePkg keeps the default port settings.  When the FramePkg is manually installed, ePO policy is set to install VSE, HIPS, there is a lag before the two installs actually start.  Can't wake them up due to different ports so just have to wait...really?

              • 4. Re: ePO FramePkg and Port Settings
                fitchsoccer342

                Well one of the first things the agent tries to do after being installed is reach out to the ePO server, and pull down any policies/tasks. So there really shouldn't be much lag time after the install to it actually installing your products. I haven't experienced much of an issue when doing so.

                 

                Although, I have only noticed this once, but we had a web server utilizing port 8081 and the agent actually never initially checked in, as the error log said another application was using the port - so we had to stop IIS and let the agent check in, change its port, and then it was good to go.. just for FYI.

                • 5. Re: ePO FramePkg and Port Settings
                  tao

                  Manual install of the FramePkg, below is the http://x.x.x.x:8081 GRANTED, the actual port should be 8085.  So, VSE won't be installed until the next policy enforcement.  Also, the new port setting will not be reflected until after VSE has been installed and the frameservice has been stopped/started. Really doesn't make any sense as to why it would take so long for the install/port change.

                   

                  10/14/2014, 11:40:21 AMInfoUpdaterSubsystem started
                  10/14/2014, 11:40:21 AMInfoSchedulerScheduler is now running
                  10/14/2014, 11:40:22 AMInfoAgentGenerating Agent ID...
                  10/14/2014, 11:40:22 AMInfoAgentAgent will connect to Server in randomized 10 minutes interval
                  10/14/2014, 11:40:22 AMInfoAgentNext policy enforcement in 5 minutes
                  10/14/2014, 11:40:22 AMInfoAgentAgent will connect to Server in : 0 minutes and 0 seconds
                  10/14/2014, 11:40:26 AMInfoAgentAgent started performing ASCI
                  10/14/2014, 11:40:26 AMInfoAgentChecking MAC address...
                  10/14/2014, 11:40:26 AMInfoManagementCollecting Properties
                  10/14/2014, 11:40:26 AMInfoAgentAgent communication session started
                  10/14/2014, 11:40:26 AMInfoAgentAgent is connecting to ePO server
                  10/14/2014, 11:40:27 AMInfoAgentPackage uploaded to ePO Server successfully
                  10/14/2014, 11:40:27 AMInfoAgentAgent communication session closed
                  10/14/2014, 11:40:27 AMInfoAgentAgent received POLICY package from ePO server
                  10/14/2014, 11:40:27 AMInfoAgentNew Site List file was received
                  10/14/2014, 11:40:27 AMInfoAgentNew server policy was successfully merged
                  10/14/2014, 11:40:27 AMInfoAgentEnforcing newly downloaded policies
                  10/14/2014, 11:40:27 AMInfoAgentAgent Started Enforcing policies
                  10/14/2014, 11:40:27 AMInfoManagementEnforcing Policies for McAfee Agent
                  10/14/2014, 11:43:21 AMInfoUpdaterSubsystem started
                  10/14/2014, 11:43:22 AMInfoSchedulerNext time(local) of task UPDATE: Tuesday, October 14, 2014
                  10/14/2014, 11:43:22 AMInfoSchedulerScheduler is now running
                  10/14/2014, 11:43:26 AMInfoAgentAgent will connect to Server in randomized full ASCI interval : 3600 seconds
                  10/14/2014, 11:43:26 AMInfoAgentNext policy enforcement in 15 minutes
                  10/14/2014, 11:43:27 AMInfoAgentAgent will connect to Server in : 8 minutes and 0 seconds