I am testing a setup I need to use at one of my sites.
I have two forests, one with an outgoing trust to the other. Users from the trusted forest need to be able to login to PC's in the trusting forest and be presented with their normal mapped network drives etc.
In AD Users and Computers I had the user account configured to map the home drive to \\servername\home\username.
Of course this didn't work when a user logged into the other forest because \\servername is not a FQDN and so could not be resolved. I got round this by entering \\servername.domain.com\home\username in the home drive properties and this works OK since the full DNS name of the server is now present.
Is this the "right" way of doing it and normal practice for this kind of scenario, or is there a better way of sorting this out, I've thought of perhaps adding an extra DNS suffix in the client DNS properties but this can't be assigned by DHCP afaik, so how do people work round this?