SharePoint Cumulative Updates “Error: Some farm products and patches were not detected

Ran into an issue while recently patching a SharePoint 2010 farm from Service Pack 1 to Service Pack 2. Patching is a bit of a science and can be complex depending the number of servers and products installed in your farm. I applied Service Pack 2 and December 2013 Cumulative Update, KB2553400, for SharePoint and Office Web Applications, 4 total updates.

Note – I have found where customers have SharePoint and Office Web Apps on different patch levels or worse Office Web Apps has never been patched. It’s best practice to have SharePoint and Office Web Apps at the same patch level.

All 2 patches installed without error. At least the install wizard said they did.

I ran psconfig.exe, aka SharePoint Products Configuration Wizard, and boom “Error: Some farm products and patches were not detected on this or other servers. If products or patches are missing locally, you must quit this program and install the required products and patches on this server before restarting this wizard.”  SharePoint thinks the issue is that one of the servers is missing the Office Web Apps December 2013 Cumulative update

 

 

The kicker, these updates were installed and if you are wondering, no we did not run into this issue when we patched our test Farm. I verified these patches were installed in Programs and Features, recently installed updates.  Restarted each SharePoint server after the updates. Still SharePoint thought we hadn’t patched one of the servers.

I remembered running into a similar issue while applying updates on another large SharePoint Farm that had 10 plus language packs. Good Times!

Resolution

1. From SharePoint Shell, run the 2 commands below on each SharePoint server.
2. Get-SpProduct – -Local
3. (Get-SpServer $env:ComputerName).NeedsUpgrade
4. Confirm “True” is returned Continue with running the SharePoint Products Configuration Wizard. If “false” no need to run configuration wizard

 

 

Thank you for the below post

http://www.concurrency.com/sharepoint/sharepoint-cumulative-updates-error-some-farm-products-and-patches-were-not-detected/

 

Log Shipping with SQL Server 2012

Log Shipping in Simple Steps

Log Shipping was introduced in SQL Server 2000 , The main advantage of this is maintain multiple servers as standby server,robust ,we can decide the time interval.

Requirement for Implementing Log Shipping

Both the All the SQL Server Services should be started with the same domain User Name,if  individual server then Start them with Same User Name and Password.Folder level Sharing should be enabled between the Server, SQL Server Agent Services should be started . SQL Server Express Edition is not Possible For Implementing Log Shipping because SQL Server Agent Services are not available.User must be Sysadmin to configure Log Shipping

Internally  when Log Shipping is configured,there are 4 jobs create between Primary Server and Secondary Server, they are  Backup Job,Copy Job,Restore Job Alert Job

Backup job:

This job is created on Primary Server,this job takes the transaction log backup of the Database on a scheduled time

Copy Job:

This job is created on Secondary Server,this job Copies the transaction log Backup from Primary Server to the Standby/Secondary Server.

Restore Job:

This job is created on Secondary Server,this job restored the  copied transaction log backup on the Secondary Server.

Alert Jobs:

This job is created on Primary Server and Secondary Server.and gives the alerts as email, when there  is a delay in backup ,copy,restore jobs.

Log shipping has disadvantages too ,network usage consumption.

Step 1:

Take a Full Backup and a transaction log Backup from the Principle server and Restore it on the Standby by Server with No recovery mode or Standby Mode.

SQL Query command to take backup

1. Use Master
2. Go
3. Backup Database MyDatabase to Disk = ‘D:\MyDatabase_Full.bak’
4. Backup log MyDatabase to Disk = ‘D:\MyDatabase_Tran.trn’

Step2:

Go to the Primary Server right click on the database ->Task_> Ship Transactin Logs..

Step 3:

Click in “Enable this as a primary Database in a Log Shipping configuration”

Step 4:

Give the network path and the Physical path of the shared folder of the database, to know the IP of your server run ipconfig /all command in the command prompt. give the backup time schedule,alert schedule, if using SQL Server 2008 you can even select the Compress Backup Option.Click on schedule and the windows opens as below

Step 5:

Click on the add Secondary Server button Option. connect to the Secondary server .As we have Restored a Full Backup and a transaction log backup. so leave the first tab.

Step 6:

click on Copy Files tab,give the physical path of the folder in Secondary Server.and set the schedule for restore Transaction log too.

Now Lo Shipping has been successfully configured ,to monitor the log shipping you can use

Step7 : To Recovery Log shipping database.

1          Use Master

2          Go

3          Restore database DBname with Recovery

Now, log shipping database is ready to use.

Thanks to the post: http://sqlservr.blog.com/2012/05/27/log-shipping-in-simple-steps/

 

Error: “Could not retrieve backup settings for primary” in Log shipping Backup job

This one is simple but interesting…

Log shipping which was running for an year, suddenly stopped working. Log shipping monitor says that there are no backups restored for last 14849 minutes… Why?

We started figuring this out, the copy and restore jobs were running fine but only the backup job was failing.

What was the error generated by the Log shipping backup job?

*** Error: Could not retrieve backup settings for primary ID ‘abfb9a42-207e-451b-968c-3ac29edc16f9’.(Microsoft.SqlServer.Management.LogShipping) ***
*** Error: Failed to connect to server SQLSERVER2001.(Microsoft.SqlServer.ConnectionInfo) ***
*** Error: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 – Could not open a connection to SQL Server)(.Net SqlClient Data Provider) ***
—– END OF TRANSACTION LOG BACKUP —–

But the name of the SQL Server name is SQLSERVER2012, so why is it looking for SQLSERVER2001? This is because the server was renamed from SQLSERVER2001 to SQLSERVER2012 recently but the sys.servers was not updated with this change.

As a result, SELECT @@SERVERNAME still points to old name so we ran commands given below to update sys.server entry and then RESTARTED SQL Server:

EXEC sp_dropserver ‘Your_OLD_Computer_Name’

GO

EXEC sp_addserver ‘Your_NEW_Computer_Name’, ‘local’

GO

Now we reconfigured log shipping to make it work. You can either do this or update the Log shipping backup with correct SQL Server instance name or create a SQL Server alias pointing back to new server name to make it work. Still not working? Leave the error message in the comments here….

Thanks to the post

ref: http://blogs.msdn.com/b/sqlsakthi/archive/2012/06/14/error-quot-could-not-retrieve-backup-settings-for-primary-quot-in-log-shipping-backup-job.aspx

Reference:

Rename a Computer that Hosts a Stand-Alone Instance of SQL Server – http://msdn.microsoft.com/en-us/library/ms143799.aspx

 

Unable to load DLL Microsoft.VisualStudio.QualityTools.RecorderBarBHO100.dll. The specified module could not be found

Working on a new environment trying to perform an new Web Test I was faced two issues:

1. Web Test Recorder doesn’t show up

Problem :When I start my recording Internet Explorer comes up but the Web Test Recorder doesn’t show up.

Solution: In IE enter Tools menu Select Explorer Bars and Click “Web Test Recorder 10.0” – (This will work for Web Test 8.0 and 9.0)

2. Cannot Stop Web Test Recording Without Getting Exception

Problem: When I clicked “Stop” in the end of Web Test Recording I get the following Exception: “Unable to load DLL ‘Microsoft.VisualStudio.QualityTools.RecorderBarBHO100.dll’: The specified module could not be found”

Solution:

Copy Microsoft.VisualStudio.QualityTools.RecorderBarBHO100.dll (For older versions RecorderBarBHO90.dll  etc)

Located under C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\PrivateAssemblies\

To – C:\Program Files\Internet Explorer and for 64bit machines also Copy To – C:\Program Files (x86)\Internet Explorer

Please refer: http://blogs.microsoft.co.il/shair/2010/11/18/how-to-quotunable-to-load-dll-microsoftvisualstudioqualitytoolsrecorderbarbho100dll-the-specified-module-could-not-be-foundquot/

 

moving content db for a site collection to another db server

 

Here are the steps you will need to take Lets call content DB “MyTESTContentDB”

1. Do a database backup for the content db “MyTESTContentDB” from sql management studio
2. Go to target DB Server and create a empty database naming “MyTESTContentDB” after the content DB
3. Restore the backup from step 1 to empty database create in step 2 “MyTESTContentDB”
4. Go to SharePoint server and run following script Dismount-spcontentdatabase “MyTESTContentDB” and type “Y” to confirm
5. Run the following script

   stsadm -o addcontentdb -url http://local.company.com/mytestsite -databasename MyTESTContentDB -databaseserver TARGETDBSERVER

You will have to input actual URL, actual db name and correct target db server name

Please refer this:http://sharepoint.stackexchange.com/questions/81172/moving-content-db-for-a-site-collection-to-another-db-server

 

How To Repair A Suspect Database In MSSQL Server Database

How To Repair A Suspect Database In MS SQL

Issue
You have a database in MS SQL that is tagged as (suspect) and you are unable to connect to the database.

Possible Causes

• The database could have become corrupted.
• There is not enough space available for the SQL Server to recover the database during startup.
• The database cannot be opened due to inaccessible files or insufficient memory or disk space.
• The database files are being held by operating system, third party backup software etc.
• There was an unexpected SQL Server Shutdown, power failure or a hardware failure.

Resolution
These steps require you to have Microsoft SQL Server Management Studio installed on your computer.  If you do not have this installed please install Microsoft SQL server Management Studio to connect database server.

 Open Microsoft SQL Server Management Studio and connect to your database

1. Click the New Query button
2. Paste the following SQL script into your New Query page replacing [YourDatabase] with the name of your database.
   EXEC sp_resetstatus [YourDatabase];

   ALTER DATABASE [YourDatabase] SET EMERGENCY

   DBCC checkdb([YourDatabase])

   ALTER DATABASE [YourDatabase] SET SINGLE_USER WITH ROLLBACK IMMEDIATE

   DBCC CheckDB ([YourDatabase], REPAIR_ALLOW_DATA_LOSS)

   ALTER DATABASE [YourDatabase] SET MULTI_USER
3. Click Execute

Your database should no longer be tagged as (suspect) and you should be able to access it.

Please refer this: https://support.powerdnn.com/kb/a398/how-to-repair-a-suspect-database-in-mssql

 

 

Restrict normal users joining computer Default limit to number of workstations a user can join to the domain

Please refer Microsoft URL

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

SUMMARY

By default, Windows 2000 allows authenticated users to join ten machine accounts to the domain. If a user attempts to join an eleventh machine account, the error messages listed in the following Microsoft Knowledge Base Article are displayed:

251335 Domain users cannot join workstation or server to a domain

This default was implemented to prevent misuse, but can be overridden by an administrator by making a change to an object in Active Directory. 

Note that users in the Administrators or Domain Administrators groups, and those users who have delegated permissions on containers in Active Directory to create and delete computer accounts, are not restricted by this limitation.

MORE INFORMATION

The number of workstations currently owned by a user is calculated by looking at the ms-DS-CreatorSID attribute of machine accounts. 

To modify Active Directory to allow more (or fewer) machine accounts on the domain, use the Adsiedit tool. 

WARNING Using Adsiedit incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Adsiedit can be solved. Use Adsiedit at your own risk.

1. Install the Windows Support tools if they have not already been installed. This is necessary only for Windows 2000 and Windows Server 2003. For Windows Server 2008 and Windows Server 2008 R2, Adsiedit is installed automatically when you install the Active Directory Domain Services role.
2. Run Adsiedit.msc as an administrator of the domain. Expand the Domain NC node. This node contains an object that begins with “DC=” and reflects the correct domain name. Right-click this object, and then click Properties.
3. In the Select which properties to view box, click Both. In the Select a property to view box, click ms-DS-MachineAccountQuota.
4. In the Edit Attribute box, type the number of workstations that you want users to be able to maintain concurrently.
5. Click Set, and then click OK.

 

How to Install PHP on IIS 6 for Windows Server 2003

How to Install PHP on IIS 6 for Windows Server 2003
One of most popular development platforms on the web is PHP which powers many popular applications and sites such as Facebook, WordPress and Joomla. While most of these systems are ‘designed’ to be used on a Linux system running the Apache Web Server, you can deploy PHP applications via IIS 6 on your Windows Server 2003 system.

Configuring PHP
In order for Windows to run PHP code, the PHP binary files need to be copied to your system. No installation is required, however some configuration must be done in order for it to properly run. The first step is to download the PHP Windows Binaries and extract them (i.e. ‘C:PHP’). For IIS 6, the non thread safe binaries should be used.

Copy the ‘php.ini-production’ file from the extracted files paste it into the Windows directory. In the Windows directory, rename this file to ‘php.ini’.

Open the ‘php.ini’ file in Notepad and configure it as needed. Out of the box, the production configuration we copied is preconfigured for what the PHP Team feels is good for a production server. There are a few changes you will need to make to configure PHP for your IIS 6 system:

• Uncomment and set the key, cgi.force_redirect = 0
• Uncomment the key, fastcgi.impersonate = 1
• Uncomment and set the key, extension_dir to the ‘ext’ folder in the path PHP was extracted to (i.e. ‘C:PHPext’).
• Set the key, date.timezone to the time zone of your server (the URL on the line above this key lists the accepted values).

At this point, your Windows system can run PHP scripts from the command line using the ‘php.exe’ tool.

Installing the IIS 6 FastCGI Extension

In order for Internet Information Services (IIS) 6 to execute and serve PHP scripts, some additional configuration is required. In this guide, we will install PHP on IIS using the FastCGI interface which provides a good balance of stability and performance. Since FastCGI is not included with IIS 6 be default, we need to download and install it.

The FastCGI installer does not require any configuration, however once the FastCGI extension is installed we need to configure it to run PHP.

Open the file ‘C:WINDOWSsystem32inetsrvfcgiext.ini’ in Notepad and find the ‘Types’ section and enter the configuration information:

[Types]
php=PHP

[PHP]
ExePath=C:PHPphp-cgi.exe
InstanceMaxRequests=5000
EnvironmentVars=PHP_MAX_REQUESTS:5000

Revise these values as needed according to your environment, but it is important that all of settings have the correct values. Once you are finished, save this file.

Configuring IIS to Run PHP via FastCGI

With both PHP and FastCGI installed and configured, all that is left is to set up IIS 6. When you open the IIS Management Console, under the Web Service Extensions make sure the “FastCGI Handler” is set to allowed.

Next, go to the Properties settings for the Web Sites group.

On the “Home Directory” tab, click the “Configuration” button.

Add a mapping for files with the .php file extension with the executable set to the FastCGI extension DLL.

Once you have applied all the changes, restart IIS.

Testing PHP

At this point, your server is ready to go, but just to be sure we can confirm your PHP setup through IIS pretty easily. Create a text file in the directory ‘C:Inetpubwwwroot’ named ‘phpinfo.php’ which simply contains the line:

<?php phpinfo(); ?>

Finally, browse to the address: ‘http://localhost/phpinfo.php’ on your server and you should see the PHP information page. If the page loads successfully, PHP is now up and running on your machine.

Conclusion

Once you have PHP up and running on your Windows system, you can take advantage of the multitude of PHP based applications available as well as develop and deploy your own.

Links

Download PHP Windows Binaries (non thread safe)

Download IIS 6 FastCGI Extension

——————————————————————————–

Thanks for: http://www.howtogeek.com/50455/how-to-install-php-on-iis-6-for-windows-server-2003/

 

Mapped Drives Are Not Seen From Elevated Command Prompt in Vista and Windows 7

SYMPTOMS

After you turn on User Account Control in Windows Vista or in Windows 7, programs may be unable to access some network locations. This problem may also occur when you use the command prompt to access a network location.
Note:To turn on User Account Control, you click Allow in a User Account Control dialog box.

CAUSE

This problem occurs because User Account Control treats members of the Administrators group as standard users. 
When a member of the Administrators group logs on to a Windows Vista-based computer or to a Windows 7-based computer that has User Account Control enabled, the user runs as a standard user. Standard users are members of the Users group. If you are a member of the Administrators group and if you want to perform a task that requires a full administrator access token, User Account Control prompts you for approval. For example, you are prompted if you try to edit security policies on the computer. If you click Allow in the User Account Control dialog box, you can then complete the administrative task by using the full administrator access token. 
When an administrator logs on to Windows Vista or to Windows 7, the Local Security Authority (LSA) creates two access tokens. If LSA is notified that the user is a member of the Administrators group, LSA creates the second logon that has the administrator rights removed (filtered). This filtered access token is used to start the user’s desktop. Applications can use the full administrator access token if the administrator user clicks Allow in a User Account Control dialog box. 
If a user is logged on to Windows Vista or to Windows 7, and if User Account Control is enabled, a program that uses the user’s filtered access token and a program that uses the user’s full administrator access token can run at the same time. Because LSA created the access tokens during two separate logon sessions, the access tokens contain separate logon IDs.  
When network shares are mapped, they are linked to the current logon session for the current process access token. This means that, if a user uses the command prompt (Cmd.exe) together with the filtered access token to map a network share, the network share is not mapped for processes that run with the full administrator access token.

 

WORKAROUND

Important This workaround may make your system unsafe. Microsoft does not support this workaround. Use this workaround at your own risk.
To work around this problem, configure the EnableLinkedConnections registry value. This value enables Windows Vista or Windows 7 to share network connections between the filtered access token and the full administrator access token for a member of the Administrators group. After you configure this registry value, LSA checks whether there is another access token that is associated with the current user session if a network resource is mapped to an access token. If LSA determines that there is a linked access token, it adds the network share to the linked location. 
To configure the EnableLinkedConnections registry value, follow these steps:

1. Click Start, type regedit in the Start Search box, and then press Enter.
2. Locate and then right-click the following registry subkey:
   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
3. Point to New, and then click DWORD Value.
4. Type EnableLinkedConnections, and then press Enter.
5. Right-click EnableLinkedConnections, and then click Modify.
6. In the Value data box, type 1, and then click OK.
7. Exit Registry Editor, and then restart the computer.

 

 

SCCM 2007 R2: Installation in Windows Server 2008 – SCCM Installation

SCCM 2007 R2: Installation in Windows Server 2008 – SCCM Installation

Before we are able to install SCCM 2007 R2 on the operating system platform Windows Server 2008 and to have Active Directory integration we need to fullfill some pre-requisites. Following are the pre-requisites for SCCM 2007 R2: Active Directory Schema has to be extended; SCCM System Management Container has to be created in Active Directory; Microsoft Remote Differential Compression feature has to be installed; WebDAV has to be installed and configured in IIS; BITS Server Extensions feature has to be installed; WSUS Server 3.0 SP1 has to be installed.   1. Installation Pre-Requisites for SCCM 2007 R2 In this part we are going to fullfill the pre-requirements for installation of SCCM 2007 R2 1.1 Extend the Active Directory Schema This task can only be executed whilst logged on with a user account that is member of the “Schema Admins” group in Active Directory. The account “Domain Admin” is member of this group. Place the installation medium for SCCM 2007 SP1 and open a Windows Explorer.   Follow the path to: %Cd-rom%\Z:\SMSSETUP\BIN\I386 In this location you will find the file: EXTADSCH.exe Start the extension of the Active Directory by double clicking the file “EXTADSCH.exe” When the DOS Box dissappears the extending part is done. Verify the extension by opening the file: C:\ ExtADSch.log If the actions was succesfull the .log file should contain the lines:   Succesfully extended the Active Directory Schema   1.2 Create the Systems Management Container in Active Directory For creating the System Management Container we need to be logged on to an Active Directory Domain Controller or need to have to “Remote Administration Tools” installed.   On a Domain Controller open the ADSI Edit snap-in.   Browse to the following location: Domain\DC\CN=System Right click the container “System” and select the option: System\New\Object The  “Create Object Wizard” appears. In the “Create Object” wizard select the option:   Container Clik on à Next Enter the following values: Value:                  System Management   Click on à Next     Click à Finish   The “System Management”container is now created. 1.2.1 Permissions on the System Management Container   To have SCCM being able to access the created container we need to change the permissions in this container.   Open the “Active Directory Users and Computers” snap-in. Click on the menu option “View” and select “Advanced Features”. The “System” OU will now be visible. Open the “System” Ou and browse to “System Management” Rightclick the “System Management” container and select the option: Properties Select the tab “Security”   Click on à Add Click on à Object Types Select the following “Object Types”: (X)          Computers (X)          Users   Click on à OK   Click on à Advanced   Click on à Find Now Select the accounts of: SCCM-Admin %SCCM Server Account% Click on à OK       Click on à OK     Grant the following permissions to the two selected accounts: Read Write Create All Child Objects Delete All Child Objects Click on à Advanced     Select the account “SCCM-Admin” and click à Edit     Select the following options: Apply to:             This object and all descendant objects (X)          Apply these permissions to object and/or containers within this container Click on à OK   Repeat these steps for hte account “%SCCM Server Account%”      Click on à OK      Click on à OK to save the changes. Now we have finished the creation of the System Management Container and setting the correct permissions,       1.3 Installation of Windows Server 2008 feature Remote Differential Compression   Logon to the SCCM Server to be and open the “Server Manager” snap-in. Select the “Features” option.   Click on à Add Features Select the option: (X)          Remote Differential Compression   Click on à Next Click on à Install Click on à Close when the installation is finished     1.4 Installation of the WebDAV extensions for IIS The WebDAV extensions for IIS Server are not available in Windows Server 2008. You have to download the installation files seperately and install them.     Download Start the installation by double clicking on the file:     webdav_x86_rtw.msi The installation wizard appears Select the option: (X)          I accept the terms in the License Agreement   Click on à Install Click on à Finish when the installation is done.       1.4.1 Configuration of the WebDAV extensions in IIS Server Manager To configure the WebDAV extensions for use with SCCM 2007 R2 follow the instructions in Microsoft’s Technet Document: http://technet.microsoft.com/en-us/library/cc431377.aspx 1.5 Installation of Windows Server 2008 BITS Extensions feature Logon to the SCCM Server to be and open the “Server Manager” snap-in and select the option “Features” Click on à Add Features Select the option: (X)          BITS Server Extensions   An additional feature component installation screen appears.   Click on à Add Required Role Services Click on à Next Click on à Next Click on à Next Click on à Install       1.6 Installation of WSUS Server 3.0 SP1 In this part of the article I will describe the installation of WSUS Server 3.0 SP1. WSUS Server 3.0 SP1 is being used by SCCM to deploy Windows Updates to managed systems. Also we will install update Kb954960 for WSUS Server 3.0 SP1. This update adds the latest productinformation which can be downloaded from the Microsoft Website. The installation source for WSUS Server 3.0 SP1 can be downloaded here   Start the installation of WSUS Server 3.0 SP1 by double clicking the file:     WSUSSetup_30SP1_x86.exe The installation wizard appears: Click on à Next In the screen that appears select the option: (X)         Full server installation including Administration Console   Click on à Next In the screen that appears select the option: (X)         I accept the terms of the License agreement   Click on à Next In the screen that appears select the option: (X)         Store updates locallyLocation:     D:\WSUS\   Click à Next In the sreen that appears select the option: (X)         Use an existing database server in this computer   Click on à Next   Click on à Next In the screen that appears select the option: (X)         Create a Windows Server Update Services 3.0 SP1 Web site   This is because the “default website” will be used by SCCM 2007 R2   Click on à Next   Click on à Next   Click on à Finish The configuration wizard for WSUS Server 3.0 SP1 appears automatically     Click on à Cancel To stop the wizard. Configuration of WSUS Server will be done from the SCCM Console.       1.6.1 Installation WSUS Server 3.0 SP1 update Kb954960   This update can be downloaded from the Microsoft Website:     Download   Start the installation by double clicking on the file:     WSUS_30SP1_KB954960_x86.exe   The installation wizard appears:   Click on à OK  Reboot the Server to initialize components    2. Installation SCCM 2007 SP1 In this part of the article I will describe the installation of Microsoft SCCM 2007 SP1. After this installation the update SCCM 2007 R2 will be installed. Make sure that the server is connected to the internet as during the installation updates are downloaded from the Microsoft Website.   Place the installation medium for SCCM 2007 SP1. The installation wizard will appear:   Click on à Run the prerequisite checker In the screen that appears enter the following values: (X)         Primary Site SQL Server and instance, if applicable:                                %SCCM Servername% SDK Server:                                                                                      %SCCM Servername% Management point computer FQDN on the internet:   %SCCM Servername%.domeinnaam   Click on à OK   If the server passes all pre-requisites for installation of SCCM 2007 R2 close the pre-requisites check and restart the installation     2.2 Installation SCCM 2007 SP1   From the Welcome Screen select the option:   Click on à Install\Configuration Manager 2007 SP1 The installation wizard appears: Click on à Next In the screen that appears select the option: (X)         Install a Configuration Manager site server   Click on à Next From the screen that appears select the option: (X)         I accept the license terms   Click on à Next From the screen that appears select the option: (X)         Custom Settings   Click on à Next From the screen that appears select the option: (X)         Primary Site   Click on à Next From the screen that appears select the option: (X)         No, I don’t want to participate right now   Click on à Next From the screen that appears enter the license key if none is present and click on à Next From the screen that appears enter the following value: Installation path:      D:\Microsoft Configuration Manager   Click on à Next From the screen that appears enter the following values: Site Code:                          001 Site name:                         %Sitename%   Click on à Next From the screen that appears select the option: (X)         Configuration Manager Mixed Mode   Click on à Next From the screen that appears select the option: (X)         Software Inventory (X)         Hardware Inventory (X)         Advertised programs (X)         Software Updates (X)         Software metering (X)         Desired configuration management (X)         Remote tools   Click on à Next From the screen that appears enter the values: SQL  Server and Instance, if applicable:               %SCCM Servername% ConfigMgr site database:                                           SCCMDB   Click on à Next From the screen that appears enter the correct value if not already entered: Enter the appropriate location for the provider:                              %SCCM Servername%   Click on à Next From the screen that appears select the following options: (X)         Install a management point %SCCM Servername%.%domainename%   Click on à Next From the screen that appears select the option: (X)         Use default port (80)   Click on à Next From the screen that appears select the option: (X)         Check for updates and download newer versions to an alternath path   Click on à Next From the screen that appears enter the values: Alternate path:                               D:\Temp\SCCM Updates   Note:     Make sure this path exists and/or create it in the background before clicking next   Click on à Next   Updates are downloaded from the Microsoft website. Click on à OK Click on à Next   Click on à Begin Install After the installation has completed verify if all components have installed succesfully. If so Click on à Next   Click on à Finish This concludes the installation of SCCM Server 2007 SP1. Now continue with the installation of R2     2.3 Installation SCCM 2007 R2 In this part I will describe the installation of SCCM 2007 R2. The R2 additions of SCCM 2007 is an update to the already installed version SCCM 2007 SP1.   Start the installation by double clicking the file: Installatie media\Splash.hta The installation wizard appears:    Click on à Install\Configuratio Manager 2007 R2 Click on à Next From the screen that appears select the option: (X)         I accept the license agreement   Click on à Next From the screen that appears enter the corect values for: Name: Organization:   Enter the licese key of not already entered en click on à Next From the screen that appears click on àNext After the completion of the installation click on à Finish    This concludes the installation of SCCM 2007 R2. Now we can start configuring SCCM 2007 R2