Developer Install on WS 2008 R2 Fails

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Running the OOB developer gateway installer on a windows server 2008 R2 box
2.
3.

What is the expected output? What do you see instead?

I expect all of the script calls to execute cleanly, however several of them 
run into runtime errors. Not sure if I should be concerned...

What version of the product are you using? On what operating system?
The latest stable version, on Windows Server 2008 R2

Please provide any additional information below.

Attached is the output of the cmd window

Original issue reported on code.google.com by tr...@nveloped.com on 11 Feb 2013 at 8:39

Attachments:

• binary_install.txt

[GoogleCodeExporter]

I have set up the smtp server, and when I place the simple.eml file in the 
pickup folder, it gets placed in the /drop folder. 

However, there is no /dev/incoming folder. Similarly, there is no 
/dev/incoming/raw folder, which makes me think that the gateway isn't actually 
processing the message, and only the smtp server is. 

Original comment by tr...@nveloped.com on 11 Feb 2013 at 9:29

[GoogleCodeExporter]

Further investigation found an issue with PowerShell scripts ran on the 
PowerShell 3.0.
See the discussion here: 
http://wiki.directproject.org/message/view/CSharp+Reference+Implementation+Issue
+Forum/60370548#60389510

Release 1.2.0.1. has update the scripts.

Many of the installation scripts call the following:
powershell -Command "set-executionpolicy unrestricted -force".   
It turns out PowerShell 3.0 fails with the quotes in this paritcular instance 
of setting execution policy.  Removing the quotes allows us to change execution 
policy to unrestricted in both PowerShell 2.0 and 3.0

Original comment by joeshook@gmail.com on 19 Feb 2013 at 6:19

• Changed state: Accepted

[GoogleCodeExporter]

Fixed in release 1.2.0.1

Original comment by joeshook@gmail.com on 19 Feb 2013 at 6:23

• Changed state: Fixed