Thanks for all the responses!

These are the requirements behind the intial request.

Currently, each user ( about 400 ) use a multitude of dos batch files when logging in. There exists a batch file which maps a P: drive to their own unique location, so the current batch file has 400 or If %username% = user , then map p: to \\server\share\xxxxx. Same goes for the group mappings, Really cool.... not. As you can imaging, there are people who do not have a P: drive, then stuff breaks and call the HelpDesk cause someone goofed in the batch file.

I have started implementing kix to replace the horrendous group drives, and that works well. But the P: drive is a bit more interesting, especially as a migration is underway at the moment.

1. I need to determine their existing P: drive when they login in, rather than try and find what they currently map too in the batch file.
2. I am required to write this file into their home directory.
3. Whenever they log back in, this file is then parsed to determine the share folder and directory.
4. The drive is then mapped accordingly.
5. Whenever the user logs off a script will be used to check and rewrite the contents of the file if they have changed the P: drive mapping.

The reason for this method is that the local IT department has determined that this is the way they want to control the users P: drive and can then update for the user as needed.

Willy

I hope this make more sense.