5 Replies Latest reply on Oct 29, 2016 2:48 PM by antaniojuan

    Call for DSM 2016.2 Beta participants

    Pedator Apprentice

      Hello,

       

      as testing on DSM 2016.2 has already started, planning the Beta (ETA end of October) is on my agenda.

      If you did not take part for DSM 2016.1 time but want to do so this time, please contact me so I can add you to the list of participants.

       

      Best regards

      Peter

        • 1. Re: Call for DSM 2016.2 Beta participants
          wardclerk Rookie

          Peter,

          Drooling for the pending beta here.  Chance of this week?

          • 2. Re: Call for DSM 2016.2 Beta participants
            Pedator Apprentice

            Hello Tyler,

             

            absolutely! Some partners already got a build on tuesday (containing known issues that are fixed meanwhile) - no negative feedback so far.

            The Beta will be made available for participating customers on Oct 28th.

             

            Best regards

            Peter

            • 3. Re: Call for DSM 2016.2 Beta participants
              Pedator Apprentice

              Hello,

               

              for all BETA participants, please note that with DSM 2016.2 the SQL Server 2005 is no longer supported.

              That means that before the update to the new version is started, the SQL server has to be updated to SQL Server 2008 or higher.

               

              Thank you!

              Peter

              • 4. Re: Call for DSM 2016.2 Beta participants
                marc.manz Rookie

                Hi,

                in the current Beta build (3628) we have found an issue on the update/installation of DSM with the new HEAT Remote. The SSI scripts required for the HEAT Remote installation aren't copied from the ISO to the share. To solve this issues manually, you have to copy the following directories from the ISO Remote\SSI directory to \\<server>\<share>\SSI and \\<server>\<share>\UpdateSources\SSI on a new installation (or the update is already done), on a update before the depot packages are created, it is enough to copy it to \\<server>\<share>\UpdateSources\SSI:

                 

                <cd_drive>:\Remote\SSI\{391D961F-139F-42F0-8053-9683B4207B49}

                <cd_drive>:\Remote\SSI\{C5483F13-3996-459C-8D9B-305A20BC69CD}

                <cd_drive>:\Remote\SSI\Remote.AdminWSExt

                <cd_drive>:\Remote\SSI\Remote.Integrator

                 

                Additionally you have to copy

                 

                "<cd_drive>:\Remote\AddOns\xhlpRemote.dll"

                ">cd_drive>:\Remote\AddOns\xniRemote.dll"

                 

                to \\<server>\<share>\addons and \\<server>\<share>\UpdateSources\addons on a new installation (or the update is already done), on a update before the depot packages are created, it is enough to copy it to \\<server>\<share>\UpdateSources\SSI:

                 

                If there are any questions reply to this.

                 

                Marc