Basically there will be two type of perquisites installed by the installation wizard, for windows and SharePoint. For SharePoint you will need an internet connection. However before running the wizard I would like to install the windows prerequisites. 

Install .Net frame work

Then we will move on to install SQL server 2012 standard

Select the following features. You can keep the default path in C:

next for service accounts you can use the administrator account or an account with local admin permissions. in my case I’m using a domain account called spfarm with local administrator permissions to the SharePoint server.

In the reporting services configuration page select Reporting Services SharePoint integrated mode

Finally verify all the settings for SQL and then click install once complete open SQL management studio and verify its working. And now its time for us to Install SharePoint 2013

Before moving on to SP setup just want to clarify that I was using an already set domain account with local admin permissions to setup SQL. So you can use the same account to setup SP as the SQL permissions will be applied for that account already. But if you are using a differnt SP account then you will need to setup SQL permissions separately.

Run SharePoint setup from CD, and select install software prerequisites. you need an internet connection for this if not you must download each component and install

The server might reboot in the process so go ahead and wait till the installer has completed- click finish when the installer have completed the installation

Enter product key

Read the terms and agreements and click next and select the installation type

Complete the installation and run the configuration wizard to configure the SP Farm

In the farm options page select create new farm – Under database connection settings make sure local server name is mentioned and your SharePoint installation account is shows (in my case its spfarm)

Under central admin site configuration keep the default and click next – verify the settings and click next  – Finally you can run the central configuration wizard to create a new SP site from the central admin

1. I have a single server connected to my domain running Windows Server 2012. On this guide I will setup Office web apps.

2. Installing prerequisites on Windows 2012 Standard server

Open PowerShell run as administrator and type this command to install the prerequisites.

Add-WindowsFeature Web-Server,Web-Mgmt-Tools,Web-Mgmt-Console,Web-WebServer,Web-Common-Http,Web-Default-Doc,Web-Static-Content,Web-Performance,Web-Stat-Compression,Web-Dyn-Compression,Web-Security,Web-Filtering,Web-Windows-Auth,Web-App-Dev,Web-Net-Ext45,Web-Asp-Net45,Web-ISAPI-Ext,Web-ISAPI-Filter,Web-Includes,InkandHandwritingServices

3. Installing the web apps server

Run setup.exe – Accept the EULA

Choose file location and click install now

I will create a new farm application with editing features enables. The command –EditingEnabled allows you to have document editing capabilities when using with SharePoint. But it really don’t matter for exchange and Lync because those don’t support any edit functions, this must be typed on windows powershell

Import-Module OfficeWebApps

New-OfficeWebAppsFarm –InternalURL "http://servername" –AllowHttp –EditingEnabled

iisreset /restart /noforce

4. Now lets verify if the web app has been successfully created. To do that use the following URL

http://servername/hosting/discovery

Then you should see something like this below (XML)

OK now your web apps server is running. next steps is to intergarte this with your SharePoint 2013, Exchange or Lync Servers. For me I will just show you the steps you need to do

• SharePoint 2013 integration
• New-SPWOPIBinding -ServerName <WacServerName> –AllowHTTP (WacServername is the internal FQDN of your web app server without http://)
• Exchange 2013 integration
• Set-OrganizationConfig -WACDiscoveryEndPoint https://Server1/hosting/discovery (server1 is the web app server name)

Thanks

Enabling diagnostic logging.

in your central admin site go to monitoring – reporting – configure diagnostic logging. if you want to enable all logins types you can click on all categories or in my case just I’m going to set InfoPath logging .

Finally when you go below there are few settings that you need to note and consider

Under log path you can leave the default or if you want the logs to be another path you can set it here. The next is the number of days the logs will be kept. Default is 14. And the next setting is important because that determines the size of the log file. I have set to 10GB in my preview.

To view the log files you can use a PowerShell command. To do so Go to SharePoint 2013 management shell and type Get-SPLogEvent | Out-GridView

http://sdrv.ms/ZG1fpR

https://skydrive.live.com/redir.aspx?cid=15a85081c9b1419f&resid=15A85081C9B1419F!585&parid=15A85081C9B1419F!259

However if your customers are using office 2007 there is an easy way out. All you have to do is get your hands on the 2007 version of project server-outlook add-in and install that in the client computer. If you don’t want to go through the trouble of setting up a project server 2007 you can download the add-in at – http://cid-15a85081c9b1419f.office.live.com/self.aspx/Public/SharePoint%202010/PsOlkAddin.zip

The funny thing is that there are no errors or workflows in the queue at this point. Finally I traced the issue. This happens when you don’t have any users in your project portfolio managers group. To add users to that,

1. Open project web app – Under settings Go to Server Settings – Under security click manage groups – click portfolio managers – under users make sure you have added the users as needed – ok and exit – Run the proposal WF and it should complete and take you to the proposal screen now