So I couldn’t find anywhere where this was documented, but I had heard that you could. What happens when doing a client side PST migration is that the PST is chunked down in to 10 Mb chunks, by default. This is controlled through a setting in web.config, in your Program FilesEnterprise VaultWebApp folder.
By default we see :
<compilation debug=”true” />
<trace enabled=”true” />
executionTimeout=”[seconds]” – time in seconds before request is automatically timed out
maxRequestLength=”[KBytes]” – KBytes size of maximum request length to accept
useFullyQualifiedRedirectUrl=”[true|false]” – Fully qualifiy the URL for client redirects
minFreeThreads=”[count]” – minimum number of free thread to allow execution of new requests
minLocalRequestFreeThreads=”[count]” – minimum number of free thread to allow execution of new local requests
appRequestQueueLimit=”[count]” – maximum number of requests queued for the application
enableKernelOutputCache=”[true|false]” – enable the http.sys cache on IIS6 and higher – default is true
enableVersionHeader=”[true|false]” – outputs X-AspNet-Version header with each request
<httpRuntime executionTimeout=”90″ maxRequestLength=”10000″ useFullyQualifiedRedirectUrl=”false” minFreeThreads=”8″ minLocalRequestFreeThreads=”4″ appRequestQueueLimit=”100″ enableVersionHeader=”true” />
The setting is maxRequestLength.
If you change it to say 2500, and restart the EV server (perhaps just IIS, I didn’t test that) then you will see much smaller chunks being sent to the server from the client. I would think that this might be handy on clients where the network connection to the server isn’t very good/fast.