Setting up Transfer Manager on a New Station

Have a new station doing night utilities and download with night utilities.  Then you need Transfer Manager installed on that station.  Here are the steps on how to do that.
Download Transfer Manager from http://www.ivans.com/downloads/

Once the file is downloaded

Then you will need to double-click on it

1. click on RUN
2. NEXT
3. FINISH (where it says C:\TM.NET Setup)
4. NEXT
5. YES – to the License Agreement
6. BROWSE (this is the Choose destination location box)
7. just change the C ( the drive letter ) to the letter that your Agency uses for your TAM network drive (such as G) G:\ivans\transman
8. then click OK
9. Then click on NEXT
10. NEXT
11. FINISH

Then you need to open up the Transfer Manager.net  Application you just installed…

1. Click on configuration
2. Click on then support mode
3. Click on Configuration
4. Then Site settings
5. Both of these need to be set at Internet
6. Then you can close out of TM.net

There is a last step to this…

1. Open TAM
2. Go to Utilities
3. Go to Company Interface Folder
4. Go to Misc. Download Utilities
5. Click on the black ARROW
6. Click on the Transfer manager path Configuration
7. You then need to select the CONTINUE Button
8. Select the Use Directory Specified below Radio button option
9. Then type the Path that you just installed the Transfermanager.Net to
10. (EXAMPLE G:\IVANS\TRANSMAN)
11. Then select the VER 3.1 or later, make sure this is checked
12. Then click on OK

IF THIS IS AN XP MACHINE:

It is very important that the following Security setting be set on your download workstation:

Start, Settings, Control Panel, Administrative Tools, Microsoft.NET Framework 1.1 Configuration, Click 1 time on the Runtime Security Policy, On the right you will then see Adjust Zone security, click NEXT, click on Local Intranet, Slide the security level up to Full trust, NEXT, FINISH. Then you can close out the .net configuration page, and the Admin Tools page as well.

The Year 2029

I have been adding individual life policies to tam and have been setting the exp date 30 years ahead when the policy expires.

Had to call tam and find out why anything after 2029 kept setting back to 1929.
They said its a windows xp issue and microsoft has to fix it and probably wont since they dont want to support windows xp anymore.  They said it might work on vista or 7.

Edit: just tried it in Windows Vista and it doesnt work on Vista either dont have a 7 machine with Tam so cant try that yet.