Select the platform where you are starting the POA:
After installing the NetWare POA software, you can start the NetWare POA in several ways:
To start the NetWare POA manually:
Go to the NetWare console of the server where the NetWare POA is installed.
or
Use Remote Console to access the server, press Alt+F1 to display the options, choose Select a Screen to View, then choose System Console.
Enter the command to load the NetWare POA.
Syntax: load gwpoa.nlm /home-[svr\][vol:]\po_dir
Example: load gwpoa.nlm /home-server1\mail:\sales
The /home startup switch is required to start the NetWare POA. If the post office is located on a different server from where the NetWare POA is running, the /dn switch or the /user and /password switches are also required so the NetWare POA can log in to that server.
The NetWare POA agent console will appear and display normal startup status messages. See Monitoring the POA.
If the NetWare POA agent console does not appear, see Post Office Agent Problems in Troubleshooting 2: Solutions to Common Problems.
When you start the NetWare POA as described above, it is configured according to the POA settings specified in ConsoleOne®. You can go to ConsoleOne and modify POA functioning as needed. See Configuring the POA.
Another way to start the NetWare POA is to use a startup file. You could use a startup file with the NetWare POA for the following reasons:
When you run the Agent Installation program, an initial POA startup file is created in the agent installation directory. It is named using the first eight characters of the post office name with a .poa extension. This initial startup file includes the /home startup switch set to the location of the post office directory.
If the post office is located on a different server from where the NetWare POA is running, you must edit the startup file and provide settings for the /dn switch or the /user and /password switches so the NetWare POA can log in to that server.
The POA startup file can be modified to use other startup switches as needed. Startup switches specified on the command line override those in the startup file. Startup switches in the startup file override corresponding settings in ConsoleOne. See Using POA Startup Switches.
When you use a startup file, you must include it on the command line when you load the NetWare POA. For example:
Syntax: load gwpoa.nlm @POA_startup_filename
Example: load gwpoa.nlm @sales.poa
In addition to the initial POA startup file, the Agent Installation program also provides a grpwise.ncf file to load the agents. If you will run only the NetWare POA, you should edit the grpwise.ncf file to remove the command to load the MTA.
If you run multiple NetWare POAs for the same post office, you will need a startup file with the /name switch and a corresponding line in the grpwise.ncf file for each POA. A POA object in Novell® eDirectoryTM is also required for each POA. See Creating a POA Object in eDirectory.
When the POA is running smoothly, you should modify the NetWare configuration file (autoexec.ncf) to load the NetWare POA and required NLM programs automatically whenever you restart the server. (If you are running the POA in a clustering environment, see Configuring the POA for Clustering for alternative instructions.)
Edit the autoexec.ncf file in the netware sys:\system directory.
Add the following command to load the agents:
grpwise.ncf
or
To start the agents in protected mode, add the following command:
protect grpwise.ncf
Save the autoexec.ncf file.
If possible, restart the server to verify that the NLM programs and the NetWare POA are loading properly.
You can start the Windows POA in several ways:
In Windows, click Start > Programs > GroupWise Agents, then start the Windows POA.
The Windows POA agent console should appear and display normal startup status messages. See Monitoring the POA.
If the Windows POA agent console does not appear, see Post Office Agent Problems in Troubleshooting 2: Solutions to Common Problems.
When you start the Windows POA as described above, it is configured according to the POA settings specified in ConsoleOne. You can go back to ConsoleOne and modify POA functioning as needed. See Configuring the POA.
Another way to start the Windows POA is to use a startup file. You could use a startup file to configure the POA for the following reasons:
When you run the Agent Installation program, an initial POA startup file is created in the agent installation directory. It is named using the first eight characters of the post office name with a .poa extension. This initial startup file includes the /home startup switch set to the location of the post office directory.
The POA startup file can be modified to use other startup switches as needed. Startup switches in the startup file override corresponding settings in ConsoleOne. See Using POA Startup Switches.
If you run multiple Windows POAs for the same post office, you will need a startup file with the /name switch and a corresponding desktop icon or Program menu item for each one. A POA object in eDirectory is also required for each POA. See Creating a POA Object in eDirectory.
After the Windows POA is running smoothly, you should add it to the Windows Startup group to start the Windows POA automatically whenever you restart the Windows machine.
In Windows NT, click Start > Settings > Taskbar > Start Menu Programs > Add.
or
In Windows 2000, click Start > Settings > Taskbar & Start Menu > Advanced > Add.
Browse to the directory where you installed the Windows POA.
Double-click gwpoa.exe, then add the startup file to the command line.
Click Next.
Select the Startup folder, provide a name for the shortcut, then click Finish.
If possible, restart the machine to verify that the Windows POA starts when you log in.
To start the GroupWise Windows POA as a service for the first time after installation:
From the Windows desktop, click Start > Settings > Control Panel.
Double-click Services, select the agent service, then click Start.
To make sure the POA starts automatically each time you restart the machine:
Click Start > Settings > Control Panel.
Double-click Services, select the agent service, then click Startup.
Select Automatic, then click OK.
Thereafter, you will be able to manage the Windows agents just as you would any other services.