Video Screencast Help

DS 7.1 Agent during unattended install different ports?

Created: 25 Mar 2013 | 2 comments
Posting for a friend... 
unattended install of windows
all servers are set to use port 8016 where normal process uses 80
so server listens on 8016 - all good
in winpe pec agent set to 8016 and works well
boots fine - gets initial deployment screen
select install and it starts installing
somewhere during the install it installs the altiris agent.
it is faulting to port 80.
tried modifying script to use 8016 but it seems something is self repairing or healing the file back to port 80
any idea how this happens or how i can get this to not occur?

Comments 2 CommentsJump to latest comment

Ludovic Ferre's picture

Hello Telefrager,

How is the Altiris Agent installation done after your unattended deployment? Do you use built-in features or send the file and use a command?

It could be the problem there.

Now you can always fix the http port using aexagentutil /Server to reset the server name and include the http port 8016 for communications.

Ludovic FERRÉ
Principal Remote Product Specialist

TeleFragger's picture

built in feature where altiris is modifying setup complete to install the agent.

That is where the problem is.. whatever modifies the setupcomplete.cmd is what is happening.

If setupcomplete exists then this file is getting overwritten making any changes done gone.

and since this is the last file that runs before the end of the build not sure how to run the aexagentutil /server with server name and port.

whatever process runing modifies setupcomplete.cmd to run altirisagent.bat

altirisagent.bat installs the agent and that is referencing port 80 not 8016.

If he modifies either setupcomplete.cmd or altirisagent.bat they get overwritten during the process.

so the nice thing would be to find where these files truely exist that are copying out and over writing.

Did we help you? Please Mark As Solution those posts which resolve your problem,