Sign in
 
Home2012Previous VersionsLibraryForumsGallery
System Center TechCenter > System Center Configuration Manager Forums > Configuration Manager 2007 Setup/Deployment > Installing ConfigMgr Site Server on Windows Server 2008

Discussion Installing ConfigMgr Site Server on Windows Server 2008

    •  
      Monday, June 23, 2008 7:17 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

       

      Today, I managed to install ConfigMgr Site Server on Windows Server 2008. It wasn't as easy as I thought... Hopefully by telling my mistakes, somebody can installed ConfigMgr much faster on Windows Server 2008.

       

      This is a test environment, so I decided to put all the eggs to the same basket. This means that the site server is also DC and SQL Server. I installed 64-bit Windows Server 2008 on a physical server and prepared it for ConfigMgr installation ie. installed SQL Server 2005 SP2,  extended AD schema, created System Management container, installed IIS7 etc.

       

      Then I checked the pre-requisites. On the first try, only BITS Server and WebDAV were missing. Fortunately, ConfigMgr documentation has a great topic: How to Configure Windows Server 2008 for Site System Roles. WebDAV was easy to install with those detailed steps. I was a little confused what extensions I need to activate on the section: To modify the requestFiltering section on BITS-enabled distribution points. I just skipped that part.

       

      Without modifying requestFilter, Prereq checker was happy, so I started to install ConfigMgr site server. Then came problem #1: I couldn't select an option to install a primary site.

       

      ConfigMgrSetup.log had the following lines:

      -----------------

      ===================== << Starting SMS V4 SP1 Upgrade Setup >> =====================
      <06-23-2008 13:14:50> Commandline :
      "E:\Softat\SCConfigMgr07_UPD_EN\SMSSETUP\BIN\I386\setup.exe"
      <06-23-2008 13:14:50> This is 64 bit.
      <06-23-2008 13:14:50> Verifying the Reg for AssetIntelligence Installation
      <06-23-2008 13:14:50> Setting the default CSV folder path
      <06-23-2008 13:14:50> SMS Build Number = 6221
      <06-23-2008 13:14:50> SMS Version = 4.0
      <06-23-2008 13:14:50> SMS Minimum Build Number = 800
      <06-23-2008 13:14:50> Verifying SMS Active Directory Schema Extensions.
      <06-23-2008 13:14:50> DS Root:CN=Schema,CN=Configuration,DC=demo,DC=net
      <06-23-2008 13:14:50> Verifying SMS Active Directory Schema Extensions.
      <06-23-2008 13:14:50> DS Root:CN=Schema,CN=Configuration,DC=demo,DC=net
      <06-23-2008 13:14:52> Setup has not detected an existing installation of a primary site server, secondary site server, site system, or Configuration Manager console on this computer.
      <06-23-2008 13:14:52> Setup has not detected an existing installation of a primary site server, secondary site server, site system, or Configuration Manager console on this computer.
      <06-23-2008 13:16:42>

      ----------------------

      Because I could install secondary site, I thought I have some problem with my SQL Server 2005 installation on Windows Server 2008. I hadn't earlier installed SQL Server 2005 on Windows Server 2008, so I wasn't sure if it needed some special steps.

       

      After a few hours, I finally understood what went wrong. My SP 1 installation DVD is only an upgrade! So I needed to install ConfigMgr RTM before trying to install SP 1. For some stupid reason, I thought ConfigMgr 2007 SP 1 upgrade could magically install the full version of ConfigMgr on Windows Server 2008.

       

      The documentation should mention that you can actually install ConfigMgr 2007 RTM on Windows Server 2008 and in my scenario it is REQUIRED.

       

      ConfigMgr 2007 RTM installed easily on W2k8 and then I could start the upgrade process. Then came the problem #2: ConfigMgr 2007 SP 1 upgrade hangs.

       

      Upgrade process started nicely and it could upgrade ConfigMgr database. The installation hangs while it is upgrading WAIK. ConfigMgrSetup.log had the following lines:

       

      <06-23-2008 14:58:15> Windows Automated Installation Kit 1.0.0.0 detected.
      <06-23-2008 14:58:15> Uninstalling Windows Automated Installation Kit...
      <06-23-2008 14:58:33> Windows Automated Installation Kit uninstalled successfully.
      <06-23-2008 14:58:33> Windows Automated Installation Kit is being installed from d:\ConfgMgr\WAIK\waikamd64.msi.

      Application log had the following events:

      Log Name:      Application
      Source:        MsiInstaller
      Date:          23.6.2008 15:12:11
      Event ID:      11729
      Task Category: None
      Level:         Information
      Keywords:      Classic
      User:          domain\Administrator
      Computer:      server

      Description:
      Product: Windows Automated Installation Kit -- Configuration failed.

      and

       

      Log Name:      Application
      Source:        MsiInstaller
      Date:          23.6.2008 15:12:11
      Event ID:      1035
      Task Category: None
      Level:         Information
      Keywords:      Classic
      User:          domain\Administrator
      Computer:      server
      Description:
      Windows Installer reconfigured the product. Product Name: Windows Automated Installation Kit. Product Version: 1.1.0.0. Product Language: 1033. Reconfiguration success or error status: 1602.

      ConfigMgr SP 1 installation didn't continue. It took me about 10 minutes to notice that there was a message box (underneath other windows): Installation Failed. When I clicked OK (the only option), ConfigMgr upgrade process continued!!! And it seemed that WAIK 1.1 is actually successfully installed.

       

      After a couple of minutes, ConfigMgr SP 1 is installed to my server.

       

      Then I noticed the problem #3: MP is not correctly reinstalled. MPsetup.log had the following lines:

      <06-23-2008 15:27:07> checking WebDAV configuraitons
      <06-23-2008 15:27:08>  WebDAV settings is not setup appropriately
      <06-23-2008 15:27:08>  [Allow property queries with infinite depth] should be true (false)
      <06-23-2008 15:27:08>  [Allow Custom Properties] should be false (false)
      <06-23-2008 15:27:08>  [Allow anonymous property queries] should be true (true)
      <06-23-2008 15:27:08>  Allow [All users read access to All content] authoring rule should exist (exist)

      This was my mistake. I didn't specify the correct WebDAV options. Prereq checker didn't give me any indication that my webdav configuration is incorrect. It only checks that WebDAV is installed, not if it has the correct options.

       

      After I put the correct options to WebDAV, MP installed nicely.

       

      After these few hours, I had a working ConfigMgr 2007 SP 1 running on Windows Server 2008.

       

    All Replies

    • Monday, June 23, 2008 8:33 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      WE DON'T SUPPORT CONFIGURATION MANANGER 2007 RTM PRIMARY/SECONDARY SITE INSTALLATIONS ON WINDOWS 2008.

       

      Therefore we don't support the upgrade scenario you detailed here. For users who want to have ConfigMgr 2007 running on Windows 2008, we recommend a new install fo ConfigMgr 2007 SP1.

       

      For your scenario, you should have installed the SP1 Eval version which can be upgraded to a full licensed version once that's obtained.

       

      WAIK is a little tricky to explain, but basically we detect the WAIK 1.0 condition where a manual uninstall and reboot is required. If you perform an command line upgrade, this will bypass the prereq checking and you will not receive the blocking setup requirement to uninstall it. Regardless, it still hits the issue and throws the dialog (albeit behind other windows). We do recommend that you run the prereq checker prior to performing a unattended upgrade so you know about any configuration issues that will affect setup.

       

      You've detailed your entire setup experience with complete accuracy. This information will be benificial to the readers on this forum. Yes, we check for WebDAV but we don't detect the correct settings (we do if you push the site role, but not when part of the site server initial install).

       
    • Tuesday, June 24, 2008 6:21 AM
       
       
      Sign In to Vote
      0
      Sign In to Vote
       Jeff Nordrum [MSFT] wrote:

      WE DON'T SUPPORT CONFIGURATION MANANGER 2007 RTM PRIMARY/SECONDARY SITE INSTALLATIONS ON WINDOWS 2008.

       

      Therefore we don't support the upgrade scenario you detailed here. For users who want to have ConfigMgr 2007 running on Windows 2008, we recommend a new install fo ConfigMgr 2007 SP1.

       

      For your scenario, you should have installed the SP1 Eval version which can be upgraded to a full licensed version once that's obtained.

       

       

      Too bad prereq checker cannot predict the future, because ConfigMgr RTM prereq checker was happy with my Windows Server 2008 installation! 

       

      You might want to update the documentation with this statement that ConfigMgr RTM installation on Windows 2008 is NOT supported even if you immediately upgrade the installation to ConfigMgr SP1.

       

      I think I'll reinstall my unsupported ConfigMgr installation, so if I find any other issues while running ConfigMgr on W2k8, they would happen on a supported scenario.

       
    • Tuesday, June 24, 2008 12:01 PM
      Moderator
       
       
      Sign In to Vote
      0
      Sign In to Vote
      Wally stated last night that the full install with SP1 is available on MVLS to EA and SA customers.

       

       
    • Tuesday, June 24, 2008 10:37 PM
      Owner
       
       
      Sign In to Vote
      0
      Sign In to Vote

      Panu, but if you look at the supported configurations documentation, we do show you which OS' are supported, and Windows Server 2008 is NOT listed for RTM, but it IS listed as supported for SP1.

       

      And we've covered it numerous times on this forum and the General forum - Configuration Manager RTM does not support Windows Server 2008, other than as a client and as a System Health Validator.

       

      If it was not complete enough for you (or others) sorry about that. We try, but obviously are not perfect.

       
    • Wednesday, June 25, 2008 6:33 AM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      I agree that the documentation is perfectly clear about which ConfigMgr version is supported with Windows Server 2008.

      Unfortunately, Microsoft's different product groups have different policies how they support OSes if their product requires some service pack to work on this OS.

       

      E.g. with SQL Server 2005, only SQL Server 2005 SP 2 is supported. You MUST first install SQL Server 2005 RTM and then you upgrade to SP2. With ConfigMgr 2007, you SHOULD NOT do the same thing. You MUST use ConfigMgr SP 1 integrated installation media.

       

      And because you first have to install SQL Server 2005 SP 2 and then you install ConfigMgr SP 1, you might continue the SQL installation method incorrectly to ConfigMgr installation.

       

      Communication is a difficult thing: no matter how hard you try, there is always some stupid like me, who just don't get it...

       

       
    • Wednesday, June 25, 2008 11:06 PM
      Owner
       
       
      Sign In to Vote
      0
      Sign In to Vote

      I would never call you stupid Panu - I might think it, but never say it :-)

       

      For all you who are now getting upset with me typing that, I've known Panu for years now, and think he knows when I'm joking, especially when I put in the smiley :-)

       

      Panu is one of our MVPs, and I think by definition, you can't be an MVP and be stupid at the same time.

       
    • Wednesday, June 25, 2008 11:21 PM
      Moderator
       
       
      Sign In to Vote
      0
      Sign In to Vote

       Wally [MSFT] wrote:
      you can't be an MVP and be stupid at the same time.

       

      Wally, you just crushed my hopes of being an MVP cause this would definately rule me out :-)

       
    • Wednesday, June 25, 2008 11:27 PM
      Owner
       
       
      Sign In to Vote
      0
      Sign In to Vote

      Doubtful, but at least now you've opened yourself to comments from everyone :-) We all have our moments when we're less than brilliant. At my age, I think they are called 'senior moments' :-)

       
    • Tuesday, July 01, 2008 7:03 AM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      Calling Panu stupid would be against my principles as well.

       

      Principle 4.5) Never pick a fight with people taller than you, they have longer arms and can hit you from a distance.

      Principle 4.6) Be extra carefull if your disadvantage is more than a few inches.

       

      Kim Oppalfens

       

       
    • Tuesday, July 01, 2008 9:12 AM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      Don't despair, every once in a while they award the exception that proves the rule, just look at Garth :-)

       

       

       John Marcum wrote:

       Wally [MSFT] wrote:
      you can't be an MVP and be stupid at the same time.

       

      Wally, you just crushed my hopes of being an MVP cause this would definately rule me out :-)

       
    • Wednesday, August 06, 2008 3:42 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      I had exactly the same experience as described above - however, choosing the SP1 Eval for a clean installation is no choice at that point: I am currently building a new infrastructure based on W2K8 localized german and there is no SP1 Eval - just RTM Eval.

       

      So - any suggestions but waiting for some months?

       

       

       

       

       
    • Thursday, August 07, 2008 8:47 AM
      Moderator
       
       
      Sign In to Vote
      0
      Sign In to Vote
      ConfigMgr with SP1 included is already available on the MVLS site (at least the EN version). That can be installed on a server 2008 box. I don't know if the localized versions are already available. But you could install ConfigMgr SP1 EN and go the ICP route (http://www.microsoft.com/downloads/details.aspx?familyid=76739d39-50a9-436f-9c3b-32a1aafb9154&displaylang=en&tm) for the clients.