https://www-secure.symantec.com/connect/articles/w...

To a certain extent, the system requirements are different if you have 20 packagers, when compared to having only one or two packagers.
I'm going to assume that you have read the Getting Started Guide and have determined which setup your environment needs - eg, whether you have the WPS sharepoint, SQL server and WPS source all on the same machine, or whether you plan to have a separate SQL server.
I believe disk space requirements are covered in the docs, but if you plan to hold the entire packaging project data and files on the WPS server, then I would recommend at least 500Gb or 1Tb of storage, especially if you have > 500 apps. That way you can keep the sources with the project files.

From a test workstation perspective, I would recommend a minimum of 512Mb RAM, otherwise intensive functions such as an SOE image capture are likely to fail.

If you have other specific questions, please post them here.

many thanks for the replies... 

https://www-secure.symantec.com/connect/articles/w...

first link posted was the one i needed.

- mike

The software also requires an SQL Server.

Forgot that little bit in there.

...make sure it gets installed before Wise Package Studio, as then WPS will pick it up and integrate with it, so that you can use WPS as the packaging mechanism for VS projects. Support for VS2008 should be in SP4 whenever it actually appears.

By the way - you only need IIS if you want to perform web captures on target machines.

If I recall correct the preflight also requires IIS as for the reporting

Yes, I'd been thinking of the functionality of the base WPS product, but of course, the Pre-Flight add on feature also requires IIS.

Although IIS is required for reporting, users would be well advised to create their own reporting functionality.

A client I worked for failed to notice that the reports were flawed, e.g. reporting files of 0 bytes or incorrect version information. Usefully, running an identical report minutes later would produce a different result for those files, although other files could then be mis-reported.

Before any exhortations, this *was* reported as a bug when the client was using v5.6. Here we are at v7.1 and he reports that it's still present. They're using my scripts instead.

Last time I looked, they were still using Crystal Reports 8.5 when the rest of the world were using version 11.
No doubt the rest of the world have moved on even further by now.
'scabbers - Is that what you ended up doing - using a modern tool to access the DB and gather information ?

All VBS, Ed. I had no need for fancy headers, fonts adjustable column widths and the rest of that kind of junk. Besides, I *detest* CR on principal.

I hate CR too, and my work PC, which is now popping up a ruler dialog box whenever I press Shift-R. Must track down what app that is and kill it.

Must track down what app that is and kill it.
I'm waiting for Ian to say: ProcMon? :)

Didn't need procmon - google was faster. It's apparently a well known annoyance associated with an IE7 developer plugin. As soon as I disabled the plugin, the problem went away. Whatever possessed Microsoft to use Shift-R as a hotkey is beyond my comprehension. Probably designed by a script kiddy who doesn't understand upper case usage through too many years of communication via texting.