2012 R2 RemoteApp RDP server won't run user logon batch scripts in GPO properly and worked perfectly in same OU with 2008 servers.

I have set up a 2012 R2 servers to function as a remoteapp RDS farm.  We have GPOs that run a batch file on logon to copy the User's outlook signatures from central location on network to the profile on the RDP server using robocopy.  These scripts are not working.  

I know the scripts are running because if I put a pause in them the RDP logon hangs(because of the pause).   I also have the GPO setting to disable the logon script delay and i know that is working because of the pause.

However I just cannot get the scripts themselves to function in remoteapp and I can't see what is happening or any errors because they run invisible.  They run when launched manually within the RDP session but not in the GPO logon script.  Any way to troubleshoot this?  This worked perfectly with 2008 RDP servers in the same OU.  The GPOs are somehow behaving differently in 2012 R2.  I also tried disabling UAC.  NOthing in the scripts requires admin rights.  It is just running robocopy and writing to a text file and the users have permissions to all locations.

What is different about 2012 R2 with logon script batch files from 2008?  How do I get this working or figure out what happening during the running of these scripts?
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Dirk KotteSECommented:
i think there are missing rights to copy the files to the location needed, or the profile-load is not complete at this time and the directories don#t exist.
i would append a ">>c:\temp\logfile.txt within the script to save output and error messages.
PS create the logfile "\temp\logfile.txt" before and set security for this file only to "everyone - full access"

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Remote Access

From novice to tech pro — start learning today.