Exchange cmdlets without confirmation prompts??
Does anyone know of a simple, proven way to run Exchange cmdlets without the confirmation request? Many of the cmdlets require a confirmation, so running them in a powershell script loop is a pain. I've seen the common parameter Confirm mentioned several places with supplying the value false, but have never gotten it to work in all my tests. Is this the only way to do it, and if it is what is the actual, proper syntax that doesn't seem to be listed in any documentation?I've tried all of the following with it already, and all returned an error....-Confirm:"False"-Confirm:False-Confirm False-Confirm "False"It was my understanding that the Confirm parameter was just a boolean value. But when left out of the cmdlet syntax it gets set to true, and if added it gets set to true. So what is the way to set it to be false when a cmdlet is executed?
January 13th, 2008 10:01pm

Code Block -Confirm:$false
Free Windows Admin Tool Kit Click here and download it now
January 14th, 2008 12:30am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics