We had just found the same issue here a couple of days ago when we moved the home folders to a new server. The reason why it has worked for us up until now is that the net use /home command looks at the local path in NT User Account or AD and that is why still sets it.
It should be Connect To: or just redirected My Documents as mentioned previously.
Must have been really fortunate then, as I've not come across this problem so far. Been running without a home drive for 6 years now.
What we've done is write a specification of requirements for software, which we send to the software supplier and they have to agree to it before they supply us with the software. If the software has crappy things in it like needing a home drive mapped, or direct access to c:, or admin priveledges then the stuff goes back for a refund.
care to share that statement of requirements?
This is all very interesting.
Thanks for all the comments.
Looks like the way to go is:
Edit all user accounts to use connect to method, then look at using the redirect for my docs. (We already use the redirect for the desktop and start menu...)
>>>Because some badly written software insists on a network drive
By this do you mean that the user actually has an H:\ drive mapping?