As long as you network is good you shouldn't have any issue. If you are thinking about a network sandbox, you should consider streaming your apps. You'll be able to perform Side-by-Side updates which are way more convenient and easy in case everything is streamed.
You have a lot of enterprise or legacy apps that don't store data on local drive, typically client-side app. To avoid the sandbox growing, you can flush it at the exit by uncommenting the following line in the package.ini:
RemoveSandboxOnExit=1
Even though network sandbox increases the network traffic and the load on the filer, having a network sandbox brings some benefits:
- keeping everything centralized
- keeping track of users sandbox size
- troubleshooting (update went wrong, sandbox locked, user doesn't find his document, etc.)
- if deployed both on virtual and physical, the user will keep his application preferences
Also note that even if you have a network sandbox, the unregister scripts for the apps will still be stored in "%APPDATA%\Thinstall\Unregister".
I set up one time a network sandbox for a customer with a NetApp filer. They are running streamed thinapps and network sandbox since one year without any issue.
In case you have roaming profiles and think it'll slow down user authentication, Persona Management provides policies to enhance performance.
See the View Administration guide regarding ThinApp sandbox folders:
Configuring User Profiles to Include ThinApp Sandbox Folders