MOSS 2010 and Project Server 2010 install instructions

MOSS 2010

run spash.html
install prerequisits
Server Farm
select complete install - not standalone
follow this blog for service accounts
in AD, create a moss2010_admin domain account
and create a moss2010_farm domain account
give email address of moss2010_admin@domain.com to both accts!
Add these account to the local Admins group of the farm servers
login to the farm servers as the moss2010_admin account
on the SQL Server - create a new user in SQL as domain\moss2010_admin - grant dbcreator and securityAdmin

******
USE [master]
GO
CREATE LOGIN [Domain\moss2010_admin]
FROM WINDOWS WITH DEFAULT_DATABASE=[master]
GO
EXEC master..sp_addsrvrolemember
@loginame = N'domain\moss2010_admin',
@rolename = N'dbcreator'
GO
EXEC master..sp_addsrvrolemember
@loginame = N'Domain\moss2010_admin',
@rolename = N'securityadmin'
GO
*******

config wizard

- Welcome- next
- Services warning - click Yes
- Connect to a server farm, select create new server farm, click next
- Database settings
- - Database server: obxSQL0801\SQl1
- - DB Access Account: domain\moss2010_farm
- Farm Security Settings
- - Passphrase - give it a pwd, next
- Centrl Admin Web App
- - no specific port, NTLM, Next
- Completing config Wiz, verify settings, next
- Config Successful, finish

Central Admin - Wizard

- Use existing managed account (not a new one, should be your moss2010_farm account), next
- Wait here... 5 min later... just a few more minutes :)
- New Top Level Site, create a site with a good name, description and select Team Site, click OK
- Wait here again, maybe go have a smoke-break or somethin.
- Now configure an alternate access mapping for something coming from outside your intranet. Mine was http://servername as the default. I edited it and added an Internet Zone URL of http://www.WhatEverYourExternalDomainNameIs.com, click Ok
- - think of it as the old host header files
- then on your local machine notebook or whatever, edit your host file to point www.WhatEverYourExternalDomainNameIs.com to your MOSS2010 Farm Server's IP address.
- - open a CMD window, type in edit c:\windows\system32\drivers\etc\hosts
- - add an entry like below:
- - - 192.168.xxx.xxx www.WhatEverYourExternalDomainNameIs.com
- Exit the file, Save and then do an ipconfig /flushdns
- open a browser - go to - www.WhatEverYourExternalDomainNameIs.com
- you may find that you need to go back into Central Admin and Add your actual domain user account to the Site Collection Admins for your new web app.

Project Server 2010

Login to Farm server as domain\moss2010_admin
run spash.html
click Install software prerequisits
- Welcome, next
- EULA, Accept, next
- Installation Complete, Finish
Click Install Project Server
- Enter PID, Continue
- EULA, Accept, Continue
- File Location, click Install Now
- Run Config Wizard, Close
Config Wizard
- Welcome, Next
- Services reset warning, click Yes
- Database Server, DB Name, click Next
- go have a smoke break
- Config Successful, click Finish
**Browser Opens
- http://servername:portnum/_admin/adminconfigintro.aspx?scenarioid=adminconfig&welcomestringid=farmconfigurationwizard_welcome&isupgrade=true
- Login as domain\mosss2010_admin
- click Start the Wizard
- Service Account and Services, leave default and click Next
- wait here or there, maybe order some carry-out chinese
- Create a new Top-Level Web App -
- - Web Site Address, select /sites/, name Projects
- - Template - Team Site, click OK
- login to the site using your domain/moss2010_admin account
- Open Site Actions, add your real domain\user account to the Site Collection Administrators

Then re-run the MOSS config Wizard to integrate MOSS and Project Server

Install and configure Project Server 2010
http://technet.microsoft.com/en-us/library/ee662109.aspx

Create a PWA site in your web app
http://technet.microsoft.com/en-us/library/ee662105.aspx

Configure Reporting
http://technet.microsoft.com/en-us/library/ee662106.aspx

Stop whining list

1. FreeNas...


2. Windows 2008 R2 2 node Cluster build


3. IIS 7.5
   
   
   
   1. php.iis.net
   
   
   2. WordPress 3.0 Post Setup
   
   
   3. mySQL - with phpmyadmin
   
   
   
   


4. SQL 2008 R2 Enterprise cluster build
   
   
   
   1. Majority node set with cluster, witness server
   
   
   2. Shared disk with quorum from iSCSI Target from FreeNAS
   
   
   
   


5. Self-Signed certs (SSL)


6. ISA - 443 to 80


7. RDP default port add/change - entry on http://d.patrickoneill.com/?p=83


8. MOSS 2007 to MOSS 2010 upgrade/migrate


9. get patches for Mom's computer :)

Users in SharePoint with email addresses not associated with the domain

This is a pretty easy one actually. 

1. Start > Run > dsa.msc (this opens Active Directory Users and Computers)


2. Select the user. On the General Tab, change the email address to an email address that your domain isn't managing (i.e. @yahoo.com, @gmail.com, etc, etc). Click OK


3. Open SharePoint Central Admin console. Click the SSP link off of the Home page of Central Admin


4. Login (duh).


5. Under User Profiles and My Sites > Click User Profiles and Properties


6. Click Start Full Import


7. After the import is completed, you should view the target user's profile and remove any Proxy addresses.

Next, if the user has already been granted access to your MOSS Web Application, you will need to remove the user and then re-add the user back into their original permissions. Then, when you go to view the user's profile details, they will show up with the user's new email address.

Adding the Knowledge Base site template for MOSS 2007

stsadm -o addsolution -filename C:\Bits\KnowledgeBase.wsp

stsadm -o deploysolution -name KnowledgeBase.wsp -allowgacdeployment -immediate

WSS Central Administration site.
Click the Operations tab, and
then click Solution management under global configuration.

After all the solutions are marked Globally Deployed,

run iisreset from the command line.
http://technet.microsoft.com/en-us/windowsserver/sharepoint/bb407286.aspx

MS IT 2.0 Recycle Bin Install steps

1. Run RecycleBinInstaller.msi


2. Welcome to the SharePoint Portal Server Recycle Bin Setup Wizard – click Next


3. Recycle Bin Folder location – C:\SPS_RecycleBin
   
   
   
   1. Log File location – C:\SPS_RecycleBin_Logs\LogFile.txt
   
   
   2. Action Log File location – C:\SPS_RecycleBin_Logs\ActionLog.txt
   
   
   3. Click Next
   
   
   
   

Note: The RecycleFolder location in which to store deleted Site Collection information must be configured to allow Read/Write permissions to all Authenticated Users.

1. Select Installation Folder:
   
   
   
   1. Leave the default folder location.
   
   
   2. Select Everyone for the installation option.
   
   
   3. Click Next
   
   
   
   


2. Confirm Installation – click Next


3. Installation Complete – click Close

Note: SharePoint Portal Server Recycle Bin will create a Registry entry for HKLM\SOFTWARE\Microsoft\IT\SharePoint Portal Extensions\Recycle Bin\.

1. Open IIS Manager and navigate to the Web Service Extensions


2. Right-click Web Service Extensions and select Add a new Web service extension…


3. Extension name – enter RecycleBinISAPI – click Add

10.  Path to file – enter C:\Program Files\Microsoft IT\SharePoint Portal Server Recycle Bin\RecycleBinISAPI.dll

1. click OK

11.   Click Add – Path to file – enter C:\Program Files\Microsoft IT\SharePoint Portal Server Recycle Bin\RecycleBinISAPIFilter.dll

12.  Click Set extension status to Allowed – click OK

13.  Verify the new Web Service Extension is allowed from IIS Manager.

14.  Expand the Web Sites within IIS Manager.

15.  Right-click the website for YourPortalSite (Default Web Site) and select Properties

16.  Select the ISAPI Filters tab

17.  Click Add

1. Filter name – enter RecycleBinISAPIFilter


2. Executable – enter C:\Program Files\Microsoft IT\SharePoint Portal Server Recycle Bin\RecycleBinISAPIFilter.dll


3. Click OK

18.  Verify ISAPI Filter – right-click the website for your portal site (Default Web Site) and select Properties

1. Select the ISAPI Filters tab – verify the RecycleBinISAPIFilter Filter Name displays a green arrow in the Status column and the Priority is set to High

19.  Select the RecycleBinISAPIFilter on the Default Web Site (for your portal site) Properties dialog and click the Move up button – click OK

20.  Expand the Default Web Site (where StaffCollaborator is located).

1. Right-click the _vti_bin virtual folder and select Properties from the context menu.


2. Under Application Settings, click Configuration, and click Insert


3. Executable – enter “C:\Program Files\Microsoft IT\SharePoint Portal Server Recycle Bin\RecycleBinISAPI.dll” (don’t forget the quotes!)


4. Click OK three times.

21.  Expand the Default Web Site (where your portal is located).

1. Right-click the _layouts virtual folder, then select the Recycle folder and select Properties from the context menu.


2. Click Create


3. Application Pool – select MSSharePointPortalAppPool


4. Click Configuration – click Add


5. Executable – enter C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\aspnet_isapi.dll


6. Extension – enter .spsrec – click OK twice.

22.  Restart IIS

23.  Open Notepad

1. Enter – Forfiles -p C:\SPS_RecycleBin -s -m *.* -d -15 -c “cmd /c del /q @path”

Note: The 15 in the command will delete all files in the path that are older than 15 days.

1. Save as RecycleBinCleaner.CMD to C:\SPS_RecycleBin_Logs

24.  Open Control Panel – create a scheduled task to run daily that will execute C:\SPS_RecycleBin_Logs\RecycleBinCleaner.CMD

1. Start time – 1AM – Run the Scheduled Task as the service account Network\SPSRecycleBinCleaner

Uninstall Process

1. Open IIS Manager from all of your IIS user web front-end servers for SPS2003


2. select Default Web Site (for for your portal site), right-mouse click and select Properties


3. Select the ISAPI Filters tab - remove the RecycleBinISAPIFilter - click OK


4. expand the Default Web site (staffcollaborator)
   
   
   
   1. select _vit_bin, right-mouse click, select Properties
   
   
   2. click Configuration
   
   
   3. Under Wildcard... - Remove the RecylceBin entry
   
   
   4. click OK - click Yes to approve - click OK twice
   
   
   
   


5. From IIS Manager - select the Web Service Extensions - select and Delete the Recycle Bin ISAPI entry


6. Control Panel > Add/Remove Programs - Select SharePoint Portal Server Recycle Bin - click Remove


7. restart IIS

SharePoint AAM Stuff

http://blogs.msdn.com/sharepoint/archive/2007/03/06/what-every-sharepoint-administrator-needs-to-know-about-alternate-access-mappings-part-1.aspx

Office SharePoint Server Publishing Infrastructure - Access Denied

If you don't activate Publishing Resources when you first install SharePoint (MOSS 2007), when you try and activate it later via site collection features, you might see an access denied error when activating. You can manually activivate Publishing Resources via stsadm:

C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN>
stsadm -o activatefeature -name PublishingResources -url http://website

Operation completed successfully.

You will then be able to activate Office SharePoint Server Publishing Infrastructure.

MOSS Search Service problem - crawl failing - bad credentials

The resolution for this was to add the following registry key

1) Click Start, click Run, type regedit, and then click OK.
2) In Registry Editor, locate and then click the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
3) Right-click Lsa, point to New, and then click DWORD Value.
4) Type DisableLoopbackCheck, and then press ENTER.
5) Right-click DisableLoopbackCheck, and then click Modify.
6) In the Value data box, type 1, and then click OK.
7) Quit Registry Editor, and then restart your computer.

http://support.microsoft.com/kb/896861

~Sandeep Lad

Then -

- stopped the "Office SharePoint Server Search" service from Central Administration
- restarted the "Office SharePoint Server Search" service from Computer Management > Services and Applications > Services
- started the "Office SharePoint Server Search" service in Central Administration
- reconfigured the search settings
- did a full index AND an incremental search.  The full index did not give me complete results, so I had to run the incremental.