Correct Application Install on a Terminal/Remote Desktop Session RRS feed

  • Question

  • I have a WinForm application which gets installed to a mapped drive on the network.  This process will get repeated for every Desktop/Laptop that needs to use this exe. 
    End Result Mapped drive contains all my DLL's and the EXE.  All network users point to this EXE.  It works great in this environment.

    My issue is a different client is trying to use a Terminal Server(TS)/ Remote Desktop Environment to run my software.  If using the same mentality they should be map a network drive and then install my software on each user session. 

    BUT their IT guy said you only need to install apps 1 time on a server.  So he did 1 time and the users are experiencing random app crashes, freezes, and strange errors that I have not been able to reproduce on any of our development machines.  Their IT person is reluctant to attempt to install on every user session claiming, "It doesnt matter".

    What is the proper/ recommended way of installing software on a TS so that user sessions are not "stepping on each others toes"?  That is what I believe it happening. 

    Thank you for any suggestions or feedback.

    Wednesday, January 30, 2019 7:24 PM

All replies

  • Hello,

    In regards to "stepping on each others toes", in this case the suspects would not be DLL or .EXE files but instead access to some form of shared data and/or configuration files.

    If it's a configuration file issue perhaps creating a personal config file in each user's Document folder.

    If data we would need more information.

    Please remember to mark the replies as answers if they help and unmark them if they provide no help, this will help others who are looking for solutions to the same or similar problem. Contact via my Twitter (Karen Payne) or Facebook (Karen Payne) via my MSDN profile but will not answer coding question on either.
    VB Forums - moderator
    profile for Karen Payne on Stack Exchange, a network of free, community-driven Q&A sites

    Thursday, January 31, 2019 3:07 AM
  • Thank you Karen,

    Actually it isn't data.  We have written our software with various data integrity checkpoints and edit checks.  We recommended installing our application on each user session. The IT person said he didnt want to do that and just installed it once on the server as administrator.  I am not sure if he put the server into "install mode" or some other special mode. 

    I have read a few internet articles about some method where you can put a server into install mode, install your software....somehow it creates some sort of config file for each user.  Then once install is complete you put the server back into normal mode.  I am not sure if that applies here or if that is what they did.  It just seems odd that on his Terminal Server our software doesnt work right...yet on  his other network it is setup on individual desktops and it works perfectly. 

    I just wasnt sure if there was a right way and wrong way of installing software on a TS.

    Thursday, January 31, 2019 3:23 AM
  • Hi,

    This forum is discussing and asking questions about the

    Best Regards,


    MSDN Community Support Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact

    Monday, February 11, 2019 2:17 AM