Hi Edt, and thanks for your interest.
Basically i wanted to remotely install the "Microsoft's files and printers sharing" services, and also the "Microsoft's network client" component.
After reading a couple of interesting threads (http://bit.ly/xHZKzI and http://bit.ly/AaWa5d), i managed to script the installation of the required components. Just for the sake of answering my own question, here's what i did:
I'm using Microsoft's snetcfg, which is part of the original Windows 2000 driver deployment kit. The resulting script looks like this :
REM install microsoft's network client
cmd /c c:\temp\snetcfg_wxp.exe -v -l C:\windows\inf\netmscli.inf -c c -i ms_msclient
REM install microsoft's files and printer sharing services
cmd /c c:\temp\snetcfg_wxp.exe -v -l C:\windows\inf\netserv.inf -c c -i ms_server
REM These services can be uninstalled using the switch "-u"
REM instead of the full "-v -l C:\windows\inf\netrass.inf -c c -i"
Then i'm using symantec GSS to perform a simple files transfer, and launch the executable + the associated script. The script works well on XP Sp3 clients.
You raised an important point, as to why i would enable file and print sharing, since we wasn't using microsoft's network components previously. Isn't it mandatory to be able to use symantec GSS to the fullest ? (inventory purpose, remote ghost client installation, etc....?)