-
Notifications
You must be signed in to change notification settings - Fork 899
Scheduling GUI Apps
The standard way of managing windows apps with Rundeck is to invoke jobs over Windows Remote Management or "WinRM". Lots of rundeck users use WinRM with great success. Issues have come up with the approach on later patch releases of Windows 2008, Vista, 7, and Windows 8 due to Session 0 Isolation for jobs that require GUI interactivity of devices traditionally managed by the graphics system of Windows. This problem is effecting newer style cloud applications that leverage the amazing processing capability of the graphics cards. This Isolation issue will also effect automated jobs using powershell to automate GUI applications through the COM programmatic interface.
There are several approaches to working around Session 0 Isolation posted in numerous blogs. This solution uses Rundeck installed locally on the Windows machine to manage (start/stop/status) the Windows application suffering from Session 0 isolation. Normal implementation would implement a spoke and hub command distribution topology where one of more central Rundeck servers would invoke
Use the