If you have set the path and it show up in the profile but it will not map for the users, then it is most likely an access problem. It will not map the drive unless the user has access to the path. If there is a typo or if the permissions are not correct, the drive will not map. It will also not map if the network is not available at the time of login. The network unavailable issue is common with laptops that the wireless doesn't connect quickly enough.
Also note that when you create Home directories through the AD Users and Computers GUI, it will create the folder (if needed) and add the permissions explicitly for the user. If you are changing the properties through powershell, you will need to create and set permissions yourself. You can do this via powershell as well.
$samAccountName = "TUser"
$domain = "Contoso"
$homePath = "\\Server\Home"
### Create Home Folder
New-Item -Path "$homePath\$samAccountName" -ItemType Directory
### Set Permissions on home folder
$aclPath = "$homePath\$samAccountName"
$acl = Get-Acl $aclPath
$identity = "$domain\$samAccountName"
$rights = "Modify"
$inheritanceFlags = "ContainerInherit, ObjectInherit"
$propagationFlags = "None"
$accessControlType = "Allow"
$rule = New-Object System.Security.AccessControl.FileSystemAccessRule("$identity","$rights","$inheritanceFlags","$propagationFlags","$accessControlType")
Set-Acl $aclPath $acl