Scheduling a powershell script - issues 1

[ShackDaddy]

Ok, I've been telling people that they should schedule an "ExportEdgeConfig.ps1" script to fire off every couple of weeks to capture changes to their environment and make sure that their edge is recoverable. But I can't get my script to work so far.

Here's what I've got right now:

powershell -PSConsoleFile "C:\Program Files\Microsoft\Exchange Server\bin\ExShell.psc1" -command ". 'C:\program files\Microsoft\Exchange Server\scripts\ExportEdgeConfig.ps1' '-CloneConfigdata:"C:\Edgedump.xml"'"

And here's my output:

C:\>powershell -PSConsoleFile "C:\Program Files\Microsoft\Exchange Server\bin\ExShell.psc1" -command ". 'C:\program files\Microsoft\Exchange Server\scripts\ExportEdgeConfig.ps1' '-CloneConfigdata:"C:\Edgedump.xml"'"Exporting Edge configuration information failed. Reason: Exception calling ".ctor" with "2" argument(s): "The given path's format is not supported."

Can anyone provide a working version?

Dave Shackelford
ThirdTier.net

 

[ShackDaddy]

Ok, I decided to create a workaround. Since my ultimate problem was passing the parameters, I decided to create my own version of the ExportEdgeConfig.ps1 script instead, one that had the path parameter hard-coded. If you want to do the same thing, look for the section of the script that looks like this:

#Usage 
#:: ./exportedgeconfig 
#-cloneConfigData:"C:\cloneConfigData.xml"

And insert this right after it:

$cloneConfigData = "C:\EdgeDump.xml"

Save that script under a new name. I called mine ExportEdgeDave.ps1. When it runs, it overwrites the existing file. I would like to be able to append the date to the script using another variable to set DaveDate to "get-date -format o" but after messing with it a while, I decided to keep it simple. If anyone else wants to offer a more elegant solution, I'm all ears.

Dave Shackelford
ThirdTier.net