Thursday, June 21, 2012 4:31 PM
I have been using mdt 2010 for a while to deploy images since the 2010 release and did not have any problems
lately all images deployed with mdt 2010 recent and earlier deployments are having what appears to
be a virtual drive "Subst" mapped as drive z:
i can remove teh mapping using subst z: /d but it returns after restart ?
is this being caused by any updates ? how i stop them form coming back ?
Thursday, June 21, 2012 7:57 PM
MDT uses the first available drive (counting backwards from Z:) to the deploymentshare and SLShareDynamicLogging property. When deployment is done MDT removes all existing network connections (even the ones MDT did not map). The subst command is not persistent that I know of.
There are two things you can check.
1) with msconfig.exe. Look at the autostart items and see if you can find any subst command.
2) check registry "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\DOS Devices" and see if you have a Z: command there.
Tuesday, August 07, 2012 5:57 PM
Thanks for the response i could not find any reference on keys you mentioned, but then i decided to search the register for just Z:
We recently started to use Uniprint on our Citrix environment and then captured images contain the Uniprint client that is creating the virtual drive Z: to point to the temp folder on a registry Key.
I am not sure i f i can remove the Key, but now i know is not related to MDT or the task sequences.
Thursday, October 18, 2012 8:02 AM
we had the same Problem, you're running UniPrint i think, and because of the new version theres a registry Key "Preferredvirtualdrive", which is set to X on default.
you can find em under "HKEY_CURRENT_USER" - "Software" - "UniPrint" - "Client".
Hope this helps to you, what i did not find out is whether this subst is necessary or not. Would be interesting, at the moment we're moved the driveletter to Q:, but if we could disable this drive mapping instead of changing the letter would be more nice.
sorry for bad english, and hope this helps you :)
Friday, May 17, 2013 3:10 AM
Not sure if you ever found a fix for this. I had the same issue and also thought it was something to do with my MDT build. Found the fix on the UniPrint forums and here it is.
You can disable the VirtualDrive for all users by creating the registry key HKLM\\Software\UniPrint\Client and create a new DWORD named "DisableVirtualDrive" and set the value to "1"
Hope this helps
- Proposed As Answer by Stephan Schwarz Monday, May 20, 2013 1:13 PM