1 2 Previous Next 10 Replies Latest reply on Oct 23, 2013 12:13 PM by Polen

    SCS Add-on for SCCM install won't let me choose SCCM2012

    aurock

      I'm trying to install the scs add-on for sccm.  When I'm going through the setup wizard, on the SCCM Settings screen the wizard detects my installation folder and site code correctly, but not the sccm version.  The radio button for 2007 is marked, and the radio button for 2012 is greyed out.  I am running SCCM 2012 SP1.  What do I need to do to get this working?

        • 1. Re: SCS Add-on for SCCM install won't let me choose SCCM2012
          Alan Alderson

          aurock,

          Can you tell me what version of the SCS Add-on you are running? Also, would it be possible to upload the log file that was created during the installation attempt? The log is located in the same folder as the SCCMAddon.exe, and is called SCCMAddon.log.


          Thanks.

          -Alan

          • 2. Re: SCS Add-on for SCCM install won't let me choose SCCM2012
            aurock

            Thanks for the reply.

             

            v1.0.0.36

             

            SCCMAddon.log only shows the following:

            2013-07-11 10:36:08,790 - DEBUG: Starting
            2013-07-11 10:36:08,806 - INFO : Starting Log
            2013-07-11 10:36:09,853 - DEBUG: Entering SettingsViewModel.ctor
            2013-07-11 10:36:10,978 - INFO : Detected x64 bit installation folder: C:\Program Files\Microsoft Configuration Manager
            

             

            I'm not sure that there's much of use there.  I never continued beyond the Settings screen, since it wouldn't let me choose SCCM 2012 and I wasn't sure it was safe to go forward with the setup.

            • 3. Re: SCS Add-on for SCCM install won't let me choose SCCM2012
              Alan Alderson

              We are currently working on a fix for this issue. I will update you as soon as it's available.

              1 of 1 people found this helpful
              • 4. Re: SCS Add-on for SCCM install won't let me choose SCCM2012
                Polen

                You got further than I did with SCCM 2012 SP1

                 

                2013-07-12 12:43:01,837 - DEBUG: Starting

                2013-07-12 12:43:01,845 - INFO : Starting Log

                2013-07-12 12:43:01,980 - DEBUG: Entering SettingsViewModel.ctor

                2013-07-12 12:43:02,098 - ERROR: Could not identify SCCM installation

                SCCMConfig.Domain.SCCMProbingException: Cannot detect SCCM Installation folder. Attempted: C:\SMS

                   at SCCMConfig.DAL.SCCMProber.Detect()

                   at SCCMConfig.Actions.ActionPerformer.Detect()

                   at Intel.SCS.ACIWizard.ViewModel.WelcomeViewModel.<Init>b__1()

                • 5. Re: SCS Add-on for SCCM install won't let me choose SCCM2012
                  Polen


                  Since the SCS Add-on does not work, can you please provide the configuration_IntelSCS8_iAMT.mof file that we need to manually configure SCS with SCCM as instructed in this blog.

                   

                  Blair Muller's Blog: Integrating SCCM 2012 with SCS 8.1

                   

                  Also, how is the sms_def.mof edited?

                   

                   

                  Thanks,

                   

                  Greg Polen

                  Texas A&M University

                  • 6. Re: SCS Add-on for SCCM install won't let me choose SCCM2012
                    Alan Alderson

                    Greg,

                    We should have a new version of the SCS Add-on available by next week.

                     

                    -Alan

                    • 7. Re: SCS Add-on for SCCM install won't let me choose SCCM2012

                      Any word on when the new version will be available?

                      • 8. Re: SCS Add-on for SCCM install won't let me choose SCCM2012
                        Alan Alderson

                        Unfortunately, there has been a slight delay with the release of the new SCS Add-on. As of now there isn't a firm date for release.

                        There is another option if you’re not able to wait for the new Add-on. You can manually integrate SCS using the instructions located here.

                        https://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=21696

                        • 9. Re: SCS Add-on for SCCM install won't let me choose SCCM2012

                          Alan,

                          Could you give us an estimate on how long until the patch is released?

                          • 10. Re: SCS Add-on for SCCM install won't let me choose SCCM2012
                            Alan Alderson

                            Ryan,

                             

                            A new Intel SCS Add-on has been released.

                             

                            Download Center

                             

                            -Alan

                            • 11. Re: SCS Add-on for SCCM install won't let me choose SCCM2012
                              aurock

                              The new version installed without any further issues, but now that I've got the discover task sequence enabled and deployed, it's failing on all clients.  Looking in the smsts.log, I see several error messages with an 0x80004005 code at the end, which I believe means access denied.  

                               

                              Does anyone know of something simple I might have overlooked which would cause this issue?

                              • 12. Re: SCS Add-on for SCCM install won't let me choose SCCM2012
                                Alan Alderson

                                Check that the task sequence user is a local admin.

                                • 13. Re: SCS Add-on for SCCM install won't let me choose SCCM2012
                                  aurock

                                  I believe the task sequence executes under the SCCM server's computer account, which does have local admin rights on our systems.  I also added the new AMT Admin account that I created and used when setting up the profile in SCS, just in case.

                                   

                                  I did make a little progress last night... I edited the "Intel AMT Discover and Report" task sequence, removing the quotation marks from the command line.  That got the batch file to run, but I'm hitting an error towards the end.  It looks like the task sequence is working now, but ACUConfig is running into issues.  It's tough to grab the "Remote_SystemDiscovery.log" file since it's deleted as soon as the task sequence finishes, but I got a copy pretty close to the end:

                                   

                                  Remote_SystemDiscovery.log

                                  2013-08-15 09:17:35: Thread:6004(INFO) : ACU Configurator , Category: HandleOutPut Source: Src\ActivatorUtils.cpp : HandleOutput Line: 210: Starting log 2013-08-15 09:17:35

                                  2013-08-15 09:17:35: Thread:6004(DETAIL) : ACU Configurator, Category: VerifyFileSignature Source: Src\ActivatorMain.cpp : wmain Line: 122: Verifying the digital signature of ACU.dll, this operation might take up to 3 minutes...

                                  2013-08-15 09:17:35: Thread:6004(INFO) : ACU Configurator , Category: VerifyFileSignature Source: Src\ActivatorUtilsWin.cpp : VerifyFileSignature Line: 457: The file "C:\_SMSTaskSequence\Packages\XYZ0006D\ACU.dll" is signed and the signature was verified.

                                  2013-08-15 09:17:35: Thread:6004(DETAIL) : ACU.dll, Category: SetCompatibilityMode Source: Src\ActivatorDll.cpp : SetCompatibilityMode Line: 104: Set compatibility mode to 8.0.

                                  2013-08-15 09:17:35: Thread:6004(INFO) : ACU Configurator, Category: -SystemDiscovery- Source: Src\ActivatorMain.cpp : wmain Line: 311: computer.domain.com: Discovering the System information...

                                  2013-08-15 09:17:35: Thread:6004(DETAIL) : ACU Configurator , Category: -Start- Source: Src\ActivatorDllWin.cpp : SystemDiscovery Line: 51: ***** Start SystemDiscovery ******

                                  2013-08-15 09:17:35: Thread:6004(DETAIL) : ACU Configurator , Category: -Start- Source: Src\HECIDiscovery.cpp : HeciDiscovery Line: 467: ***** Start HeciDiscovery ******

                                  2013-08-15 09:17:35: Thread:6004(DETAIL) : ACU Configurator , Category: -Start- Source: Src\HECIDiscovery.cpp : CheckAMT Line: 78: ***** Start CheckAMT ******

                                  2013-08-15 09:17:35: Thread:6004(DETAIL) : ACU Configurator , Category: -HECI- Source: Src\HECIWin.cpp : HECIWin::Init Line: 185: Connected to the Intel(R) Management Engine Interface driver, version 7.1.70.1198

                                  2013-08-15 09:17:35: Thread:6004(DETAIL) : ACU Configurator , Category: -Start- Source: Src\HECIDiscovery.cpp : FWUpdateData Line: 40: ***** Start FWUpdateData ******

                                  2013-08-15 09:17:35: Thread:6004(DETAIL) : ACU Configurator , Category: -END- Source: Src\HECIDiscovery.cpp : FWUpdateData Line: 61: ***** END FWUpdateData ******

                                  2013-08-15 09:17:35: Thread:6004(INFO) : ACU Configurator , Category: AMT Mode Source: Src\HECIDiscovery.cpp : CheckAMT Line: 382: Intel(R) AMT  in PROVISIONING_MODE_ENTERPRISE

                                  2013-08-15 09:17:35: Thread:6004(DETAIL) : ACU Configurator , Category: -END- Source: Src\HECIDiscovery.cpp : CheckAMT Line: 461: ***** END CheckAMT ******

                                  2013-08-15 09:17:35: Thread:6004(DETAIL) : ACU Configurator , Category: -HECI- Source: Src\HECIWin.cpp : HECIWin::Init Line: 185: Connected to the Intel(R) Management Engine Interface driver, version 7.1.70.1198

                                  2013-08-15 09:17:35: Thread:6004(DETAIL) : ACU Configurator , Category: -Start- Source: Src\HECIDiscovery.cpp : FWUpdateData Line: 40: ***** Start FWUpdateData ******

                                  2013-08-15 09:17:35: Thread:6004(DETAIL) : ACU Configurator , Category: -END- Source: Src\HECIDiscovery.cpp : FWUpdateData Line: 61: ***** END FWUpdateData ******

                                  2013-08-15 09:17:40: Thread:6004(DETAIL) : ACU Configurator , Category: -Start- Source: Src\HECIDiscovery.cpp : PKIDiscovery Line: 790: ***** Start PKIDiscovery ******

                                  2013-08-15 09:17:40: Thread:6004(DETAIL) : ACU Configurator , Category: Hash Handle Source: Src\HECIDiscovery.cpp : GetPKIHashes Line: 873: Hash Handles number:15

                                  2013-08-15 09:17:40: Thread:6004(DETAIL) : ACU Configurator , Category: -END- Source: Src\HECIDiscovery.cpp : PKIDiscovery Line: 837: ***** END PKIDiscovery ******

                                  2013-08-15 09:17:40: Thread:6004(DETAIL) : ACU Configurator , Category: -Start- Source: Src\HECIDiscovery.cpp : GetAmtFQDN Line: 1256: ***** Start GetAmtFQDN ******

                                  2013-08-15 09:17:40: Thread:6004(DETAIL) : ACU Configurator , Category: -END- Source: Src\HECIDiscovery.cpp : GetAmtFQDN Line: 1333: ***** END GetAmtFQDN ******

                                  2013-08-15 09:17:40: Thread:6004(DETAIL) : ACU Configurator , Category: -Start- Source: Src\HECIDiscovery.cpp : ConfServerDiscovery Line: 1021: ***** Start ConfServerDiscovery ******

                                  2013-08-15 09:17:40: Thread:6004(DETAIL) : ACU Configurator , Category: Status message Source: Src\HECIDiscovery.cpp : ConfServerDiscovery Line: 1082: Error message not found- 0x80008cd9. (0x80008cd9)

                                  2013-08-15 09:17:40: Thread:6004(DETAIL) : ACU Configurator , Category: -END- Source: Src\HECIDiscovery.cpp : ConfServerDiscovery Line: 1095: ***** END ConfServerDiscovery ******

                                  2013-08-15 09:17:40: Thread:6004(DETAIL) : ACU Configurator , Category: GetPID Source: Src\HECIDiscovery.cpp : HeciDiscovery Line: 715: AMT Status code - Invalid AMT mode. (0xc000426b) (GetPID)

                                  2013-08-15 09:17:40: Thread:6004(DETAIL) : ACU Configurator , Category: -Start- Source: Src\HECIDiscovery.cpp : ReInitPTHI Line: 1449: ***** Start ReInitPTHI ******

                                  2013-08-15 09:17:45: Thread:6004(DETAIL) : ACU Configurator , Category: -HECI- Source: Src\HECIWin.cpp : HECIWin::Init Line: 185: Connected to the Intel(R) Management Engine Interface driver, version 7.1.70.1198

                                  2013-08-15 09:17:45: Thread:6004(DETAIL) : ACU Configurator , Category: -Start- Source: Src\HECIDiscovery.cpp : LMSDiscovery Line: 1102: ***** Start LMSDiscovery ******

                                  2013-08-15 09:17:45: Thread:6004(INFO) : ACU Configurator , Category: Discovery Source: Src\HostBasedSetup.cpp : HostBasedSetup::Discovery Line: 410: Calling function Discovery...

                                  2013-08-15 09:17:45: Thread:6004(INFO) : ACU Configurator , Category: Local System Account Source: Src\HostBasedSetup.cpp : HostBasedSetup::GetLocalSystemAccount Line: 199: Calling function GetLocalSystemAccount over MEI...

                                  2013-08-15 09:17:45: Thread:6004(DETAIL) : ACU Configurator , Category: -HECI- Source: Src\HECIWin.cpp : HECIWin::Init Line: 185: Connected to the Intel(R) Management Engine Interface driver, version 7.1.70.1198

                                  2013-08-15 09:17:45: Thread:6004(INFO) : ACU Configurator , Category: Local System Account Source: Src\HostBasedSetup.cpp : HostBasedSetup::GetLocalSystemAccount Line: 233: Function GetLocalSystemAccount over MEI ended successfully

                                  2013-08-15 09:17:46: Thread:6004(INFO) : ACU Configurator , Category: Discovery Source: Src\HostBasedSetup.cpp : HostBasedSetup::Discovery Line: 454: Host Based Setup is supported

                                  2013-08-15 09:17:46: Thread:6004(INFO) : ACU Configurator , Category: Discovery Source: Src\HostBasedSetup.cpp : HostBasedSetup::Discovery Line: 484: Current Control Mode: 0 (Not provisioned)

                                  2013-08-15 09:17:46: Thread:6004(INFO) : ACU Configurator , Category: Discovery Source: Src\HostBasedSetup.cpp : HostBasedSetup::Discovery Line: 523: Allowed Control Modes: 2 (Admin) and  1 (Client)

                                  2013-08-15 09:17:46: Thread:6004(INFO) : ACU Configurator , Category: Discovery Source: Src\HostBasedSetup.cpp : HostBasedSetup::Discovery Line: 527: Function Discovery ended successfully

                                  2013-08-15 09:17:46: Thread:6004(DETAIL) : ACU Configurator , Category: -END- Source: Src\HECIDiscovery.cpp : LMSDiscovery Line: 1175: ***** END LMSDiscovery ******

                                  2013-08-15 09:17:46: Thread:6004(DETAIL) : ACU Configurator , Category: -Start- Source: Src\HECIDiscovery.cpp : SecurityDiscovery Line: 1192: ***** Start SecurityDiscovery ******

                                  2013-08-15 09:17:46: Thread:6004(DETAIL) : ACU Configurator , Category: -END- Source: Src\HECIDiscovery.cpp : SecurityDiscovery Line: 1218: ***** END SecurityDiscovery ******

                                  2013-08-15 09:17:46: Thread:6004(DETAIL) : ACU Configurator , Category: -Start- Source: Src\HECIDiscovery.cpp : FeaturesDiscovery Line: 1235: ***** Start FeaturesDiscovery ******

                                  2013-08-15 09:17:46: Thread:6004(DETAIL) : ACU Configurator , Category: -END- Source: Src\HECIDiscovery.cpp : FeaturesDiscovery Line: 1250: ***** END FeaturesDiscovery ******

                                  2013-08-15 09:17:46: Thread:6004(DETAIL) : ACU Configurator , Category: -Start- Source: Src\HECIDiscovery.cpp : UuidDiscovery Line: 1339: ***** Start UuidDiscovery ******

                                  2013-08-15 09:17:46: Thread:6004(DETAIL) : ACU Configurator , Category: -END- Source: Src\HECIDiscovery.cpp : UuidDiscovery Line: 1352: ***** END UuidDiscovery ******

                                  2013-08-15 09:17:46: Thread:6004(DETAIL) : ACU Configurator , Category: -Start- Source: Src\HECIDiscovery.cpp : TcpIpDiscovery Line: 1358: ***** Start TcpIpDiscovery ******

                                  2013-08-15 09:17:46: Thread:6004(DETAIL) : ACU Configurator , Category: -END- Source: Src\HECIDiscovery.cpp : TcpIpDiscovery Line: 1443: ***** END TcpIpDiscovery ******

                                  2013-08-15 09:17:46: Thread:6004(DETAIL) : ACU Configurator , Category: -END- Source: Src\HECIDiscovery.cpp : HeciDiscovery Line: 773: ***** END HeciDiscovery ******

                                  2013-08-15 09:17:46: Thread:6004(DETAIL) : ACU Configurator , Category: GetDNSLookupName Source: Src\SystemDiscovery.cpp : MachineDataOp::FullDiscovery Line: 188: Failed to get the FQDN. (0xc0002823) (GetDNSLookupName)

                                   

                                   

                                  Based on the documentation for the Add-On, I expected the Intel AMT Discovery and Report task sequence to go out and find systems that support AMT and populate the appropriate device collections on the SCCM server.  Then the Intel AMT Remote Configuration task sequence would run on all of the AMT Compatible systems where AMT is not configured.  However, I have just came across another thread in which your posts seem to indicate that my understanding is not be correct: http://communities.intel.com/thread/42824

                                   

                                  Now I'm just confused. 

                                  1 2 Previous Next