Closed codaamok closed 1 year ago
thanks so much @codaamok! no, you do not need anything special other than sometimes using -Force when using Import-Module to ensure your changes are enabled. This change looks solid and the integration tests pass 😊
I made some more changes:
DefaultParameterSetName
attribute; it threw an error not knowing which param set to use when the function was called without any paramswsusscn2.cab
) as suchLet me know your thoughts
Oh I think I'll add -UseWindowsUpdate
in Install-KbUpdate
, too
Thanks again, this code looks great -- appreciate the added functionality 👍🏼 Will merge and publish once tests pass again.
Hey, I hope you're well! Don't merge just yet, I have a question 😄
I have done two things in this PR:
-UseWindowsUpdate
inGet-KbNeededUpdate
; this lets users "forcefully" search against Windows Update even if Windows is configured to scan against WSUS - achieved by just setting ServerSelection to 2 on the UpdateServer interface.-Credential
parameter fromConnect-KbWsusServer
as it wasn't usedDo I need to do anything special to build the module in order to test with it? I still need to some more testing but initial testing proves OK. Right now I'm just modifying locally and importing the module from the repository.