My client wanted to configure the User Profile Synchronization Service Application for the Collaboration Farm in the DMZ zone. When I wanted to create the User Profile I got a well-known (on Google) error.
Microsoft.SharePoint.Administration.SPIisWebServiceApplicationPool named “User Profile Service Appl” already exists under the parent Microsoft.SharePoint.Administration. Rename your object or delete the existing object…
A way should be using another Application Pool, but at my new client they are “governance” geek and the Application Pool, Web Application, Managed Accounts and many other should be the same or at least follow the governance decided by the web architects.
So I couldn’t use the easy way and had to find another way to proceed: How to delete the older Application pools? They don’t show up in IIS Manager. There is then only 1 way to delete the application pools and that’s by using PowerShell!
- Open PowerShell with Administrator rights and run Run ‘Get-SPServiceApplicationPool’
Some benefits of using microblog features, feeds, and the Distributed Cache include the following:
- Allows users to stay in touch with individuals and specific groups of people over time and distance.
- Allows users to stay informed about what’s going in the organization.
- The focus of the interactions is around people or teams, and not so much the topic being discussed.
- It is difficult to keep track of activities related to documents, discussions, and lists in SharePoint without manually visiting the item regularly. Feeds collect and deliver information to users that they would otherwise have to spend time searching for.
- The feed gives users a single place where they can stay up-to-date with all of the content and people they work with.
- Allows quick conversations to take place.
These are the steps that occur:
Web Analytics on SharePoint 2010 4
User request a page and action gets picked up by the Web Analytics service that runs on SharePoint
The Web Analytics service logs this in the “.usage” files
A Timer job called “Microsoft SharePoint Foundation Usage Data Import” that by default runs every 30 minutes imports the logs into the staging database.
Each night the “Microsoft SharePoint Foundation Usage Data Processing” Timer job runs and transforms the data into the reporting database
The last run time of the import from staging and the aggregation is logged in the Settings table in the Reporting database
Kurt L Hudson is a Senior Technical Writer for Microsoft’s Server and Cloud Division (SCD) primarily writing about Active Directory Certificate Services (AD CS), public key infrastructure (PKI), Active Directory Domain Services (AD DS), and Windows Azure Active Directory. Works with Hyper-V almost every day for testing server and client operating systems. Publishes information on the TechNet Library, TechNet Wiki, ScriptCenter, Microsoft Showcase, and TechNet Edge. Works closely with the product and test teams to improve the interfaces and help of future Microsoft operating system versions.
Please visit his profile here for more information