System architecture and coping with Session 0 isolation in Windows Vista

I am running into complications with one of our applications resulting from the new session 0 isolation Microsoft introduced in Windows Vista. Our VB6 application (running as a service via srvany.exe) interacts with the desktop via a control panel user interface and systray icon. All of our applications communicate via TCP sockets.
The purpose of this application of ours is to allow users to manage our legacy backend data collection utilities that drive our user interfaces (such as showing/hiding their display windows).

There are two architectural problems we are now encountering while still trying to run our management application at service level:

1. As our application can no longer interact with the desktop, users cannot use it to show and hide the legacy programs it manages (as these processes have been started at service level by the management application).

2. If our management application was to run at service level but start the legacy programs as user level, logging off the PC would result in our legacy programs needing to be restarted.  This would also result in the legacy programs ceasing data collection for the period of time in which they are restarted.

Any changes to system architecture would have to be completed in the management application, as the legacy programs serve their purpose and are static EXEs.

Does anyone have any suggestions how we could rework our system architecture to permit the legacy programs to interact with the desktop (at the very least)?

Thanks in advance for any and all feedback.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

You're right... Vista has changed things so that's not an option anymore.
I think the only real solution is to break your application into two parts... and service part and the User Interface part.    That way, the service can be started with elevated privilegs and continue to run after log off... and all interaction with the user would be done via a separate UI app that talks to the service.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
rite_ehAuthor Commented:
Thanks for the response. I too have come to the conclusion that this (messy) change is what is required.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Vista

From novice to tech pro — start learning today.