Do you have PEP turned on?  This can be disabled safely from the Administrator login menu.

I think you mean DEP? Yes it's as windows services only.

As far as standard mode is concerned. I tried it today from the client machine and it was the same or slower. 

I also tried to launch as administrator as someone asked earlier and that did not help. 

I also just tried to turn off real time protection on the server and launch on the client running directly on the server and it still took 30 seconds to open company maintenance. 

I meant PEP.  There have been a couple instances of problems when the service went down, and if you have a firewall blocking the address I could see how that might slow things down.

I know Sage won't like me saying this but I disable it on every system I install.

I meant PEP.  There have been a couple instances of problems when the service went down, and if you have a firewall blocking the address I could see how that might slow things down.

I know Sage won't like me saying this but I disable it on every system I install.

oh that, the last sage support person turned that off.

I think I found something that helped. So I went into the server and client network configs and disabled IPv6, added the domain name to the domain suffix and now my menus are loading in about half the time. 15 seconds is still pretty long but i'll take it over 30 seconds. 

15 sec is what I see for the launcher but other menu items would usually be a little faster. So it looks like it was a network issue trying to route to and from the server. Glad you got it to go faster

the 15 sec is to open any menu inside of the app. So it's still slow but it's definitely faster now. Why exactly I don't know without detailed logging from Sage. Support is telling me that they can't do detailed logging and to use perfmon. Not sure how Perfmon is going to give me details of what Sage is doing during the long periods of time. 

The delay in time is more than likely a wait for response from the application server. Is that delay the same on the server? When you setup the client on the server use the localhost IP address (don't want to require translation of name to ip). See if it is quick there. If it isn't fast with the client on the same server as the application server, you will not get it faster on the clients. This should rule out network delay if it is still slow on the server. (as long as you still have any antivirus, firewall, anything like those not running)

Yes it seems slow there as well as the clients. So there's something wrong with the server itself ?

Do you get a slowness there if you run it in Standard mode? Some call it MAS90 mode. I think it was mentioned before but was it run on the server with everything off that could be scanning what is happening? If it is still slow there then it could be Disk IO. Did you say you were on a SAN?

strange, when I run it on the server I get this strange error. But when I did the same thing at the client side it worked in MAS90 mode.

Yes we are on a SAN and I can probably run iometer and get over 3GB/s writes last time we checked. 

figured out my issue. I was trying to run from my workstation folder but i needed to run it in the sage server folder.  MAS90 mode took 45 seconds to open company maintenance. So that's definitely slower

run it from the server install not the client install files.  (edited to fix my transposing of locations)

Well if there is no antivirus or other programs monitoring applications like the antivirus then I would look at DISK IO. If the processor and memory are not maxed out in usage.