6 Replies Latest reply on Aug 30, 2018 11:27 AM by ggrassart

    Ivanti EPM 2017.X and 2018.X Provisioning Issues

    tsujared Apprentice

      has anyone else had the issue when performing provisioning tasks even though the task box is unchecked where it says to stop if task fails, the task fails and the provisioning stops. I then have to relaunch the ldprovision.exe to get it to continue. sometimes the tasks just stop responding and I have to reboot and relaunch ldprovision to get it to finish. This has been an ongoing problem since 2017.1. No one seems to really have an answer. It seems as if the connection from the task to the computer just stops. It is random. It is not always the same task. Surely this is working as designed?

       

      2018-08-20_161447.jpg

      2018-08-20_161832.jpg

        • 1. Re: Ivanti EPM 2017.X and 2018.X Provisioning Issues
          phoffmann SupportEmployee

          Actually - the relationship is the other way around. It's not so much "Task => Computer" but "Computer => Task".

           

          Basically "LDprovision" loads up, and contacts the Core (/tries to) and goes "Hey, what is there for me".

           

          The fact that (re-)launching LDPROVISION works, indicates that the Core is keeping track of "where the client is" just fine.

           

          My personal experience / expectation in similar situations tends to be "iffy DNS" / similar networking based problems. The other option is that IIS / the app-pool on your Core is struggling with responding / picking up the request and passing it on to the DB.

           

          In effect usually the scenario is something like this:

          • Client powers up (at some point in the provisioning process) ... as usual
          • ... client tries to reach the Core ...
            • ... client then either CAN'T reach the Core (DNS / networking problem)
            • ... or the client CAN reach the Core, but IIS doesn't send the request on to the DB due to it having issues (usually seen as 503-s in the IIS log).

           

          Check your IIS log when you have this problem to see...

          • ... whether your client HAS reached the Core successfully ...
          • ... whether IIS has had issues in handling the request.

           

          ... a basic process flow & "how to read IIS logs" can be found as part of a webinar here -- [Tech Brief On-Demand Webinar 2016] Provisioning with LANDESK Management Suite .

           

          This is usually "infrastructure" problems (either networking (most common) and/or IIS-related (so resourcing, etc) ).

          1 of 1 people found this helpful
          • 2. Re: Ivanti EPM 2017.X and 2018.X Provisioning Issues
            ggrassart Apprentice

            Is it a windows  10 imaging? do you use Autologon?

             

            are you sure windows don't use OEM licence  and not kms licence?  

             

            in your oobesession of unattend  do you have  :

            SkipMachineOOBE>true</SkipMachineOOBE>   

                            <SkipUserOOBE>true</SkipUserOOBE>

                        </OOBE>

            ?

            is the problem is present on specific device or not ?

            • 3. Re: Ivanti EPM 2017.X and 2018.X Provisioning Issues
              tsujared Apprentice

              ggrassart this is our oobe. i remove the passwords for obvious reasons

               

              <OOBE>

                              <HideEULAPage>true</HideEULAPage>

                              <ProtectYourPC>3</ProtectYourPC>

                          </OOBE>

                          <UserAccounts>

                              <AdministratorPassword>

                                  <Value></Value>

                                  <PlainText>false</PlainText>

                              </AdministratorPassword>

                          </UserAccounts>

                          <AutoLogon>

                              <Password>

                                  <Value></Value>

                                  <PlainText>false</PlainText>

                              </Password>

                              <Username>administrator</Username>

                              <Enabled>true</Enabled>

                              <LogonCount>3</LogonCount>

                          </AutoLogon>

                      </component>

              • 4. Re: Ivanti EPM 2017.X and 2018.X Provisioning Issues
                ggrassart Apprentice

                Add in your oobe

                <skipuseroobe>true</skipuseroobe>

                <skipmachineoobe>true</skipmachineoobe>

                 

                And retry

                I think it can solve your issue

                • 5. Re: Ivanti EPM 2017.X and 2018.X Provisioning Issues
                  tsujared Apprentice

                  but we dont want to skip oobe completely we use some things in there.

                  • 6. Re: Ivanti EPM 2017.X and 2018.X Provisioning Issues
                    ggrassart Apprentice

                    You can set the settings.

                     

                    If you have configured oobe in your unattend e. Settings they will  be set correctly

                     

                    make the test And compare.