winrm - Powershell 4.0 Remoting with Non Admin Domain Account -
i'm looking configure powershell remoting non-admins on group of servers. right have working configuration allows admin domain accounts connect servers no error. authentication method using credssp, using ssl , works domain admin account.
on other hand have user domain account usertest. account mapped domain group maps locally (on each server) remote desktop user groups. allows user rdp server has no administrator privileges. going stay way , not option make local administrator.
the purpose of user allow non-admin accounts execute set of scripts against server using restricted session, connecting domain admin account. problem comes when i'm trying connect usertest account. server responds access denied error:
[servera] connecting remote server servera failed following error message : access denied. more information, see about_remote_troubleshooting topic. + categoryinfo : openerror: (servera:string) [], psremotingtransportexception + fullyqualifiederrorid : accessdenied,pssessionstatebroken
going trough analytic eventlogs found error message follows:
the wsman service not launch host process process given request. make sure wsman provider host server , proxy registered.
this configuration have setup:
created pssessionconfiguration named remotedesktopusers
register-pssessionconfiguration -name remotedesktopusers -startupscript c:\start.ps1
set-pssessionconfiguration -name remotedesktopusers -showsecuritydescriptorui (added remote desktop users group sessionconfiguration)
so yeah, have googled, should necessary configuration need able psremote non-admin accounts. mentioned using domain admin account connecting sessionconfiguration works fine, thinking i'm missing kind of permission/privilege/sddl allows user access:
windows server 2008 r2 sp1
powershell 4.0
winrm productversion = os: 6.1.7601 sp: 1.0 stack: 3.0
you're running problem because of using credssp
any particular reason have use credssp? popular use of credssp provided situations in need configure jump server remote 1 machine, another, , there out again server. it's well-known second-hop funtionality , such huge security hole credssp kind of pain configure, intentionally.
you have configure credssp in 3 places, once on machine you'll remoting, again on machine you'll jumping to, , on each machine you'll connecting jump server.
if have use credssp, follow great guide here on scripting guy's blog.
if don't need credssp
try whole process using default/wsman authorization, , bet problems go away.
Comments
Post a Comment