AWS Thinkbox Discussion Forums

Win8 Client install & Network Paths

Deprecated Deadline 6 Bug Reports
#1

Hi Ryan,

I’ve installed D6 beta 14 and 15 on Win8 (both upgrade and clean install) and both times when asked for the repository location my mapped networked drives weren’t in the directory list.

I had to manually type \server\share for it to go forward.

I didn’t have this problem on Win Server 2008.

Is this a known issue or unique to me?

#2

This is in the Client Installer right? I wonder if it’s a limitation of the folder browser control that our installer software uses, although after looking at it, it looks like the typical Windows folder browser control. You’re looking under the Computer section in the browser right? I have no idea why it wouldn’t be there…

Cheers,

  • Ryan
#3

This also happens for me on a clean install of Windows 7 with the latest version of the Deadline Client Beta (RC3). It seems you cannot browse to any network location (be it a mapped network drive or a network location) You also cannot manually type any location with a mapped network drive, but you can type in a network location.

i.e…

  • Browsing for a Deadline6 repository on a network machine in the installer doesn’t work.
  • Manually typing in a server location which is mounted to a drive letter (e.g. R:\DeadlineRepository) does not work
  • Manually typing in a server location to an unmounted machine (e.g. \DeadlineServer\DeadlineRepository) DOES work
#4

I can’t reproduce this here, on Windows 7 or Windows 8. I’m able to browse to my mapped drives under Computer, and I can them in without any complaints.

When you run the client installer, are you running it as a user that’s different than the logged in user? For example, are you using a network admin account? Mapped drives are only mapped for the current user, so if you’re running the installer as a different user, that would explain this.

Cheers,

  • Ryan
#5

I’m running the installer as the logged in user, who has admin rights. My mapped network drive that I want to connect to is a linux samba share. Other than that, I can’t give you any more info. Sorry!

#6

So I was actually able to reproduce this on my machine (Win8), and I’m pretty sure it has to do with UAC, and running things in the Admin context (which is required for our installer). I have no idea why it works for Ryan, but I’ve experienced this outside of our installer as well (Python scripts run as administrator can’t find mapped drives for me, for example). I did a bit of googling and found this thread (apparently this has been around since Vista):
vistaheads.com/forums/micros … rives.html

Privacy | Site terms | Cookie preferences