Microsoft Data Protection Manager (DPM) with MOSS 2007

-
Steps for installation of DPM to protect MOSS environment.
1- Install the MOSS then WSS sp1 then MOSS sp1
2- Install Knowledge Base article 941422, "Update for Windows SharePoint Services 3.0" (http://go.microsoft.com/fwlink/?LinkId=100392).
3- Install Knowledge Base article 941422 on all protected servers on which Windows SharePoint SharePoint Services 3.0, Microsoft Office SharePoint Server 2007, and Microsoft Office SharePoint Server 2007 SP1 are installed.
4- Prepare the DPM Box: (Install DPM on a server different than the servers used on the  MOSS Farm)


 1- Install Windows Server 2003 with Service Pack 2 (SP2) or later.
 2- Install Update for Windows Server 2003 (KB940349)
 3- Install Windows PowerShell 1.0 English-Language Installation Package for Windows Server 2003 (KB926139)
 4- Windows Deployment Services (WDS) on Windows Server 2003 Service Pack 2 (SP2) servers.
 -OR-
 SIS on Windows Storage Server 2003 R2.
 5- Install nternet Information Services (IIS) 6.0 for Windows Server 2003
 6- Install Microsoft .NET Framework 2.0
 7- Install Microsoft SQL Server 2005
 Microsoft SQL Server 2005 Workstation components:
 You can use an existing remote instance of SQL Server for your DPM database. If you choose to use a remote instance of SQL Server, you must install sqlprep.msi.
 To use an instance of SQL Server on a remote computer, run sqlprep.msi, which is located on the DPM product DVD in the DPM2007\msi\SQLprep folder.
 Verify that the user account you will be using to run the SQL Server service and the SQL Server Agent service has read and execute permissions to the SQL Server installation location.
 Note: The remote instance of SQL Server cannot be on a computer that is running as a domain controller.

 8- Microsoft SQL Server 2005 with Reporting Services.
 If SQL Server Reporting Services is installed on the remote SQL Server, DPM Setup will use that Reporting Service. If SQL Server Reporting Services is not installed on the remote computer running SQL Server, you must install and configure the service on the remote computer running SQL Server.
 9- Microsoft SQL Server 2005 Service Pack 2.
 10- Install DPM
 11-Start the WSS Writer service on the WSS Server and then provide the protection agent with credentials for the WSS farm.

Comments

Post a Comment

Popular posts from this blog

Adjust the Search SharePoint Performance level

-
-Set-SPEnterpriseSearchService -PerformanceLevel PartlyReduced On all search app servers -Open NodeRunner process configuration file below in Notepad C:\Program Files\Microsoft Office Servers\15.0\Search\Runtime\1.0\noderunner.exe.config. Update  <nodeRunnerSettings memoryLimitMegabytes=”0 ″ /> . This is the configuration to limit NodeRunner process memory usage, replace  0  to 500 or 1000 -Restart  SharePoint Search Host Controller  service
Read more

SharePoint 2013 User Profile synchronization versus import

-
Reference is : 2013 advanced Training User Profile Service administrators in SharePoint 2013 can use profile synchronization to manage and synchronize the user and group profile data stored in the SharePoint 2013 profile store with profile data stored in directory services and BDC systems. There are two distinct forms of profile import and synchronization available in SharePoint 2013: ·          One-way profile import. This is a new implementation of a simple import process that was first provided in SharePoint Server 2007. It uses the SharePoint Active Directory Import option to import user profile data from Active Directory Domain Services (AD DS). Note: One-way profile import only works with Active Directory and does not support other directory services. ·          Two-way profile synchronization. This uses the SharePoint Server 2013 profile synchronization method that was first introduced in SharePoint Server 2010. It uses Microsoft Forefront Identity Manager (FIM)
Read more

Usage and Popularity Trends Report not showing correct numbers

-
Recently came into issue that popularity trends showing zero while users are accessing documents so I have that there is a parameter called TailTrimming as mentioned in this reference blog   https://blogs.technet.microsoft.com/tothesharepoint/2014/01/23/view-and-configure-usage-analytics-reports-in-sharepoint-server-2013/ For example, for the Views usage event the TailTrimming parameter is by default set to 3. This means that the usage analytics reports will be updated for an item when the item has been viewed a minimum three times within the last 24 hours. For example, if the item Fabrikam Laptop16 M6000 has been viewed twice within the last 24 hours, these two views won’t show up in the usage analytics reports. If within the next 24 hours the Fabrikam Laptop16 M6000 item is viewed 4 times, the usage analytics report will be updated with 4 views. to adjust it needs to run the following commands $SSP = Get-SPEnterpriseSearchServiceApplicationProxy $tenantConfig = $SSP.GetAn
Read more