Mapping Drive Letters

I have OS X Server 10.4.8 running in a school with all Windows PCs. I'm trying to figure out how to get the PCs to authenticate to the OS X server and upon logging in, map several share points on the server to drive letters on the clients (PCs). I know WGM offers a place to map the home directory, but what about other share points and drive letters.
I'd like this to happen automatically like through a login script or something.

In the OS X Server's /etc directory, you will find a netlogon directory. It is the default location for login scripts if you are running a Windows domain.
The script for which you are looking will look something like this:
net use Y: \\WINDOWSSERVERNAME\SHARENAME
This command will mount the Windows sharepoint on the Windows server you specify to the Y: drive on the client machine. Just save this command into a text file : /etc/netlogon/login.bat
If you have multiple shares to mount, just use the same format with different drive letters in the batch file. If you learn some Windows scripting, you can do fancier things, like clear out existing drive mappings before mounting the network drives.
There is a spot in Workgroup Manager to set the Windows login script for users at the individual level, if you want to mount different drives for different people.

Similar Messages

Little Known Fact About Mapping Drive Letters

It's easy enough to create a shared folder on one computer and map a drive letter to access the folder on a different computer. Usually the mechanism behaves flawlessly with a hiccup here and there. But, did you know, that a logged on session has two sets
of drive letters? It's true. You create drive letters whilst not running as administrator and you access those drive letters whilst running as not administrator. But, the moment you run as administrator, those drive letters vanish without a peep of explanation
from Windows. However, you are free to create drive letters as administrator and access those drive letters as administrator. I'm sure there is a very good technical reason for this. Something about a security token being different between the two states.
But that does not forgive whoever is responsible for warning the end users about this.
MARK D ROCKMAN

you are correct when you log on even as administrator your rights are still a user, when you attempt a task that requires the administrator privilege you are elevated to that level, if you have UAC turned on you would see the box come up. this is to inform
you that you are now running under administrator privileges, this is by design, this is also what happens when you run the command prompt as a administrator. It's mostly for security reasons imagine a virus or a program being able to launch a elevated
command and basically taking over the networks shared information simply because you opened a command prompt wit admin rights.
Microsoft has many people that keep saying "how come I can do this and access this" they then publish their findings and the malicious software people take advantage of the security hole so they have to patch, you shouldn't be mad at Microsoft
"I don't work there" be mad at the people creating malicious code.

Re-Map drive letters on Windows 7 in bootcamp...

Hello computer geniuses....
I have an early 2008 macbook pro running Mountain Lion and Windows 7 via bootcamp.
My problem: My job requires that I constantly conect to dropbox to share projects with co-workers. Recently we changed the drive path for dropbox from the c: drive to the d: drive.
So... Is there a way to create a D: drive in a windows 7 bootcamp partition? Or, is there a way to install windows 7 via bootcamp with D: as the drive letter instead of C:
Thanks everyone

This is how to do it but read the CAUTION below before proceeding!!!!
In Windows you need to go to
Control Panel
then open
Administrative Tools
In Administrative Tools select
Computer Management..
You now need to go to Storage and open
Disk Management
After Disk Management opens you'll be able to see all your Drives represented.
Find Your C: Drive and Right Click the C: Drive
A Submenu will now open up.
Select Change Drive Letter and Path
You now can select the Change Button in that window.
Another window opens and select
Assign The Following Drive Letter, click the arrow key and select D: as the new drive letter.
OK everything and when you reboot the C: Drive will now be Drive D:.
CAUTION
BE AWARE THAT IF YOU HAVE INSTALLED ANY APPLICATIONS ON THE C: DRIVE WINDOWS WILL BE LOOKING TO FIND THEM ON DRIVE C: WHICH NO LONGER EXISTS.
Window will display an error message about the Program being MIA and ask you to locate it for Windows.
You will have to browse to the program so Windows can find it.

Creating a symlink directory on a network share to a path below a mapped drive letter, local path, or UNC path does not work

Am I correct in assuming I can not create a `symlinkd` to a network share, local path, or a UNC path on a network share that will be accessible by clients?
###Mapped drive letters don't work:
1) navigate to a network share:
pushd \\windows2008server\share\
2) make a hardlink:
mklink /d test_sharedir t:\directory\
dir .\test_sharedir
#Directory of Z:\test_sharedir
#File Not Found
UNC paths don't work:
1) navigate to a network share:
pushd \\windows2008server\share\
2) make a symlink:
mklink /d test_dirunc \\windows2008server\share
dir .\test_dirunc
#Directory of Z:\test_dirunc
#File Not Found
I can create a functional `symlinkd` on a local drive to a mapped drive letter or a UNC path.
Are my assumptions above correct?
We are in the middle of a migration and have created two symlinkd to UNC paths for shared DLLs, one below c:\windows\system32\ (directing to a share containing 64-bit DLLs) and one below c:\windows\syswow64 (directing to a share containing 32-bit DLLs).
On the file server, we have had a path to 32-bit DLLs (from Windows 7 clients: s:\dll\). I am attempting to rename this directory so that it is accessible via "s:\dll32\" and would like to create a symlinkd that links "s:\dll" to
"s:\dll32" [again where S: is a mapped drive on a Windows 2008 server]. How do I do this?
Thanks,
Matt

Hello Mandy,
The link you sent me is for Netapp CIFS server daemon contained within DataOnTap (the Netapp OS) to follow symlinks. I am inquiring about the Microsoft products Windows Server and Windows 7.
To gain a better understanding of the Microsoft Windows Server and client (Windows) CIFS stacks and interaction of the stacks, I have referred to Figure 6 "Server Message Block Server Model" within the following (albeit older) document: http://download.microsoft.com/download/2/8/0/2800a518-7ac6-4aac-bd85-74d2c52e1ec6/tuning.doc
You will see the following:
I assume that the Windows Server CIFS server service must be "smart enough" to determine that a CIFS client is attempting access to a SYMLINKD and actually fill the request by following the SYMLINKD. The CIFS server service does not appear
to operate like this.
1) Am I correct in my assumption that the CIFS client (redirector) and the CIFS server (server) do not following symbolic links (whether they be file or directory)?
2) If not, how do I submit a feature request for this so that it can be reviewed and approved or not approved for inclusion/hotfix release?
Thanks for your time,
Matt Brown
[UPDATE]
Note that you can use a `directory junction` instead of using a SYMLINKD, to link to LOCAL resources (source). However, `directory junctions` do not allow access to resources over UNC.

Scipt to prompt and authenticate users to AD and then map 2 next available drive letters to 2 network shares

Hi,
So I have been trying to write some code that will
prompt users to authenticate to AD and use that authentication to map the next 2 available drive letter to two network shares.
I have adopted using the HAT format as this provides me with the ability to prompt for a username and password and authenitcate to AD.
<script language="vbscript">
Function setSize()
window.resizeTo 350,300
Window.moveTo (screen.width-240)/2, (screen.height-600)/2
End Function
Function cmdSubmit_OnClick()
Dim strUser 'User Name variable
Dim strPW 'User Password variable
if auth.username.value = "" Then
msgbox ("ERROR: No User account information provided. Please Try Again!")
cmdSubmit_OnClick = False
Elseif auth.password.value = "" Then
msgbox ("ERROR: No User account information provided. Please Try Again!")
cmdSubmit_OnClick= False
Else
strUser = auth.username.value
strPW = auth.password.value
Authenticate strUser, strPW
End If
End Function
Public Sub Authenticate (Byref strUser, Byref strPW)
On Error Resume Next
Const ADS_SECURE_AUTHENTICATION = &H1
Const ADS_SERVER_BIND = &H200
Dim strPath 'LDAP path where the Users accounts are listed
Dim LDAP 'Directory Service Object reference variable
Dim strAuth 'Parses the User Name and Password through the DSObject
strPath = "LDAP://fanzldap.au.fjanz.com/rootDSE"
Set LDAP = GetObject("LDAP://company/rootDSE")
Set strAuth = LDAP.OpenDSObject(strPath, strUser, strPW, ADS_SECURE_AUTHENTICATION Or ADS_SERVER_BIND)
If Err.number <> 0 Then
intTemp = msgbox(strUser & " could not be authenticated", vbYES)
if intTemp = vbYes Then
'window.location.reload()
End If
Else
For Each obj in strAuth
If obj.Class = "user" Then
If obj.Get("samAccountName") = strUser Then
msgbox ("Success! " & strUser & " has been authenticated with Active Directory")
window.close()
Set wShell = CreateObject("Wscript.shell")
wShell.run "Firstletterali.vbs"
End If
End If
Next
End If
End Sub
</script>
<head>
<body style="background-color:#B0C4DE">
<img src=Title.jpg><br>
<HTA:APPLICATION
APPLICATIONNAME="User Login"
BORDER="thin"
SCROLL="no"
SINGLEINSTANCE="yes"
WINDOWSTATE="normal">
<title>NAS Authentication</title>
<body onload="vbs:setSize()">
<div class="style2">
<h3>NAS Archive Authentication</h3>
</div>
<form method="post" id="auth" name="auth">
<span class="style3"><strong>User Name:  </strong></span>
<input id="Username" name="Username" type="text" style="width: 150px" /><br>
<span class="style3">
<strong>Password:     </strong></span>
<input id="password" name="password" type="password" style="width: 150px" /><br><br>
      
<input type="submit" value="Submit" name="cmdSubmit" />
<input type="button" value="Exit" onclick="self.close()">
</form>
</body>
</html>
using the above I can succefully authenticate users but I cant work out how to then use that authenticattion to map the next to available drive letters to a network source.
The code I have for that is
Option Explicit
Dim strDriveLetter, strRemotePath, strRemotePath1, strDriveLetter1
Dim objNetwork, objShell
Dim CheckDrive, DriveExists, intDrive
Dim strAlpha, strExtract, intAlpha, intCount
' The section sets the variables
strRemotePath = "\\mel\groups\Team\general"
strRemotePath1 = "\\mel\groups\Team\specific"
strDriveLetter = "B:"
strDriveLetter1 = "H:"
strAlpha = "BHIJKLMNOPQRSTUVWXYZ"
intAlpha = 0
intCount = 0
err.number= vbEmpty
' This sections creates two objects:
' objShell and objNetwork and then counts the drives
Set objShell = CreateObject("WScript.Shell")
Set objNetwork = CreateObject("WScript.Network")
Set CheckDrive = objNetwork.EnumNetworkDrives()
' This section operates the For ... Next loop
' See how it compares the enumerated drive letters
' With strDriveLetter
On Error Resume Next
DriveExists = False
' Sets the Outer loop to check for 24 letters in strAlpha
For intCount = 1 To 24
DriveExists = False
' CheckDrive compares each Enumerated network drive
' with the proposed drive letter held by strDriveLetter
For intDrive = 0 To CheckDrive.Count - 1 Step 2
If CheckDrive.Item(intDrive) = strDriveLetter _
Then DriveExists = True
Next
intAlpha = intAlpha + 1
' Logic section if strDriveLetter does not = DriveExist
' Then go ahead and map the drive
'Wscript.Echo strDriveLetter & " exists: " & DriveExists
If DriveExists = False Then objNetwork.MapNetworkDrive _
strDriveLetter, strRemotePath
call ShowExplorer ' Extra code to take you to the mapped drive
' Appends a colon to drive letter. 1 means number of letters
strDriveLetter = Mid(strAlpha, intAlpha,1) & ":"
' If the DriveExists, then it is necessary to
' reset the variable from true --> false for next test loop
If DriveExists = True Then DriveExists = False
Next
WScript.Echo "Out of drive letters. Last letter " & strDriveLetter
WScript.Quit(1)
'Sub ShowExplorer()
'If DriveExists = False Then Wscript.Echo strDriveLetter & " Has been mapped for archiving"
'If DriveExists = False Then objShell.run _
'("Explorer" & " " & strDriveLetter & "\" )
'If DriveExists = False Then WScript.Quit(0)
'End Sub
On Error Resume Next
DriveExists = False
' Sets the Outer loop to check for 24 letters in strAlpha
For intCount = 1 To 24
DriveExists = False
' CheckDrive compares each Enumerated network drive
' with the proposed drive letter held by strDriveLetter1
For intDrive = 0 To CheckDrive.Count - 1 Step 2
If CheckDrive.Item(intDrive) = strDriveLetter1 _
Then DriveExists = True
Next
intAlpha = intAlpha + 1
' Logic section if strDriveLetter1 does not = DriveExist
' Then go ahead and map the drive
'Wscript.Echo strDriveLetter1 & " exists: " & DriveExists
If DriveExists = False Then objNetwork.MapNetworkDrive _
strDriveLetter1, strRemotePath1
call ShowExplorer ' Extra code to take you to the mapped drive
' Appends a colon to drive letter. 1 means number of letters
strDriveLetter1 = Mid(strAlpha, intAlpha,1) & ":"
' If the DriveExists, then it is necessary to
' reset the variable from true --> false for next test loop
If DriveExists = True Then DriveExists = False
Next
WScript.Echo "Out of drive letters. Last letter " & strDriveLetter1
WScript.Quit(1)
Sub ShowExplorer()
If DriveExists = False Then Wscript.Echo strDriveLetter & " Has been mapped for archiving"
If DriveExists = False Then objShell.run _
("Explorer" & " " & strDriveLetter & "\" )
If DriveExists = False Then WScript.Quit(0)
End Sub
Now the above script will find the next availabe letter and map one location to it...I still havent worked out to create another loop for it to do it again. It obviously also requires that you already be authenticated to map to that location.
I looking for some help on how to marry these to scripts together.
Thanks
Ali

Hi Ali
Here is some code that will enumerate two free adjacent drive letters. It starts searching from "C" all the way to "Z" for two drives letters that are adjacent and returns the results in an array then echos the results. You can easily adapt this code to
map your network drives to each drive letter. Hope that helps
Cheers Matt :)
Option Explicit
Dim objFSO
On Error Resume Next
Set objFSO = CreateObject("Scripting.FileSystemObject")
ProcessScript
If Err.Number <> 0 Then
WScript.Quit
End If
On Error Goto 0
'Functions Processing Section
'Name : ProcessScript -> Primary Function that controls all other script processing.
'Parameters : None ->
'Return : None ->
Function ProcessScript
Dim driveLetters, driveLetter
If Not GetFreeDrives(driveLetters) Then
Exit Function
End If
For Each driveLetter In driveLetters
MsgBox driveLetter, vbInformation
Next
End Function
'Name : GetFreeDrives -> Searches for a pair of free adjacent drive letters.
'Parameters : adjacentDrives -> Input/Output : variable assigned to an array containing the first two free adjacent drives.
'Return : GetFreeDrives -> Returns True if Successful otherwise returns False.
Function GetFreeDrives(adjacentDrives)
GetFreeDrives = False
Dim drive, driveLetter, drivesDict, i
Set drivesDict = NewDictionary
driveLetter = "C"
'Add the drives collection into the dictionary.
For Each drive In objFSO.drives
drivesDict(drive.DriveLetter) = ""
Next
'Check drive letters C: to Z: for two free adjacent drive letters and set the "driveLetter" variable to the first one.
For i = Asc(driveLetter) To Asc("Z")
If Not drivesDict.Exists(Chr(i)) And Not drivesDict.Exists(Chr(i + 1)) Then
driveLetter = Chr(i)
Exit For
End If
Next
'If two free adjacent drive letters were not found then exit.
If driveLetter = "" Then
Exit Function
End If
adjacentDrives = Array(driveLetter, Chr(Asc(driveLetter) + 1))
GetFreeDrives = True
End Function
'Name : NewDictionary -> Creates a new dictionary object.
'Parameters : None ->
'Return : NewDictionary -> Returns a dictionary object.
Function NewDictionary
Dim dict
Set dict = CreateObject("scripting.Dictionary")
dict.CompareMode = vbTextCompare
Set NewDictionary = dict
End Function

Report on remote users mapped drives

After a very thorough search, I can't find anyone else who has had this question answered.
I have a need to on-the-fly report on the mapped drives and their letters of users on remote computers. Running "Get-WmiObject -Class Win32_MappedLogicalDisk | select Name, ProviderName" only returns my drives under my credentials, not the remote user. Looking
at HKU:\sid\network apparently only reports persisent mapped drives or drives mapped by the customer and not drives mapped by logon script that are not persistent.
There doesn't seem to be a way to do this on-the-fly which is dissapointing, so I'm hoping you'll have a trick up your sleeve!
The only way I can figure to get the information, but not on the fly, is to have a logon script run as the user and grab the info and save it somewhere. I'm really hoping not to resort to that. All of that becomes historical info and won't reflect changes
that happen after logon, so it's not going to always be a true reflection of reality.
The key seems to be running a wmi query as someone else that you don't have credentials for. Is that possible? Or do you have another suggestion?
Ian

I believe this post may already be closed. I, however, would like to add my findings: When I run this against different pc's with different users logged on: Get-WmiObject
-Class Win32_MappedLogicalDisk -ComputerName <remote computer> | select Name, ProviderName
(Keep in mind that I'm a local admin on my pc as well as the destination pc's
as well.)
1. The logged on user is non-admin on their pc.
Mapped drives are not retrieved
2. The logged on user is admin on their pc.
Mapped drives are retrieved
3. I'm logged on to the remote pc (local admin)
Mapped drives are retrieved
Conclusion: As long as the target pc logged on user is local admin on that pc then the
mapped network drives will be pulled by the previously mentioned command. Otherwise, it will come back empty.
A question posted previously was: "I'm
curious why you need to know mapped drives??" In my case, I am trying to back up mapped network drives for all domain users. However, logon or logoff scripts are not
an option.
The real question should be: Why is the previously mentioned command not pulling the mapped network drives when the logged on user is not a local admin on the target pc?
I believe the answer is that the drives are not mapped to the remote computer per se, but to the user's process on the remote computer. And while an admin on that computer has significant power over the hardware and operating system, it cannot take control
of the process, which is locked by the user's credentials.
Consider remote control. My regular account is logged onto another computer. I run mstsc to establish a remote control session on that remote system under the same credentials. The effect is to disconnect the other remote session and lock the system on its
console, and for the new session to inherit the original process, seeing the same desktop with the same apps open.
I then run mstsc to establish another remote control session, this time using an account that is an administrator on that system. It tells me my regular account is already logged on, and gives me two options, abort my new session, or log the user out. using
my admin credentials, I cannot take over the user's session and see what applications he has open or what drives he may have mapped.
Al Dunbar -- remember to 'mark or propose as answer' or 'vote as helpful' as appropriate.

DFS and Windows 7 x64 strange behavior when trying to access a DFS link through mapped drive

I've manually mapped a network drive (Q Drive) to a DFS location. Whenever I go into "My Computer" and open the Q Drive it shows the DFS links but when I double click one of the links it randomly takes me back to the "My Computer" starting point showing my standard drive letters. If I click through the Q drive and the DFS several time it all of the sudden works. Sometimes this circle of clicking can go on for 5-10 times before it works properly.
I'm running the x64 edition of Windows 7. Any suggestions on how to make this work properly? Its very annoying.

GPO mapped namespace where you can't connect through the mapped drive letter but can connect through the DFS UNC namespace? Do you use access based enumeration?
I personally think it has something to do with network bandwidth, the security token and offline files. =)
You can access the namespace itself but not any of the linked shares (try checking the ACL:s on the shares and you get permission denied, but you still see them, ie they are listed).
I found a post sometime ago about corrupted/trunkated security tokens. If the member was part of too many AD groups the token was trunkated and corrupted. That was going to be my next move. Sniff the traffic and see what actually happens when the issue occur
if theres something to be learnt there. Since it works correctly through the UNC adress but not through the drive letter you ough to be able to see what is different between the two requests.
http://blogs.technet.com/b/askds/archive/2008/05/14/troubleshooting-kerberos-authentication-problems-name-resolution-issues.aspx
One thing I noted was that it only happened to remotely connected computers on slow 3G connections (we use Direct Access). Never on LAN-connected computers with GB access or remote computers with fast (>15Mbps) access. We also use folder redirection,
which I think could be part of the problem, ie the share never goes online, atleast for us the issue was itermittent, it never happend all of the time, just from time to time. And if I disconnected and reconnected it could fix the issue for that particular
sessions, usually it didn't but occasionally it did (just pulling the network cable and put it back). Check the offline/online status the folders show up as offline even though they are online.
Enough of my ramblings. Sorry to hear you still have the problem and I hope you find a way to solve it.

Mapped drive duplicating in windows 8.1

I upgraded to Windows 8.1 a little while ago and have run Windows Update recently. For the most part, things seem to be working fine.
One issue that I have noticed is that one of my mapped drives keeps duplicating. This seems to happen after every restart, or shutdown.
I have Hyper-V set up and I mapped drive T:\ to a folder on that drive. It has been working fine for a year.
After getting the latest update for Windows 8.1, when I go into File Explorer, I will see that drive listed as all other available drive letters as well as drive T:\.
I can disconnect them, but it is a pain to have to do that over and over - I cannot map other drive letters to other folders if they are in use. I need to do that periodically for testing client issues.
I have searched the forums and did not find any open threads for this.
It is a standalone workstation that is networked with other computers but it is not on a domain. This is the only other computer I use all the time that has Windows 8.1 installed.
Please help.

Hi,
You can try clean boot to determine if a 3rd party software causes this issue.
If this is not the cause, I suggest you modify the registry value of mapped drivers to see if this issue persists:
HKEY_CURRENT_USER \ Software \ Microsoft \ Windows \ CurrentVersion \ Explorer \ Map Network Drive MRU then delete the duplicated drive path.
If this issue persists, please try another user account for test.
Regards,
Yolanda
Yolanda
TechNet Community Support
No 3rd party software is causing the issue.
I went to
HKEY_CURRENT_USER \ Software \ Microsoft \ Windows \ CurrentVersion \ Explorer \ Map Network Drive and there is only the default, nothing else.
There are no other user accounts on this machine.
mjmart61

Mapped drives and linked graphics

I have started a new position as a tech writer and have inherited files that will have to be maintained. As I am opening various files, I am finding a lot of broken links. As I investigate (by hovering over the file in the Links pallette), it appears that the basic file path is correct. But what I notice is that the drive letter on the broken ones is not the same. So for example, a link that works is Z:\Artwork\Product Name\filename.eps but a link that is broken is V:\Artwork\Product Name\filename.eps
I also find some links that work, which link to the actual networked drive name instead of a mapped name, for example \\drivename\Artwork\Product Name\filename.eps
If I try and link to a file myself, and then look at the path, it shows the path with the Mapped drive.
So first of all, I assume that the broken links are caused by a user who did not map that drive to the same letter as was used by others. Is that correct? Second, how did someone create a link to the drive name instead of the mapped drive letter? Since I am going to have to fix these broken links, Since some of these files may also be used by the marketing folks, I would like to come up with an approach so that anyone else opening the file will not encounter broken links, if they have not mapped the drives to the same letters.
Thanks for your help.

Well, either someone chose a different letter, or the drive letters were assigned from above by an IT department (and ordinary users are locked out of mapping new drives).
It's possible to map the same share twice, if you have the power to do so. So just remap V: to the same network share as Z: and you're good to go, for your own purposes. I'm not sure how you could set it up to cover the rest of your question (so that anyone else opening the file would not get the missing links dialog) without relinking everything yourself. I suppose it'd be scriptable.

In server 2008 r2 i cant prevent access to extra drive letters(apart from a,b,c,d) via gpo

in server 2008 r2 i want to prevent access to extra drives like g,h,i,j drives via GPO i have been able to successfully hide these extra drives but not able to prevent access to restrict them i have hidden these extra drive letters via code pasting
with hidedrives.adm file on right clicking adminstrative templates in GPO and adding templates but i dont know the code for preventing access to drives. HELP me need this fast

Hi Manish,
Based on your description, we can try enabling the following policy:
User Configuration\Administrative Templates\Windows Components\Windows Explorer\
Prevent access to drives from My Computer
If we enable this policy, users cannot view the contents of the selected drives in My Computer and Windows Explorer. Also, they cannot use the
Run dialog box, the Map Network Drive dialog box, or the Dir command to view the directories on these drives.
However, this policy does not prevent users from using programs to access local and network drives. And, it does not prevent them from using the Disk Management snap-in to
view and change drive characteristics.
Regarding this policy, the following article can be referred to for more information.
Prevent access to drives from My Computer
http://technet.microsoft.com/en-us/library/cc978514.aspx
Best regards,
Frank Shen

SCCM 2012 OSD with Multiple Drive letters using StandAlone Media

Hey guys I have a client who is required to partition their Windows 8.1 installation in three different partitions:
C:(OS Partition)
d:(SQLData Partition)
E:(Client Data Partition)
G:(CD-ROM)
I Already know that I should not use multiple drives for OSD but this is the requirement I have been given...
When I deploy my TS through PxE or USB Bootable Media all the drives are labeled correctly... C,D and E but if I Use Standalone USB Media then I end up with C, E and F and G as CDRom. I know that WinPE assigns a drive letter to the usb stick usually d: but
not always so how can I set the USB Standalone media to act the same way as PxE and Usb Boot Media? is there a way to have PE set the USB drive to drives latter in the alphabet? s, t or w?
Please help

Hey Joyce thanks for the response but I am not talking about the fact that the drives are labeled differently in PE I am stating that once the imaging process is complete the drive letters are not the same when doing a deployment through PxE or USB Bootable
media... When using Full standalone USB media to deploy the exact same TS the drive letter assignment is not consistent so to be as clear as I can I will explain again...
When doing a deployment from PxE, USB BOOT Media or USB BOOT Media attached to a VM, all the drives end up correct at the end of the deployment so C: is the OS drive D: is the Data Drive and E: is the Maps Drive (Keep in mind that if I do a usb
bootable media deployment and leave the USB in the computer I have the same issue as the standalone media)
But if I run the deployment from a STANDALONE USB Media then everything runs as it should but when I enter windows and look at my drive letter assignment the C: is the OS drive the D: drive is the USB the E: drive is the Data drive and G: is the Maps
Drive...
Which means to me that when windows is assigning drive letters it is assigning the USB Drive as D and not something less intrusive like y: or o:
So the question is: How can I have the drive letters assigned properly when using full standalone media So that my deployments are consistent when deploying through PxE, Usb Boot Media and USB Standalone media? Did no one ever test this out? and if so is
this what I can expect from SCCM 2012R2 For consistency to not be available across all deployment methods?

Multiple Drive Letters to Share

Hi,
We have had an issue where a PC assigned multiple drive letters to a share when it should have just assigned U:.
I have never seen this before the PC is running Windows 7 64 bit and the server with the share is Server 2008 R2. Our PDC is Server 2012.
The drives are mapped via group policy preferences.
I have noticed some CD/DVD drives mapping twice before, but this hasn't really caused an issue.
Please advise.
Kind Regards,
John

Hi,
Have you checked the log under event viewer\Applications and Sevices\Microsoft\Windows\Group Policy? Anything valuable about this issue?
You can also configuer logging and tracing about mapped drive udner Computer Configuration\Administrator Templete\System\Group Policy\Logging and Tracing\"Configure drive maps preference logging and tracing" in case this issue happens again.
Yolanda Zhu
TechNet Community Support

How To Change Map Drive for my Database?

Hi all,
I bought an external Usb Disk with 1TB storage capacity and attached it to my laptop, because I am running out of space for new 11g Database Creation.
It was mapped by default at G:\ then I created a new database 11g on it. Then during night time, I shutdown my laptop and remove my external disk.
Next morning I startup my laptop again and attached by external disk. But to my surprise it is mapped as E:\ so I can not startup my database :(
How can I switch it back to G:\ please.
Thanks a lot.

KinsaKaUy? wrote:
Hi all,
I bought an external Usb Disk with 1TB storage capacity and attached it to my laptop, because I am running out of space for new 11g Database Creation.
It was mapped by default at G:\ then I created a new database 11g on it. Then during night time, I shutdown my laptop and remove my external disk.
Next morning I startup my laptop again and attached by external disk. But to my surprise it is mapped as E:\ so I can not startup my database :(
How can I switch it back to G:\ please.
Thanks a lot.
Hi,
Right click on my computer, choose manage, choose disk management under storage, choose your external drive, right click and choose change drive letters and path, change it to G:
Cheers

Replace Mapped Drives with UNC Paths via Group Policy Preferences

We are currently using Group Policy Preferences to map network drives to drive letters for our users. Given the risk of ransomware, etc. these days we want to provide users with a UNC link rather than a mapped drive letter. Can anyone tell me
the best way to do this?
Thanks,
Joe

> We are currently using Group Policy Preferences to map network drives to
> drive letters for our users. Given the risk of ransomware, etc. these
> days we want to provide users with a UNC link rather than a mapped drive
> letter. Can anyone tell me the best way to do this?
Create shortcuts :)
Martin
Mal ein
GUTES Buch über GPOs lesen?
NO THEY ARE NOT EVIL, if you know what you are doing:
Good or bad GPOs?
And if IT bothers me - coke bottle design refreshment :))

Drive Letters in ise

I know that existing network drive letters don't appear in the PowerShell ISE. Is there any workaround for this?
Example:
My login script includes a couple of mapped drives.
F: \\main\home\
U: \\main\data
W: \\main\warehouse
With the normal powershell command line, these drives are accessible.
But in the ISE, they don't show up at all with Get-PSDrive.
With NET USE the drive letters are there, but are shown as "unavailable"
PS>net use
New connections will be remembered.
Status Local Remote Network
Unavailable F: \\192.168.219.55\larryk Microsoft Windows Network
Unavailable U: \\192.168.219.55\main Microsoft Windows Network
Unavailable W: \\192.168.219.55\warehouse Microsoft Windows Network
Unavailable X: \\192.168.219.55\main\it\newsletters\gwk Microsoft Windows Network
The command completed successfully.
Unless I'm not correct, this makes it tough to write a PowerShell script that works both in the ISE and at the regular PS command line. Or, what am I missing?
-- L

Hi, Bill...
I'm using PowerShell to query a database and then write the results to a shared network folder on a Linux server which is mapped to a drive letter. I'm using the ISE... (I *love* the ISE), and it just would be a lot easier if had those
mapped drives available. I'm thinking that the workaround is to execute test-path to test whether the path is usable. If the test-path returns false, then map a temporary drive. But it seems like a bit of a kludge, and I wasn't sure if there was
some best practice that I was missing.
I'm also curious to know why the drives are visible, but inaccessible, in the ISE.
Does the ISE actually create a separate environment different from, or "on top of" the normal PS command line environment?
And, why doesn't the ISE session inherit the mapped drives?
--- L

Mapping Drive Letters

Similar Messages

Maybe you are looking for