Unable to map TFS projects to network drive in Visual Studio 2013

Question

I'm having trouble mapping my TFS projects to a network drive in Visual Studio 2013. I am on an instance of Windows 8.1 in Parallels Desktop 9 for OSX. I keep my various dev files on my OSX file system, not on the VM image. This was not a problem for me using Visual Studio 2012 (see screen shot below), however with Visual Studio 2013 I do not see my Z drive as being available to me. What's changed with 2013? Is there something I can do to get 2013 to work the same way 2012 did for this purpose?

Edit: Also, if I attempt to just enter the correct path in manually, it accepts it but then I get a variety of "could not find part of the path..." errors. Third screenshot shows this.

Edit: Ok, I can not even open projects in VS2013 that are on a network drive. The Open File Dialog that is presenting for opening a project does not show my network paths available, and once again when I enter them manually I get an error. Has Microsoft just completely killed this in 2013?

Visual Studio 2012 mapping:

Visual Studio 2013 mapping:

Manually entered path errors:

Open Project Errors

Answer 1

In my experience this happens when visual studio is ran as an administrator. The drives are mapped for the logged in user but not for the admin user that is running visual studio. You should be able to verify this by looking at the processes in Windows Task Manager and checking which user is running visual studio.