Disconnect-pnponline does not remove PSDrive - SPO:

[crshnbrn66]

###Notice: many issues / bugs reported are actually related to the PnP Core Library which is used behind the scenes. Consider carefully where to report an issue:###

Reporting an Issue or Missing Feature

When connecting to a sharepoint site you can add -CreateDrive to the connection. This creates a Powershell Drive of SPO:

This same drive works after you issue a disconnect-pnponline

Expected behavior

Please describe what output you expect to see from PnP-PowerShell Cmdlets. The cmdlet should remove the PS drive and no longer be valid.

Actual behavior

[DBG]: PS SPO:\sites\apps>> Disconnect-PnPOnline

[DBG]: PS SPO:\sites\apps>> dir

Folder: SharePointPnP.PowerShell.Online.Commands\SPO::\sites\apps

Name Type Items/Size Last Modified

---

_catalogs Folder 0 7/6/2016 4:07:06 PM
_cts Folder 0 7/6/2016 4:07:05 PM
_private Folder 0 7/6/2016 4:07:03 PM
_vti_pvt Folder 0 7/6/2016 4:07:03 PM
AgaveCatalog Folder 0 7/6/2016 4:07:43 PM
AppCatalog Folder 8 1/3/2017 9:46:23 PM
AppRequests Folder 0 7/6/2016 4:07:44 PM
FormServerTemplates Folder 0 7/6/2016 4:07:15 PM
images Folder 0 7/6/2016 4:07:03 PM
Lists Folder 0 7/6/2016 4:07:06 PM
m Folder 0 7/6/2016 4:07:47 PM
SiteAssets Folder 1 9/21/2016 8:09:00 PM
SitePages Folder 2 7/6/2016 4:07:47 PM
sites Folder 0 1/3/2017 8:29:30 PM
Style Library Folder 0 7/6/2016 4:07:08 PM
default.aspx File 4059 7/6/2016 4:07:48 PM

[DBG]: PS SPO:\sites\apps>> get-pnpsite
get-pnpsite : No connection, please connect first with Connect-PnPOnline
At line:1 char:1

• get-pnpsite

•   + CategoryInfo          : NotSpecified: (:) [Get-PnPSite], InvalidOperationException
    + FullyQualifiedErrorId : System.InvalidOperationException,SharePointPnP.PowerShell.Commands.Site.GetSite
  
  
  

[DBG]: PS SPO:\sites\apps>> dir spo:

Folder: SharePointPnP.PowerShell.Online.Commands\SPO::\sites\apps

Name Type Items/Size Last Modified

---

_catalogs Folder 0 7/6/2016 4:07:06 PM
_cts Folder 0 7/6/2016 4:07:05 PM
_private Folder 0 7/6/2016 4:07:03 PM
_vti_pvt Folder 0 7/6/2016 4:07:03 PM
AgaveCatalog Folder 0 7/6/2016 4:07:43 PM
AppCatalog Folder 8 1/3/2017 9:46:23 PM
AppRequests Folder 0 7/6/2016 4:07:44 PM
FormServerTemplates Folder 0 7/6/2016 4:07:15 PM
images Folder 0 7/6/2016 4:07:03 PM
Lists Folder 0 7/6/2016 4:07:06 PM
m Folder 0 7/6/2016 4:07:47 PM
SiteAssets Folder 1 9/21/2016 8:09:00 PM
SitePages Folder 2 7/6/2016 4:07:47 PM
sites Folder 0 1/3/2017 8:29:30 PM
Style Library Folder 0 7/6/2016 4:07:08 PM
default.aspx File 4059 7/6/2016 4:07:48 PM

Steps to reproduce behavior

Please include complete code samples https://gist.github.com/crshnbrn66/88578228ce45f6c316516fc05dd7f160

Which version of the PnP-PowerShell Cmdlets are you using?

• PnP PowerShell for SharePoint 2013
• PnP PowerShell for SharePoint 2016
• [ x] PnP PowerShell for SharePoint Online

What is the version of the Cmdlet module you are running?

(you can retrieve this by executing Get-Module -Name *pnppowershell* -ListAvailable)
Major Minor Build Revision

---

2 10 1612 0

How did you install the PnP-PowerShell Cmdlets?

• MSI Installed downloaded from GitHub
• [x ] Installed through the PowerShell Gallery with Install-Module
• Other means

[erwinvanhunen]

Thank you for reporting this issue! I merged a fix with PR #651 into the dev branch, which will be released next month.