When working with FIM, you’ll need to access some of the folders on your FIM servers more frequently. like C:\Program Files\Microsoft Forefront Identity Manager\2010\Synchronization Service\Extensions.
It would be far more easier to have a drive letter for it, right?
You’ll find plenty of articles on the net to map a drive letter to a directory.
It’s fairly easy to use the subst command.
From the subst help (via command prompt: subst /?)
Associates a path with a drive letter.
SUBST [drive1: [drive2:]path] SUBST drive1: /D
drive1: Specifies a virtual drive to which you want to assign a path.
[drive2:]path Specifies a physical drive and path you want to assign to a virtual drive.
/D Deletes a substituted (virtual) drive.
Type SUBST with no parameters to display a list of current virtual drives.
subst z: “C:\Program Files\Microsoft Forefront Identity Manager\2010\Synchronization Service\Extensions”
The disadvantage of the subst command is, it dissapears when you reboot.
If you prefer a more permanent solution, use the registry (sample below is Windows 2008 based..Regedit v5.)
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\DOS Devices]
“Z:”=”\\??\\C:\\Program Files\\Microsoft Forefront Identity Manager\\2010\\Synchronization Service\\Extensions”
or you add it manually (in that case, add a new string value to the DOS Devices key.
Value: \??\C:\Program Files\Microsoft Forefront Identity Manager\2010\Synchronization Service\Extensions
You could also put the subst command in a batch file and run it on startup (by putting the script in the startup folder).
Some other solutions suggest to use a drive mapping, but keep in mind that network security and share security comes in play.
Which usually is another layer or complexity on top of a simple solution.
A good FIM admin is
lazy, sorry, time efficient but effective.