<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://forums.asp.net/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Search results matching tag 'New-Mailbox'</title><link>http://forums.asp.net/search/SearchResults.aspx?q=&amp;tag=New-Mailbox&amp;orTags=0&amp;o=DateDescending</link><description>Search results matching tag 'New-Mailbox'</description><dc:language>en-US</dc:language><generator>CommunityServer 2007 SP1 (Build: 20510.895)</generator><item><title>Re: New-Mailbox Issues</title><link>http://forums.asp.net/thread/2583452.aspx</link><pubDate>Wed, 27 Aug 2008 04:00:00 GMT</pubDate><guid isPermaLink="false">4c671506-2930-414c-a40b-8bf57ded5924:2583452</guid><dc:creator>loxschpen</dc:creator><description>&lt;p&gt;Well I have good news and bad news for you.&lt;/p&gt;
&lt;p&gt;First the bad: the fact of it all is that you CANNOT run the Exchange Management Shell from ANY ASP&amp;gt;NET application. Why is this you ask? Well our friends over at Microsoft have taken the ability to impersonate out of their new environment. I know I am in the same boat as you as I automated 3 companies with wonderful web services for Exchange 2000 and 2003 using CDOEXM....&lt;/p&gt;
&lt;p&gt;SO what is the good new? Well its this, you can run your scripts under a NON impersonated account. So what I did was create a new service account for Exchange 2007 and then tested to made sure it worked.&amp;nbsp; Now that I had that account I created a new WCF Workflow library in VS2008. Once I did that I was able to install it in IIS 7 and run the WF as my new service account.&lt;/p&gt;
&lt;p&gt;We can now get to work by taking an interface application via the web into our new WCF Workflow. Not only does the workflow make things nice and easy on programming, but custom error handling and even rollbacks are done for me. Now if something fails, I notify the user via an AJAX panel of the status of the job and dont let them submit the same one again until the issiues are fixed. This allowed me to teach the WF all about how to solve certain error codes making my applications moron proof.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;I am writing an article for the Code Project and DevX on it and I will have it posted out soon. Let me know if this helps you or what other direction you have gone down.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Regards,&lt;/p&gt;
&lt;p&gt;Timothy&lt;/p&gt;</description></item></channel></rss>