Describe the bug
hi, if you add a custom script, where you are using the native scriptlet Get-ScheduledTask it is conflicting with the function from BisF.psm1 which is identically named.
Steps to reproduce
- create a new custom script and store it in the custom folder
- you can use following simple line: (Get-ScheduledTask -TaskName $taskName).State
- in log file it is now looping, cause get-scheduledtask will trigger the function from module, and it does not have the same capabilities as the built in scriptlet
Expected behavior
maybe rename the BisF function to Get-BisFScheduledTask as this is commonly used in the module.
Screenshots
No response
Desktop, please complete the following information.
No response
Smartphone, please complete the following information.
No response
Additional context
Describe the bug
hi, if you add a custom script, where you are using the native scriptlet Get-ScheduledTask it is conflicting with the function from BisF.psm1 which is identically named.
Steps to reproduce
Expected behavior
maybe rename the BisF function to Get-BisFScheduledTask as this is commonly used in the module.
Screenshots
No response
Desktop, please complete the following information.
No response
Smartphone, please complete the following information.
No response
Additional context