Improvements for Deploy-MEMCMPackage

[thoen008]

Additional features could be added or changed for this function.

• Right now the collection settings are in the packageconfig.json. We could move those settings to the Global and rewrite some of the logic. The reason I left them in the packageconfig was so that each collection could have it's own deployment settings per collection for that application and a different application packageconfig could have different deployment settings.
• There are additional settings available in the New-CMApplicationDeployment function used by this function. These could be added.
• Not tested on multiple sites
• When looking for an existing deployment it is assuming a match of publisher and product name is sufficient. Maybe this isn't good enough?
• This function is slow. It does multiple ConfigMgr function calls. Maybe using the admin service would be faster? Or direct SQL calls.
• The function New-CMApplicationDeployment will always set the available time to the current date/time. I did not find a way to not set that.
• It is currently using a + days model to set when the available start and available deadline are. So if you set the value of availStart to 6 it will add 6 days to the current date. Maybe this isn't ideal.
• Do we want some write information in this function for future troubleshooting?
• The New-CMApplicationDeployment function parameter -TimeBaseOn accepts UTC or LocalTime but when you set it to LocalTime it still uses UTC to set the start available and start deadline timestamps. The function currently uses Set-CMApplicationDeployment to fix this after the deployment is made. Maybe there is a better way.