Bind remote tmux window to local session

Question

I have been looking around but nothing I've found even understands what I want. I want to run tmux as a service on all of my machines as my user. Then, with as simple a process as possible, connect to the remote machine from within tmux on the local machine, create a new session (or attach an already running one) on the remote server but bind its new window to the local session. In essence I can now use my standard keys to switch to the window locally but split the window into panes like I'm on the remote system (so each pane is a shell on the remote system).
Essentially, with a tiling window manager, I don't enjoy having more than one terminal open on the same workspace if can be helped. If I do, now I have to use two different sets of keys to switch first application focus and then a different set to manipulate tmux. Is this even possible? If not, what's the major limitation (Tmux, yes. What about it?)?
My Solution:
Well, I've came to a better solution, let X handle local terminal multiplexing. I recently switched to i3 from XMonad and find it's window interaction much cleaner (ie it's not just resizing them everywhere but actually hides, minimizes, full screens, etc). I now only use Tmux in TTYs, the console, and in remote sessions (when I SSH from Tmux I just run a non-multiplexed shell on the server). This is probably the better solution anyways. It's absurdly redundant to run Tmux in XOrg when your window manager is a multiplexer anyway.
Last edited by Nycroth (2014-09-18 12:16:50)

Answer 1

Yes all the cmdlets appear in EMS. 
The output on another workstation using controso.com as a credential...
PSC:\Users\username> $session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri http://server/powershell/ -Authentication Kerberos -Credential $cred
[server] Connecting to remote server failed with the following error message : WinRM cannot process the
request. The following error occured while using Kerberos authentication: There are currently no logon servers availabl
e to service the logon request.
 Possible causes are:
  -The user name or password specified are invalid.
  -Kerberos is used when no authentication method and no user name are specified.
  -Kerberos accepts domain user names, but not local user names.
  -The Service Principal Name (SPN) for the remote computer name and port does not exist.
  -The client and remote computers are in different domains and there is no trust between the two domains.
 After checking for the above issues, try the following:
  -Check the Event Viewer for events related to authentication.
  -Change the authentication method; add the destination computer to the WinRM TrustedHosts configuration setting or us
e HTTPS transport.
 Note that computers in the TrustedHosts list might not be authenticated.
   -For more information about WinRM configuration, run the following command: winrm help config. For more information,
 see the about_Remote_Troubleshooting Help topic.
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc
The credential i used was controso.com\(my username) and my password