NET USE:
net use \\servername\printersharename
There are other ways to install a printer to a user using the runndll32
command but that's way more complicated.
Pushing a file via login scripts:
The issue I have with that is
1) You are pushing the same file to "X" # of people.
2) The c:\documents\data directory does not get backed up {I am
ASSuming}
3) In the event of a system re-install you have to search a users HD to
make sure no local files exist.
Solutions:
1) Place the file in a shared location and send e-mail with link info:
\\servername\sharename\filename
This will allow everyone to access the file. You can make it read
only if desired or even a
template so they can save their revised copy to their normal
location.
If you use Exchange, public folders is the 'other' answer
2) To get the local documents off of the users hard drive you can use AD
to create a GPO
which moves their MY DOCUMENTS directory to a shared location.
However, if you must do as you are saying - and assuming all users have the
same data location you simply should use a shared folder and a UNC path to
copy the data to the local machine(s).
In the login script:
copy /Y \\dotservername\sharename\filename c:\documents\data
That should work.