Disconnect from smb share with powershell on Windows 10
I'm trying to disconnect a smb share with a Powershell command in Windows 10:
net use * /delete
However, this command does not work, because the share is not shown with net use. The output is There are no entries in the list.
Get-SmbConnection is showing the results I'd expect,
ServerName ShareName UserName Credential Dialect NumOpens
---------- --------- -------- ---------- ------- --------
FILESERVER extra xxxxxxxx xxxxxxxx 3.0 1
FILESERVER home xxxxxxxx xxxxxxxx 3.0 1
FILESERVER IPC$ xxxxxxxx xxxxxxxx 3.0 0
FILESERVER public xxxxxxxx xxxxxxxx 3.0 2
But I do not know how to disconnect a share with this information.
The reason for my question: I want to write a batch script which disconnects all network shares from a PC after log off (e.g. Win+L keys). On Windows 7 and 8 I use the mentioned net use * /delete command, which does not work on Windows 10, as shown above.
The SMB shares are accessible with the GUI (Explorer -> Network ...) and I can save, change and delete files on them. But the share is not mapped to a drive letter.
Following is a bit output for stuff that does not help, but it seems my question is still not clear enough:
Get-SmbConnection : see above, I want to close these!
Get-SmbSession : No output.
Get-SmbMapping : No output.
Get-SmbShare :
Name ScopeName Path Description
---- --------- ---- -----------
ADMIN$ * C:WINDOWS Remoteverwaltung
C$ * C: Standardfreigabe
IPC$ * Remote-IPC
print$ * C:WINDOWSsystem32spooldrivers Druckertreiber
windows-10 powershell network-shares samba
asked Sep 28 '16 at 12:46
dicedice
1118
add a comment |
I'm trying to disconnect a smb share with a Powershell command in Windows 10:
net use * /delete
However, this command does not work, because the share is not shown with net use. The output is There are no entries in the list.
Get-SmbConnection is showing the results I'd expect,
ServerName ShareName UserName Credential Dialect NumOpens
---------- --------- -------- ---------- ------- --------
FILESERVER extra xxxxxxxx xxxxxxxx 3.0 1
FILESERVER home xxxxxxxx xxxxxxxx 3.0 1
FILESERVER IPC$ xxxxxxxx xxxxxxxx 3.0 0
FILESERVER public xxxxxxxx xxxxxxxx 3.0 2
But I do not know how to disconnect a share with this information.
The reason for my question: I want to write a batch script which disconnects all network shares from a PC after log off (e.g. Win+L keys). On Windows 7 and 8 I use the mentioned net use * /delete command, which does not work on Windows 10, as shown above.
The SMB shares are accessible with the GUI (Explorer -> Network ...) and I can save, change and delete files on them. But the share is not mapped to a drive letter.
Following is a bit output for stuff that does not help, but it seems my question is still not clear enough:
Get-SmbConnection : see above, I want to close these!
Get-SmbSession : No output.
Get-SmbMapping : No output.
Get-SmbShare :
Name ScopeName Path Description
---- --------- ---- -----------
ADMIN$ * C:WINDOWS Remoteverwaltung
C$ * C: Standardfreigabe
IPC$ * Remote-IPC
print$ * C:WINDOWSsystem32spooldrivers Druckertreiber
windows-10 powershell network-shares samba
asked Sep 28 '16 at 12:46
dicedice
1118
In the future, if a command you expect to work is not working, add any error message or mention that there are none to your post.
– root
Sep 28 '16 at 13:21
Thank you for your edit and corrections, I clarified it a bit more, added the "error messages" and a bit background information.
– dice
Sep 28 '16 at 13:57
It seems to me that this windows-8-net-use-no-longer-works is exactly the same problem
– dice
Sep 30 '16 at 11:14
add a comment |
I'm trying to disconnect a smb share with a Powershell command in Windows 10:
net use * /delete
However, this command does not work, because the share is not shown with net use. The output is There are no entries in the list.
Get-SmbConnection is showing the results I'd expect,
ServerName ShareName UserName Credential Dialect NumOpens
---------- --------- -------- ---------- ------- --------
FILESERVER extra xxxxxxxx xxxxxxxx 3.0 1
FILESERVER home xxxxxxxx xxxxxxxx 3.0 1
FILESERVER IPC$ xxxxxxxx xxxxxxxx 3.0 0
FILESERVER public xxxxxxxx xxxxxxxx 3.0 2
But I do not know how to disconnect a share with this information.
The reason for my question: I want to write a batch script which disconnects all network shares from a PC after log off (e.g. Win+L keys). On Windows 7 and 8 I use the mentioned net use * /delete command, which does not work on Windows 10, as shown above.
The SMB shares are accessible with the GUI (Explorer -> Network ...) and I can save, change and delete files on them. But the share is not mapped to a drive letter.
Following is a bit output for stuff that does not help, but it seems my question is still not clear enough:
Get-SmbConnection : see above, I want to close these!
Get-SmbSession : No output.
Get-SmbMapping : No output.
Get-SmbShare :
Name ScopeName Path Description
---- --------- ---- -----------
ADMIN$ * C:WINDOWS Remoteverwaltung
C$ * C: Standardfreigabe
IPC$ * Remote-IPC
print$ * C:WINDOWSsystem32spooldrivers Druckertreiber
windows-10 powershell network-shares samba
asked Sep 28 '16 at 12:46
dicedice
1118
I'm trying to disconnect a smb share with a Powershell command in Windows 10:
net use * /delete
However, this command does not work, because the share is not shown with net use. The output is There are no entries in the list.
Get-SmbConnection is showing the results I'd expect,
ServerName ShareName UserName Credential Dialect NumOpens
---------- --------- -------- ---------- ------- --------
FILESERVER extra xxxxxxxx xxxxxxxx 3.0 1
FILESERVER home xxxxxxxx xxxxxxxx 3.0 1
FILESERVER IPC$ xxxxxxxx xxxxxxxx 3.0 0
FILESERVER public xxxxxxxx xxxxxxxx 3.0 2
But I do not know how to disconnect a share with this information.
The reason for my question: I want to write a batch script which disconnects all network shares from a PC after log off (e.g. Win+L keys). On Windows 7 and 8 I use the mentioned net use * /delete command, which does not work on Windows 10, as shown above.
The SMB shares are accessible with the GUI (Explorer -> Network ...) and I can save, change and delete files on them. But the share is not mapped to a drive letter.
Following is a bit output for stuff that does not help, but it seems my question is still not clear enough:
Get-SmbConnection : see above, I want to close these!
Get-SmbSession : No output.
Get-SmbMapping : No output.
Get-SmbShare :
Name ScopeName Path Description
---- --------- ---- -----------
ADMIN$ * C:WINDOWS Remoteverwaltung
C$ * C: Standardfreigabe
IPC$ * Remote-IPC
print$ * C:WINDOWSsystem32spooldrivers Druckertreiber
windows-10 powershell network-shares samba
windows-10 powershell network-shares samba
asked Sep 28 '16 at 12:46
dicedice
1118
asked Sep 28 '16 at 12:46
dicedice
1118
edited Oct 4 '16 at 9:13
dice
asked Sep 28 '16 at 12:46
dicedice
1118
asked Sep 28 '16 at 12:46
dicedice
1118
asked Sep 28 '16 at 12:46
dicedice
1118
1118
In the future, if a command you expect to work is not working, add any error message or mention that there are none to your post.
– root
Sep 28 '16 at 13:21
Thank you for your edit and corrections, I clarified it a bit more, added the "error messages" and a bit background information.
– dice
Sep 28 '16 at 13:57
It seems to me that this windows-8-net-use-no-longer-works is exactly the same problem
– dice
Sep 30 '16 at 11:14
add a comment |
In the future, if a command you expect to work is not working, add any error message or mention that there are none to your post.
– root
Sep 28 '16 at 13:21
Thank you for your edit and corrections, I clarified it a bit more, added the "error messages" and a bit background information.
– dice
Sep 28 '16 at 13:57
It seems to me that this windows-8-net-use-no-longer-works is exactly the same problem
– dice
Sep 30 '16 at 11:14
In the future, if a command you expect to work is not working, add any error message or mention that there are none to your post.
– root
Sep 28 '16 at 13:21
In the future, if a command you expect to work is not working, add any error message or mention that there are none to your post.
– root
Sep 28 '16 at 13:21
Thank you for your edit and corrections, I clarified it a bit more, added the "error messages" and a bit background information.
– dice
Sep 28 '16 at 13:57
Thank you for your edit and corrections, I clarified it a bit more, added the "error messages" and a bit background information.
– dice
Sep 28 '16 at 13:57
It seems to me that this windows-8-net-use-no-longer-works is exactly the same problem
– dice
Sep 30 '16 at 11:14
It seems to me that this windows-8-net-use-no-longer-works is exactly the same problem
– dice
Sep 30 '16 at 11:14
add a comment |
1 Answer
1
active
oldest
votes
Try Remove-SmbMapping. Assuming you're on the client, it looks like this is the one you want to use. You can probably pipe results from Get-SMBConnection to Remove-SmbMapping
answered Sep 30 '16 at 12:36
XalorousXalorous
43128
Yes, I am on the client. I added the results from 'Get-SmbMapping' in my question. I can add one and can remove one but I cannot remove the open SmbConnections
– dice
Oct 4 '16 at 9:21
Get-SMBConnectionshows the credential of the account that connected the share. Are you using the same account to disconnect it? Also, checkRemove-SmbMappingfor a-Forceswitch. Sounds like MS has changed the way mapping works and the new best practice has not made it to the public at large.
– Xalorous
Oct 4 '16 at 12:10
Yes, I runGet-SmbConnectionas admin and it shows the right user name and credential (in the form machinenameusername, not the admin account). Yes it seems that unmapped smb works different in smb3. In earlier versions I could usenet use * /dto "remove" the connection and lock in again with user credentials, this does not work any more.
– dice
Oct 4 '16 at 12:41
You have no shares as client, don't you?
– Yurij
Jan 25 at 17:09
add a comment |
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1129183%2fdisconnect-from-smb-share-with-powershell-on-windows-10%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Try Remove-SmbMapping. Assuming you're on the client, it looks like this is the one you want to use. You can probably pipe results from Get-SMBConnection to Remove-SmbMapping
answered Sep 30 '16 at 12:36
XalorousXalorous
43128
Yes, I am on the client. I added the results from 'Get-SmbMapping' in my question. I can add one and can remove one but I cannot remove the open SmbConnections
– dice
Oct 4 '16 at 9:21
Get-SMBConnectionshows the credential of the account that connected the share. Are you using the same account to disconnect it? Also, checkRemove-SmbMappingfor a-Forceswitch. Sounds like MS has changed the way mapping works and the new best practice has not made it to the public at large.
– Xalorous
Oct 4 '16 at 12:10
Yes, I runGet-SmbConnectionas admin and it shows the right user name and credential (in the form machinenameusername, not the admin account). Yes it seems that unmapped smb works different in smb3. In earlier versions I could usenet use * /dto "remove" the connection and lock in again with user credentials, this does not work any more.
– dice
Oct 4 '16 at 12:41
You have no shares as client, don't you?
– Yurij
Jan 25 at 17:09
add a comment |
Try Remove-SmbMapping. Assuming you're on the client, it looks like this is the one you want to use. You can probably pipe results from Get-SMBConnection to Remove-SmbMapping
answered Sep 30 '16 at 12:36
XalorousXalorous
43128
Yes, I am on the client. I added the results from 'Get-SmbMapping' in my question. I can add one and can remove one but I cannot remove the open SmbConnections
– dice
Oct 4 '16 at 9:21
Get-SMBConnectionshows the credential of the account that connected the share. Are you using the same account to disconnect it? Also, checkRemove-SmbMappingfor a-Forceswitch. Sounds like MS has changed the way mapping works and the new best practice has not made it to the public at large.
– Xalorous
Oct 4 '16 at 12:10
Yes, I runGet-SmbConnectionas admin and it shows the right user name and credential (in the form machinenameusername, not the admin account). Yes it seems that unmapped smb works different in smb3. In earlier versions I could usenet use * /dto "remove" the connection and lock in again with user credentials, this does not work any more.
– dice
Oct 4 '16 at 12:41
You have no shares as client, don't you?
– Yurij
Jan 25 at 17:09
add a comment |
Try Remove-SmbMapping. Assuming you're on the client, it looks like this is the one you want to use. You can probably pipe results from Get-SMBConnection to Remove-SmbMapping
answered Sep 30 '16 at 12:36
XalorousXalorous
43128
Try Remove-SmbMapping. Assuming you're on the client, it looks like this is the one you want to use. You can probably pipe results from Get-SMBConnection to Remove-SmbMapping
answered Sep 30 '16 at 12:36
XalorousXalorous
43128
answered Sep 30 '16 at 12:36
XalorousXalorous
43128
answered Sep 30 '16 at 12:36
XalorousXalorous
43128
answered Sep 30 '16 at 12:36
XalorousXalorous
43128
43128
Yes, I am on the client. I added the results from 'Get-SmbMapping' in my question. I can add one and can remove one but I cannot remove the open SmbConnections
– dice
Oct 4 '16 at 9:21
Get-SMBConnectionshows the credential of the account that connected the share. Are you using the same account to disconnect it? Also, checkRemove-SmbMappingfor a-Forceswitch. Sounds like MS has changed the way mapping works and the new best practice has not made it to the public at large.
– Xalorous
Oct 4 '16 at 12:10
Yes, I runGet-SmbConnectionas admin and it shows the right user name and credential (in the form machinenameusername, not the admin account). Yes it seems that unmapped smb works different in smb3. In earlier versions I could usenet use * /dto "remove" the connection and lock in again with user credentials, this does not work any more.
– dice
Oct 4 '16 at 12:41
You have no shares as client, don't you?
– Yurij
Jan 25 at 17:09
add a comment |
Yes, I am on the client. I added the results from 'Get-SmbMapping' in my question. I can add one and can remove one but I cannot remove the open SmbConnections
– dice
Oct 4 '16 at 9:21
Get-SMBConnectionshows the credential of the account that connected the share. Are you using the same account to disconnect it? Also, checkRemove-SmbMappingfor a-Forceswitch. Sounds like MS has changed the way mapping works and the new best practice has not made it to the public at large.
– Xalorous
Oct 4 '16 at 12:10
Yes, I runGet-SmbConnectionas admin and it shows the right user name and credential (in the form machinenameusername, not the admin account). Yes it seems that unmapped smb works different in smb3. In earlier versions I could usenet use * /dto "remove" the connection and lock in again with user credentials, this does not work any more.
– dice
Oct 4 '16 at 12:41
You have no shares as client, don't you?
– Yurij
Jan 25 at 17:09
Yes, I am on the client. I added the results from 'Get-SmbMapping' in my question. I can add one and can remove one but I cannot remove the open SmbConnections
– dice
Oct 4 '16 at 9:21
Yes, I am on the client. I added the results from 'Get-SmbMapping' in my question. I can add one and can remove one but I cannot remove the open SmbConnections
– dice
Oct 4 '16 at 9:21
Get-SMBConnection shows the credential of the account that connected the share. Are you using the same account to disconnect it? Also, check Remove-SmbMapping for a -Force switch. Sounds like MS has changed the way mapping works and the new best practice has not made it to the public at large.– Xalorous
Oct 4 '16 at 12:10
Get-SMBConnection shows the credential of the account that connected the share. Are you using the same account to disconnect it? Also, check Remove-SmbMapping for a -Force switch. Sounds like MS has changed the way mapping works and the new best practice has not made it to the public at large.– Xalorous
Oct 4 '16 at 12:10
Yes, I run
Get-SmbConnection as admin and it shows the right user name and credential (in the form machinenameusername, not the admin account). Yes it seems that unmapped smb works different in smb3. In earlier versions I could use net use * /d to "remove" the connection and lock in again with user credentials, this does not work any more.– dice
Oct 4 '16 at 12:41
Yes, I run
Get-SmbConnection as admin and it shows the right user name and credential (in the form machinenameusername, not the admin account). Yes it seems that unmapped smb works different in smb3. In earlier versions I could use net use * /d to "remove" the connection and lock in again with user credentials, this does not work any more.– dice
Oct 4 '16 at 12:41
You have no shares as client, don't you?
– Yurij
Jan 25 at 17:09
You have no shares as client, don't you?
– Yurij
Jan 25 at 17:09
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1129183%2fdisconnect-from-smb-share-with-powershell-on-windows-10%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
In the future, if a command you expect to work is not working, add any error message or mention that there are none to your post.
– root
Sep 28 '16 at 13:21
Thank you for your edit and corrections, I clarified it a bit more, added the "error messages" and a bit background information.
– dice
Sep 28 '16 at 13:57
It seems to me that this windows-8-net-use-no-longer-works is exactly the same problem
– dice
Sep 30 '16 at 11:14