Publishing Windows Apps via SSGD

August 29th, 2007 by Andre van Eyssen

Sun Secure Global Desktop supports publishing individual applications and desktop sessions from Windows Terminal Services.

Here is a very quick guide which includes some of the Windows steps (because we’re UNIX people, right?)

Step Number 1: Install your Windows 2003 Server. I fired one up under vmware because this was for a short test case.

Step Number 2: When Windows 2003 Server prompts you to configure a role, select Terminal Services and proceed through that configuration process.

Step Number 3: start->run->gpedit.msc and then Computer Configuration->Windows Settings->Security Settings->Local Policies->User Rights->Allow log on through Terminal Services and configure your user settings.

Step Number 4: Manage Your Server->Terminal Services Configuration. Right click on RDP-tcp and choose properties. Click the permissions tab and ensure permissions are correct.

Step Number 5: Test your configurations manually and make sure you can log in.
If you can’t, seek Windows advice from your local Windows expert.

Step Number 6: Log into SSGD with the administrative account and use the magical wizard to create a server entry for your Windows server.

Step Number 7: Use the magical wizard to create an RDP desktop session.

Step Number 8: To publish an application, you’ll need to first note the full path of the executable. Next, fire up the magical wizard and select Windows Application and choose “Independant” for the Application Display. Fill the other details in with sensible values, making sure you get that path right for your application.

Step Number 9: Enjoy it all. Don’t forget to chase up the Terminal Services license requirements.

Steps 6, 7 and 8 are all easily achievable using the commandline, but after dealing with all that hideous Windows business you’ll want to see some instant gratification instead of reading manpages and documentation.

Best of luck!

Posted in Desktop, UNIX | 1 Comment »

One Response

  1. Windows | www.purplecow.org Says:

    […] Update: Resolved, solution here. […]