As many of you may know , Microsoft SharePoint has been the largest-selling software product in the history of the company. In the last 11 years, since the arrival of SharePoint 2001, SharePoint has captured a large share of the collaboration market. Today, SharePoint 2010 is used widely as a content or document management system, for company intranets, extranets and public websites. We can define these terms as: Intranet - An intranet is the internal facing portal in your company for your employees Extranet - An extranet is the protected external facing portal in your company. It is used by business partners, clients and special customers Public Website - The public website is the public-facing version of your website. There are many benefits for organizations that use a common tecnology and framework for all of their web properties.  These include: Savings in software licensing costs A smaller pool of developers competent in similar technologies Historically, companies have been unable to use a common technology across the web properties because of the cost of the solutions, and the difficulty of using the solutions. SharePoint 2010 includes a number of rich content management features that help organizations to manage their content and keep it current.  These features include: Various page layout options allowing website creators to create pages quickly Ability to support rich streaming media Ability to roll up content easily Common meta data that allows content to be published once and available anywhere Better control during the authoring process Workflows for content review and approval Easy deployment from staging to production Web analytics In our subsequent blog posts, we will be discussing the specific features of SharePoint 2010 and third party products to help create a useful customer portals or extranets. About the Authors: This article is written by Niraj Tenany from Netwoven.  Niraj is the CEO of Netwoven and works with clients to assist them with their content management and big data strategies.  Niraj has extensive experience with SharePoint, Livelink, Documentum, Business Objects, Cognos and Microsoft BI tools.  Netwoven is a professional services firm founded by ex-Microsoft employees.  Netwoven specializes in the design and implementation of Enterprise Content Management, Business Intelligence, Business Process Management, Cloud Services, and Mobile Applications.  For additional information, please contact us at info@netwoven.com.

The SHRM Annual Conference & Exposition is just around the corner and the YPAC is gearing up for the event!  What does "YPAC" mean? YPAC stands for the Young Professionals Advisory Council.  As explained on SHRM’s website, the YPAC exists to serve the interests of SHRM young professional (YP) members and provide guidance to SHRM for attracting and retaining non-member YPs.  The YPAC also exists to ensure that SHRM YP activities are relevant to members and SHRM. Who is the YPAC? ...

Big Data has been a topic of intense discussion and media hype during the last year or two.  A number of people have asked Netwoven consultants the following questions: -          What is Big Data? -          What is Hadoop? -          What is Microsoft’s strategy for Hadoop -          How can I use Hadoop for my business? -          Is Big Data only about Hadoop? -          What is Predictive Analytics? -          How does Search integrate with Hadoop? -          How do SharePoint and Hadoop Integrate? -          How can users use PowerPivot and Hadoop? -          How can users use Powerview and Hadoop together? -          How is SQL Server and Hadoop integrated? -          How is SSAS and Hadoop integrated? -          Is statistics dead with big data since we do not have to deal with smaller datasets anymore? Netwoven has been actively working with Big Data, Hadoop, and Predictive Analytics.  Our team of consultants will be providing you with information through our blog at http://netwovenblogs.com. In this first blog article, we discuss what Big data is.  It has several definitions: -          According to some, BIG DATA IS ALL ABOUT seeing and understanding the relations within and among pieces of information that, until very recently, we struggled to fully grasp. -          Big data is data that exceeds the processing capacity of conventional database systems. The data is too big, moves too fast, or doesn’t fit the structures of your database architectures. To clarify matters, the three Vs of volume, velocity and variety are commonly used to characterize different aspects of big data. They’re a helpful lens through which to view and understand the nature of the data and the software platforms available to exploit them. Volume points to the volume of data that is flowing down the pipe today that organizations need to deal with.  Think about the volume of information that Bing, Google, Facebook create. Velocity points to the speed at which the information is coming down the pipe. Variety points to the various types of information that is generated today such as linkedin, blog, audio, video, facebook, twitter type of information. In addition to the three V’s a fourth V often has been added to mean ‘Value’. In the next blog post, we will go into more details of Big Data. Niraj Tenany Niraj specializes in Enterprise Content Management and Big Data business strategies and technologies. Follow Niraj:

Over the past year I have seen a huge uptake in the use of JavaScript Model View with SharePoint. A Model View library allows you to separate your data, presentation, and the transformation of that data to presentation view. The uptake is probably caused by two factors, first a rejuvenated interest in the MVC pattern, and second is the RESTful services SharePoint 2013 brings to the table. SharePoint 2010 also had these RESTful services, but they were new and didn’t provide all the functions that the 2013 services do. Here is a great drawing to explain the MVVM concept: Model: The data and business objects View: The presentation, the user interface View Model: A code representation of the data and UI operations In the next few installments of this blog I will go over some of the popular MV libraries out there (Backbone.JS, KnockOutJS, and Ember.JS) and how to make them work with SharePoint. After that we will take my favorite KnockOutJS and walkthrough how to provide a fully functioning newsfeed from SharePoint 2013 social feeds. Intro Backbone.js Ember.js KnockOutJS Reading Social Feeds Writing to Social Feeds Tying it all together Matt Maher Matt is a SharePoint architect currently focused on end user solutions, Office365, enterprise social apps, and server infrastructure. Follow Matt:

Overview You are trying to perform Windows Update and you receive the following Error: Error - "WindowsUpdate_8024001B OR WindowsUpdate_dt000″ Resolution Follow below steps to resolve the Update issue: Click on "Start" and type "cmd" (without the quotations) When you see the "cmd" icon, Right Click on it and select "Run as administrator" On the open Command Prompt window copy and paste the commands (all at once) net stop wuauserv net stop cryptSvc net stop bits net stop msiserver ren C:\Windows\SoftwareDistribution SoftwareDistribution.old ren C:\Windows\System32\catroot2 catroot2.old net start wuauserv net start cryptSvc net start bits net start msiserver pause Wait for the process to complete Close the Command Prompt Now, go to Windows Update and try installing the updates. Check if it helps. Note: This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, refer the steps: Click on the "Windows+R" keys simultaneously, type "regedit" (without the quotes) and hit "Enter". Now, click on "File" and select "Export". Save it to the desired location. If you make any mistakes while editing the registry, then you can just Right Click on the Exported file and select "Import" Now try to check for Update one more time and you should be able to resume your Update…

  Look at this chart. Does it resemble your employer’s organizational chart?    Now envision this: No pyramid. No managers. No directors. No vice presidents, senior vice presidents or chiefs.    Say hello to holacracy. It’s the latest method of operating an organization that removes power from a traditional leadership hierarchy and distributes it to every employee in an organization. In a holacracy there are no titles. Employees chart their own course, choose their own...

A number of people thought that Microsoft was not paying much attention to the Big Data space and that all developments were happening in the Linux platform.  Well, Microsoft was working in the background and exploring ways to provide these offerings using the familiar Microsoft tools.  Below is an overview of the various components in the Microsoft’s Hadoop offering: Below is a summary of the Hadoop components and it’s integration with the Microsoft ecosystem: Microsoft ported Hortonworks Data Platform (HDP) to Windows and is offering that as a service called HDInsight HDInsight runs as a service on Windows Azure and the HDInsight Server runs on Windows New Javascript libraries to integrate .NET programming with Hadoop ODBC Driver to Hive for analyzing data in Hadoop System Center extensions for managing Hadoop clusters Hadoop connectors for SQL Server Niraj Tenany Niraj specializes in Enterprise Content Management and Big Data business strategies and technologies. Follow Niraj:    

Overview: Error in MOSS 2007 search, this error occurs when index sever and query server are different and more than one query server exists. It turned out that the index had been corrupted on that server while the index was propagating from the index server. End User experience: While Searching from Portal, you get the below errors "Your search cannot be completed because of a service error" or "The search request was unable to connect to the Search Service" Problem:  When having two servers configured so that one acts as Search Indexing server (APP server) and the other acts as Search Query server (WFE), you get multiple errors in event log and the search does not work. On the Indexing server, errors are:  Error #1 Event Type: Error Event Source: Office Server Search Event Category: Search service Event ID: 10038 Description: Query machine <xyz> has been taken out of rotation due to this error: The object is not initialzed.   0x8004180b. It will be retried in 15 seconds. Component: 3a87986b-8ffe-41db-ae22-5e3fd1b9f4d9 Error #2 Event Type:Warning Event Source: Office Server Search Event Category: Search service Event ID: 10039 Description: Retry of query machine <xyz> has failed with error: The object is not initialzed.   0x8004180b.  It will be retried again in 60 seconds. Component: 3a87986b-8ffe-41db-ae22-5e3fd1b9f4d9 Error #3 Event Type: Error Event Source: Office Server Search Event Category: Content index server Event ID: 4127 Description: Content index on Portal_Content could not be initialized. Error The system cannot find the file specified.   0×80070002.Component: 3a87986b-8ffe-41db-ae22-5e3fd1b9f4d9 On Query Server the errors are: Event Type: Error Event Source: Office SharePoint Server Event Category: Office Server Shared Services Event ID: 6482 Description: Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (8fd1e03c-96df-4b7a-bd33-8da3fa924f03). Root cause of this symptom This problem occurs mostly when your Office SharePoint Service Search is not working (or configured correctly) or index had been corrupted on that server due to machine rebooting or some other reasons. Solution: First make sure the permissions are set correctly. Moreover, see that the Farm Search Service Account is in Administrators group and in WSS_ADMIN_WPG group on the Indexing and Query servers. After that stop and start theOffice SharePoint Server Search service in Central Admin. Also need to check that search service account have write permission on shared index of query server. 1. Stop Office SharePoint Service on all servers (command line option StsAdm.exe -o osearch -action stop) 2. Stop and Start MOSS timer service on all servers (OWSTIMER) (net stop "Windows SharePoint Services Timer"net start "Windows SharePoint Services Timer"  (If you wish to change the index location, you can do it then go for step 3) 3. Start office SharePoint Service Search service on index server first. (my observation is stsadm.exe command line tool works better StsAdm.exe -o osearch -action start -role index) 4. Start Office SharePoint Services Search Service on Query Server(s) next. (Command line option StsAdm.exe -o osearch -action start -role query) 5. Wait for couple of minutes. 6. Edit Shared Service Provider (SSP) settings. Select Index Server in drop down list. Provide service credentials and directory path for index location. Click OK 7. Wait for about 10 minutes and check server and search administration page. Restart requirement You do not have to restart the servers, need to configure and run full crawl.

Manufacturers are facing big problems when it comes to recruiting enough top-tier factory workers, but there’s a fix few employers think about — #workflex. Those employers who implement more flexibility on their factory floors are finding workflex is helping them attract and retain top talent. This topic will be front and center during an upcoming session at the Society for Human Resource Management’s (SHRM) annual conference next month in Las Vegas. (SPECIAL CONFERENCE OFFER BELOW) Manufacturers are facing big problems when it comes to recruiting enough top-tier factory workers, but there’s a fix few employers think about — #workflex....

Overview You have SharePoint 2010 deployed. You want to display your search results in a data grid format. Data Grid display would then give you opportunity to sort, filter and page. Solution The OOTB SharePoint 2010 CoreResultsWebpart provides the placeholder to display the search results, but by extending this webpart by adding the DataGrid control and custom loading the search result, we can get the grid visualization. Coding Example Let’s fire-up the Visual Studio in your SharePoint Development Server and create a visual webpart project. This can be done with the following steps: 1. Add reference to Microsoft.Office.Server.Search.dll from \Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\ISAPI 2. In webpart.cs file Inherit the webpart class from CoreResultsWebPart instead of default webpart. Then add the namespace Microsoft.Office.Server.Search.WebControls. The webpart is now inherited from CoreResultsWebPart. 3. Now, go to the usercontrol page (.ascx) of the visual webpart and add a gridview by dragging it from the Visual Studio toolbox. 4. In codebehind of the usercontrol (.ascx.cs) add a method named LoadSearchGrid and add the following namespaces: using Microsoft.Office.Server.Search; using Microsoft.Office.Server.Search.Query; using Microsoft.Office.Server.Search.WebControls; QueryManager object is used to get the xml returned by SharePoint Search and added as a datasource (xml Data Source) to the gridview. To achieve this, add the following codes to LoadSearchGrid method: // gets the instance of the querymanager QueryManager queryManager = SharedQueryManager.GetInstance(this.Page).QueryManager; Thereafter, define a DataSet and DataTable object. DataSet dtSet = null; DataTable dtTable = null; To get the Xml returned by Search add the following codes: if (queryManager != null && queryManager.Count > 0) { XmlDocument xdoc = new XmlDocument(); //We are using XmlDocument xdoc = queryManager.GetResults(queryManager[0])//xml returned by search // Get blended results if (xdoc != null) { XmlReader xmlReader = new XmlNodeReader(xdoc); dtSet = new DataSet(); dtSet.ReadXml(xmlReader); if (dtSet.Tables.Count > 1) { dtTable = dtSet.Tables["Result"]; //Add the DataTable object as a dataSource to GridView added in ascx page by the following codes: gridView.DataSource = dtTable; gridView.DataBind(); } } } Finally, Call the LoadSearchGrid function from Page_Load method by adding the following block of codes: if (!Page.IsPostBack) { LoadSearchGrid(); } 5. Handle the exception using proper try catch blog in code. 6. Build the solution and deploy. The search will be shown in gridview now. The query, fetched properties and every configurable properties of the CoreResultsWebpart in the custom CoreResultsWebpart can be manipulated. For sorting search result in gridview, a custom method is added which shall be discussed in my next article. Hope you will find this blog helpful and look forward to your comments!  

In the context of SP Online or SP 2013, we visualize them to be omnipotent, or if not for this, then atleast have much more vigour than their predecessors. What also bestows to the pool of features is also the availability of the SharePoint Designer (SPD) 2013 workflow. However, a little use of workflows using SPD 2010 also can extend the OOTB capabilities. Workflows need not just be visualized as a process to flow items or streamlines tasks among users, rather in the simplest form, a workflow can also update data in field. This article sheds lights on exploiting the capability of SP Online in conjunction with a SPD 2010 workflow to dynamically create documents in a document library. A SharePoint document library not only acts as a repository for documents, but it can also be used to dynamically generate documents as mentioned before. The process requires coupling the document library with a custom list with the same field definitions as the document library using a workflow and editing the document template to format it using Quick Parts to place fields of the document library. Though the process is worthwhile to generate documented format of a list containing simple text, there are still some limitations to this way of creation, in the use of embedding pictures or styling text. The following section details the entire process. Creating a Custom List for feed The process is verified to work well only with data of single or multiline text (selected as Plain Text). For the purpose of demonstration, a simple document library is created with columns of type single and multiline text. N.B.: In the document library, the Title column of the document library is renamed Member Name. To feed to this document library, a list is created, with columns mapped to that of the document library. N.B.: In this list, the Title column of the document library is renamed Member Name. As mentioned earlier, the only restriction with using multiline text is the use of Plain Text as illustrated below. Customizing the Document Library In the document library, go to Settings -> Advanced Settings and in the Document Template section, Edit Template. The template is opened in the default word application. To format the document to use data from the columns of the document library, position the cursor in the document and from the menu, go to Insert -> Quick Parts -> Document Property and select the column. Having formatted this template to place data as desired, save the template in the same location of the document library, but in docx format. Upon exiting from the word application, modify the extension of the document template in the document library to point to the modified template (docx instead of dotx). The document template is now ready to display details corresponding to each row of the document library as data gets filled in. The last task now remains to populate the document library. Dynamically populating the Document Library Having already created the custom list with columns mapped to that of the document library, create a workflow for the list, to copy list data to the document library. A single action SPD SP 2010 workflow suffices, by triggering it when items are created or modified in the list. In the given example, the document library is named Biographies, while the list is named Biography Details. In the list workflow, add an action to create item in the document library. Click on the document library name to set each field from the corresponding field in the list for all the relevant columns. Having done this, the final mapping will appear as in the below image. While all other fields can be edited or removed as desired, the only catch in the mapping process is to set the Path and name (*) field that is a non-removable field. This field essentially points to the file path, and it is required that this be set as illustrated below. N.B.: Here Member Name is nothing but the Title column (primary column) of the document library or the list. The workflow is now ready to be saved and published. As details begin being entered or modified in the list, the workflow will make corresponding changes in the data of the document library and create corresponding documents.

Overview You are browsing SharePoint site, and under the document library you try to open office document to edit from the client programs such as Word/Excel/PowerPoint. Issue If you face one of the below issues while trying to open an office document (Word, Excel, PowerPoint) Error Message 1: "there’s a configuration problem preventing us from […]

Overview You can upload your app for SharePoint to either the public SharePoint app store or to an organization’s private app catalog. A private app catalog is a dedicated site collection in a SharePoint 2013 web application (or a SharePoint Online tenancy) that hosts document libraries for apps for SharePoint and apps for Office. Putting the catalog into its own site collection makes it easier for the web application administrator or tenant administrator to limit permissions to the catalog. If the app is uploaded to the public app store, Microsoft runs some validation checks on it. For example, it checks whether the app manifest markup is valid and complete and verifies that any SharePoint solution packages (.wsp files) that are included do not include disallowed elements or Features with a scope broader than Web. The content of the package is also inspected for objectionable content. If the app passes all tests, the app package is wrapped into a file and signed by Microsoft. For more information about the validation process, see the SharePoint developer center. Uploading an app for SharePoint to an organization’s app catalog is as easy as uploading any file to a SharePoint Foundation document library. You fill out a pop-up form in which you supply the local URL of the app package and other information, such as the name of the app. When the app is uploaded to an organization’s app catalog, similar checks take place and apps that do not pass are marked as invalid or disabled in the catalog. Steps 1. Before you begin, you must have your custom app developed available as .app files with the codes put together in a single folder. Also your SharePoint online must have an app catalog site for which you should be office 365 Global administrator. 2. Open SharePoint admin center for Office 365 and click on apps in the navigation bar and open the office 365 app catalog. 3. Click on distribute apps for SharePoint to deploy your custom developed apps. You can manage any app request from users for existing apps here or also deploy office apps from here.   4. Click on new to add the custom add to the existing catalog and browse to your location where the .app files are stored locally. 5. Once deployed, please provide permission to at least one user who can use this app by clicking on Share with menu. Your app is now deployed and ready to be consumed. Conclusion Further reference of building and deploying apps can be found at https://msdn.microsoft.com/en-us/library/office/jj163230(v=office.15).aspx

The first five Society of Human Resource Management Annual Conferences that I attended found me at a booth in the Exhibitor Hall. It is a labor of love. You stand on your feet for 12 hours conducting conversations with people who may or may not be your ideal customer. The Exhibitor Hall is talked about in jest as swagville; the hard working...

Exchange Cut-Over Migration to Office 365 Overview:  An organization can migrate a maximum of 1,000 Exchange 2003, Exchange 2007, or Exchange 2010 mailboxes to the cloud using a cutover Exchange migration. To migrate more than 1,000 Exchange 2003 or Exchange 2007 mailboxes, you can perform a staged Exchange migration. You can’t migrate Exchange 2010 mailboxes using a staged Exchange migration. Therefore, to migrate more than 1,000 Exchange 2010 mailboxes, you must implement a hybrid deployment. For more information, see Exchange Hybrid Deployment and Migration with Office 365. Caution: Assuming that you have a valid office 365 subscription and Directory Sync is not enabled. Cutover migration provisions users into office 365 and hence directory sync should be disabled prior to migration. Steps: A Cutover migration to office 365 involves in a set of steps that the Microsoft team has well documented to move on on-premise exchange (2003,2007 & 2010) mailboxes into a different service. We will look into how to move on-exchange 2010 to office 365 tenant. Following steps can outline the entire process. Step 1. Planning  Microsoft has provided a solution for all three types of exchange migration On-Premise Hybrid Cloud only Goto  Exchange Deployment Assistant site to perform an assessment of your present exchange deployment. Follow the on screen steps to perform the tests.     Step 2. Test On-Premise Exchange for readiness  Setup Assistant app gathers the following discovery information: On-premises infrastructure servers and components Network architecture and Domain Name System (DNS) settings Authentication solutions Directory design Bandwidth Mail routing, mail and other client applications, mail archiving and compliance Certificates Hardware and software Current Office 365 configuration, including: Any custom domains you may have set up DNS settings already configured Current service settings After deployment recommendations are accepted, Setup Assistant runs automated readiness checks to identify potential blocking issues for the selected options and make sure you’re ready to deploy: Office Setup - We’ll check your PC’s Outlook configuration as well as several other Office settings. Computer Settings - We’ll check to see you have the latest updates on your PC, Internet browsers, and other configuration settings. Domains - We’ll check your Office 365 domains and DNS settings to verify that you’re good to go with the updates you need to complete your domain registration. Users and Groups - We’ll check if your organization uses Active Directory, and we’ll evaluate if you’re ready for directory synchronization and single sign-on. Steps Log on to a computer in your organization by using administrator credentials. If your organization uses a domain, make sure this is a domain-joined computer. On the same computer, log onto your Office 365 tenant by using administrator credentials. If your Office 365 tenant is on its first 30 days, on Welcome, Office 365 is ready to go page, choose Configure Office 365. Or, in the Office 365 admin center, choose the setup tab. On Setup Assistant page, make sure your computer meets the software requirements listed. If not, you can choose any of the provided links to install the missing items. Choose next to install the Setup Assistant app. If you choose continue without installing app, you will be directed to a list of feature selections that give you options to manually setup your Office 365 experience. After the app has installed it will first collect discovery information about your current setup and make recommendations for how to best move forward to setting up Office 365. After you accept deployment recommendations, the app will run automated readiness checks to make sure your environment is ready to move to Office 365. Readiness checks will alert you to potential issues that can block deployment and help you fix them. Setup assistant dashboard will list overview topics that help you review the next steps, and it will also list procedures that you will need to step through to complete your setup. Step 3. Prepare for Migration  Configure Outlook Anywhere on your on-premises Exchange server - The e-mail migration service uses RPC over HTTP, or Outlook Anywhere, to connect to your on-premises Exchange server. For information about how to set up Outlook Anywhere for Exchange 2010, Exchange 2007, and Exchange 2003, see the following: Exchange 2010: Enable Outlook Anywhere Exchange 2007: How to Enable Outlook Anywhere Exchange 2003: Deployment Scenarios for RPC over HTTP How to Configure Outlook Anywhere with Exchange 2003 Important:  Your Outlook Anywhere configuration must be configured with a certificated trusted by a certificate authority (CA). It can’t be configured with a self-signed certificate. For more information, see How to Configure SSL for Outlook Anywhere. Assign the migration administrator permissions to access mailboxes in your Exchange organization   The on-premises account that you use to run a migration batch must have the necessary permissions to access all user mailboxes. You can assign the Full Access permission for individual mailboxes or assign the Receive As permission for a mailbox database. For more information, see the following: Cutover Exchange migration For a cutover migration, the migration administrator account must be: A member of the Domain Admins group in Active Directory in the on-premises organization or Assigned the FullAccess permission for each on-premises mailbox 0r Assigned the Receive As permission on the on-premises mailbox database that stores the user mailboxes. Staged Exchange migration: For a staged migration, the migration administrator account must be A member of the Domain Admins group in Active Directory in the on-premises organization or Assigned the FullAccess permission for each on-premises mailbox AND the WriteProperty permission to modify the TargetAddress property on the on-premises user account or Assigned the Receive As permission on the on-premises mailbox database that stores the user mailboxes AND the WriteProperty permission to modify theTargetAddress property on the on-premises user account.  IMAP migration: For an IMAP migration, the CSV file for the migration batch must contain- The user name and password for each mailbox that you want to migrate or The user name and password for an account in your IMAP messaging system that has the necessary administrative privileges to access all user mailboxes. To learn whether your IMAP server supports this approach and how to enable it, see the documentation for your IMAP server. Remote move migration in Exchange hybrid deployments: For remote move migrations, the migration administrator account must be- A member of the Domain Admins group in Active Directory in the on-premises organization or A member of the Exchange Recipients Administrators group in Active Directory in the on-premises organization or A member of the Organization Management or Recipient Management group in Exchange 2010 and Exchange 2013 Use the EAC to assign the Full Access permission   Use the Shell to assign the Full Access permissionThe following examples show different ways to use the Add-MailboxPermission cmdlet to assign the Full Access permission to the migration administrator account for mailboxes in your on-premises organization.This example assigns the migration administrator account (for example, migadmin) the Full Access permission to the mailbox of Terry Adams. Add-ADPermission -Identity "Mailbox Database 1763498182″ -User migadmin -ExtendedRights receive-as Use the Shell to assign the WriteProperty permission Add-ADPermission -Identity "Mailbox Database 1763498182″ -User o365 -ExtendedRights receive-as Use the Shell to assign the WriteProperty permission  Get-User -ResultSize unlimited -Filter {(RecipientTypeDetails -eq ‘UserMailbox’)} | Add-ADPermission -User migadmin -AccessRights WriteProperty -Properties TargetAddress Step 4. Prepare for Migration Endpoints Before you start creating migration endpoint, ensure that MRSProxy is enabled in your on-premise exchange server Use the EAC to enable the MRS Proxy endpoint on Exchange Server 2010 In the EAC, navigate to Recipients > Servers > Virtual Directories. In the Select server drop-down list, select the name of the Client Access server on which you want to enable the MRS Proxy endpoint. Or select All servers to display the virtual directories on all Client Access servers in your organization. In the Select type drop-down list, select EWS to display the Exchange Web Service (EWS) virtual directory for the selected server. In the list of virtual directories, click EWS (Default Web Site) for the Client Access server that you want to configure, and then click Edit . On the EWS (Default Web Site) properties page, select the Enable MRS Proxy endpoint check box, and then click Save. Step 5. Create Migration Endpoints Open up the Office 365 Exchange Administration Console and go to Recipients > Migration > More > Migration endpoints and click on the plus sign to add a new endpoint. Select the outlook anywhere type for migration endpoints. Enter the mail box and on-premise domain admin credential    Step 6. Create cutover migration batch In the EAC, navigate to Recipients > Migration. Click New + and then click Migrate to Exchange Online. Select the migration Type - Cutover batch The new batch creation automatically detects the servers from the previously created endpoints. Configure the connection settings  Name the migration batch    Select manually start the batch which can give you control to start at a convenient time if any other Migration preparation is left pending. Also provide a list of recipient to get notified on completion of the Batch and click new to finish creation. Start the migration batch  Once the batch is started, it may take considerable amount of time depending on the mail box volume. The migration dashboard will show status (syncing.) Automatically detect connection settings with Autodiscover Manually specify connection settings Once the Migration Batch has executed, look for any error for which sync is not successful. These needs to be resolved so that all user’s mail boxes are migrated successfully. In Blogs to follow, we will look into how to get the final migration steps completed: Errors in Cut-Over Batch execution Configure your MX record to point to Office 365 Post Cutover Migration Task and exchange decommissioning

Overview You have deployed SharePoint 2013 and the MySite functionality has been deployed. When you visit your mysite and switch to the My Tasks screen you will see the below error message. "Sorry, we’re having trouble refreshing your tasks. Contact your administrator if you continue to have problems" Cause You will need to enable the Work Management Service App. Solution From your SharePoint Central Administration, under the Applications and Manage Service Applications, create a new Service Application for Work Management Service Application. Hope you find this blog helpful. Do let me know your thoughts below!

In the simplest form of data filtration, we set up Views on lists or libraries to skim data of interest. Views work on individual lists or libraries and can also be referenced in web parts added to pages. But, while working in a larger context, a Content Query Web Part is a useful tool to filter aggregated data sources in a site collection. The configuration capabilities of the CQWP web part are large, however, in the given content, I’ve extended the limit of filtration for document libraries. The preference of a Content Query Web Part over Content Search Web Part is purely on choice. However, this article specifically deals in context of SP Online or SP 2013. It is known that in the same site collection, document libraries using the same site columns can be easily filtered using the CQWP. However, by default only 3 basic filter mechanisms are available. To cascade the filter criteria is an effort that requires customizing this web part. By cascading I mean implementing the following set of requirement, which will be used as an example in this article. Example: The given example surely appears very simple, but the limitations of an OOTB CQWP curb its implementation. The following sections simplify the translation of a business requirement in context of its implementation. How to customize filter of an OOTB CQWP The process is a sequence of steps beginning with the basic configuration of the web part on the page to trickle down to the selection of the desired data sources. Having done this, the web part should be exported from the flyout menu option. The main task for building the filtration logic and editing the exported web part file is explained in the following sections. How to translate a business requirement In the context of the aforementioned example, the logic is built as elaborated below. Identify the number of first level sub-queries. In the given example, the query can be split into 3 sub-queries that are ANDed Split each sub-query into further simplified evaluation criteria. This step is iterative until the query can further be simplified. In the given example, each sub-query equates the respective site columns to a set of values that are ORed Having performed the above breakdown process, each sub-query now needs to be implemented to gradually aggregate to the complete requirement set. How to build the query Constructing queries require a minimum of following details: Names of site columns Entourage of values to be evaluated Logical operators to match the value criteria Using logical filters on site columns requires that the columns be addressed by their internal names and not their display names that appear visually. Internal column name can be found in either of the following 2 ways: Checking the properties of the column in the list or document library. Right-click the column, and then click Properties. The internal name of a column appears in the Address (URL) property after ‘Field=’ Using a CAML query tool like the CAMLDesginer2013. Upon selecting display names of selected lists/libraries, the tool displays internal names in the query building section. My personal preference would be using the query tool, for the reason that the tool addresses the other two requirements of query construction - the list of allowed values for the type of column definition and the match criteria to be applied on them. e.g.: A multiple choice column ‘ABC’ evaluates its value as ‘multichoice’, while a single choice column ‘DEF’ evaluates the values simply as ‘choice’. N.B.: All other evaluation types are not listed in this article as they can be discovered from the tool. Now, having discovered column internal names and the manner in which values can be evaluated, building the logic section is not much of a brainer, though it does require inspecting pair of eyes. The cue here is to disintegrate the required logic into groups of two, starting from the innermost logic and start building upon the aggregation The aforementioned example, can be targeted from the top most sub-query. Construct a logic for matching the site column for one from the given set of values and couple it with another set of value. Step# 1 The construct of the build is to create evaluation logics for site columns and values and then proceed with coupling groups of two such matches with logical operators. Here, the column ‘Artefact Type’ (internal name ‘Artefact_x0020_Type’) is of the type Choice, allowing only single values. In the given context, this column has to be evaluated to be equal at least one from the given 3 values - ‘Assessment’, ‘Case Study’, ‘Solution Description’ or ‘White Paper’, hence the use of the logical operator ‘<Or>’ for the given match criteria ‘<Eq>’. Having done this, consider this group to generate one logical result ready to be coupled with another match. Hence, the construct is analogous with the text is green an indicator of already accomplished evaluation in the above step. Step# 2 This gives us enough platform to proceed to the final evaluation of the first sub-query. Step# 3   Now that the first sub-query is built, consider the entire construct to yield a single logical result. Upon inspecting the business requirement, this result is Anded with that of the another sub-query, which can be built on similar understanding. Step# 4 The sub-queries at Step# 3 & Step# 4 can now be logically paired as in the given requirement. Step# 5 Similarly, we proceed further simplifying the third sub-query as below: Step# 6 And then coupling Step# 5 & Step# 6 in the final stage. This query can either be tested for execution in the CAML query builder application before or iteratively by editing the downloaded web part and uploading it. How to customize the web part In the downloaded web part file (.dwp), search for the property ‘QueryOverride’ and extend it with the constructed logical query as below: The web part is not ready to be finally uploaded to the page. Follow the successive screen shots as instructions to upload the custom web part. This web part can now be added to the page like any other OOTB web part. However, it’s worth mentioning that its visibility or presence is limited to the page and not the site. Hence import it to multiple pages across the same site if you need to reuse it.

Overview You have deployed SharePoint 2013 and the MySite functionality has been deployed. When you visit your Mysite and switch to the My Tasks screen, you find the following error message: "We weren’t able to start syncing your tasks because one or more pre-requisites for connecting to Exchange server could not be found. Please contact your administrator to resolve this issue." Cause & Solution You will need to have Exchange 2013 in your environment. You will also need to install Exchange 2013 Web Services Managed API 2.0 http://technet.microsoft.com/en-us/library/jj554516.aspx Hope this helps. Look forward to your questions and comments!

  I have three daughters, and I love them all! But sometimes being their dad exposes me to the oddest things. This last month the greatest oddity has been the myriad theories offered behind Taylor Swift’s song "Bad Blood." If you ask my 21-year-old, she will scoff at the fact that you don’t know everything there is to know about pop culture and say you are too old to get it. If you ask my 12-year-old, she will give you a well-reasoned theory about the strife between Swift and Katy Perry and then shift her attention back to Instagram with...

Overview We know to provide infrastructure support for SharePoint Apps we have to do a number of configuration steps. I have worked for a number of business where the App infrastructure for their on-premises SharePoint farm has not been set up but there are some important business requirement to be implemented without trusted solution and managed code as a practice. In this article I will show you a structured way of developing custom SharePoint functionalities using jQuery and SharePoint JavaScript CSOM which is very compatible with SharePoint hosted Apps. Solution: The main components that are required to develop client side functionality are HTML, CSS, and JavaScript along with SharePoint list/libraries which holds related data. You can just use SharePoint designer as the only tool to develop these components or any of your favorite editor is good. I will demonstrate the structure and separation of code using SharePoint designer: 1. Open you site using SharePoint Designer and on the navigation click on "Site Assets". 2. Now because you can have multiple custom functionalities, for a good structure and code management you can create following folder structure: Each separate functionalities could be a subfolder under "Utilities folder. 3. Say you are developing a functionality for showing announcements, so you can create following three files under "AnnouncementTicker" folder: Do your required coding for the components. Refer to the ".css" and ".js" files from the ."html" files. 4. Now as your custom coded components are ready, open the page in browser where you need to add the functionality. Edit the page and add a Content Editor Web Part in the required zone and link the ".html" file. In the Content Editor Tool Pane, under Content Link, type the link of the ".html" file, for example "SiteAssets/Resources/Utilities/AnnouncementTicker/AnnouncementTicker.html". 5. Save the page and you can see the results. For updating the functionality you do not need any deployment. Just edit the code from the corresponding files using SharePoint Designer and save to see the update in browser. Pretty fast and efficient development process compared to SharePoint Hosted App Development! A real life example will be good and for this I am demonstrating the "Announcement Ticker" functionality to be added on a say dashboard page: 1. Create a SharePoint List "Announcements" which will host all announcement/notification/news details. 2. Only the active announcements (current date within publishing start and end date time) will display on dashboard page. This way you can set up future announcements and will automatically display on dashboard when start date time appears and will expire from dashboard after the specified publishing end date time. If an announcement contains an external link, clicking on "More" button will open the link in a new window else the announcement details will appear in a modal window. 3. You can configure multiple active announcements and those active announcements will scroll one by one on dashboard page. I have used JQuery, Bootstrap and SharePoint JavaScript Client Object Model as the main technologies for the solution. Use SharePoint designer to open your site and create following folder structure inside "SiteAssets" library - "/SiteAssets/Resources/Utilities/AnnouncementTicker" and create following three files inside the "AnnouncementTicker" folder: AnnouncementTicker.html AnnouncementTicker.js AnnouncementTicker.css The code of the files are given below on this article. Please note that you have to download Bootstrap and JQuery plugin file(s) and add to the "Resources" folder as shown in the code.  Once you have the files ready add a "Content Editor WebPart" in the appropriate place and add reference to the "AnnouncementTicker.html" file in the content editor web part and you get the ticker functionality like below: Clicking on the "More…" button will display the announcement details in a bootstrap modal like below: AnnouncementTicker.html <html><head><scripttype="text/javascript"src="/_layouts/15/sp.runtime.js"></script><scripttype="text/javascript"src="/_layouts/15/sp.js"></script><linkrel="stylesheet"href="/SiteAssets/Resources/bootstrap/css/bootstrap.min.css"><linkrel="stylesheet"href="/SiteAssets/Resources/bootstrap/css/bootstrap-theme.min.css"><scriptsrc="/SiteAssets/Resources/Plugins/jquery-1.11.1.min.js"type="text/javascript"></script> <scriptsrc="/SiteAssets/Resources/bootstrap/js/bootstrap.min.js"type="text/javascript"></script> <linkrel="stylesheet"href="/SiteAssets/Resources/Utilities/AnnouncementTicker/AnnouncementTicker.css"/> <scriptsrc="/SiteAssets/Resources/Utilities/AnnouncementTicker/AnnouncementTicker.js"type="text/javascript"></script> </head> <body> <divclass="container-fluid"> <divclass="alert alert-info alert-dismissible announcementAlerts"role="alert"> <table> <tr> <td> <spanclass="badge badge-info bAnnouncement"><iclass="glyphicon glyphicon-volume-up"></i></span><strong>Announcements!</strong> </td> <tdstyle="vertical-align:top;"> <ulid="AnnouncementTicker"class="AnnouncementLabel"></ul> </td> </tr> </table> <buttontype="button"class="close"data-dismiss="alert"style="top:-55px; vertical-align:top;text-align:right;"> <spanaria-hidden="true">×</span><spanclass="sr-only">Close</span> </button> </div> <divclass="modal fade"id="announcementDetail"tabindex="-1″role="dialog"aria-hidden="true"> <divclass="modal-dialog"> <divclass="modal-content"> <divclass="modal-header"> <buttontype="button"class="close hidden"data-dismiss="modal"aria-label="Close"><spanaria-hidden="true">×</span></button> <h3class="modal-title"id="announcementDetailDialogTitle"></h3> </div> <divclass="modal-body"id="announcementDetailDialogBody"></div> <divclass="modal-footer"> <buttontype="button"class="btn btn-warning"data-dismiss="modal"><iclass="glyphicon glyphicon-remove-circle"></i> Close</button> </div> </div> </div> </div> </div> </body> </html> AnnouncementTicker.js $(document).ready(function () {LoadAnnouncements();});function LoadAnnouncements() {var clientContext = new SP.ClientContext.get_current();var oList = clientContext.get_web().get_lists().getByTitle(‘Announcements’);var camlQuery = new SP.CamlQuery(); var camlQueryText = "<View>" + "<Query>" + "<Where>" + "<And>" + "<Leq>" + "<FieldRef Name=’PublishingStartDateTime’ />" + "<Value IncludeTimeValue=’TRUE’ Type=’DateTime’><Today /></Value>" + "</Leq>" + "<Geq>" + "<FieldRef Name=’Expires’ />" + "<Value IncludeTimeValue=’TRUE’ Type=’DateTime’><Today /></Value>" + "</Geq>" + "</And>" + "</Where>" + "<OrderBy>" + "<FieldRef Name=’Modified’ Ascending=’False’ />" + "</OrderBy>" + "</Query>" + "</View>"; camlQuery.set_viewXml(camlQueryText); this.collAnnouncementListItems = oList.getItems(camlQuery); clientContext.load(collAnnouncementListItems); clientContext.executeQueryAsync( Function.createDelegate(this, this.onAnnouncementQuerySucceeded), Function.createDelegate(this, this.onQueryFailed) ); } function onAnnouncementQuerySucceeded(sender, args) { var announcementCount = collAnnouncementListItems.get_count(); if (announcementCount > 0) { var listItemInfo = "; var listItemEnumerator = collAnnouncementListItems.getEnumerator(); var announcementHTML = ""; var annDlgTitle = ""; var annDlgBody = ""; while (listItemEnumerator.moveNext()) { var oListItem = listItemEnumerator.get_current(); var announcementID = oListItem.get_item(‘ID’); var announcementTitle = oListItem.get_item(‘Title’); var announcementBody = oListItem.get_item(‘Body’); var announcementExternalLink = ""; if (oListItem.get_item(‘ExternalLink’) != null) { announcementExternalLink = oListItem.get_item(‘ExternalLink’).get_url(); } var pubSDT = $.date(oListItem.get_item(‘PublishingStartDateTime’)); annDlgTitle += ‘<span id="annDlgTitle’ + announcementID + ‘"><h3 class="annDlgTitle"><span class="label label-info"><i class="glyphicon glyphicon-calendar"></i> ‘ + pubSDT + ‘</span> - ‘ + announcementTitle + ‘</h3></span>’; annDlgBody += ‘<div id="annDlgBody’ + announcementID + ‘">’ + announcementBody + ‘</div>’; announcementHTML += ‘<li><span class="label label-info"><i class="glyphicon glyphicon-calendar"></i> ‘ + pubSDT + ‘</span> - <span class="AnnTitle">’ + announcementTitle + ‘ <button data-externallink="‘ + announcementExternalLink + ‘" onclick="javascript:OpenAnnouncementDetails(‘ + announcementID + ‘, this);" type="button" class="btn btn-xs btn-primary"><i class="glyphicon glyphicon-fullscreen"></i> More…</button></span></li>’; } $("#AnnouncementTicker").html(announcementHTML); $("#announcementDetailDialogTitle").html(annDlgTitle); $("#announcementDetailDialogBody").html(annDlgBody); setInterval(function () { RotateAnnouncement() }, 5000); } } function RotateAnnouncement() { $(‘#AnnouncementTicker li:first’).slideUp(function () { $(this).appendTo($(‘#AnnouncementTicker’)).slideDown(); }); } function onQueryFailed(sender, args) { alert(‘Request failed. ‘ + args.get_message() + ‘\n’ + args.get_stackTrace()); } function OpenAnnouncementDetails(itemID, moreBtn) { $("[id*=annDlgTitle]").each(function (i) { $(this).css(‘display’, ‘none’); }); $("[id*=annDlgBody]").each(function (i) { $(this).css(‘display’, ‘none’); }); $("#annDlgTitle" + itemID).css(‘display’, "); $("#annDlgBody" + itemID).css(‘display’, "); $(‘#announcementDetail’).modal({ keyboard: false }); if ($(moreBtn).attr(‘data-externallink’) != "") { setTimeout(function () { window.open($(moreBtn).attr(‘data-externallink’), ‘AnnouncemwntWindow’, ‘status=1,toolbar=0,resizable=1,scrollbars=1′); }, 500); } returnfalse; } $.date = function (dateObject) { var m_names = new Array("January", "February", "March", "April", "May", "June", "July", "August", "September", "October", "November", "December"); var d = new Date(dateObject); var day = d.getDate(); var month = m_names[d.getMonth()]; var year = d.getFullYear(); if (day < 10) { day = "0″ + day; } var date = month + " " + day + ", " + year; return date; };  AnnouncementTicker.css .AnnouncementAlerts {height: 60px;}#AnnouncementTicker {height: 60px;overflow: hidden;list-style: none!important; padding: 0px; margin: 0px!important; padding-left: 10px; vertical-align: top; } #AnnouncementTickerli { height: 60px; list-style: none!important; padding: 0px!important; margin: 0px!important; vertical-align: top; } .AnnouncementLabel { list-style: none!important; padding: 0px!important; margin: 0px!important; vertical-align: top; } .AnnDate { font-style: italic; font-size: 13px; } .AnnTitle { padding-left: 0px; font-size: 14px; color: black; } .bAnnouncement { font-size: inherit!important; } .badge-info { background-color: #3a87ad; } .annDlgTitle { margin-top: 0px!important; margin-bottom: 0px!important; } .AnnTitleLink { font-weight: bold; }

Overview You have deployed SharePoint 2013 and Office Web Apps 2013 and integrated both platforms. End users are trying to open OWA supported Office Documents (Word, Excel, PowerPoint) for Editing in the Browser or trying to Co-author. You may receive an error message such as below- "PowerPoint Web App cannot open this presentation for editing. Please try again later." Cause & Solution Based on the error message it is very obvious that someone has checked out the document for editing.  From the Document Library check if any other user has tried to edit the document by looking at the document check out status. Conversely if you are trying to coauthor the document, ensure that the document is NOT checked out. Another feature that you will need to be aware at the Document Library Settings is that Enforce-Check out is not enabled. With Enforce-Check out enabled, you will never get to perform the Co-authoring. Hope this helps! Look forward to your queries and comments below.

Overview You have deployed SharePoint 2013 with Reporting Services in the SharePoint Integrated mode. From the Central Administration, System Settings>Manage Services on Server, you try to start the SQL Server Reporting Services service.  You receive the following error message- "Reporting Services scale-out deployment is not supported in this edition of Reporting Services. This edition only supports one instance of the SQL Server Reporting Services Service in the farm. The SQL Server Reporting Services service cannot be started on this server unless it is stopped on all other servers in the farm." Cause & Solution You are using the SQL Server Standard Edition. SQL Server Reporting Services Scale-out mode is supported by following SQL Server editions: Enterprise, Business Intelligence. (Refer MSDN: Features Supported by the Editions of SQL Server 2012) With your SQL Server 2012 Enterprise or Business Intelligence editions, under your SharePoint 2013 (2010) you could always scale out to more than one SharePoint server. (Refer MSDN Add an Additional Report Server to a Farm (SSRS Scale-out) ) While you have SQL Server 2012 Standard edition, under the SharePoint 2013 Farm, you can have only one instance of SQL Server Reporting Services in the SharePoint Integrated mode. While you try to start another instance of Reporting Service in the farm on different server within the Farm, you will receive the above message. If you intend to start the SQL Server Reporting Services on a different server than the service is currently running, you should first stop the service on the current running service and then start on your desired server. But also be aware other installation and configuration requirements for hosting the SSRS Service on the Server before you try to start the SSRS Service on a new server Hope this helps!

Introduction This is SharePoint 2013 in built bug. We need to apply this solution after load balancing. We observed load balancing of multiple web fronts environment for 2007, 2010 and 2013. In MOSS 2007 and 2010, Incoming email service is perfectly load balanced. When more than one front-end server is set up to process incoming email messages on a MOSS 2007 and SharePoint 2010 farm, all of the WFE servers can process email messages and can fail over to any other server. Where as in SharePoint 2013 environment, we use shared/network drop folder when incoming email service runs in multiple WFE. This article will describe the following points - Impact of the Issue Investigation on this issue Root cause of this Issue Solution for this Issue Impact of the Issue When multiple WFEs will be connected through load balancer in SharePoint 2013, we will not be able to do load balance for incoming email service as still we can run incoming email service in multiple WFE. It means that if one server in which incoming email service timer job is running will be down then incoming email will be stopped working for whole farm. In SharePoint 2013, Incoming email timer job is running in only one WFE server, never run on multiple WFE if still the incoming email service is configured to run on all WFE. Another point is - if this service will run in multiple load balanced WFE server in SharePoint 2013, few email will be delivered correctly (server in which timer job is running) and few will be stuck in drop folder (server in which timer job is not running) Preliminary investigation for Incoming Email service From the above impact of the issue we can understand that timer job is mainly guilty for this type of issue. Incoming email service timer job is responsible to deliver email from drop folder to SharePoint library. In 2007, we found that Incoming email service timer job is running in all WFE servers at same time when it is scheduled. In SharePoint 2013, Incoming email timer job is running in only one WFE server, never run on multiple WFE if still the incoming email service is configured to run on all WFE. Root Cause of this Issue In Moss 2007 and SharePoint 2010, the Incoming Email service timer job had a SPJobLockType of None, which means that the job ran on all servers in the farm, given the Incoming Email service was provisioned We can also find out which Jobs have a lock of type none run once on each server in the farm. Because each server in the farm has one timer service instance, a job intended to run on every server does not need to take any locks - each server simply knows it can run the job without further concern. We need to use this power shell command - Get-SPTimerJob | ? {$_.LockType -eq "None"} In SharePoint 2013, that SPJobLockType has changed to Job, which means it only runs on a single member in the farm.  This is a problem for those who wish to use round-robin MX records.  While in SharePoint 2010, you could have multiple SharePoint servers, using equally weighted MX records servicing Incoming Email requests, in 2013, you can only have a single server servicing Incoming Email requests. For this case we can use - Get-SPTimerJob | ? {$_.LockType -eq "Job"} There are 3 Locks available. SPJobLockType.None — if you set it none, the instance will run in all the available servers in the Farm (e.g. Application Server Timer Job) SPJobLockType.ContentDatabase - this will cause 3 instances to be running in each of the Web-Frontends. SPJobLockType.Job - this will cause only one instance of the job to run on any of the front-end servers. (Note: it is possible to see multiple instances listed in the Job Status .. but if you look at the time it was last run.. only one would have run lately) This is a Microsoft SharePoint 2013 in-built issue Solution for this Issue Microsoft has already released a Hotfix for this issue in December 10, 2013. Please click on this URL for reference - http://support.microsoft.com/kb/2837677/en-us But the December 2013 CU didn’t help? In some cases when an administrator applied the December 2013 CU they did not see the expected change in the SPJobLockType.  In these cases the problem occurred because the Internal E-mail service was already in place prior to the application of the December 2013 CU.  So the SPJobLockType remained the same (in Job state).  What the administrators in this case needed to do was to remove the existing Internal E-mail service feature and its timer job and then add them back again after the December 2013 CU was applied.  When these steps were followed the problem went away. Delete the Job: $job = Get-Sptimerjob | ? {$_.Name -eq "job-email-delivery"} $job.Delete() Re-enable the "Incoming E-mail", this will recreate the job  - Central Admin->System Settings - Configure incoming e-mail settings - Configure all option as necessary  Confirm the Locktype : None for job-email-delivery get-sptimerjob job-email-delivery | fl Restart the timer job across all servers. After implementing all the steps now, everything is working fine in the environment.  

  I admit - I love Vegas. While I’m at this year’s SHRM Annual Conference, I do plan on checking out the latest restaurants and maybe even taking in a show. But the most fun I have during the SHRM conference is spending time networking. It’s really fun to meet people I’ve only traded tweets with or connect with longtime friends from my days as a volunteer leader. Yes, going to sessions is important - especially that 7:00 a.m. one about the new overtime regulations. (I will be looking for some serious caffeine that morning!) And, I...