Sage 100

Punch In/Out shortcut for TimeCard launches the program VERY slowly after 2013 Advanced to 2017 Advanced upgrade when launched over WAN (T1). The upgrade included a server move (from 2008 to 2012). File extensions excluded from RT virus-scanning. Anyone else run into this or have ideas how to determine why there is such a delay (5 minutes now vs seconds before)? Note: icon set up per Sage KB 34887. We tried substituting server name with IP address, but that didn't help.

Is everything else zippy with the upgrade? How fast does the punch in/out run when logged on as a user?

The Punch In / Punch Out screen is running Mas90 style (not Advanced client / server Mas200 style) over a WAN between buildings in different locations (maybe different cities). I would expect it to take 60 - 300 seconds, depending on physical distance, whether there's fiber cable, and whether there was a dedicated Internet connection instead of the normal shared Internet connection If it was taking 5 seconds before then the Punch In icon must have been RDP connected to a Terminal Server which was really running the Punch In screen. That or Citrix connected. There is one other thing. There's a KB article somewhere on how to setup a V/I auto-run import job to run on Advanced where it actually processes on the server instead of the normal Standard / Mas90 style (I know b/c I contributed that knowledge bit when I was there). The point is you can potentially configure the Punch In to run the same way and get back a ton of speed. Maybe your 2013 was even setup that way. You can tell by going to App Server Config and choosing Apps tab. Then check if you see a 3rd entry instead of the normal 2.

@JeffSchwenk, launches quickly inside Sage. @AlnoorCassim, is this the KB article? Looks intriguing, if this is it, I'll give it a shot. They previously ran from a desktop icon and I'm 95% sure it wasn't an RDP. There are only 2 entries in App Server Config on the old version.

Barbara yes that's the article.

Need a 2nd (or more) set of eyes. I followed the instructions in the KB as best I could, but not there yet. Wonder if the issue is in the .BAT file or the configuration in App Server. @AlnoorCassim

Ummm mostly in the App Server Config. Try the following: 0) Login to Sage 100 itself from that wkstn as user TC in the CSS company. That is to say the Launcher is up. Now do File / Run / TCWDAA and make sure you see what you're expecting. Also for another reason. 1) In App Server Config for PUNCHCSSR for the Start In Directory, the path should be: E:\Quantera\2017\Mas90\Home (I assume E: is a local drive of the server not a mapped drive) 2) In the .BAT file omit the AUTO. Only V/I supports that and in your case you want the Punch-In window to appear. 3) In the .BAT file add a new line with the word PAUSE. This stops the execution and helps you see if any error appears in the command prompt window itself. Take it out once it's all working.

Thanks @AlnoorCassim 0. Program launches successfully; 2. Done. 1. and 3. - probably will have to wait till Friday afternoon, when they all take off at noon. Stay tuned . . .

It works! By the way, on (only) one of the desktops, I found an RDP icon that launched that user to a terminal server, which had a TimeClock icon that he used. Other users deny they accessed it that way in the past.

For the deniers maybe they had the Punch-In setup with RDP but instead of seeing a TS desktop it was configured for them as a Published Application / RemoteApp to the TS. It would be seamless and they would never know they were going thru TS.