Terminal server automatic log off? - microsoft.public.greatplains

I just noticed an odd behavior last night when running a session on our terminal server. I was logged in to GP (version 9) on the terminal server and started up a long-running SOP batch posting job. I disconnected from the remote session (disconnected, not logged off) to let the job run overnight. When I reconnected to the session the next morning, I found that GP had logged itself off. I was able to log back in without getting the 'already logged in' message, so it must have cleanly terminated my login. Is that normal behavior? Why did it happen? I would have thought I would still be logged in to GP when I reconnected to the terminal server session. -- Bud Cool Microsoft Certified Business Management Solutions Specialist, GP 9.0 Financials Currently supporting: GP 9.0, SP4

Not normal. Here when we need to maintain (apply service packs, reboot) Citrix servers we will shadow an open Dynamics GP session (i.e. take control) and take the user out properly. That is one explanation that matches your experience. Did you get your Posting Journal? -- Tim Foster "Bud" wrote: > I just noticed an odd behavior last night when running a session on our > terminal server. > > I was logged in to GP (version 9) on the terminal server and started up a > long-running SOP batch posting job. I disconnected from the remote session > (disconnected, not logged off) to let the job run overnight. When I > reconnected to the session the next morning, I found that GP had logged > itself off. I was able to log back in without getting the 'already logged in' > message, so it must have cleanly terminated my login. > > Is that normal behavior? Why did it happen? I would have thought I would > still be logged in to GP when I reconnected to the terminal server session. > > > > > > > > -- > Bud Cool > Microsoft Certified Business Management Solutions Specialist, GP 9.0 > Financials > Currently supporting: GP 9.0, SP4

If your Posting job is a macro, the macro might take you out correctly. Omni Tools can do this (inactivity sensing) but normal Dynamics GP does not. -- Tim Foster "Bud" wrote: > Don't hit me :-), but we don't print the posting journals...so no output was > expected. But, for some reason, it completely logged me out. > > I don't normally run the posting jobs - I was filling in for someone who was > on vacation. However, they said they experience the same behavior. > > -- > Bud Cool > Microsoft Certified Business Management Solutions Specialist, GP 9.0 > Financials > Currently supporting: GP 9.0, SP4 > > > "Tim Foster" wrote: > > > Not normal. > > > > Here when we need to maintain (apply service packs, reboot) Citrix servers > > we will shadow an open Dynamics GP session (i.e. take control) and take the > > user out properly. That is one explanation that matches your experience. > > > > Did you get your Posting Journal? > > > > -- > > Tim Foster > > > > > > "Bud" wrote: > > > > > I just noticed an odd behavior last night when running a session on our > > > terminal server. > > > > > > I was logged in to GP (version 9) on the terminal server and started up a > > > long-running SOP batch posting job. I disconnected from the remote session > > > (disconnected, not logged off) to let the job run overnight. When I > > > reconnected to the session the next morning, I found that GP had logged > > > itself off. I was able to log back in without getting the 'already logged in' > > > message, so it must have cleanly terminated my login. > > > > > > Is that normal behavior? Why did it happen? I would have thought I would > > > still be logged in to GP when I reconnected to the terminal server session. > > > > > > > > > > > > > > > > > > > > > > > > -- > > > Bud Cool > > > Microsoft Certified Business Management Solutions Specialist, GP 9.0 > > > Financials > > > Currently supporting: GP 9.0, SP4

Bud, Actually this could be configured in Terminal Services Configuration, it seems that your current Terminal Services is configured to logoff inactive or idle sessions after a while, check your configuration and make sure to set the logoff to "Never". Regards, -- Mohammad R. Daoud MVP, MCP, MCBMSP, MCTS, MCBMSS Mob: +962 - 79 -999 65 85 mohdaoud@gmail.com http://mohdaoud.blogspot.com/ "Bud" wrote: > We're not using a macro - it's just straight GP. That's why it's so weird. > > -- > Bud Cool > Microsoft Certified Business Management Solutions Specialist, GP 9.0 > Financials > Currently supporting: GP 9.0, SP4 > > > "Tim Foster" wrote: > > > If your Posting job is a macro, the macro might take you out correctly. > > > > Omni Tools can do this (inactivity sensing) but normal Dynamics GP does not. > > > > -- > > Tim Foster > > > > > > "Bud" wrote: > > > > > Don't hit me :-), but we don't print the posting journals...so no output was > > > expected. But, for some reason, it completely logged me out. > > > > > > I don't normally run the posting jobs - I was filling in for someone who was > > > on vacation. However, they said they experience the same behavior. > > > > > > -- > > > Bud Cool > > > Microsoft Certified Business Management Solutions Specialist, GP 9.0 > > > Financials > > > Currently supporting: GP 9.0, SP4 > > > > > > > > > "Tim Foster" wrote: > > > > > > > Not normal. > > > > > > > > Here when we need to maintain (apply service packs, reboot) Citrix servers > > > > we will shadow an open Dynamics GP session (i.e. take control) and take the > > > > user out properly. That is one explanation that matches your experience. > > > > > > > > Did you get your Posting Journal? > > > > > > > > -- > > > > Tim Foster > > > > > > > > > > > > "Bud" wrote: > > > > > > > > > I just noticed an odd behavior last night when running a session on our > > > > > terminal server. > > > > > > > > > > I was logged in to GP (version 9) on the terminal server and started up a > > > > > long-running SOP batch posting job. I disconnected from the remote session > > > > > (disconnected, not logged off) to let the job run overnight. When I > > > > > reconnected to the session the next morning, I found that GP had logged > > > > > itself off. I was able to log back in without getting the 'already logged in' > > > > > message, so it must have cleanly terminated my login. > > > > > > > > > > Is that normal behavior? Why did it happen? I would have thought I would > > > > > still be logged in to GP when I reconnected to the terminal server session. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > Bud Cool > > > > > Microsoft Certified Business Management Solutions Specialist, GP 9.0 > > > > > Financials > > > > > Currently supporting: GP 9.0, SP4

I have posted an article about this subject, check it out here: http://mohdaoud.blogspot.com/2010/03/configure-terminal-services-sessions.html Regards, -- Mohammad R. Daoud MVP, MCP, MCBMSP, MCTS, MCBMSS Mob: +962 - 79 -999 65 85 mohdaoud@gmail.com http://mohdaoud.blogspot.com/ "Mohammad R. Daoud" wrote: > Bud, > > Actually this could be configured in Terminal Services Configuration, it > seems that your current Terminal Services is configured to logoff inactive or > idle sessions after a while, check your configuration and make sure to set > the logoff to "Never". > > Regards, > -- > Mohammad R. Daoud > MVP, MCP, MCBMSP, MCTS, MCBMSS > Mob: +962 - 79 -999 65 85 > mohdaoud@gmail.com > http://mohdaoud.blogspot.com/ > > > "Bud" wrote: > > > We're not using a macro - it's just straight GP. That's why it's so weird. > > > > -- > > Bud Cool > > Microsoft Certified Business Management Solutions Specialist, GP 9.0 > > Financials > > Currently supporting: GP 9.0, SP4 > > > > > > "Tim Foster" wrote: > > > > > If your Posting job is a macro, the macro might take you out correctly. > > > > > > Omni Tools can do this (inactivity sensing) but normal Dynamics GP does not. > > > > > > -- > > > Tim Foster > > > > > > > > > "Bud" wrote: > > > > > > > Don't hit me :-), but we don't print the posting journals...so no output was > > > > expected. But, for some reason, it completely logged me out. > > > > > > > > I don't normally run the posting jobs - I was filling in for someone who was > > > > on vacation. However, they said they experience the same behavior. > > > > > > > > -- > > > > Bud Cool > > > > Microsoft Certified Business Management Solutions Specialist, GP 9.0 > > > > Financials > > > > Currently supporting: GP 9.0, SP4 > > > > > > > > > > > > "Tim Foster" wrote: > > > > > > > > > Not normal. > > > > > > > > > > Here when we need to maintain (apply service packs, reboot) Citrix servers > > > > > we will shadow an open Dynamics GP session (i.e. take control) and take the > > > > > user out properly. That is one explanation that matches your experience. > > > > > > > > > > Did you get your Posting Journal? > > > > > > > > > > -- > > > > > Tim Foster > > > > > > > > > > > > > > > "Bud" wrote: > > > > > > > > > > > I just noticed an odd behavior last night when running a session on our > > > > > > terminal server. > > > > > > > > > > > > I was logged in to GP (version 9) on the terminal server and started up a > > > > > > long-running SOP batch posting job. I disconnected from the remote session > > > > > > (disconnected, not logged off) to let the job run overnight. When I > > > > > > reconnected to the session the next morning, I found that GP had logged > > > > > > itself off. I was able to log back in without getting the 'already logged in' > > > > > > message, so it must have cleanly terminated my login. > > > > > > > > > > > > Is that normal behavior? Why did it happen? I would have thought I would > > > > > > still be logged in to GP when I reconnected to the terminal server session. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > Bud Cool > > > > > > Microsoft Certified Business Management Solutions Specialist, GP 9.0 > > > > > > Financials > > > > > > Currently supporting: GP 9.0, SP4

Wouldn't the user still be presented with the "already logged in" message? I think they would. -- Tim Foster "Mohammad R. Daoud" wrote: > Bud, > > Actually this could be configured in Terminal Services Configuration, it > seems that your current Terminal Services is configured to logoff inactive or > idle sessions after a while, check your configuration and make sure to set > the logoff to "Never". > > Regards, > -- > Mohammad R. Daoud > MVP, MCP, MCBMSP, MCTS, MCBMSS > Mob: +962 - 79 -999 65 85 > mohdaoud@gmail.com > http://mohdaoud.blogspot.com/ > > > "Bud" wrote: > > > We're not using a macro - it's just straight GP. That's why it's so weird. > > > > -- > > Bud Cool > > Microsoft Certified Business Management Solutions Specialist, GP 9.0 > > Financials > > Currently supporting: GP 9.0, SP4 > > > > > > "Tim Foster" wrote: > > > > > If your Posting job is a macro, the macro might take you out correctly. > > > > > > Omni Tools can do this (inactivity sensing) but normal Dynamics GP does not. > > > > > > -- > > > Tim Foster > > > > > > > > > "Bud" wrote: > > > > > > > Don't hit me :-), but we don't print the posting journals...so no output was > > > > expected. But, for some reason, it completely logged me out. > > > > > > > > I don't normally run the posting jobs - I was filling in for someone who was > > > > on vacation. However, they said they experience the same behavior. > > > > > > > > -- > > > > Bud Cool > > > > Microsoft Certified Business Management Solutions Specialist, GP 9.0 > > > > Financials > > > > Currently supporting: GP 9.0, SP4 > > > > > > > > > > > > "Tim Foster" wrote: > > > > > > > > > Not normal. > > > > > > > > > > Here when we need to maintain (apply service packs, reboot) Citrix servers > > > > > we will shadow an open Dynamics GP session (i.e. take control) and take the > > > > > user out properly. That is one explanation that matches your experience. > > > > > > > > > > Did you get your Posting Journal? > > > > > > > > > > -- > > > > > Tim Foster > > > > > > > > > > > > > > > "Bud" wrote: > > > > > > > > > > > I just noticed an odd behavior last night when running a session on our > > > > > > terminal server. > > > > > > > > > > > > I was logged in to GP (version 9) on the terminal server and started up a > > > > > > long-running SOP batch posting job. I disconnected from the remote session > > > > > > (disconnected, not logged off) to let the job run overnight. When I > > > > > > reconnected to the session the next morning, I found that GP had logged > > > > > > itself off. I was able to log back in without getting the 'already logged in' > > > > > > message, so it must have cleanly terminated my login. > > > > > > > > > > > > Is that normal behavior? Why did it happen? I would have thought I would > > > > > > still be logged in to GP when I reconnected to the terminal server session. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > Bud Cool > > > > > > Microsoft Certified Business Management Solutions Specialist, GP 9.0 > > > > > > Financials > > > > > > Currently supporting: GP 9.0, SP4

That was it! Ours was set to end a disconnected session after 3 hours. I guess it works like when you shut down Windows on your PC - it cleanly closes all open programs before terminating - which would explain why we don't get the 'already logged in' message in GP the next day. -- Bud Cool Microsoft Certified Business Management Solutions Specialist, GP 9.0 Financials Currently supporting: GP 9.0, SP4 "Mohammad R. Daoud" wrote: > I have posted an article about this subject, check it out here: > > http://mohdaoud.blogspot.com/2010/03/configure-terminal-services-sessions.html > > Regards, > -- > Mohammad R. Daoud > MVP, MCP, MCBMSP, MCTS, MCBMSS > Mob: +962 - 79 -999 65 85 > mohdaoud@gmail.com > http://mohdaoud.blogspot.com/ > > > "Mohammad R. Daoud" wrote: > > > Bud, > > > > Actually this could be configured in Terminal Services Configuration, it > > seems that your current Terminal Services is configured to logoff inactive or > > idle sessions after a while, check your configuration and make sure to set > > the logoff to "Never". > > > > Regards, > > -- > > Mohammad R. Daoud > > MVP, MCP, MCBMSP, MCTS, MCBMSS > > Mob: +962 - 79 -999 65 85 > > mohdaoud@gmail.com > > http://mohdaoud.blogspot.com/ > > > > > > "Bud" wrote: > > > > > We're not using a macro - it's just straight GP. That's why it's so weird. > > > > > > -- > > > Bud Cool > > > Microsoft Certified Business Management Solutions Specialist, GP 9.0 > > > Financials > > > Currently supporting: GP 9.0, SP4 > > > > > > > > > "Tim Foster" wrote: > > > > > > > If your Posting job is a macro, the macro might take you out correctly. > > > > > > > > Omni Tools can do this (inactivity sensing) but normal Dynamics GP does not. > > > > > > > > -- > > > > Tim Foster > > > > > > > > > > > > "Bud" wrote: > > > > > > > > > Don't hit me :-), but we don't print the posting journals...so no output was > > > > > expected. But, for some reason, it completely logged me out. > > > > > > > > > > I don't normally run the posting jobs - I was filling in for someone who was > > > > > on vacation. However, they said they experience the same behavior. > > > > > > > > > > -- > > > > > Bud Cool > > > > > Microsoft Certified Business Management Solutions Specialist, GP 9.0 > > > > > Financials > > > > > Currently supporting: GP 9.0, SP4 > > > > > > > > > > > > > > > "Tim Foster" wrote: > > > > > > > > > > > Not normal. > > > > > > > > > > > > Here when we need to maintain (apply service packs, reboot) Citrix servers > > > > > > we will shadow an open Dynamics GP session (i.e. take control) and take the > > > > > > user out properly. That is one explanation that matches your experience. > > > > > > > > > > > > Did you get your Posting Journal? > > > > > > > > > > > > -- > > > > > > Tim Foster > > > > > > > > > > > > > > > > > > "Bud" wrote: > > > > > > > > > > > > > I just noticed an odd behavior last night when running a session on our > > > > > > > terminal server. > > > > > > > > > > > > > > I was logged in to GP (version 9) on the terminal server and started up a > > > > > > > long-running SOP batch posting job. I disconnected from the remote session > > > > > > > (disconnected, not logged off) to let the job run overnight. When I > > > > > > > reconnected to the session the next morning, I found that GP had logged > > > > > > > itself off. I was able to log back in without getting the 'already logged in' > > > > > > > message, so it must have cleanly terminated my login. > > > > > > > > > > > > > > Is that normal behavior? Why did it happen? I would have thought I would > > > > > > > still be logged in to GP when I reconnected to the terminal server session. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > Bud Cool > > > > > > > Microsoft Certified Business Management Solutions Specialist, GP 9.0 > > > > > > > Financials > > > > > > > Currently supporting: GP 9.0, SP4

Similiar Articles:

Terminal server automatic log off? - microsoft.public.greatplains ...
I just noticed an odd behavior last night when running a session on our terminal server. I was logged in to GP (version 9) on the terminal server...

Automatic Logoff/User Change - microsoft.public.windowsxp.general ...
Terminal server automatic log off? - microsoft.public.greatplains ... Automatic Logoff/User Change - microsoft.public.windowsxp.general ... Terminal server automatic log ...

Access on terminal services - microsoft.public.access
Access on terminal services - microsoft.public.access How can my application detect if it is running in a Terminal ... Terminal server automatic ... app-v vs remote app ...

Access 2000 on Terminal Server - microsoft.public.access ...
I would also probably set = a server task to automatically run compact and repair on ... I currently have four users that >log onto this terminal server to use this Access ...

How to switch users without completely logging off from current ...
Terminal server automatic log off? - microsoft.public.greatplains ... How to switch users without completely logging off from current ... Terminal server automatic log off ...

Force logoff after inactivity? - microsoft.public.scripting ...
Terminal server automatic log off? - microsoft.public.greatplains ... Terminal server automatic log off? - microsoft.public.greatplains ... Terminal server automatic log ...

Automatic Shutdown of Access Database - microsoft.public.access ...
Terminal server automatic log off? - microsoft.public.greatplains ... Automatic Shutdown of Access Database - microsoft.public.access ... Auto Login - microsoft.public ...

Reconcile to GL - Amount Diff between Reconcile report and AR HATB ...
Terminal server automatic log off? Utf 6 752

Last reboot of Server 2008 - microsoft.public.windows.server ...
Last reboot of Server 2008 - microsoft.public.windows.server ... Terminal server automatic log off? - microsoft.public.greatplains ... I just noticed an odd behavior last ...

Duration getting changed automatically. - microsoft.public.project ...
Terminal server automatic log off? - microsoft.public.greatplains ... Duration getting changed automatically. - microsoft.public.project ... Terminal server automatic log ...

Windows Terminal Server and User Auto Log-Off for RDP
Solution on this post is for those who want to auto-log-off when users disconnect terminal server. ... on an app server, but I can't get the session to automatically log off. I ...

Terminal Services auto log off: terminal, auto, server, off, log
Keywords: Terminal, Services, auto, log, off. Terminal Server idle time; Terminal server ... have a requirement to "automatically terminate a session and log out after ...

Log off or disconnect: Terminal Services - Microsoft Corporation ...
Terminal Services Product Help in Windows Server 2003. ... Log off or disconnect. Updated: January 21, 2005. Applies To: Windows Server 2003, Windows ...

Automatically Log off Disconnected Sessions, in the Terminal ...
Hello all, In our 2003 environment, we have a hard time getting people to "log off" their TS sessions to servers so we constantly field e-mails asking us to 'clear ...

7/25/2012 8:36:04 PM