As Thomas pointed out, the recommended method of importing packages into MSP is to copy them into the PackagesToInstall folder. Using this method, there is no possibility of a timeout occurring on the import.

I need to correct my last posting. While using the PackagesToInstall folder is the recommended method of importing large apf files, the statement that there is no possibility of a timeout is not accurate. There is a chance of a timeout on the database import for VERY large packages (was reported when attempting to upload a file slightly larger than 500MB). However, we do not publish a definite max file size limit because it could vary based on several factors. Examples of these factors include SQL Server hardware performance, connection speed between MSP and SQL, package contents and more.

I have had page time-outs occurring loading OS packages up into MSP as well, keen to hear about how people get around this??? Steve

...have the same experience on very large packages like OS packages. If you cannot upload the package via Web UI you could copy the package to folder "\Motorola MSP\PackagesToInstall" on the MSP Server.   Thomas