16

go to windows\system32 directory. Then make a backup of servermanager.exe and then rename to servermanagercmd.exe i hope it will work then! It works.. for me - Amardeep


14

SharePoint 2013 is not supported on Windows Server 2012 R2. This will possibly change with the release of SP1 for SharePoint 2013 this spring. More: http://support.microsoft.com/kb/2891274


8

IT architecture is something you mature into with experience. Just focus on developing good solutions, and build those skills. Always take opportunities to work on projects that cover different areas - for example, if you've built lots of web parts, work on a project that uses BCS or InfoPath, or Excel Services. Always pay attention to the hardware & ...


7

RunWithElevatedPrivileges requires its own SPWeb. If you reuse a existing SPWeb, you won't run elevated, but with the initial context. A common approach applied to your code can be : public class MyProvisioningProvider : SPWebProvisioningProvider { // <summary> // Gets called when a web is provisioning when the template // chosen has ...


7

The solution is to launch the Web Platform Installer (WebPI) and search for "Workflow Manager". Make sure you add and install the Workflow Manager CU2 update that supports Server 2012 R2. You may also need to install the CU2 prerequisite: Cumulative Update for Service Bus 1.0 (KB2799752).


7

The best approach IMO would be to: Setup the new server with OS and SP Launch the SP configuration Wizard on this new server Make it join the existing farm, i.e. make it point to the same config DB (and obviously same SQL server) as the first Web-front. Don't forget to choose to host the Central Admin on this new server (you're asked for this during ...


5

I believe that with the constructor you are using, the last three properties need the SPUser.LoginName, SPUser.Name, and SPUser.Email. I've had trouble with site creation code in the past when these parameters were not correct. Any reason why you are not capturing the actual exception in the catch block?


5

You can also do Implicit Remoting, which allows you to import all of the SP10 Powershell commands into a local session. The method described above works as well, but you are essentially running the commands from the server, so if you are on a server with different modules (such as Exchange 2010) you will have a difficuly time running those on the SharePoint ...


5

SharePoint Server 2013 SP1 supports Windows Server 2012 R2. I see no reason why you shouldn't run your SharePoint Server on a 2012 R2 Server. Just make sure you install SP1 correct before adding logic, solutions and content to your farm. Currently, Microsoft SharePoint Server 2013 is not supported for installation on computers running the Windows Server ...


5

Open Command Prompt use below command C:\path_of_download_directory\spdsp2013-kb2817441-fullfile-x86-en-us.exe PACKAGE.BYPASS.DETECTION.CHECK=1


4

You will need licenses for the development environments as well. Microsoft offers MSDN subscription (Premium includes also SharePoint) for this purpose, and while the subscription is not free, it is considerably cheaper than actual production licenses of Windows Server and SharePoint Enterprise. If you are a startup, see if BizSpark would suit for you. Also,...


4

No! you can't do that without SharePoint Installation, or with a client that could be connected to SharePoint Server In order to run Windows PowerShell remote you have to enable Windows Remote Management on the Server running SharePoint 2010 and the client that you want to run the commands from. On SharePoint Server Enable-PSRemoting Once remoting is ...


4

Do I need to do any configuration at Central Administrator? If you want it just for your personal machine then you shouldn't touch CA. You need to perform some additional steps, e.g. creating a group policy and modifying IE Enhanced Security Configuration. Follow this article out, How do I make our SharePoint site stop asking me to login? – Part I How ...


4

SharePoint Server 2013 Windows Services Document Conversions Launcher for Microsoft SharePoint Server 2013 (DCLauncher15) Document Conversions Load Balancer for Microsoft SharePoint Server 2013 (DCLoadBalancer15) SharePoint Server Search 15 (OSearch15) SharePoint Administration (SPAdminV4) SharePoint Search Host Controller (SPSearchHostController) ...


3

Here is what you should do: Run the task under designated service account e.g. CONTOSO\sp_powershell The account needs to have proper privilages, it needs SharePoint Shell Access (check Add-SPShellAdmin for more details)


3

This fixed my problem.... 1) From Internet Explorer select Tools -> Internet Options -> Security tab 2) Select Local internet -> Sites -> Advanced -> 3) Under Add this website to the zone: type https://*.microsoftonline.com -> Add


3

The problem was my profile. It was kind of corrupt. Somehow whenever I logged-in on my SharePoint 2013 server, windows could not find my profile and used a temperary profile. Removing this profile and restarting the server solved the problem. Removing temperary profiles describes the following various steps to solve the problems How to fix it if you see ...


3

The solution is to launch the Web Platform Installer 5 and search for "Workflow Manager 1.0 refresh". Make sure you add and install the Workflow Manager CU2 Get refresh update that supports Server 2012 R2.


3

Before the release of Microsoft SharePoint Server 2013 Service Pack 1 (SP1), Microsoft did not support the installation of SharePoint Server 2013 in a Windows Server 2012 R2-based environment. However, with the release of SharePoint Server 2013 SP1, this configuration is supported in Windows Server 2012 R2. http://support.microsoft.com/kb/2891274/en-us


3

First of all, you should check the Hardware and software requirements for SharePoint 2013 based on your SharePoint edition and match this with your machine. Regarding which roles to activate on the Windows Server (AD-DS & DNS, but what about CA?) and which not to activate if you need to install AD on the same machine for dev or learning purpose but you ...


3

Look at this post concerning SharePoint 2013 requirements : Minimum real world requirements for SP2013 You should go for Windows Server 2008 R2 + SQL Server 2008 R2 that are a bit lighter than the 2012 versions. Concerning the Virtual Machine, I recommend you to use Virtual Box


3

There is no guidance on it but as per my experience, We never rebooted the server in regular intervals. There are times when a reboot required. install a update for SharePoint or windows which required reboot install any add-on on the server which required reboot if there is an issue with Server which required reboot...memory usage out of control, Http ...


2

Check the centeral admin running with a service account Do Site.WebApplication.FormDigestSettings.Enabled=false; make sure that applywebtemplate running with long run process


2

Please follow the link for SC creation details - http://blog.falchionconsulting.com/index.php/2009/07/custom-sharepoint-2007-site-collection-creation-page/. It describes the correct way of creation for site collection for users - WFE (not CA).


2

Are you using a local account as the sharepoint services account? If you are, then sharepoint will not be able to traverse your active directory structure or request the information it needs via LDAP in order to populate the address book and so-on. This would explain why users can access the site via windows authentication, yet are still unable to manage ...


2

There is no ideal server spec for a SharePoint setup. It all depends on what services you are using, the size of the data, what custommizations are done, how much the users actually are using the farm. You need to test! Start with the default recommendations from Microsoft and look at their sample architectures: http://technet.microsoft.com/en-us/...


2

So you setup the smtp server on one of your SharePoint servers, and then have your email service forward all emails to that smtp server. Exchange only is useful because it integrates with AD and thus all of your SharePoint enabled groups and lists can appear in your address book. EDIT: Setup stmp in iis on one of your servers, the have your email relay ...


2

You need (1) SharePoint 2013 farm installed & configured (looks like you have that) and (2) a Workflow Manager 1.0 farm installed & provisioned. Once you do that, you then run the PowerShell cmdlet in your post. For the -SPSite attribute, you need to point to a valid SharePoint site collection. For the -WorkflowHostUri, you need to point to the ...


2

You need a Windows User CAL to leverage SharePoint Foundation (doesn't matter how your users authenticate to it), that is how Foundation is provided "for free" (it isn't free). For SQL, it depends on how you license it. SQL Express is "free", there are no specific license terms/CALs but there are serious limitations with the product. For SQL Standard/...


2

You should use the credentials of the account you used to install SharePoint in the first place (then you can grant permissions to other accounts). If you are unsuccessful in logging in with correct credentials on the server you may need to disable loopback check: http://blogs.technet.com/b/sharepoint_foxhole/archive/2010/06/21/disableloopbackcheck-lets-do-...


Only top voted, non community-wiki answers of a minimum length are eligible