I have EnableLinkedConnections
set to 1, as mentioned in
[URL="KB937624. Running Windows 8 Enterprise x64.
My user account User1 has mapped network drives, let's assume configuration looks as follows:
X: drive is mapped to \server1.domain.comusersuser1
Y: drive is mapped to \server2.domain.comshareddocumentsdepartment1
When I run elevated cmd, I get X and Y drives automatically. However they appear to be mapped to one level of folders above:
X: drive becomes mapped to \server1.domain.comusers
Y: drive becomes mapped to \server2.domain.comshareddocuments
Any guess on why this may happen?
Update. Net use in elevated prompt shows correct path, but the drive actually appears to be mapped one level above, as I already described.
View the full article
set to 1, as mentioned in
[URL="KB937624. Running Windows 8 Enterprise x64.
My user account User1 has mapped network drives, let's assume configuration looks as follows:
X: drive is mapped to \server1.domain.comusersuser1
Y: drive is mapped to \server2.domain.comshareddocumentsdepartment1
When I run elevated cmd, I get X and Y drives automatically. However they appear to be mapped to one level of folders above:
X: drive becomes mapped to \server1.domain.comusers
Y: drive becomes mapped to \server2.domain.comshareddocuments
Any guess on why this may happen?
Update. Net use in elevated prompt shows correct path, but the drive actually appears to be mapped one level above, as I already described.
View the full article