8 Replies Latest reply on Mar 4, 2011 12:42 PM by LucD

    Confirm any "Set" commandlet?

    drwoodberry Enthusiast

      I am not sure if this is just me, or others are experiencing this issue, but I am in the process of modifying scripts I wrote using the 4.0 CLI to work with 4.1 PowerCLi. I have noticed outside the fact that you can no longer use $null for a password variable..it has to be an empty string, but that it seems that every statement that uses "Set" requires the -Confirm:$false to be in the command. In 4.0 this was not the case. Is this a common change? I have not downloaded or read the latest 4.1 cmdlet reference, but I was curious if this was normal and why.