Hi, I am having issues trying to map drives based on IP Addresses using Powershell. We have four locations with the following IP, Location1 20.30.40_ Location2 20.30.50_ & so on. Currently I have the below setup;

PowerShell Script To Map NetworkDrive based on IP Address

$ErrorActionPreference = "SilentlyContinue"

$Shell = New-Object -Com WScript.Shell
$Network = New-Object -Com WScript.Network
$UserName = $Network.UserName
$User = Get-ADUser -Indentity $UserName

$Computer = "."
$Nic = Get-CimInstance -Computer $computer -class Win32_NetworkAdapterConfiguration -Filter IPEnabled = True"
Foreach ($Item in $colItems {
ForEach $Address in $IPAddress) {
$IPAddress = Split($Address, ".")
If (($IPAddress[0] -ne 10) -And ($IPAddress[1] -ne 20) {$Address = $IPAddress[2]}
}
}

If $IPAddress[0] -EQ 20 And $IPAddress[1] -EQ 30 And $IPAddress[2] -EQ 40 Then

Get-PSDrive S | Remove-PSDrive
New-PSDrive -Name "S" -Root "\\wide\setup" -Persist -PSProvider "FileSystem"

If $IPAddress[0] -EQ 20 And $IPAddress[1] -EQ 30 And $IPAddress[2] -EQ 50 Then

Get-PSDrive P | Remove-PSDrive
New-PSDrive -Name "P" -Root "\\wide\prog" -Persist -PSProvider "FileSystem"

Hello Waqkas,

Coincidentally, I was working on something similar recently. The first issue I see is IPAddress from Win32_NetworkAdapterConfiguration will include the IPv6 address as well. I have a vbs script that pulls just the IPv4 address. It should work in this scenario, will a little tweeking.

Is there more to your script? Your for each loops use $colItems and $IPAddress ($IPAddresses?) as collections to loop through, but I don't follow where those were assigned any values. Something like $IPAddress = $nic.IPAddress (but this includes IPv6, which we will have to remove)

There are a few typos, but guessing that is from retyping the script into the forum post

I will see what I can come up with,, having your full script would be helpful.

Thanks for watching,
Mike

@Mike-Rodrick Hi Mike,
I have ran the script in ISE & I am now currently getting an error on the below;

If ($IPAddress[0] -EQ 20 -And $IPAddress[1] -EQ 30 -And $IPAddress[2] -EQ 40)

Here is the full script;

PowerShell Script To Map NetworkDrive based on IP Address

$ErrorActionPreference = "SilentlyContinue"

$Shell = New-Object -Com WScript.Shell
$Network = New-Object -Com WScript.Network
$UserName = $Network.UserName
$User = Get-ADUser -Indentity $UserName

$Computer = "."
$Nic = Get-CimInstance -Computer $computer -class Win32_NetworkAdapterConfiguration -Filter IPEnabled = "True"
Foreach ($Item in $colItems) {}
ForEach ($Address in $IPAddress) {
$IPAddress = Split($Address, ".")
If (($IPAddress[0] -ne 20) -And ($IPAddress[1] -ne 30)) {$Address = $IPAddress[2]}
}

If ($IPAddress[0] -EQ 20 -And $IPAddress[1] -EQ 30 -And $IPAddress[2] -EQ 40)

Get-PSDrive S | Remove-PSDrive
New-PSDrive -Name "S" -Root "\\wide\setup" -Persist -PSProvider "FileSystem"

Get-PSDrive J | Remove-PSDrive
New-PSDrive -Name "J" -Root "\\wide\jet" -Persist -PSProvider "FileSystem"

Get-PSDrive P | Remove-PSDrive
New-PSDrive -Name "P" -Root "\\wide\prog" -Persist -PSProvider "FileSystem"

If ($IPAddress[0] -EQ 20 -And $IPAddress[1] -EQ 30 -And $IPAddress[2] -EQ 50)

Get-PSDrive F | Remove-PSDrive
New-PSDrive -Name "F" -Root "\\wide\support" -Persist -PSProvider "FileSystem"

Get-PSDrive G | Remove-PSDrive
New-PSDrive -Name "G" -Root "\\wide\livedata" -Persist -PSProvider "FileSystem"

Add-Type -AssemblyName PresentationFramework
[System.Windows.MessageBox]::Show("All drives have now been mapped. Please click ok to continue")

Hey Waqkas,

See if this will work for you. I went a slightly different route. Instead of using Get-CimInstance to get the IPv4 address, I used Test-Connection, which returns a Win32_PingStatus object that can be manipulated. I also added the -Persist and -Scope options to the New-PSDrive cmdlet, to make the mapped drives available outside the PowerShell session (File Explorer and other apps) and survive reboots.

I would want to add some error handling to the script, just suppressing them isn't the best way to go, but I wanted to get you the code I had so far. I also left out the MsgBox, since it wasn't really checking to see if the drives actually mapped successfully.

$ErrorActionPreference = "SilentlyContinue"

# Get IPv4 address and convert to string type
$ipv4 = (Test-Connection -ComputerName $env:computername -count 1).IPV4Address.ipaddressTOstring

# Create array of octet values
$sub = $ipv4.Split('.')

# Check first and second octet values for match
if ($sub[0] -eq 20 -and $sub[1]-eq 30) {

    # Map drives based on third octet
    if ($sub[2] -eq 40) {
        New-PSDrive -Name "S" -PSProvider FileSystem -Root \\wide\setup -Persist -Scope Global
        New-PSDrive -Name "J" -PSProvider FileSystem -Root \\wide\jet -Persist -Scope Global
        New-PSDrive -Name "P" -PSProvider FileSystem -Root \\wide\prog -Persist -Scope Global
    }
    elseif ($sub[2] -eq 50) {
        New-PSDrive -Name "F" -PSProvider FileSystem -Root \\wide\support -Persist -Scope Global
        New-PSDrive -Name "G" -PSProvider FileSystem -Root \\wide\livedata -Persist -Scope Global
    }
}

Hope this helps, let me know if it works or if you need more help.

Thanks for watching!

@Mike-Rodrick Hi, Thank you very much, this is exactly what I was looking for. It worked perfectly.

Just another thing, Is there a way to make the powershell work by double clicking .ps1 file?

@Mike-Rodrick Is there a way I can run the script with the Local Area Connection & Wireless Network enabled at the same time? Currently I have to disable the wireless to get the script to run.

Hey @Waqkas-Ahmed,

Glad to help!

It is by design that .ps1 files do not execute when you double-click on them. This is for security. An easy way to spread malware was to send someone a .vbs script, hoping they would not pay attention and double-click it to open it. The script would execute and now they are infected. There is probably a way to hack the registry to get .ps1 scripts to run when double-clicked, or you could create a .bat file that called the .ps1 file, then a shortcut to call the .bat file. Just thinking out loud, lol.

How are you distributing the script? I would suggest using Group Policy and add the .ps1 file as a logon script. This would eliminate the need to run the script manually.

I'm not sure why the script isn't working with the wireless adapter enabled. I am able to run it on my laptop which has one wired adapter, one wireless adapter, and several virtual adapters for VMWare. What error are you getting?

Mike

@Mike-Rodrick I have just double checked. Our IP for the wireless is different. Any way I can add that to the script. Location 1 IP 20.20.40_
Location 2 IP 20.20.50_ etc...

Regarding the the double click. I will add it to the group policy at logon.

Thanks.

@Mike-Rodrick I have managed to add to the script to get it working with wireless IP.

Thanks for your help.