Sivarajan's Blog

SharePoint | Office 365 | Azure | JavaScript

How to create a reusable SharePoint Server 2013 bootable VHD using trial downloads – Part 4

Creating a SQL Server 2012 SP1 image with CU9 By default, we can create the SQL server image only for Database Engine Services and we cannot include BI features. But if we are creating an image with cumulative update 2 or above then, we can include all SQL server features. http://blogs.technet.com/b/scvmm/archive/2013/01/25/expanded-sysprep-support-in-sql-server-2012-sp1-cu2.aspx 1. Run the setup via command prompt and include the CU9 location. For my case, I have kept my update in SQLUpdates folder. 2. Image creation wizard will be opened and we can see our CU9 updates are included in Product Updates tab. 3. In the Feature Selection tab, select the required features 4. In the Ready to Prepare Image tab, we can see the action as PrepareImage 5. In the Instance Configuration tab, provide the instance id and this will be used after configuring the SQL Server later. 6. In the Complete, we can see the status of each selected features. Now we have completed the image creating for SQL Server 2012 SP1 + CU2. Create Slipstreaming SP1 into SharePoint Server 2013 We will follow the below post to, merge the SP1 with SharePoint 2013. Otherwise, we have to install the SQL Server 2013 and then run the SP1. It will make our life easier. The following post is based on SharePoint 2010 + SP1. But the same approve will work for SP2013 + SP1 also. http://blogs.msdn.com/b/ronalg/archive/2011/07/11/slipstream-sharepoint-2010-sp1-and-language-packs-w-sp1-into-rtm.aspx For my case, I have done the slipstream process like below, Now we have completed the SharePoint 2013 + SP1 slipstream process. Installing SharePoint 2013 + SP1 Here we can find the overview of SP 2013 installation http://social.technet.microsoft.com/wiki/contents/articles/14209.sharepoint-2013-installation-step-by-step.aspx Now we are going to install the SharePoint 2013 but the configuration will do the later. For installing the prerequisites, go to our SP2013 folder and run the prerequisiteinstaller file to install the prerequisites software. Click Finish and restart the machine. Open the same SP2013 folder and run the setup file again. After successful installation, it will ask us to run the configuration wizard. We will do the configuration later. So uncheck the checkbox and close the wizard. Installing all other Software’s We don’t have any restriction or limitation for installing the following software’s. 1. Visual Studio 2013 2. MS Office 2013 3. Visio 2013 4. SharePoint Designer 2013 Simply run the setup file and install the above software’s.  In the next post, we will see that how to create the master VHD. For other posts on this series Overview of the native bootable VHD and list of required software Create a native bootable virtual hard drive, installing windows server 2012 and configure boot menu Enabling desktop features in windows server 2012 SQL Server installation using slipstream mode, create the SP1 slipstream into SharePoint 2013 and single shot installation Create a master native bootable VHD using sysprep method Configuring Active Directory and Domain Services, SQL Server 2012 and SharePoint 2013

How to create a reusable SharePoint Server 2013 bootable VHD using trial downloads – Part 3

We will see here how to configure the Windows 2013 server step by step. After restarting our machine, we can see the new boot menu selection. On select the Windows 2012 Server trial option, wizard will guide us to configure the server. Note: Please remember to back up the VHD for each successful completion of software installations. . If we did any mistake in the installation process, we can simply restore the VHD file from backup and continue the steps instead of starting from scratch. For other posts on this series Overview of the native bootable VHD and list of required software Create a native bootable virtual hard drive, installing windows server 2012 and configure boot menu Enabling desktop features in windows server 2012 SQL Server installation using slipstream mode, create the SP1 slipstream into SharePoint 2013 and single shot installation Create a master native bootable VHD using sysprep method Configuring Active Directory and Domain Services, SQL Server 2012 and SharePoint 2013 Customizing the Windows Server 2012 for Development Environment By default, we cannot use our Windows Server as our Windows 7 or 8 OS. We will see how to change the server for that. Click the Server Manager Menu icon in the left corner in the task bar, navigate to Manage and Server Manager Properties menu item and please do the following changes. This will increase our server performance. 2. Again go to the Server Manager, select the Local server in the left navigation, in the properties window, and click the Computer name for giving a meaningful machine name. 3. It will ask us to restart the machine, and select the Restart later button. 4. Again go to the Server manager, and navigate to Local Server Click the IE Enhancement Security Configuration, and to the following changes 5. Like that, change your time zone. 6. In the same location, click the Windows Firewall, and click Turn Windows Firewall on or off in the left navigation and do the following changes, 7. Now restart the server. 8. After restarting the server, revisit the previous steps and make sure all the changes are happened as we expected. 9. Navigate to the Server Manager, and select the Dashboard in the left navigation and click the Add roles and features under the Configure this local server section. 10. In the Wizard, Select Installation Type as Role-based or feature-based installation 11. In the Server Selection tab, continue with default values, and skip the Server Roles tab now. 12. In the Features tab, do the following selection and click the Next and install the selected features. 13. After successful installation, restart your server. 14. Now the server is ready and you can able to connect your server with WIFI. 15. In the Task bar, we can see the notification alert Turn on Windows SmartScreen, select warn before running on unrecognized app option. In the next post, we will install the SQL server using PreparedImage option.

How to create a reusable SharePoint Server 2013 bootable VHD using trial downloads

Overview Few of my friends are from Microsoft backgrounds and they are more interested to learn the SharePoint. They always raise the first question to me on how to setup the SharePoint on their laptop and desktop. My answer for their question is, buy a Lenovo W530 with 32GB RAM (my laptop configurations :)) and you can find a lot of posts available in the internet for setting the SharePoint through Microsoft Hyper-V. But most of them have a machine with 4 or 8 GB RAM and Windows 7 or Windows 8 as a base OS. Due to this constraints, they never started SharePoint still now. So I plan to build the native bootable VHD for them. It guess that this will solve the RAM issue. Another side, we need a Software license for Windows Server 2012, SharePoint Server 2013, Visual Studio 2013 and MS Office 2013 for long use. So I plan to build the native VHD using trial downloads and use the sysprep method installation for reusing the trial VHD for multiple times to avoid trial expiration problem. The main advantage of this approach is that, you don’t need to create the physical hard drive partition for installing Windows Server 2012 and does not affect your base OS and this is just pluggable when we required. I hope that this post series will be helpful if someone has the same situation. Note: This intention of this blog post is, how to use the trial downloads for evaluation/learning purpose and not for production use. For other posts on this series Overview of the native bootable VHD and list of required software Create a native bootable virtual hard drive, installing windows server 2012 and configure boot menu Enabling desktop features in windows server 2012 SQL Server installation using slipstream mode, create the SP1 slipstream into SharePoint 2013 and single shot installation Create a master native bootable VHD using sysprep method Configuring Active Directory and Domain Services, SQL Server 2012 and SharePoint 2013 List of Required Software Use the following link to download the required software’s for creating a VHD and the trial keys are available on each download pages. Windows Server 2012(180 days’ trial periods) - http://technet.microsoft.com/en-us/evalcenter/hh670538.aspx - download ISO evaluation version SQL Server 2012 SP1(180 days’ trial periods) - http://technet.microsoft.com/en-us/evalcenter/hh225126.aspx Cumulative update package 9 for SQL Server 2012 Service Pack 1 - http://support.microsoft.com/kb/2931078 - This will support a complete BI features through sysprep mode installation. Download and extract the exe from zip file. SharePoint Server 2013 (180 days’ trial periods) - http://technet.microsoft.com/en-us/evalcenter/hh973397.aspx SharePoint Server 2013 Service Pack 1 http://support.microsoft.com/kb/2880552/en-us Visual Studio Professional 2013 (90 days’ trial periods) http://www.microsoft.com/en-us/download/details.aspx?id=40763 Microsoft Office Professional 2013 (60 day’s trial periods) http://technet.microsoft.com/en-us/evalcenter/jj192782.aspx SharePoint Designer 2013 (free) - http://www.microsoft.com/en-us/download/details.aspx?id=35491 Microsoft Visio Professional 2013 (60 day’s trial periods) - http://technet.microsoft.com/en-US/evalcenter/hh973399?WT%2Eintid1=ODC_ENUS_FX103791368_XT104000918&WT%2Eintid2=ODC_ENUS_FX103791368_XT104000916 (This is required for SharePoint 2013 designer workflow) Note: All the software are from Microsoft are ISO files. If we want to open this ISO files from Windows 7, we can use the Virtual CloneDrive software. In the next post, we will see that how to create the bootable VHD using ImageX.

SharePoint 2013 Designer Workflow – Creating a Custom Task Outcome – Part 3

Overview In this post, we will see that how to create the custom task outcome. First we will see what that is and why the task outcome is so important. Default Task Outcome By default, if you assign a task to someone in SharePoint 2013 workflow, the task output will look likes below. But as per our helpdesk workflow requirement, while employee raise a ticket, the new task will be created and assigned to IT Admin user group. In this stage (Waiting for IT Admin Approval stage), he can either assign to Support Team for implement or assign back to Employee if there is any clarification and he is not going to approve or reject functionality. So our new task form output will be look like that, We need to follow the below steps for implementing the new requirement. Create a new Task Outcome Column Create a new Content Type Changes in Helpdesk Workflow Use the Task Outcome Step 1: Create a new Task Outcome Column We will create a new site column RequestClarificationOrAssign with the following values Step 2: Create a new Content Type We will create a new site content type Request Clarification Or Assign - IT Admin View based on Workflow Task (SharePoint 2013) Content Type. And then add a site column RequestClarificaitonOrAssign with newly created content type. Now add this content type with Helpdesk Task list and the task list content type will look like, Step 3: Changes in Helpdesk Workflow Edit the Helpdesk WF workflow using SharePoint Designer 2013 Inside the Waiting for Approval Stage, select the Assign a Task to IT Admin action Select the Task Properties Expand the Outcome Options Select the Task content type as Request Clarification Or Assign – IT Admin View So the output will look like below Save and republish the workflow. When we create the new task, the task output screen will look like below Step 3: Use the Task Outcome IT Admin will click either the Request Clarification or Assign button. So we should capture the action using local variables and will use in If condition action Again select the Assign a Task to IT Admin action Select the Task Outcome Create the local variable ReqClarificationOrAssignOutcome 4. Now edit the If condition next to Waiting for Approval stage 5. Set the local variable ReqClarificationOrAssignOutcome like below 6. Based on the IT Admin action, the next stage will be either Request Clarification or Assign for Implementation Summary I hope that now we know how to create and use custom task outputcome.

SharePoint 2013 / Office 365 : Debugging a Designer Workflow – Part 2

In the designer workflow series, we will see that how to debug the current helpdesk workflow. Unfortunately we cannot debug a SharePoint Designer Workflow. But we can easily debug the workflow if we have developed using Visual Studio 2012/2013. Alternatively we can use the following tools to trace the designer workflow. Log to history list Activity Fiddler (This will work only if we are accessing a workflow using http and not https) Using <system.diagnostics> Log to history list Activity In the previous post, we saw that how to use local variables. For the demo purpose, I just edited the Helpdesk Config list item and changed the TASK_APPROVAL_TEAM key value from IT ADMIN to UNKNOWN ADMIN. Now we will edit the existing helpdesk workflow and add the Log to history activity to explore the assignedTo local variable. Save and republish the helpdesk workflow. When we create a new task, due to UNKNOWN ADMIN  SharePoint user group, the current workflow was suspended. Here Log to history list activity help us to explore the workflow local variables. Using Fiddler We aware that the SharePoint 2013 workflow is not running inside the SharePoint worker progress. Windows Azure Workflow platform will be used for hosting and monitoring the SharePoint 2013 workflow. The communication between our system and workflow platform using two web services (http://localhost:12291 and http://localhost:12290). For more information, http://technet.microsoft.com/en-us/library/jj658588.aspx We can easily explore the each response or request using Fiddler if our on-premise SharePoint platform is connected via http workflow service. But this option will not be helpful if we are developing a workflow using Office 365. By default Office 365 is running via https. Using <system.diagnostics> I found the blog post with detailed walkthrough on how to enable the default workflow foundation trace log. After enabling that we can use the ULS log viewer for filtering the SharePoint log data. <system.diagnostics>       <switches>           <add name="System.Workflow LogToFile" value="1" />           <add name="System.Workflow.Runtime" value="All" />           <add name="System.Workflow.Runtime.Hosting" value="All" />           <add name="System.Workflow.Runtime.Tracking" value="All" />           <add name="System.Workflow.Activities" value="All" />           <add name="System.Workflow.Activities.Rules" value="All" />            </switches>   </system.diagnostics>   References http://msdn.microsoft.com/en-us/library/office/dn508412.aspx http://msdn.microsoft.com/en-us/library/office/dn292551.aspx#bkm_03 http://blogs.technet.com/b/victorbutuza/archive/2009/02/26/how-to-enable-workflow-tracing-debug.aspx