Solved

EXE takes a long time to open from network location

Posted on 2012-04-02
10
218 Views
Last Modified: 2013-03-02
Hi,

We have a business application installed on a virtual VM running Windows Server 2008 R2.
The software is configured to run as a RemoteApp through  Windows Remote Desktop Services. All users on our WAN use the software this way and it works great.

We have a few users located in the same LAN as the VM and we would like them to be able to run the software directly across the LAN. So we set them up with mapped drives to the server and put the shortcuts on their desktops.

Here's where it gets weird. When they open the network shortcut directly it takes no less than 5 minutes to see the software login screen. Once the user logs in everything works great and it's very responsive. I've monitored the task manager during the startup and it looks like RAM usage for the EXE is increased very slowly from ~1MB to ~27MB, it is at this point that the software opens up on the screen.

I've tried this on both Windows 7 Pro and XP Pro. I've turned off IPv6 both on server and workstation. I've turned off TCP Chimney, RSS, and NetDMA on the server. I've updated the NIC drivers, put the software in the list of firewall exceptions both on the server and the workstations. Our physical server has dual Xeons and 48GB of RAM 8 of which are dedicated to the VM.

Not sure why this is so slow but I'd like to get it fixed and I'm running out of options.

Thanks
0
Comment
Question by:marishal
  • 5
  • 4
10 Comments
 
LVL 19

Expert Comment

by:bevhost
ID: 37800488
What antivirus program do you use?
eg: Microsoft Security Essentials is notorious for this, as it scans the EXE for virus before it lets it be opened for execution.  I expect others have similar problems.
0
 
LVL 31

Expert Comment

by:Justin Owens
ID: 37801639
You are comparing apples to rocks. :)  Running as a RemoteApp forces the server to do the computing and network communications the application uses.  It just sends the results to the client machine.  Running from a network share forces a much bigger network pipe, forces the client to do the computing, and will interfere with the RemoteApp server in other ways.  In addition to making sure the AV clients on the server(s) and workstation(s) are correctly configured with proper exclusions, I would recommend a couple of things:

1. Make sure the application will support remote EXE execution from a network share.  Some applications simply will not support that configuration.  There is no reason to spin your wheels if you are doing something the application was not designed to do.

2. Create an additional VM which is not a RemoteApp server and see if you get better results by breaking up that workload.

DrUltima
0
 

Author Comment

by:marishal
ID: 37801761
Thanks guys for your input. As much I like to include all details I obviously have missed some :)

There's no anti-virus on the server and I tried it on a workstation without an AV - no impact

The software was running in a different branch in a similar set-up (Remote Desktop Services server) and local users were able to load the software on the network fast, so the software itself supports "remote execution".

Is there anything else pertaining to Windows 2008 R2 that I need to do to enable or make sure that "remote execution" is working properly?

I can't split VMs because 1) not sure if the application will handle multiple front ends with 1 database and 2) we will need additional licenses and management overhead for something you would think should work out of the box.

Thanks
0
Simplifying Server Workload Migrations

This use case outlines the migration challenges that organizations face and how the Acronis AnyData Engine supports physical-to-physical (P2P), physical-to-virtual (P2V), virtual to physical (V2P), and cross-virtual (V2V) migration scenarios to address these challenges.

 
LVL 31

Expert Comment

by:Justin Owens
ID: 37801836
Why can't your local users also run it as a RemoteApp?
0
 

Author Comment

by:marishal
ID: 37801909
Because if they ran in RemoteApp they will use up RD licenses and we prefer to avoid the additional expense (we're currently adding users).

It is also quite frustrating that we're running the latest and greatest yet we can't open a 27MB file over the network in a timely manner.
0
 
LVL 31

Expert Comment

by:Justin Owens
ID: 37801932
Can you give us the name (and version) of the application you are trying to run?

DrUltima
0
 

Author Comment

by:marishal
ID: 37802819
It's called Humanis and we're running version 2007.0.0.62
0
 
LVL 31

Expert Comment

by:Justin Owens
ID: 37850813
marishal,

There are actually several software packages I found with that title.  Would you mind giving the vendor information as well?  I am trying to research it to see if a remote operation environment is supported.  Often times vendor white papers will include information like that.

DrUltima
0
 

Accepted Solution

by:
marishal earned 0 total points
ID: 38926363
The server was replaced and we no longer have this issue
0
 

Author Closing Comment

by:marishal
ID: 38944827
There were no other solutions
0

Featured Post

Efficient way to get backups off site to Azure

This user guide provides instructions on how to deploy and configure both a StoneFly Scale Out NAS Enterprise Cloud Drive virtual machine and Veeam Cloud Connect in the Microsoft Azure Cloud.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

To effectively work with Diskpart on a Server Core, it is necessary to write some small batch script's, because you can't execute diskpart in a remote powershell session. To get startet, place the Diskpart batch script's into a share on your loca…
The recent Microsoft changes on update philosophy for Windows pre-10 and their impact on existing WSUS implementations.
This tutorial will walk an individual through locating and launching the BEUtility application to properly change the service account username and\or password in situation where it may be necessary or where the password has been inadvertently change…
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…

830 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question