Sage 100

I'm sure this has been addressed before somewhere, but I can't seem to find anything. Client just upgraded from 4.05 to 4.5 and now when they launch a task, it always is behind the Launcher. Anybody seen this? Client is getting really aggravated with me and I've no clue why it's doing it.

I mean that whatever task is launched is never the active task. Just clarifying.

90 or 200? All workstations or just one. What is the OS of the workstation?

I posted about this sometime last year. I was seeing the same behavior on a customer's Terminal Server. If I recall correctly, we decided that this was just some dumb bug, and nobody really had a good solution. If there is more information now, I'd still love to know the answer, too.

And that was what I was about to post, they are going through terminal services to a MAS100 Standard install.

Deb try to uninstall and reinstall the client.

Sorry to be a bit dumb, but the TS client?

Long ago I recall that the launcher would be ""minimized"" to the task bar when you launched MAS. It sounds similar to your issue. I think that you had to right click the minimuzed task, select maximize, then exit and reopen mas.

Deb, I was referring to the MAS client on the workstation.

Same recommendation as John - I think we had a conversation here about how Sage would launch but not have focus. Uninstalling and reinstalling workstation setup appeared to be the resolution in that case. Not sure if this is the same situation but may be worth a try.

@ Deb - please let us know if this works. Recently had the same issue with a windows virtual machine (running in a mac environment - oh joy!)

I have resolved this issue by modifying the registries on Windows 2008 TS. I have attached the knowledgebase article, but here are the basic steps: Modify ForegroundLockTimeout regkey for each remote user. Go to Start | Run |. Type Regedit. Browse to HKEY_CURRENT_USER\Control Panel\Desktop. Double-click ForegroundLockTimeout. Enter 0 in the Value Data field (leave as Hexadecimal). Click OK and exit Registry Editor. Repeat steps 1 thru 6 for each remote user session.

Thanks everyone, I'll try the uninstall/reinstall of wkstn setup first and then let you know if that works. They aren't having a ""minimized"" situation, so am not sure the fix from @CatherineFrias will resolve their problem, but will try it if the MAS client doesn't work.

So, here's what the IT guy sends me. Any suggestions for what to tell him? ""I can do this; however, remember that the new MAS client is not installed on the workstationsonly on the terminal server, so it would require reinstallation on the server, not the workstations. This means it would have to be done at night when everyone is off the system, and I am a bit unsure of the process of reinstalling the workstation on the serveror if the workstation installation can even be done on the server separately from the main MAS90 server configuration. I am, though, searching for the specific solution to the problem, and hopefully, there is something that will not require reinstallation. If not, we may have to reinstall tonight.

Is the TS a DIFFERENT box than the MAS server? Were you involved with the installation at all or is this a DIY install?

The TS server is not separate from the MAS server...all other functions are on the old slower server. The installation and setup of the server was managed by the Reseller and the company's IT folks...not me.

If he shivered at reinstallation I can't wait to hear the reply when you suggest modifying the registry...

did you ever get this resolved @DebThomas - having a similar issue - RDP, right to MAS 90 server, all new tasks open behind current task. Version 4.5 PU5

Nope, no answer Eric. It still miffs the client. I've not found a solution.

The ForegroundLockTimeout registry edit didn't work?

Same questions as Phil. We have not run into this issue and regularly TS to MAS on 2008 servers at clients; however, when we eventually do have this issue, I would have the IT person try the registry entry for a session and see if it worked. If so, see if they can produce a reliable group policy. I am not sure how this actually works as there is only a single MAS client on the TS. Must be session related.

haven't tried it yet but we will

It seemed to work for me when I applied it to my RDP login.

@DebThomas - just want to confirm that the fix that @CatherineFrias posted does work for this issue (tasks opening behind other tasks in MAS)- corrected the problem for all the users at this particular client using RDP.

Cool @EricAnderson ! I'll pass it along to the IT guys at the client. They won't let me near their Registry... :)