<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/"><channel><title>Tools</title><link>http://mindsharpblogs.com/paul/category/106.aspx</link><description>Tools</description><managingEditor>Paul Schaeflein</managingEditor><dc:language>en-US</dc:language><generator>.Text Version 0.95.2004.102</generator><item><dc:creator>Paul Schaeflein</dc:creator><title>DeliverPoint :Permissions - Registered License for free</title><link>http://mindsharpblogs.com/paul/archive/2008/06/02/5724.aspx</link><pubDate>Mon, 02 Jun 2008 15:16:00 GMT</pubDate><guid>http://mindsharpblogs.com/paul/archive/2008/06/02/5724.aspx</guid><wfw:comment>http://mindsharpblogs.com/paul/comments/5724.aspx</wfw:comment><comments>http://mindsharpblogs.com/paul/archive/2008/06/02/5724.aspx#Feedback</comments><slash:comments>1</slash:comments><wfw:commentRss>http://mindsharpblogs.com/paul/comments/commentRss/5724.aspx</wfw:commentRss><trackback:ping>http://mindsharpblogs.com/paul/services/trackbacks/5724.aspx</trackback:ping><description>&lt;P&gt;We released an update to our product today. DeliverPoint :Permissions v3 includes a limited-functionality license for free. All the details can be found on &lt;A href="http://www.deliverpoint.com"&gt;http://www.deliverpoint.com&lt;/A&gt;.&lt;/P&gt;
&lt;P&gt;All of us at Barracuda are excited about this product. And we've hit our groove with quarterly releases, which means you can expect much more going forward!&lt;/P&gt;&lt;img width="0" height="0" src="http://www.schaeflein.net/blog/cptrk.ashx?id=99e6953f-e066-4c8b-84c1-b7850e62a133"&gt;&lt;img src ="http://mindsharpblogs.com/paul/aggbug/5724.aspx" width = "1" height = "1" /&gt;</description></item><item><dc:creator>Paul Schaeflein</dc:creator><title>Porting a SharePoint Designer (SPD) Workflow to Visual Studio.Net – Part 1</title><link>http://mindsharpblogs.com/paul/archive/2008/03/12/4434.aspx</link><pubDate>Wed, 12 Mar 2008 04:33:00 GMT</pubDate><guid>http://mindsharpblogs.com/paul/archive/2008/03/12/4434.aspx</guid><wfw:comment>http://mindsharpblogs.com/paul/comments/4434.aspx</wfw:comment><comments>http://mindsharpblogs.com/paul/archive/2008/03/12/4434.aspx#Feedback</comments><slash:comments>22</slash:comments><wfw:commentRss>http://mindsharpblogs.com/paul/comments/commentRss/4434.aspx</wfw:commentRss><trackback:ping>http://mindsharpblogs.com/paul/services/trackbacks/4434.aspx</trackback:ping><description>&lt;P&gt;I am working on getting a community site up to host these articles as well as the code. My hope is that all interested developers will contribute their solution to the various Actions that can be selected in SharePoint designer. &lt;/P&gt;
&lt;P&gt;This post is the first in a series. The series will discuss the porting steps as we presented in Seattle, but with the details filled in. (We had only 75 minutes to present, which is way too little.) Part 1 will discuss the virtual machine setup and the creation of the SharePoint Designer workflow that will be ported. &lt;/P&gt;
&lt;P&gt;Virtual Machine Setup &lt;/P&gt;
&lt;P&gt;When a workflow is created in SharePoint Designer, the site is updated with a few pieces that enable it to work. We want to ensure that we port all of these pieces, so we will be using two different web applications. The first at http://spdflow will be used for the SharePoint Designer workflow. The second at http://vsflow will host the Visual Studio workflow. Rather than use different port numbers for the web application, the hosts file (C:\WINDOWS\system32\drivers\etc\hosts) is updated with each of these host names. &lt;/P&gt;
&lt;P&gt;&lt;IMG src="http://www.schaeflein.net/blog/content/binary/hosts.jpg" border=0&gt;&lt;/P&gt;
&lt;P&gt;The virtual machine will also have the necessary applications installed: SharePoint Designer 2007 and Visual Studio 2005 with the Office SharePoint Server 2007 SDK. &lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;SharePoint Designer&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;We will use SharePoint Designer to create a workflow. The workflow will perform the most popular actions -- collecting data, creating a task and writing to the history list. This is accomplished via the following steps:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;In SharePoint Designer, open the site http://spdflow. 
&lt;LI&gt;Click File | New | Workflow. The Workflow Designer wizard is displayed. 
&lt;LI&gt;Name the workflow SPDFlow and attach it to the Announcements list. Leave the start options at the default, which is manually. (We'll be starting it often.) 
&lt;P&gt;&lt;IMG src="http://www.schaeflein.net/blog/content/binary/wizard1.jpg" border=0&gt;&lt;/P&gt;
&lt;LI&gt;Click on the Initiation button on the bottom 
&lt;LI&gt;Add a Workflow Initiation Parameter named InitiationField with a default value of Barracuda. Then click OK 
&lt;P&gt;&lt;IMG src="http://www.schaeflein.net/blog/content/binary/InitField1.jpg" border=0&gt;&lt;IMG src="http://www.schaeflein.net/blog/content/binary/InitField2.jpg" border=0&gt;&lt;/P&gt;
&lt;LI&gt;Back in the Workflow Designer wizard, Click Next. 
&lt;LI&gt;In Step 1, click on the Conditions button and choose Compare Announcements field. 
&lt;P&gt;&lt;IMG src="http://www.schaeflein.net/blog/content/binary/Step1Conditions.jpg" border=0&gt;&lt;/P&gt;
&lt;LI&gt;Choose the Modified By field and the account name of the current user. 
&lt;P&gt;&lt;IMG src="http://www.schaeflein.net/blog/content/binary/FieldName.jpg" border=0&gt;&lt;/P&gt;
&lt;P&gt;&lt;IMG src="http://www.schaeflein.net/blog/content/binary/SelectUsers.jpg" border=0&gt;&lt;/P&gt;
&lt;LI&gt;Click on the Actions button and choose Collect Data from User. 
&lt;P&gt;&lt;IMG src="http://www.schaeflein.net/blog/content/binary/CollectData.jpg" border=0&gt;&lt;/P&gt;
&lt;LI&gt;Click on the "data" link to invoke the Custom Task Wizard. 
&lt;P&gt;&lt;IMG src="http://www.schaeflein.net/blog/content/binary/CustomTaskWizard1.jpg" border=0&gt;&lt;/P&gt;
&lt;LI&gt;Enter "Collect Data Task" for the task name and click Next 
&lt;P&gt;&lt;IMG src="http://www.schaeflein.net/blog/content/binary/CustomTaskWizard2.jpg" border=0&gt;&lt;/P&gt;
&lt;LI&gt;Click Add to create a field. 
&lt;P&gt;&lt;IMG src="http://www.schaeflein.net/blog/content/binary/CustomTaskWizard3.jpg" border=0&gt;&lt;/P&gt;
&lt;LI&gt;Name the field "TaskField" and enter a default value of "DeliverPoint" 
&lt;P&gt;&lt;IMG src="http://www.schaeflein.net/blog/content/binary/CustomTaskWizard4.jpg" border=0&gt; &lt;IMG src="http://www.schaeflein.net/blog/content/binary/CustomTaskWizard5.jpg" border=0&gt;&lt;/P&gt;
&lt;LI&gt;Click Finish on the Custom Task Wizard. You will receive a warning about running instances, which can be ignored. 
&lt;LI&gt;Click on the "this user" link in Step 1 Actions. Select the account name for the current user. 
&lt;P&gt;&lt;IMG src="http://www.schaeflein.net/blog/content/binary/ThisUser.jpg" border=0&gt;&lt;/P&gt;
&lt;LI&gt;Click on the "Variable: collect" link in Step 1 Actions. Rather than put the data in a generically named variable called "collect," choose "Create a new variable" and name it "ListItemID" 
&lt;P&gt;&lt;IMG src="http://www.schaeflein.net/blog/content/binary/ListItemID.jpg" border=0&gt;&lt;/P&gt;
&lt;LI&gt;Click on the Variables button at the bottom of the Workflow Designer form. Even though we did not choose the variable named "collect," it was created for us. Remove it, and any other unused variables, from the list. 
&lt;LI&gt;Click Finish.&lt;/LI&gt;&lt;/UL&gt;
&lt;P&gt;SharePoint Designer will save the workflow and associate it with the Announcements list. Test the workflow by returning to the browser and navigating to the Announcements list.&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;On the context menu of a list item, select Workflows 
&lt;P&gt;&lt;IMG src="http://www.schaeflein.net/blog/content/binary/AnnouncementItem.jpg" border=0&gt;&lt;/P&gt;
&lt;LI&gt;On the Workflows page in the Start a New Workflow section, click on the name of the workflow (SPDFlow) 
&lt;P&gt;&lt;IMG src="http://www.schaeflein.net/blog/content/binary/AnnouncementItemDetail.jpg" border=0&gt;&lt;/P&gt;
&lt;LI&gt;The initiation form is displayed. Click Start 
&lt;P&gt;&lt;IMG src="http://www.schaeflein.net/blog/content/binary/InitiateWorkflow.jpg" border=0&gt;&lt;/P&gt;
&lt;LI&gt;The Announcements list is displayed, with a new column on the far right. The column name matches the name of the workflow and the value is "In Progress" 
&lt;P&gt;&lt;IMG src="http://www.schaeflein.net/blog/content/binary/InProgress.jpg" border=0&gt;&lt;/P&gt;
&lt;LI&gt;Click on "In Progress" to display the Workflow Status page 
&lt;P&gt;&lt;IMG src="http://www.schaeflein.net/blog/content/binary/WorkflowStatus.jpg" border=0&gt;&lt;/P&gt;
&lt;LI&gt;In the middle of the page is the name of the task: CollectDataTask. Click on this link to display the task. 
&lt;P&gt;&lt;IMG src="http://www.schaeflein.net/blog/content/binary/TaskDisplay.jpg" border=0&gt;&lt;/P&gt;
&lt;LI&gt;Click on Edit Item in the tool bar. This will display the custom task edit form for this workflow 
&lt;P&gt;&lt;IMG src="http://www.schaeflein.net/blog/content/binary/CustomTaskEditForm.jpg" border=0&gt;&lt;/P&gt;
&lt;LI&gt;Click on Complete Task 
&lt;P&gt;At this point we have a workflow that was created in SharePoint Designer. The next post is this series will move us further along our path. Stay tuned!&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;img src ="http://mindsharpblogs.com/paul/aggbug/4434.aspx" width = "1" height = "1" /&gt;</description></item><item><dc:creator>Paul Schaeflein</dc:creator><title>Porting a SharePoint Designer (SPD) Workflow to Visual Studio.Net</title><link>http://mindsharpblogs.com/paul/archive/2008/03/03/4399.aspx</link><pubDate>Mon, 03 Mar 2008 23:02:00 GMT</pubDate><guid>http://mindsharpblogs.com/paul/archive/2008/03/03/4399.aspx</guid><wfw:comment>http://mindsharpblogs.com/paul/comments/4399.aspx</wfw:comment><comments>http://mindsharpblogs.com/paul/archive/2008/03/03/4399.aspx#Feedback</comments><slash:comments>5</slash:comments><wfw:commentRss>http://mindsharpblogs.com/paul/comments/commentRss/4399.aspx</wfw:commentRss><trackback:ping>http://mindsharpblogs.com/paul/services/trackbacks/4399.aspx</trackback:ping><description>&lt;P&gt;Many have asked. Many have said it is not possible. At the SharePoint Conference in Seattle today (March 4&lt;SUP&gt;th&lt;/SUP&gt;, 2008), Todd Bleeker is presenting the steps necessary to take a workflow created in SharePoint Designer and port/convert it to a workflow template in Visual Studio! &lt;/P&gt;
&lt;P&gt;The process started with an innocent question back in the fall of 2007 at Mindsharp's TechWeek. All of the Mindsharp Authorized Trainers, and one lucky developer (me) we assembled to share what we know and learn from others. One session address this workflow topic. The session ended when the steps we attempted crashed the site collection. (Thank goodness for virtual machines!) The topic list of that week was submitted to Microsoft as potential sessions at the SharePoint Conference. They selected the workflow porting session to be presented. &lt;/P&gt;
&lt;P&gt;The task fell to SharePoint MVP and superstar presenter Todd Bleeker. As usual, Todd threw his considerable enthusiasm at the topic. I had the privilege of being a second set of eyes and a sounding board to Todd during the days leading up the presentation. Not only did I learn a ton about workflows, but I also interacted with many smart people who contributed ideas, encouragement and humor to us in the last 48 hours. I am honored to be the one to make this post, but I am not solely responsible for its content. I want to specifically mention &lt;A href="http://www.mindsharp.com/Default.aspx?top=ABOUT%20US&amp;amp;left=TODD%20BLEEKER_(OWNER)"&gt;Todd Bleeker&lt;/A&gt; (of course), Kimmo Forss of Microsoft, &lt;A href="http://www.whiteconsulting.com/about.htm"&gt;Marilyn White&lt;/A&gt; of White Consulting, &lt;A href="http://www.thorprojects.com/blog"&gt;Rob Bogue&lt;/A&gt; of Thor Projects, &lt;A href="http://www.mannsoftware.com/Blog/"&gt;David Mann&lt;/A&gt; of Mann Software and Woody Windischman. &lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;[Details to follow]&lt;/P&gt;&lt;img width="0" height="0" src="http://www.schaeflein.net/blog/cptrk.ashx?id=89c2e843-0a13-4301-8172-649fe5f9418a"&gt;&lt;img src ="http://mindsharpblogs.com/paul/aggbug/4399.aspx" width = "1" height = "1" /&gt;</description></item><item><dc:creator>Paul Schaeflein</dc:creator><title>SharePoint Utility: Adminstration Extension Download for SharePoint</title><link>http://mindsharpblogs.com/paul/archive/2007/09/12/2830.aspx</link><pubDate>Wed, 12 Sep 2007 13:12:00 GMT</pubDate><guid>http://mindsharpblogs.com/paul/archive/2007/09/12/2830.aspx</guid><wfw:comment>http://mindsharpblogs.com/paul/comments/2830.aspx</wfw:comment><comments>http://mindsharpblogs.com/paul/archive/2007/09/12/2830.aspx#Feedback</comments><slash:comments>1</slash:comments><wfw:commentRss>http://mindsharpblogs.com/paul/comments/commentRss/2830.aspx</wfw:commentRss><trackback:ping>http://mindsharpblogs.com/paul/services/trackbacks/2830.aspx</trackback:ping><description>&lt;P&gt;One common pain point for SharePoint administrators is the Windows SharePoint Services Timer Service, also known as OWSTIMER.EXE. The Timer Service is responsible for executing several processes that are part of the product. A few of the more well-known processes are the search crawl refresh, recycle bin processing and the workflow processes. Also, the Timer Service is the process that SharePoint uses to push web.config modifications and solutions to all front end servers in the farm. &lt;/P&gt;
&lt;P&gt;Two specific issues that are related to the Timer Service are its memory consumption and limited user interface. The Application Extension Download for SharePoint (AED for SharePoint) from Barracuda is designed to help system administrators deal with these issues. The download can be found in the Premium Content section of the Mindsharp web site. (The utility is free, but you will need to provide your name and email.) &lt;/P&gt;
&lt;H4&gt;Timer Operations Syntax &lt;/H4&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;B&gt;Restart Timer &lt;/B&gt;
&lt;P style="MARGIN-LEFT: 36pt; FONT-FAMILY: Consolas, serif"&gt;stsadm -o restarttimer &lt;BR&gt;{ -farm | -server &lt;SERVER name&gt;;&lt;SERVER name&gt; } &lt;BR&gt;[-exclude &lt;SERVER name&gt;;&lt;SERVER name&gt;] &lt;BR&gt;&amp;nbsp;&lt;BR&gt;Restarts the Windows SharePoint Services Timer service &lt;BR&gt;on servers in the farm. &lt;BR&gt;&amp;nbsp;&lt;BR&gt;Use the -farm parameter to restart the service on all servers &lt;BR&gt;in the farm that have the service installed. &lt;BR&gt;&amp;nbsp;&lt;BR&gt;Use the -server parameter to specify the servers on which to &lt;BR&gt;restart the service. &lt;BR&gt;&amp;nbsp;&lt;BR&gt;Use the -exclude parameter in conjuction with -farm to restart &lt;BR&gt;the service on all servers except those listed.&lt;BR&gt;&amp;nbsp;&lt;/P&gt;
&lt;H4&gt;Enumerate Timer Jobs &lt;/H4&gt;
&lt;P style="MARGIN-LEFT: 36pt; FONT-FAMILY: Consolas, serif"&gt;stsadm -o enumtimerjobs &lt;BR&gt;[-view {service | webapp}] &lt;BR&gt;[-service &lt;SERVICE name&gt;] &lt;BR&gt;[-webapp &lt;WEB url application&gt;] &lt;BR&gt;[-schedule] &lt;BR&gt;&amp;nbsp;&lt;BR&gt;Displays the Timer Job Definition information. &lt;BR&gt;&amp;nbsp;&lt;BR&gt;
&lt;H4&gt;Start Timer Job &lt;/H4&gt;
&lt;P style="MARGIN-LEFT: 36pt; FONT-FAMILY: Consolas, serif"&gt;stsadm -o starttimerjob &lt;BR&gt;{ -service &lt;SERVICE name&gt;| -webapp &lt;WEB url application&gt;} &lt;BR&gt;-job &lt;JOB name&gt;&lt;BR&gt;&amp;nbsp;&lt;BR&gt;Forces a one-time execution of the specified job. &lt;BR&gt;&lt;IMG height=0 src="http://www.schaeflein.net/blog/cptrk.ashx?id=29f6b96e-2d52-48b6-8c2b-543e62d82569" width=0&gt;&lt;/B&gt;&lt;/B&gt;&lt;/P&gt;&lt;img src ="http://mindsharpblogs.com/paul/aggbug/2830.aspx" width = "1" height = "1" /&gt;</description></item><item><dc:creator>Paul Schaeflein</dc:creator><title>AED for SharePoint</title><link>http://mindsharpblogs.com/paul/archive/2007/09/11/2827.aspx</link><pubDate>Tue, 11 Sep 2007 07:39:00 GMT</pubDate><guid>http://mindsharpblogs.com/paul/archive/2007/09/11/2827.aspx</guid><wfw:comment>http://mindsharpblogs.com/paul/comments/2827.aspx</wfw:comment><comments>http://mindsharpblogs.com/paul/archive/2007/09/11/2827.aspx#Feedback</comments><slash:comments>0</slash:comments><wfw:commentRss>http://mindsharpblogs.com/paul/comments/commentRss/2827.aspx</wfw:commentRss><trackback:ping>http://mindsharpblogs.com/paul/services/trackbacks/2827.aspx</trackback:ping><description>&lt;P&gt;At my new job, I work with a lot of &lt;A href="http://www.mindsharp.com/Default.aspx?top=ABOUT%20US"&gt;very smart people&lt;/A&gt;. I was chatting with &lt;A href="http://www.mindsharpblogs.com/Ben"&gt;Ben Curry&lt;/A&gt;, and he remarked about the troubles that a lot of administrators have with the OWSTimer.exe program. So, I wrote an extension to STSADM that will help manage this program. You can find the &lt;A href="https://www.mindsharp.com/"&gt;Adminstration Extension Download for SharePoint&lt;/A&gt; on the Mindsharp site. &lt;/P&gt;
&lt;P&gt;Feedback is appreciated. &lt;/P&gt;&lt;IMG height=0 src="http://www.schaeflein.net/blog/cptrk.ashx?id=2d1412e5-2dae-4d9c-8ba7-bafaff8fe174" width=0&gt;&lt;img src ="http://mindsharpblogs.com/paul/aggbug/2827.aspx" width = "1" height = "1" /&gt;</description></item></channel></rss>