Log Off when Application Closes

[Joshua A. Booker]

Users who get an Access App instead of a desktop on TS can't log off
properly. At one point, it was logging off after Access was closed, but now
it just stays with the blue screen and in TS manager it says disconnected.
The server shuts old sessions after a certain interval, but why doesn't it
log off properly as it once did?

Is there a way to control the session and tell it to log off in VBA? Is
this a result of choosing NT compatable in the TS config?

TIA,
Josh

 

[Matthew Harris [MVP]]

Instead of calling the Access application directly, why
don't you have the terminal server call a batch script
first. You can make this batch script bring up Access.
You can also force the batch script to wait until Access
is closed, then have it call the logoff.exe.

Something like...

Start /wait c:\path\to\access.exe

-M

 

[Joshua A. Booker]

Thanks for the logoff.exe tip.

I'd like to know why it doesn't do what the documentation says it will. Why
doesn't it logoff automatically as it once did? Is it because the app is
started from the environment settings of the AD Users and Groups on the DC
now instead of Local Users on the TS box? There must be a reason does
anyone know?

Josh

 

[Vera Noest [MVP]]

Some process must still be running in the user context, preventing
the connection from closing. When you have closed the Access
application, but still have the window open, can you bring up Task
Manager and check if you see any running processes there?
Could be an antivirus program or something like that.

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup ---

 

[Brianos]

does access.exe itself close???

if not, there is a sysmodules registry poke to ensure that apps get
closed by on exit.

cheers, Brianos

 

[Joshua A. Booker]

Vera,

When a user has closed Access, they can't bring up TaskMgr because there is
no desktop or start menu it's just a Blue screen. CrtlAltDel brings up
TaskMgr on my client workstation.

TIA,
Josh

 

[Joshua A. Booker]

Vera,

Thank you for your response. I checked TaskMgr and found the following
processes:

WINLOGON.EXE
CSRSS.EXE
fxrdpclp.exe
taskmgr.exe

When I end task fxrdpclp then close taskmgr, it logs off. Does this mean
Microsoft's clipboard fix is at fault? Can I uninstall this since the
shared clipboard thing still doesn't work anyway?

If so, how do I uninstall it.

TIA,
Josh