Issues with Explorer Shares on Alternate Logged Credentials

[kintaroju]

Hi Roger,

One issue that I recently noticed is when the console user A is logged on the system, and when I open client center for configuration manager as user B via "run as different user", user B can use most of the functionality of the application except for anything to do with Windows Explorer functionality. So if I try to use the ribbon item "Custom Actions\Explore Shares" any of the functions will not work if the application is "run as a different user" via user B when user A is the primary console user.

The only work around would be to log in user B as the console user and kick user A off that system. I know that some organizations have this two tiered permissions situation and was wondering if you could maybe enable a option to change the default explorer application from the native system explorer to maybe like Explorer++ so that way this issue won't occur.

If you need more clarification, let me know.

Cheers

[rzcrjz]

workaround for this on https://superuser.com/questions/290940/how-to-launch-windows-explorer-with-the-privileges-of-a-different-domain-user/290949 => Start the Registry Editor as an Administrative User. Navigate to, take ownership of, and grant yourself Full Control permission to the key HKEY_CLASSES_ROOT\AppID{CDCBCFCA-3CDC-436f-A4E2-0E02075250C2} Rename the value RunAs to _RunAs. Close Regedit.

[SCCMAdmin]

FYI I cannot recreate this issue as described by @kintaroju . We have a two tiered user account system. I thought I would assist but I will say that I can't considering that outcome.

[cmacnichol]

@rzander I can confirm this issue in Context with System Center Configuration Manager. My Organization requires that we open SCCM with alternate Admin credentials. The same ones I use to remotely connect to Workstations as well. When the Client Center is launched from the Console extension, as the admin user, everything works except the Explore Shares functionality. Where if I open Client Center stand alone and attempt to connect it will work as designed.

[Xento]

I think this is normal, because you can't open the explorer as other user. When you install totalcommander vor example than you can run this as other user and connect directly to a share.

Am Di., 6. Aug. 2019 um 13:44 Uhr schrieb Chris [email protected]:

@rzander https://github.com/rzander I can confirm this issue in Context with System Center Configuration Manager. My Organization requires that we open SCCM with alternate Admin credentials. The same ones I use to remotely connect to Workstations as well. When the Client Center is launched from the Console extension, as the admin user, everything works except the Explore Shares functionality. Where if I open Client Center stand alone and attempt to connect it will work as designed.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/rzander/sccmclictr/issues/57?email_source=notifications&email_token=AAJ5HRK4ZN5IHCPVPGCHZZLQDFPYJA5CNFSM4ETXJZSKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3U3VQQ#issuecomment-518634178, or mute the thread https://github.com/notifications/unsubscribe-auth/AAJ5HRNHE624K3M2G3VKIQ3QDFPYJANCNFSM4ETXJZSA .