This was originally posted in the Server 2012 forum, but perhaps it's more applicable to Windows 7.             

I've joined the Windows 7 Pro workstations to the Domain using the SERVER2012/Connect app and that seemed to work fine.  I made the Users all Standard, not Admin, and access to the Shared folders is working fine too.  Users appear to be in the Administrators group on the local machine, which is what I need.

However, a number of our applications aren't working correctly ... one writes changes to HKey Current User and those changes will not stick.  Some IE sites that require changes have to be made each time; those changes don't save.  Some of the ODBC connections to SQL databases are behaving strangly as well.  I tried checking permissions on the Windows Registry keys, and they looked OK.  Turning off User Access Control did not help either.

If I log on to the workstation not using the Domain Account I don't have this problem.  And, one of the workstations which had performed the Windows 10 Upgrade while connected to the previous Domain Controllder works fine.

Any direction would be greatly appreciated!   Thx DMiller

Hi DMiller,

Thank you for your question.

Could you tell us more details which is about the issue on Windows 7?

Did the issue occur on any Windows 7?

We could do a clean boot on issued Windows 7 by the following link:

https://support.microsoft.com/en-us/kb/929135 

If there are any questions regarding this issue, please be free to let me know.

Best Regard,

Jim

Something is different about the way the user is added to the locaL machine using the Server 2012 CONNECT app.  I've been manually taking ownership of certain registry keys in the HKEY Local User section and replacing permissions; it's been a rather tedious process.  Uninstalling and reinstalling the applicatinos (there are several from different vendors) did not help.  Also, certain bank web sites only work properly if you launch IE 11 as Administrator. 

When I sign on to the machine using a non-domain account we have no issues at all. 

i'ved used the CONNECT app in other places without this issue; what's different about this one is that I had to leave the old domain before I could join the new 2012 domain.

Thx DMiller

Hi DMiller,

Windows 2012 domain is same with old domain in some basic function.

We could install a new OS and not install third application, then join it into domain to check if the issue persist.

If it work very well, the issued could be caused third application.

In addition, we could check if there are any errors in application logs and post it for our troubleshooting.

If there are any questions regarding this issue, please be free to let me know.

Best Regard,

Jim