VMware Horizon Community
janasrs
Enthusiast
Enthusiast

Missing drive mapping

Have a number of drive mappings set up and most of the time they all work, but periodically, staff will not get the drive mapping established for their home drive. Nothing horribly unique about this particular mapping, except that it uses an environmental variable to point to their specific home drive hidden share - so the "remote path" is "\\FileServerName\%username%$". This mapping seems to work 99% of the time. If it is missing, logging off generally resolves the issue. Its also possible to manually create the drive mapping when it is missing. The data is accessible via the UNC - so I can verify the resource is available.

No other drive mappings are missing when the home drive mapping is missing. The majority of the mappings that do succeed are pointing to other shares are on the same file server.

The logs don't show anything useful - other than seeing NO reference to indicate an attempt was made to create the drive mapping.

While not the worst thing, it has the potential to interfere with other things such as shortcuts which may be checking for the existence of files/folders on the mapped drive - plus it freaks out staff when they think their home drive is missing.

Any thoughts?

10 Replies
danieldietrich
Contributor
Contributor

Have you set the following GPO?

Computer Configuration\Administrative Templates\System\Logon\Always wait for the network at computer startup and logon

Best regards Daniel Dietrich VCP, VCAP, vExpert & EUC-Champion
janasrs
Enthusiast
Enthusiast

Thanks for your reply - yes, that GPO is enabled.

Reply
0 Kudos
DEMdev
VMware Employee
VMware Employee

Hi janasrs,

The logs don't show anything useful - other than seeing NO reference to indicate an attempt was made to create the drive mapping.

If there's nothing in the logs regarding that particular drive mapping, that's really weird... That would basically mean that the UEM agent did not see the XML configuration file for that drive mapping.

If the drive does not get mapped during logon, does a FlexEngine.exe -UemRefreshDrives during the session make it show up?

janasrs
Enthusiast
Enthusiast

I have not tried that - but next time its reported I will see if that is successful. Thanks for your suggestion.

DEMdev
VMware Employee
VMware Employee

Hi janasrs,

Please keep me posted, as this is a scenario I've never seen before.

Reply
0 Kudos
janasrs
Enthusiast
Enthusiast

It happened to a different user today and the -UEMRefreshDrives did seem to fix it. I'm suspecting this is an AppVolumes issue - thinking one of the appstacks are using g: during startup.

I did see this in the log from the point when the user logged on - which suggests it was in use when it tried to map it:

2018-05-15 07:12:13.335 [ERROR] Drive mapping refers to local drive 'G' ('G-Private drive.xml')

For the same user from the other day, I see this during the drive mapping process - which also makes me believe G: was in use when it came time to establish mappings at logon.

2018-05-11 07:11:46.905 [DEBUG] Successfully unmapped drive 'G:' ('G-Private drive.xml')

2018-05-11 07:11:46.921 [DEBUG] Set friendly name for drive 'G:' to 'G:\ - Private drive' ('G-Private drive.xml')

2018-05-11 07:11:46.921 [INFO ] Successfully mapped drive 'G:' to '\\servername\userid$' ('G-Private drive.xml')

I thought I had run into g: drive issues early on in our use of Appstacks, so I thought I resolved that, but perhaps a new one that I've introduced into the environment is causing these issues.

DEMdev
VMware Employee
VMware Employee

Hi janasrs,

[ERROR] Drive mapping refers to local drive 'G' ('G-Private drive.xml')

Yes, having the drive letter in use by a disk would definitely prevent UEM from mapping that drive.

2018-05-11 07:11:46.905 [DEBUG] Successfully unmapped drive 'G:' ('G-Private drive.xml')

2018-05-11 07:11:46.921 [DEBUG] Set friendly name for drive 'G:' to 'G:\ - Private drive' ('G-Private drive.xml')

2018-05-11 07:11:46.921 [INFO ] Successfully mapped drive 'G:' to '\\servername\userid$' ('G-Private drive.xml')

The first line indeed indicates that G: was already in use, but as a drive mapping. Those we can unmap (if you so configure your drive mapping); that does not apply for "physical" drive letters, though... :slightly_smiling_face:

VMvvol
Enthusiast
Enthusiast

Hi UEMDev,

I am also having this problem one's in a while, my network share are mapping based on one script file

Any one know why app volumes are using those drive letters?

Thank you,

Volga.

Reply
0 Kudos
Sravan_k
Expert
Expert

I think app volumes app stacks will attache to c: drive [some thing like snapvolumes]

You can find it from task manager under performance tab -disk's... [it should show like this C: [snapvolumes\....]]

Thank you,

vKmr.

Reply
0 Kudos
DEMdev
VMware Employee
VMware Employee

Hi VMvvol,

Any one know why app volumes are using those drive letters?

Although quite a few people in the UEM forum are also using App Volumes, it's probably better to ask this question in the App Volumes forum.

Reply
0 Kudos