Forum Discussion
disconnect-vpnuser error. (Powershell, RRAS)
Type the following commands after you get the failure.
$error.CategoryInfo
$error.Exception
If you used the GUI, are able to disconnect the user
Also when you can the error from Windows PowerShell, did you check Windows Event Log \ PowerShell
- farismalaebMar 14, 2021Iron Contributor
PowerShell will use some CIM classes to do this task, lets try it and run the following command in the RRAS Server itself
$xArg=@{ ComputerName =$null PassThru = $null UserName = @('DOMAIN\TheUserName') } Invoke-CimMethod -ClassName PS_VpnUser -Namespace "Root\Microsoft\Windows\RemoteAccess" -MethodName "DisconnectByUserName" -Arguments $xArg
Btw, are you using Microsoft Direct Access or its just an RRAS
Let me know if the command above disconnects the user.
in the background, this is what PowerShell should be calling.- WillCunMar 15, 2021Copper Contributor
Thanks for the reply again. When I run the script that you provided I get the below error. Similar to what I get in running disconnect-vpnuser. I am using just VPN without Direct Access. The sad thing is I have used disconnect-vpnuser on this server before. I'm using a standard phonebook entry for the user to connect via SSTP to the VPN. I have rebuilt WMI, disabled RRAS and reinstalled with the default settings. I have even built a new server that even gives the same error. At this point I'm looking into Group Policy settings to see if something is causing this error.
Invoke-CimMethod : User domain\user cannot be disconnected.
At line:6 char:1
+ Invoke-CimMethod -ClassName PS_VpnUser -Namespace "Root\Microsoft\Windows\Remote ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (domain\user:) [Invoke-CimMethod], CimException
+ FullyQualifiedErrorId : REMOTEACCESS 200,Microsoft.Management.Infrastructure.CimCmdlets.InvokeCimMetho
dCommand
PSComputerName
--------------- farismalaebMar 15, 2021Iron Contributorwould you please check windows update history?
when this command last time was working and the installed update after that