2 Replies Latest reply on Aug 16, 2017 1:06 AM by RZimmer

    OSD Self-Service sometimes not working

    RZimmer Apprentice

      Hello all!

       

      I am currently setting up our new DSM environment along with OSD Self-Service Packages.

      Everything is working fine, except for the Self-Service menu. Sometimes it is called after WinPE load and sometimes not.

       

      Having a look into Client Proxy logs, I have noticed that this only happens, if the Client Service on the secondary BLS is being contacted.

      Here a cutout from the log where it is not working:

      16:18.47.880  2 ClientProxy.dll  Starting Procedure: Get next task
      16:18.47.880  2 ClientProxy.dll  Parameter 'client ID': 1407
      16:18.47.880  2 ClientProxy.dll  Parameter 'action ID': 0
      16:18.47.880  2 ClientProxy.dll  Parameter 'task type': 0 (unknown)
      16:18.47.880  2 ClientProxy.dll  Parameter 'task status': 0 {OK}
      16:18.47.880  2 ClientProxy.dll  Parameter 'task message': 
      16:18.47.880  2 ClientProxy.dll  Parameter 'Platform Bitmask': 80000000
      16:18.47.880  2 ClientProxy.dll  Parameter 'Native Bitmask': 200000
      16:18.47.897  2  CMSClntLib.dll          Calling 'http://B001CVS000219:8080/blsClientManagement/ClientService.svc/Sync?qos=20'
      16:18.48.083  2  CMSClntLib.dll          Webservice call suceeded with status code 200
      16:18.48.094  2 ClientProxy.dll        Result 'activated for installation': yes
      16:18.48.104  2 ClientProxy.dll          Software Package WinPE 4 / 5 / 10 (64 Bit) Boot Environment (BootEnvironmentPackage.1115) will be treated as a pilot installation.
      16:18.48.116  2 ClientProxy.dll          Create NWCM login for depot server with ID 66069 - result-status 0 {OK}.
      16:18.48.154  2         FPS.dll          File package is opened.
      16:18.48.155  2         FPS.dll          Closing the file package '\\?\C:\Program Files (x86)\Common Files\enteo\RepositoryCache\1115\rev\1\'.
      16:18.48.162  2 ClientProxy.dll          Create NWCM login for depot server with ID 66069 - result-status 0 {OK}.
      16:18.48.173  2         FPS.dll          File package is opened.
      16:18.48.173  2         FPS.dll          Closing the file package '\\?\C:\Program Files (x86)\Common Files\enteo\RepositoryCache\711\rev\1\'.
      16:18.48.180  2 ClientProxy.dll    Resolved Client: '1407' "{3B6B88CF-C444-954A-93A6-C99847E2AF18}" [id:1407;ip4:10.1.124.107;smbios:{3B6B88CF-C444-954A-93A6-C99847E2AF18};UEFI]
      16:18.48.184  2 ClientProxy.dll  Result 'action ID': 3834317868
      16:18.48.184  2 ClientProxy.dll  Result 'task type': 3 (basic inventory)
      16:18.48.184  2 ClientProxy.dll  Result 'task parameters': 
      16:18.48.184  2 ClientProxy.dll  Result Status: 0 {OK}
      16:18.48.184  2 ClientProxy.dll  Finished Procedure: Get next task
      16:18.48.185  : End Of Logfile
      

       

      And here where it is working if the Primary BLS is being contacted:

      16:09.05.599  2 ClientProxy.dll  Starting Procedure: Get next task
      16:09.05.599  2 ClientProxy.dll  Parameter 'client ID': 1370
      16:09.05.599  2 ClientProxy.dll  Parameter 'action ID': 0
      16:09.05.599  2 ClientProxy.dll  Parameter 'task type': 0 (unknown)
      16:09.05.599  2 ClientProxy.dll  Parameter 'task status': 0 {OK}
      16:09.05.599  2 ClientProxy.dll  Parameter 'task message': 
      16:09.05.599  2 ClientProxy.dll  Parameter 'Platform Bitmask': 80000000
      16:09.05.599  2 ClientProxy.dll  Parameter 'Native Bitmask': 200000
      16:09.05.616  2  CMSClntLib.dll          Calling 'http://B001CVS000218:8080/blsClientManagement/ClientService.svc/Sync?qos=20'
      16:09.05.731  2  CMSClntLib.dll          Webservice call suceeded with status code 200
      16:09.05.742  2 ClientProxy.dll        Result 'activated for installation': yes
      16:09.05.753  2 ClientProxy.dll    Resolved Client: '1370' "{3B6B88CF-C444-954A-93A6-C99847E2AF18}" [id:1370;ip4:10.1.124.107;smbios:{3B6B88CF-C444-954A-93A6-C99847E2AF18};UEFI]
      16:09.05.758  2 ClientProxy.dll      Software Package WinPE 4 / 5 / 10 (64 Bit) Boot Environment (BootEnvironmentPackage.1115) will be treated as a pilot installation.
      16:09.05.770  2 ClientProxy.dll      Create NWCM login for depot server with ID 66069 - result-status 0 {OK}.
      16:09.05.805  2         FPS.dll      File package is opened.
      16:09.05.805  2         FPS.dll      Closing the file package '\\?\C:\Program Files (x86)\Common Files\enteo\RepositoryCache\1115\rev\1\'.
      16:09.05.812  2 ClientProxy.dll      Software Package Self Service (PreOSActionPackage.1243) will be treated as a pilot installation.
      16:09.05.812  2 ClientProxy.dll      Create NWCM login for depot server with ID 66069 - result-status 0 {OK}.
      16:09.05.839  2         FPS.dll      File package is opened.
      16:09.05.839  2         FPS.dll      Closing the file package '\\?\C:\Program Files (x86)\Common Files\enteo\RepositoryCache\1243\rev\1\'.
      16:09.05.846  2 ClientProxy.dll  Result 'action ID': 2137255054
      16:09.05.846  2 ClientProxy.dll  Result 'task type': 3 (basic inventory)
      16:09.05.846  2 ClientProxy.dll  Result 'task parameters': 
      16:09.05.846  2 ClientProxy.dll  Result Status: 0 {OK}
      16:09.05.846  2 ClientProxy.dll  Finished Procedure: Get next task
      16:09.05.847  : End Of Logfile
      

       

      I have already cleared caches of all OSD Proxies, but I get the same result.

       

      EDIT: after a few more tries I have noticed that it doesn't matter which BLS is being contacted.

      Self-Service Package is assigned as variable on the designated OU. Problem persists: sometimes OSD Self Service is being called, sometimes not.

       

      Am I missing something here? I have no clue where else to look.

       

      Regards,

      Raimund

        • 1. Re: OSD Self-Service sometimes not working
          _Mel_ Master

          what happens if it's not called ? is another package executed ? - that's normal, as regular OSD policies have priority over self service

           

          if you don't have multiple self service packages, this would explain why there are different packages used (ID 711 if the first logfile and ID 1243 in the second logfile)

           

          you can get more logging by changing in the registry on the osd proxy in the key

          HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NetSupport\ExtendedLogfileSettings\ClientProxyRpc

          the Value "getNextTask" to 0

          ...changing the "(Default)" value to "0" will enable debug logging for all functions

          1 of 1 people found this helpful
          • 2. Re: OSD Self-Service sometimes not working
            RZimmer Apprentice

            setting "getNextTask" to 0 helped to find the problem. Thanks Mel

             

            I have noticed in Client Proxy Log that the scheme extension for Operation System was already set, which caused the assignment of Win 10 to the client, thus eliminating the self service capability due to

            a lower priority of the self service package. Explains why it is always called once the operating system is installed.

            Reverting default value for scheme extension to nothing and self service is called again.

             

            Thanks again for the advice