Cannot run application on Windows 10 client connected to Server 2012 r2.

Dear Experts -

Recently we upgraded in-house PCs to Windows 10.

PCs are normally logged in to the  server as domain/user.

All seemed to be fine until last week.

Now one appication will not run unless the client PC is logged in as a Domain/ Administrator, obviously it is not wise to let client PCs login as domain administrator.

I have contacted the providers of the application who say its a permissions problem, but will not be more specific.

Any ideas ?

Many Thanks.
Chris ColemanAsked:
Who is Participating?
 
JohnConnect With a Mentor Business Consultant (Owner)Commented:
Now one application will not run unless the client PC is logged in as a Domain/ Administrator

You should not allow this to happen. It is for sure not a Windows 10 problem and the application providers should tell you how to change permissions to allow the application to run as Standard User.

Consider changing the application if they cannot help you (they appear to be behind the 8-ball and not keeping up).
0
 
Anand PandyaCommented:
You can try by running specific application/service using Run as different user and and that user in administrators group of that machine. Hope it should work else will require some more details.
0
 
Chris ColemanAuthor Commented:
Experts,

           Yeah changing the application is a big problem, its essential for the business and has run successful for at least 10 years.

Its uses a database which is located on the server.

Strange thing is that it was working on windows 10 until a bunch of updates came in about 10 days ago.

Anyway I have to visit the client in the morning - I'll post here when I've finished problem solving.

Many Thanks.
0
 
Chris ColemanAuthor Commented:
After contacting the venders again and after quite a heated conversation they not so gracefully admitted that it might not be a permissions problem.

It turned out to be a DB connection that was failing (periodically), after instructing me on a different way to connect to SQL the problem appears to be solved.

Sine the problem was periodic/random I'll assume at it could possibly happen again, but think that unlikely because before fixing it we found away to make it happen upon demand.

Therefore I'll close ..

Thanks Again..
0
 
JohnBusiness Consultant (Owner)Commented:
Thank you for the update and I was happy to help.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.