An observation from today.
Currently net.exe is executed when the user logs in and maps a network drive (may also use credentials based on the user, etc.). This is achieved as follows:
Scenario 1. Normal conditions
Under the registry key HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run. Create a string value name MountDrive and data net.exe use b: /persistent:no \\localhost\mydrive
Behaviour: Command runs, drive is mapped.
Now suppose command fails occasionally. To understand why, I would like to redirect the output of net.exe into the text file. That should be easy to do.
Scenario 2. Modified Value in Registry
I modified the registry entry to
net.exe use b: /persistent:no \\localhost\mydrive >>C:\netlog.txt
Behaviour: Command runs, drive is mapped, but no output file. If I run the same command from command line, the drive is mapped and output file is created (as expected).
Next, I came up with a workaround
Scenario 3. Run a cmd file from Registry.
- create map.cmd with the contents net.exe use b: /persistent:no \\localhost\mydrive >>C:\netlog.txt
- place it on C: drive
- modify the registry entry to C:\map.cmd
Behaviour: Command runs, drive is mapped, output file is created with the contents The command completed successfully. Why does it behave like that - I don't know.
by Evgeny. Also posted on my website