Powershell – Create network shared folder using Powershell on Windows 7

network-sharepowershell

I need to create a shared network folder on windows 7 using PowerShell – I cant get access to New-SmbShare as this is for windows 8 and Windows 2012 Server – any examples would be great.

Am I limited to WMI calls?

Best Answer

Copy-paste ready version:

function New-Share ($foldername, $sharename) { 
    if (!(test-path $foldername)) { 
        new-item $foldername -type Directory } 

    if (!(get-wmiObject Win32_Share -filter “name='$sharename'”)) { 
        $shares = [WMICLASS]”WIN32_Share”

        if ($shares.Create($foldername, $sharename, 0).ReturnValue -ne 0) {
            throw "Failed to create file share '$sharename'"
        }
    }    
}

Related Solutions

Powershell – Determine Users Accessing a Shared Folder Using PowerShell

I came up with the following script:

$computer = "LocalHost"
$namespace = "root\CIMV2"
$userSessions = Get-WmiObject -class Win32_ServerConnection -computername $computer -namespace $namespace

if($userSessions -ne $null)
{
    Write-Host "The following users are connected to your PC: "

    foreach ($userSession in $userSessions)
    {
        $userDetails = [string]::Format("User {0} from machine {1} on share: {2}", $userSession.UserName, $userSession.ComputerName, $userSession.ShareName)
        Write-Host $userDetails
    }    

    Read-Host
}

The following articles were useful:

As always, if you can't find a way to do it in PowerShell, see if someone has done something similar in C#.

Slow shared folder refresh on windows 7

I had exactly the same issue but with Samba 4 exports and Windows 7 clients. It is definitely client side error. After some thorough troubleshooting, I simply added the registry key and it worked like a charm after hitting the F5 button once.

Only had to add this registry key:

DirectoryCacheLifetime[DWORD] = 0

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Lanmanworkstation\Parameters

The values mentioned in this article seem to be invalid, as these registry values no longer exist. I believe that the default expiry time for the cache is 10 minutes rather than 10 seconds. http://technet.microsoft.com/en-us/library/ff686200%28v=ws.10%29.aspx

UPDATE(20/04/2015)

If you are interested in applying this on server side without the need to configure the clients you must add the following line in the [global] section within smb.conf:

server max protocol = SMB2_02

This will limit the server down to protocol SMB2 rather than the default SMB3 which comes with Samba 4 but it compromises the transfer speed. I believe that protocol SMB2_02 is an early version of SMB2 which doesn't support caching, so it should work in this case.

However I noticed that a few clients were still experiencing caching issues and had to manually change registry as described above.

Unfortunately there isn't much documentation about the various SMB protocol versions. Here is what the man page for smb.conf says about this:

Reference: https://www.samba.org/samba/docs/man/manpages-3/smb.conf.5.html#SERVERMAXPROTOCOL

Best Answer

Related Solutions

Powershell – Determine Users Accessing a Shared Folder Using PowerShell

Slow shared folder refresh on windows 7

Related Topic