Test-SPSite – Runs one or all site collection health checks on the site collection and its contents. Repair-SPSite – Runs one or all site collection health checks on the site collection and its contents.
Get-SPTimerJob (Timer Job Commands) – You can use Timer Job specific commands to verify the timer job and start and also to start to stop them.
Office 365 & SharePoint Dev Tip - Now, Identify your Applications or Add-ins before they expire to prevent outrage. Subscribe to monthly Newsletter for round-up of Tips, News and articles related to SharePoint, Office 365 and Azure IaaS Cloud.
In the Closing Ticket step we will wait until the Ticket Status is set to Closed and we will exist the workflow. In the Re-Opening Ticket step we wait for the Ticket Status to be marked as Re-Open, so let us add the corresponding action, as well as logging. Some words about the Parallel Block – the execution of this block is considered to be over, when all its components are done. After finalizing this article you will be familiarized with main Workflow concepts, like creating stages, actions, loops, conditions and variables. Albeit there are different ways to implement a Ticket Tracking System in SharePoint, the solution presented in this article is a trivial one.
Once ticket is marked as Done, it will be reassigned back to the employee that created the ticket.
The ticket assignee will be sent weekly reminders about the ticket, until the ticket is done. The creator of the ticket will decide if the ticket has been really resolved and will mark it as Closed. Looking on the requirements above, you will notice that there are some decisions to be made during the ticket life cycle – emails has to be sent, reminders has to be created based on the status of the ticket. Although we can live just by using this Custom List, however we really miss the notifications or other custom behavior whenever a ticket is created or updated. You are probably very excited to create your first Workflow to see how it works, so let us move on.
Before going to the next step, please note that you can create 3 workflow types – List, Reusable and Site Workflows. The next displayed screen asks you for the Title and Description of the workflow so please go ahead and add them.
Important note: if you do not have the SharePoint 2013 Workflow available in the Platform Type dropdown then most likely you use a SharePoint On-Premise installation and Workflow has not been configured so you need to set these up. As first step, let us create a really simple operation – send an email to the assignee of the ticket. You will be displayed a reach list of options of how to get the user you want to send the email to. In the above screen you can find the here word which we want to be clickable and user would be redirected to the ticket URL. From any previous development experience, you surely know that it essential  to create log entries, since they will be very helpful when debugging problems. To finalize to Workflow we need to send it to the latest stage, which is called End Workflow. Please note that if you try to deploy your first Workflow on your own SharePoint On-Premise server you will most likely run into many problems doing this for the first time, since many things have to be configured before you can successfully deploy your first Workflow.
This article is part of an introductory series regarding SharePoint 2013 and describes document management procedures, based on a proposed SharePoint Use Case. SharePoint list concept is one of the core features in SharePoint – it offers a powerful way to create and manage lists. Please note that when you specify the Custom List name, this name will be used in URL to access that particular list, therefore pay attention to the special characters. The next step will be the assignment of a certain Word template to the freshly created content type. To add the created document to the Content Type, go the Site Content settings page and click on the Advanced Settings link. Browse for the created document template and click OK to assign the document to the content type. Please go and create the 2nd content type – Software Requirements Document in the similar way as the previous one. SharePoint has another core feature, called Document Library and it represent a container for Documents. Besides the template content, please note that additional fields will be added to the document – the Title and the Project assigned to the document.
Let us review the site hierarchy, as presented in this diagram and create a list containing the site hierarchy and access rules. As you remember, in previous article we created a Site Collection altogether with a root Site. The created Site has been granted access only for the Site Collection administrators, so no one from any department is not able to access the website. To do that, login as Site Collection Administrator (this user was created in the previous step). We need all our departments having the Write access on the Ketl Company Site, therefore let us add users to the Ketl Company Members group. In the displayed popup, add the Active Directory groups created in one of the previous steps. Please note that if you click on the Show Options checkbox, you will be able to unselect the option of sending invitation email for all the added users, as I did in my example. In the Permission section, we do not want to inherit the permissions from the parent site, because we want only the Support department to have access to the new Site. Give contribute (edit) access to the Support Department, and owner access to the SharePoint Administrator group and press OK.
Please note that there is a small problem with the new Site – we do not have any way to go back to the parent site – only the Support link is available in the top bar. After you created all the department sites, you should be displayed the follow screen when accessing Site Content page logged in as SharePoint Administrator. First we note that we have several departments, and each department has its own requirements.
We have a Management department which might want to have access to other departments’ information, like for instance to the Sales department, while restricting access for anyone to their own information. There are also items that will need to be accessed by all the departments, like vacation requests. You will always have this dilemma – should you create a Sub Site or a Site Collection to group logically the resources in your system.
Sites on the other hand can share information – you can define content types, columns, templates that can be defined on the Site Collection level and therefore can be used by any Site that is part of the Site Collection. Considering the above, the right decision to make is to create a single Site Collection which will contain the necessary sub sites. Web Application lets you select the Web Application to which the Site Collection will belong.
As we want to keep things flexible, we would choose the 2nd option – use a managed path as Url. Keep in mind, this is written from the perspective of a FIM consultant who had to nut it out using the Microsoft Installing FIM 2010 R2 on SharePoint Foundation 2013 guide and my own ingenuity.
The reason you need to do this via the Management Shell, is that Classic Authentication has now been deprecated in SPF 2013 in favour of Claims-Based authentication. You have to run your sites in SharePoint 2010 Experience mode anyway, as the FIM Portal doesn’t support being installed on a SharePoint 2013 site collection. The screenshots detail an installation performed on Windows Server 2012, however I have also run through these steps on Windows 2008 R2. This is fairly straight forward, as the SPF Pre-requisites installer will setup almost all of the Windows Features, such as IIS, as well as the other SPF 2013 pre-requisites.


If you choose stand-alone, FIM will install an express database and pre-configure a SharePoint site. Now that SharePoint Foundation is installed, you need to create a new Server Farm and configure SharePoint Central Administration.
Note: SharePoint Foundation 2013 will actually issue a health warning in Central Administration if your database is on the same server as your SharePoint server. Okay, now that the Server Farm has been created, and Central Administration is configured, the next step is for you to create your SharePoint Web Application. Now that your Web Application has been created, you can actually go in and create a site collection for FIM through the SharePoint Central Administration GUI.
Note: As mentioned above, I had an issue where the site collection was still being created in 2013 Experience Mode, despite selecting the 2010 option during creation. Anyway, because of the lack of documentation at the time, I really had to work a lot of this out the first time I had to run through it, so I wanted to put it down as a guide for others who also want to install and configure FIM 2010 R2 SP1 on SharePoint Foundation 2013.
Tried so much I can think of (configuration files, spns, entirely new installation ending up with same result) etc etc. My first installation worked fine (harbars post), when doing the exact same installation in another environment I ended up with this error.
That error is generally thrown by the FIM Portal when a user trying to login to the Portal isn’t configured correctly in the Portal. I can get into admin central just fine and I see the site collection as created by this article. I am following the below given article to configure the FIM with an AD connector & FIM connector, AD is single site, single domain. Is the “FIMSPECIALIST\FIMSPAppPool” the local admin account on the server you used for the install? I’m now in the process of creating an automated install of FIM and found a lot of information for doing so.
The web cast at link referenced introduces new self-service web application, called Tenant Information Portal, which can be used to visually track principal status. To do this, click on the Stage: Assigning Ticket header, until the entire stage gets a blue color. As you will notice from the hints displayed in the Parallel Block, all the actions inside this bloc will execute in parallel. Upload the workflow, wait 1 week and see the reminder coming Or, you can change the Pause for 1 minute just for testing! The main goal of this article is to focus on Workflows in SharePoint 2013, rather than on the best implementation of a Ticketing System. As mentioned before, SharePoint has created a really powerful mechanism to add custom logic and behaviors, called SharePoint Workflow. You will notice that you will encounter already familiar concepts, like Lists, Content Types, Sub Sites. In most of the case you will be working with List Workflows, so leave the other options for later. The other 2 options are real-life scenarios, and basically tell us when the workflow will be fired. In the highlighted section of Workflow editor (you should see a small Orange line) simply type Send and press enter. We want to display the ID and Title of the ticket as well as a link to the assigned ticket, so that the user can easily access it. That is really easy to do for Workflows, just type Log in the highlighted section, and select the Log action.
For instance, when our ticket is Re-Opened and therefore assigned back to user, we can say to workflow to go to the same stage as the one we just created, meaning sending and email to the assigned person. Please note that the Workflow was just created in the SharePoint Designer and it is not available in the SharePoint site unless is deployed.
We have created a list, we have create a Workflow that executes whenever a ticket is added to the list. There are some predefined types, like Contacts, Announcements and Link, as well as generic types, which are considered to be a base for the user defined type. Please note that SharePoint has created default columns for our custom list (check the section in green). SharePoint has a special feature to categorize content within the system – this is called Content Type.
As you can see in the Title column has been automatically added to the created content type. Let us add a new column that would store the project for which the requirement document is created.
We will use this particular root Site (called Ketl Company) to store the features used by all the departments. Just type the group name, and you will be suggested the existing Users or Groups from the Active Directory.
Selecting Yes in the 2nd option will create a link in the top navigation of the Ketl Company Site. This will create the corresponding groups and grant access to the Support site to the Support Department employees. We can resolve this by adding a link to the top navigation, by clicking the EDIT LINKS in the top of the page. You can move the newly created link to the first position, so that the navigation looks consistent with the parent Site.
You can do some tests regarding user permissions – you can try to log in as users from different departments and see how SharePoint displays the content for different permissions. The next articles will refer to customization of the department sites, according to department needs. This makes us think that we would need to hold each department logic in a separate entity (Site Collection or Site). This is a generic term and in SharePoint it can mean many things – Site Collection, Site, Library or a particular document.
Please note that the instruction to be followed are valid for both SharePoint Online and SharePoint on Premise. Click on the small arrow next to the URL and select the Web Application we created in the previous step. As such, you can’t select it as an option via the GUI and you even get a big red warning message (see below) when configuring a new site via the shell. If there are any warnings, or errors, it’s pretty helpful in telling you what you need to do. If you’re familiar with SharePoint, you can do this via the SharePoint Management Shell using Powershell, however you can use the GUI at this stage. Also, select NTLM as the authentication provider, or else you will have issues logging in to SharePoint Central administration. You can now close this window, as we will create your Web Application via Powershell, in the next step.
You actually need to use the SharePoint Management Shell, which is a Powershell interface, in order to do this, as the GUI will set up your site in a way that means FIM can’t use it. If you get this error, delete your site collection and re-create it, double-checking that you select 2010 Experience Mode. These are required for you to be able to actually login to the FIM Portal once it’s installed. The first opens firewall Windows ports for your portal, so you can access it from other machines. I may come back and add to this over time so that it’s a more comprehensive guide, but this should get you started. Similarly, when you login to the FIM Portal, you’re using the credentials you used to install the FIM Portal with? Have you ever automated the install and configuration of SharePoint Foundations for the FIM Service\Portal?


On one hand we need to wait until the ticket is closed and exit the workflow, while on the other hand we should wait for the ticket to be Re-Open and then to go to the 1st stage. For a proper organizing of the Workflow let us add two steps inside the parallel block – the Closing Ticket step and the Re-Opening Ticket step.
As you remember, we display the status of the workflow in a separate column, which is attached to the Support Tickets list.
If the ticket is marked as Closed, the parallel block will still hang, because the 2nd wait action will never finish (it is unlikely that the ticket is marked as Closed and then as Re-open, unless intentionally). The Workflow created a Local Variable for you, whose value will control the execution of the parallel block.
However, we still have one dilemma though – after the parallel block is done where and how do we redirect the user?
First, pay attention that we need to add this block in the Transition to stage section, so please focus on that section, by clicking on it.
For SharePoint On-Premise this requires a lot of additional work, like installing Workflow service, configure SharePoint to integrate with Workflow etc. It is important to mention at this point that any List Workflows is strongly bound to a particular list. In our case the other 2 options mean that the Workflow will start either when we create a Ticket (the 2nd option), or when the Ticket will be updated (the 3rd option).
Please note that SharePoint Designer is filtering the available actions while you are typing.
As you will see in the net chapters, list views can contain information coming from workflows.
SharePoint is storing the log entries into a hidden list – you will not be able to access it through menu, but if you enter the right URL you will be able to see the list.
They create different types of documents for each of projects – they need to create Business Requirement documents or Technical Specification documents. To do this, log in as SharePoint Administrator, go to the IT site, and click on the Site Content link. One of these generic types is the Custom List which allows you to build and customize your own list.
Let us add a new column – we would like to assign a project manager to each of the projects, therefore let us add a new column that would store this information.
To create a content type, log in as Administrator, go to Site Content types of the IT site. For instance Document Content Types will filter in the 2nd dropdown only the content types specific to Documents.
First thing to do is to allow the list to accept the Content Types created in the previous step. Please note that the link will be visible only for the users with access permission to the Support site, which in this case is only Support department. However, since we are currently discussing the resources on high level, it would actually mean Site Collection or Site. Please note that after adding the Managed Path, you will lose the Site Collection screen – you will be redirected to the Central Administration page instead.
So until SPF 2010 SP2 is released, anyone wishing to install the FIM Portal for FIM 2010 R2 SP1 on Windows Server 2012 will need to use SharePoint Foundation 2013. I also see no point in using an express database if you have access to a proper SQL Server database. I put mine on the same SQL Server that I use for the FIMPortal, but only because I’m in a development environment. After all that preparation, installing the FIM Service and Portal is actually quite straight forward. The only difference is that we send the email to the user that created the ticket. Let us also add some logging information regarding the current stage.
Let us select the 2nd option – which means that we want the developed workflow to fire when a new Ticket is created. Whenever we need to insert something from the SharePoint context, we should click on the Add or Change Lookup button as in the image below.
Please note that to have a fully working scenario, you must have a SMTP server correspondingly configured and integrated with SharePoint. Also, we do not want to inherit the navigation (3rd option), because we will not be able to modify the navigation of the Support site afterwards. As you remember, it is important to specify proper names to the stages, since they will end up displayed in the UI.
The next stage should wait in parallel for one of the actions to complete – either ticket to be marked as closed, or to be re-opened.
If we leave the Workflow the way it is now, the last stage and the one that will be displayed at the end of the Workflow will be named Reviewing Ticket, which sounds inadequate after the workflow is finalized.
How do we force the Parallel block to end, if one of its components has finished its execution? So, what is left to do is to set the variable TicketReviewed to true in the end each of the component of the parallel block.
After doing this, return to the Workflow edit page, by clicking the Edit Workflow ribbon button. An already familiar selection screen will be open to you and all you have to do is to select the appropriate item value. Also, very important – the user to which you assign the task to should have a valid email set in Active Directory or SharePoint Online. Documents also need to have a versioning system, so that the employees can keep track of changes.
As result you will be displayed a popup asking you to provide the name of the list to be created.
On the displayed page, click, the New subsite link and start the creation of the new Sales department site. So, let us keep this option set to No and we will customize the top bar menu items after the site creation. The advisable thing to do is to create first the needed Managed Path and only then start the creation of Site Collection. The nice manner to exit from a workflow is to create a fake stage, called Ticket Closed whose only role will be adding some extra logging, and of course the neat display in the Workflow column. This will guarantee us that whenever either of the parallel steps ends, the parallel block itself will end.
Worth to mention, that in the Lists and Libraries section you will be able to see the previously created Support Ticket list. The next thing to do is to add a really powerful action, called Wait for Field Change in Current Item. So we need to find a way to dynamically bind the To field of the email settings to the Assigned To field of the current ticket. What the current action does is wait until the ticket’s Status is being updated to Done.
An app catalog site contains a special type of Document Library that is used to upload and store app package files.
There cannot be more than one App Catalog site collection in a web application or each web application can have only one App Catalog site collection.
Then in the Manage App Catalog page click on create a new app catalog site and then click on OK.
Before that you can also check the Web Application or if you want you can change the web application.



Powerpoint presentation substitute
Player haters ball quotes
Windows live movie maker watermark
Sales and marketing strategy pdf espa?ol


Comments to «Create a web application and site collection in sharepoint 2013»

  1. TSHAO Says:
    Scenes that have to be brought to life, editing the movie was difficult capitalize on the.
  2. KAMILLO Says:
    It's intuitive and become the front porches player But that's the curse we publishers suffer.
  3. KaRtOf_in_GeDeBeY Says:
    Video editing plan, Windows colour grading, motion graphics, visual effects and multi-channel audio.