Best Way to Deploy Application
Hi Experts!
I need an quick, efficient and easy way to deploy an executable that resides on a VM on my network. This VM also houses the backend database for this application (SQL Server 2008 R2) so they would somehow need to tie into the database as well. About 6 to 10 people would be using this application.
Any help with this is GREATLY APPRECIATED!
P.S. TS is not available on the 2008 Server box for some reason under "Server Manager." > Roles > Add Roles.
I need an quick, efficient and easy way to deploy an executable that resides on a VM on my network. This VM also houses the backend database for this application (SQL Server 2008 R2) so they would somehow need to tie into the database as well. About 6 to 10 people would be using this application.
Any help with this is GREATLY APPRECIATED!
P.S. TS is not available on the 2008 Server box for some reason under "Server Manager." > Roles > Add Roles.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
DustinKikuchi
In Server 2008 R2 Terminal Services was renamed to Remote Desktop Services. If that's an option for you, start there.
ASKER
The Remote Desktop Services is great. I guess I need to put a copy of the .exe out there in each profiles Desktop? I actually did that with one of my co-workers and he RDP'd out to that box, clicked on the .exe and is getting an error. It's gotta be that it's not seeing the DB or he doesn't have the appropriate permissions to see the backend. I've went in to the db and into the properties of the database > Permissions and have given "Guest" profile access to execute. Still a no go though, he's getting the same dialog prompt.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I've actually tried to create the .MSI and run the "Create .rdp" file both return the following error attached. it's connecting to the VM like it should, prompts them to logon, which they do, then it even unwraps the .exe to the desktop. They will get the error attached when trying to execute the application. My application comes with a logon prompt, which you must enter credentials to get into it, but surely it wouldn't be asking for those credentials. I've been having my two people that have been testing this on their boxes enter in their network login credentials, should they be entering in the applicaitons credentials instead? Besides the executable should I also be adding something else with the database. If I were a betting person I'd say they aren't seeing the database for some reason due to permissions issues with the database not the frontend app.
"dbreporting" is the name of the database""
Capture.JPG
"dbreporting" is the name of the database""
Capture.JPG
It looks as if RDP is doing what it should be doing. I would guess that the app is at least finding the database as you're not getting an error stating that dbreporting cannot be found, but permissions do seem to be an issue. Upon initial connection via RDP your users are likely being prompted for their credentials to log in to the server itself, however if they have saved those credentials it's entirely possible that they are being send directly to your application's login prompt.
If at all possible I would suggest trying to access the application via RDP yourself so that you can see exactly what is happening to get a better handle on the situation. At this stage, unfortunately, remote diagnosis is going to be difficult.
If at all possible I would suggest trying to access the application via RDP yourself so that you can see exactly what is happening to get a better handle on the situation. At this stage, unfortunately, remote diagnosis is going to be difficult.
ASKER
My latest efforts:
1.) Shared out the program folder on server that contains all of the applications files, .exe etc.
2.) Installed .NET Frameworks 4.0 and Crystal Reports on client machine (Program needs these to run correctly.)
3.) Created a shortcut to the .exe from the client machine to the server.
4.) Should be able to login with application credentials at logon prompt of application (Not Server)
Getting this error now when doing the above: See attached.
Capture.JPG
1.) Shared out the program folder on server that contains all of the applications files, .exe etc.
2.) Installed .NET Frameworks 4.0 and Crystal Reports on client machine (Program needs these to run correctly.)
3.) Created a shortcut to the .exe from the client machine to the server.
4.) Should be able to login with application credentials at logon prompt of application (Not Server)
Getting this error now when doing the above: See attached.
Capture.JPG
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for all the great input.