We are looking to start using a number of various Custom PowerShell Modules in our business, some of which will be using during PS Remoting.
For this reason, I thought that it would be more efficient and convenient to have these custom modules deployed to “C:\Program Files\WindowsPowerShell\Modules” for quick use during Invoke-command and PS Remoting sessions.
I know that this can be easily achieved via Group Policy and the Replace File option or similar, but I don’t think that this would be very efficient
The other option would be to possibly use a logon script to check if the files differ and update them - again, I wasn’t sure if this would be practical.
Does anyone have any suggestions how we can deploy Custom PowerShell Modules centrally and keep them up-to-date in a timely manner with minimal administrative overhead?
My guess is that in the early days, we might update them to LIVE a couple times a week or month it would be great to barley worry about them and still have consistent functionality on each machine.
Any suggestions are greatly appreciated (my best is a logon script that checks to see if the modules have been modified)