Some of you may run into a known issue with what type of command lines for MSI/MSP based updates you can now use in the new System Center Updates Publisher 2011. In previous version of Updates Publisher we have left the command line unrestricted, meaning you could put pretty much anything in there. This caused a lot of problems due to invalid command line parameters (see here for more details) such as /qn or /q for MSI and MSP based updates.
With Updates Publisher 2011 we decided to put validation on the field to force a name=value format, the only format allowed per WSUS/WUA. In doing so we inadvertently put a restriction on the use of the dash “-“, meaning that if you have a command line parameter that includes the product key such as PID=1234-1234-1234-1234-1234 will be invalid. Another example is if you have a computer name with a dash in it (i.e. server=jason-pc) will also not work. You will not be able to import or create such an update in Updates Publisher 2011. This is a known issue with no current workaround. We will look at addressing it in a future release.
Apparently "." (periods) are restricted as well. I added SMSSLP=host.mycompany.com and it failed the validation check. When I removed the periods, the command-line passed the validation check.
Thank you for reporting. I've added information to this known issue.
It is now January 2013 is there a fix or a workaround for this yet?
Not yet, are you having the issue with periods or dashes or some other variation?
Yes, I am trying to publish the ConfigMgr Client MSP's and would like to specify the SLP and FSP with FQDN's
January 2014; still no fix!?