Any tool that supports HTTPS POST commands will work.

The following are the steps to use the Microsoft wfetch tool:
 

1. From a Windows command prompt perform the following command on the desktop of the IM client machine:

ipconfig /all

The output looks like this:

Windows IP Configuration

Host Name . . . . . . . . . . . . : L-L3CB433
Primary Dns Suffix . . . . . . . : enterprise.foo.com
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : ges.foo.com
corp.foo.com
enterprise.foo.com
foo.com

Ethernet adapter Wireless Network Connection:

Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : Intel(R) PRO/Wireless 3945ABG Network Connection
Physical Address. . . . . . . . . : 00-18-DE-B2-40-D4

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : corp.bar.local
Description . . . . . . . . . . . : Intel(R) PRO/1000 PL Network Connection
Physical Address. . . . . . . . . : 00-16-41-A9-8D-62
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 172.17.40.137
Subnet Mask . . . . . . . . . . . : 255.255.254.0
Default Gateway . . . . . . . . . : 172.17.40.1
DHCP Server . . . . . . . . . . . : 172.17.33.31
DNS Servers . . . . . . . . . . . : 172.17.33.31
155.64.2.141
Primary WINS Server . . . . . . . : 172.17.33.31
Lease Obtained. . . . . . . . . . : Wednesday, July 23, 2008 1:13:47 PM
Lease Expires . . . . . . . . . . : Saturday, July 26, 2008 1:13:47 PM

Ethernet adapter Local Area Connection 5:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Windows Mobile-based Device #2
Physical Address. . . . . . . . . : 80-00-60-0F-E8-00
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 169.254.2.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DHCP Server . . . . . . . . . . . : 169.254.2.1
Lease Obtained. . . . . . . . . . : Wednesday, July 23, 2008 8:25:19 AM
Lease Expires . . . . . . . . . . : Friday, August 22, 2008 8:25:19 AM



2. Download and install the Microsoft wfetch tool: http://www.microsoft.com/downloads/details.aspx?FamilyID=b134a806-d50e-4664-8348-da5c17129210&displaylang=en.
3. Run the wfetch tool.
4. Choose POST from the Verb dropdown.
5. Enter aimpro.premiumservices.aol.com in the Host textbox.
6. Enter the following into the Path textbox:


NOTE: This test should be done twice. The first time using the cldn and the second using the pldn. Depending on how AOL provisioned the domain determines which test will return the correct results.

The cldn parameter contains the connection-specific DNS suffix information. The pldn parameter contains the Primary DNS Suffix. Most customers are provisioned using the pldn.

Use the CLDN


/dcs/?cldn=1%2B<replacewithConnectionSpecificDNS>%2BLocal+Area+Connection%2BSiS+900-Based+PCI+Fast+Ethernet+Adapter+-+Packet+Scheduler+Miniport&pldn=NULL&snd=&clientName=imApp&clientVersion=37.6.8.7.7.368


• Replace the text <replacewithConnectionSpecificDNS> with the value from the Connection-specific DNS Suffix in the ipconfig output. If the Connection-specific DNS Suffix is empty change the value to NULL.

For the example above the entry is:


/dcs/?cldn=1%2Bcorp.bar.local%2BLocal+Area+Connection%2BSiS+900-Based+PCI+Fast+Ethernet+Adapter+-+Packet+Scheduler+Miniport&pldn=NULL&snd=&clientName=imApp&clientVersion=37.6.8.7.7.368

Use the PLDN



/dcs/?cldn=1%2BNULL%2BLocal+Area+Connection%2BSiS+900-Based+PCI+Fast+Ethernet+Adapter+-+Packet+Scheduler+Miniport&pldn=<replacewithPrimaryDNS>&snd=&clientName=imApp&clientVersion=37.6.8.7.7.368 
 

• • Replace the <replacewithPrimaryDNS> text with the value from the Primary DNS Suffix in the ipconfig output. If the Primary DNS Suffix is empty change the value to NULL.

For the example above the entry is:


/dcs/?cldn=1%2BNULL%2BLocal+Area+Connection%2BSiS+900-Based+PCI+Fast+Ethernet+Adapter+-+Packet+Scheduler+Miniport&pldn=enterprise.foo.com&snd=&clientName=imApp&clientVersion=37.6.8.7.7.368

6. The response for either the PLDN or CLDN is XML like the following:


<?xml version="1.0" encoding="UTF-8"?>
<response>
<statusCode>200</statusCode>
<statusText>Ok</statusText>
<data name="conn.settings" priority="0">
<proxy.use_proxy>false</proxy.use_proxy>
<end-point.port>443</end-point.port>
<end-point.conntype>ssl</end-point.conntype>
<cc.url>https://aimpro.premiumservices.aol.com/cc/ClientConfigurationWS.jws?WSDL </cc.url>
<end-point.hosttype>uas</end-point.hosttype>
<end-point.conntimeout>10</end-point.conntimeout>
<end-point.host>replacewithDNSname</end-point.host>
</data>
<data name="client.urls" priority="0">
<change_password></change_password>
</data>
</response>


where replacewithDNSname is the name of the DNS host provisioned with AOL. If the name matches the DNS entry for your IM Manager server then the AOL provisioning is completed.

Technical Information
If you are unsure of the domain used by the AIM client turn on client logging for the AIM client and log in. Use the following KB article for collecting AIM client logging: How To Capture AIM Client Logging for AIM 6.X.

Effective 5/1/10, there has been a change in Symantec IM Manager’s support of the AOL Instant Messenger platform. This change may result in changes to your end-user experience with AOL Instant Messenger and Symantec IM Manager. If you are using encrypted AIM redirection, Symantec will no longer provision new domains using the AOL DCS. New provisioning for encrypted AIM will require redirection on the end-user client side, instructions can be found here: (www.symantec.com/docs/TECH132521). In addition, there may be delays or unsupported compatibility with new or modified versions of the AOL IM Clients.