Answer:
Yes. The server and client can both run on the same machine, however, both will suffer in performance if you do so. This is only recommended if you have an extremely fast machine and/or a dual processor machine.

Answer:
Quick server set up info:

Navigate to your America’s Army / System directory and locate the file labeled RunServer.bat. Right click on the file and select edit. Scroll down to the last line in the file and change the name of the map to which ever map you desire. Close the file and click yes to save changes. Now double click on the same file, RunServer.bat, to launch the server using the map you’ve selected.

Also: With the release of America’s Army 2.7: Overmatch, several server configuration changes have been made including the addition of several port addresses that need to be available for the server through your firewall.

In order to allow other users to join your server, you need make sure the following ports are open for outgoing and incoming traffic in your firewall:

UDP - 1716, 1717, 1718, 8777, 27900
TCP - 20025-45, 20046, 20047, 20048, 14200

Failure to open these ports will prevent the server from accepting connections from other players or prevent other players from being able to see your server online.

There are several settings that also need to be defined in your server configuration INI file (in the Windows version, these files are located in “My DocumentsAmerica’s Army Server Settings{settings file name}.ini”).

[Engine.GameEngine]
ServerActors=DBAuth.DBMBS

[DBAuth.DBAuth]
GameServerIP=

Make sure that you set the actual IP address of the America’s Army Server under GameServerIp= (for example, “GameServerIp=000.000.000.000”). The supplied address must be your actual internet IP address (you can find this at http://www.myipaddress.com), if this is left blank or you supply the IP address for your internal network (such as 192.168.0.x), your server will not be able to accept connections from the internet.

Answer:
From the console (hit '~' to access the console) type "open 123.456.7.89?password=PASSWORD" Where 123... is the IP of the server you are connecting to, and "PASSWORD" is the Admin password for that server.

Answer:
In addition to the extra console commands listed below, Admins are locked into spectator mode, but they can view *all* Players and all Viewpoints regardless of the server spectator settings. Additionally, the Admin spectator is not prevented from flooding the server with spectate change requests. You cannot switch to normal mode if you logged in as an Admin.

Commands:

kick PLAYERNAME
The player specified by PLAYERNAME will be kicked from the game and sent to Leavenworth. (This will *not* go on their
permanent record.

kickban PLAYERNAME
The player specified by PLAYERNAME will be kicked from the game and his IP will be banned from your server. (This will *not* go on their permanent record.

switch MAPNAME
Change to the map specified by MAPNAME.

playerlist
Print a list of all players in the game to the .log.

admin CONSOLECOMMAND
Execute any console command on the server
(Make sure you know what you're doing before you use this!)

More admin commands can be found in this forum topic: (Console commands).

Answer:
Look for the following line in your .ini file:

bRequireAuthorization=true

and change it to

bRequireAuthorization=false.

Answer:
Running a dedicated Linux server for America's Army is, in many ways, identical to running a UT2003 server. Admins that have been working with the Unreal series in any form will be largely familiar with ArmyOps right away.

Also, if you have been using the Windows version of the dedicated server, just about any information you find on the web in regards to it also applies to operating the Linux version.

There are, however, a few significant differences, so I will walk you through a quick setup and highlight these as I go.

Understand that running a server is not friendly to the neophyte; you're going to need to punch in cryptic things at a terminal's command line prompt and edit configuration files. There is are no graphical user interfaces for
this.

First, you want to set up a sane environment. Install the server by running the ".bin" file you downloaded:

sh ./armyops210-linux.bin

This will give you an installer that will walk you through getting the basic package installed.

Just about every aspect of the server is control via the "ini file":
this is a text file with various knobs and switches. A template is available in the server's "System" directory; you should work from a copy of this file:

cd /usr/local/games/armyops210/System
cp ./Default.ini ./server.ini

Now you can edit server.ini to your liking.

First, if you just want a LAN game with your friends and don't want to concern yourself with the honor system or anything, then all you _have_ to change is one line:

bRequireAuthorization=true

should be changed to:

bRequireAuthorization=false


Now, start the server:

./server-bin lan bridge -nohomedir -INI=server.ini

"lan" tells the program that you want a non-public game, and "bridge" is the map you want to play on. Please reference the "Maps" directory for a list of available maps:

ls /usr/local/games/armyops/Maps/


"-nohomedir" is a Linux-specific command line switch that tells the program to keep all the files in the game's directory. Without this, some files will be spread out to your home directory, which can be confusing, but desirable
in some situations.

The "-INI=server.ini" tells the program what configuration to use. This is handy if you have multiple, diverse configurations you wish to switch between quickly. If you don't specify this, the server will use "ArmyOps.ini" (creating it by copying Default.ini if it's missing) as a default.

At this point, you should be able to see your server in the LAN browser from inside the game and begin playing immediately.

If you want to run a public server that shows up in the server browser, you need to register your server with the Army. Please visit the registration page at http://login.americasarmy.com/ to do so.

Running a public server requires that "bRequireAuthorization" setting to be
set to "true". Once your server is in the system, players can join online. If you don't register your server, players will be dropped after connecting.

After you are registered and have set bRequireAuthorization to "true", you
start the server like this:

./server-bin global bridge -nohomedir -INI=server.ini

The difference is, of course, the "lan" flag is replaced with "global".

If you want PunkBuster enabled on your servers, go edit the "pb/pbsvgame.cfg" file inside the game's "System" directory and make sure it contains this:

sv_punkbuster 1

...and restart your server. That should be all you need to enable PunkBuster support. If you see something like this after starting the server:

Game engine initialized
PunkBuster Server: pb_sv_SsNext = 689942 (0 to 999999)
PunkBuster Server: pb_sv_LogNext = 11 (1 to 999999)
PunkBuster Server: 0 Power Players loaded from /usr/local/games/armyops/System/pb/pbpower.dat
PunkBuster Server: 0 PB Rcon Filters loaded from /usr/local/games/armyops/System/pb/pbrcon.dat
PunkBuster Server: PunkBuster Server (v1.032 | A1311 C1.032) Enabled
PunkBuster Server: Game Version [2.1.0]

...then PunkBuster is functioning. It will log information to "pb/svlogs/" in the game's "System" directory.

To shut down the server, hit CTRL-C in the terminal.

There are a great many features of the server that can be tweaked from the .ini file, but that is not Linux-specific, and well documented in other places. Please refer to the official ArmyOps 2.4 manual (available
from http://www.americasarmy.com/support/gamemanual.php ) and the official forums at http://forum.americasarmy.com/ for further information and aid.