Windows Installer 3.0 + Telnet

[Deimos01]

I am currently trying to figure out if windows xp pro has any additonal security policies installed that would hinder the installation of msi package via telnet prompt. What we are trying to do is perform a silent install from one computer to another through the telnet services. We first connect to the the remote computer through computer management and enable telnet services. Next we use the telnet client of the local machine to connect to the remote telnet server. At this point and through the telnet command line we created a new directory and copy the installation files to the remote computer. Finally, at the command prompt we set up msiexec for a silent install: msiexec /q /I xxx.msi. I know there are other ways to set up this remote installation, but because we have legacy systems on our network, this is how is has to done. Now the installation goes off without a hitch when the remote computer is a windows 2k machine, but as soon we try to perform the same procedure on a windows xp pro (sp2) machine the installation hangs (the computer does not hang, the installation does). I set up msi to output a verbose log file via the switch /L*v. The log indicates that a .exe file failed to terminate. It failed to terminate because it failed to initialize. Now, if I use the same command locally (actually sitting at the computer I wish to perform the remote install) and issue the same command, the installation is successful. I should note 'simple file sharing' is disabled and I am logging into the local and remote computers as Administrator. I should also note that I did edit the msi package and commented out the exe file and the installation was successful (the program that it is trying to execute is an externel progress bar that is used for post installation). I guess my question is, is there any reason why windows xp professional, telnet server, or msi 3.0 would not allow a program to execute? This problem isolated to windows xp; the installation works fine with windows 2000 and windows 2000 Server. I would greatly appreciate any advice on how I can resolve this issue.