We use Roaming network profiles with redirected appdata, and when our users try to open the Unity software (latest version) it hangs after the initial splash screen.
After digging around, I found that the “node_modules” folder, which should go into “%Appdata%\Roaming\Unity\Packages” is not being created in the users’ redirected Appdata folders.
If I copy the folder (and it’s contents) manually into a user’s redirected appdata then the software no longer hangs.
Is there anything anyone can suggest to avoid having to do this for a large number of users,
Thanks,
Tim
1 Like
Hi Tim,
You’ve got much further than we have…!
We have split appdata and profile paths, the only thing that works for us is turning off AppData redirection and allowing it to go local. Good luck!!
What I’ve now done is:
Copied the folder to a shared drive.
Created a simple XCOPY batch file to copy the folder into the correct part of the user’s redirected appdata on the network.
Told the teacher to get kids to run the batch file before they use the software for the first time.
Of course, they’ll need to redo this if their appdata folder is recreated. If no-one gives me a fix, I’ll throw together something more sophisticated - perhaps replace the Unity icon with a batch file that checks for the folder, copies it if not there, and then opens the software.