Tag Info

New answers tagged

1

Create a Content Type then create a set of columns for the Content Type that describes your Project content type. Then create your list using the content type and populate it. In search only search for ContentType:MyProject and you will get your result. I do this for Site Directory info all the time.


0

You could either go with multiple App-parts and use audiances like Benny sugested or take advantage of "Me" in the filter like described down under. The advantage of using "Me" is that if someone new comes around and gets issues/tasks assigned to them you wont have to make a New App-part and go through with the audiance-procedure. Using 1 App-part for ...


0

It looks like you need to make use of audience in SharePoint. Add the different groups or members that need to have issues filtered in different ways. Then add App Parts to the page. You can add more than one App Part of the same list, assigning different audiences and filters the way you want. When you have all the App Parts in place, add audience to ...


0

Finally figured out my problem: I can't have a web application that has the same name as the site collection, and the site is a host-header site, so configuration is a bit different than path-based sites. I wrote more information here, if anyone is interested: http://www.consentfactory.com/migrating-sharepoint-2010-to-2013/


1

Create standard windows scheduler task and run batch file with your PowerShell commands: http://technet.microsoft.com/en-us/library/cc721871.aspx http://stackoverflow.com/questions/2035193/how-to-run-a-powershell-script


2

You can try: Configuring a SQL job to backup the content databases - as opposed to SharePoint's backup commandlets or Use a Windows Scheduled Task to run your Powershell commands For the scheduled task I usually have two files: backup.bat - with the commandline below, that executes the second file ...


0

Browsing from site collection -> subsite would actually take me to the new site collection that I created since I added a managed path entry when creating the new site collection of the same name. To remove the subsite I temporarily deleted the managed path for root/sitecollection which forced root/subsite to become active again along that path. I was then ...


1

You cant have more than one root site collections, and i dont think you can create 2nd site under "/" path. Once you created the 1st root level site collection then SharePoint will not give you option to create another one under the "/" path( i check from Central admin). You can create the manages path as "/TeamA and /TeamB". Root site collection is ...


1

Couple of things need clarification: You said in the web App "/" site missing but other sites are still their, what that mean...other sites mean "/sites/sitename" or subsite of the"/" site? How many total site collection you can see in that web application. Possible Solutions: Make sure the content Database Attached to the web app( the one which having ...


0

You can go from Higher Patch / build level to Lower( in your case from SP2 to SP1). But i am thinking about couple of possible workaround. if you have frequent backup of your Test farm databases then restore the database from backup and then from Production Central admin take the backup of site collection using the Recover content from an unattached ...


1

If the error is with the custom site template, you need to upgrade your SP2010 visual studio olution that contains site definition/templates to visual studio 2012 and deploy your solution in the target SP2013 environment. To be able to use custom site templates in SP2013, it has to be in the 15 HIVE. Also, while doing a visual upgrade from SP2010 to SP2013 ...


-1

Use Export-SPWeb and Import-SPWeb to achieve same result as with stsadm


0

Does anyone know how to do this on Sharepoint 2013 ? (Sorry, I don't have enough points to post this as a comment)


1

As you said now server side installation / powershell then your option is very much limited. Save the list / library as template on source side and then move it to destination site collection, after that create new library using that template. This will move all documents to new site collections. But if you want just few documents then i would create temp ...


0

You can use Export/Import to carry over versions of the document. The Export-SPWeb cmdlet gives you a parameter that allows you to specify if you want to export the versions of the list items/documents as well Export-SPWeb http://site -Path "site export.cmp" -IncludeVersions All http://technet.microsoft.com/en-us/library/ff607895(v=office.15).aspx


0

So my issue was never with the managed paths. Two things were causing the site not to load properly. The first was enabling the feature that supported the web part that was being used. In this case it was the "SharePoint Server Publishing" feature. The other issue involved a custom template. I initially disregarded this because the custom template was a ...


0

Couple of things to check. Do you have any customization or site templates etc?did you hard-coded any urls? You have to take care of security groups as well. After exporting the subsite, try to create new site with blank templates. New-SPSite http:///sites/test -OwnerAlias "DOMAIN\JDoe" -ContentDatabase WSS_New_Site then import it using the import-spweb. ...



Top 50 recent answers are included