3 Replies Latest reply on Apr 7, 2016 8:10 AM by frgpugs

    Patch Manager showing Error

    ishant_walia

      Hi All,

           I was trying to add a computer in Patch manager but while adding it has been giving error again and again . Please check the error details mentioned below.

       

      "The following attempts were made:

       

       

      ARP Resolution result: No

      DNS Resolution result: Yes

      NETBIOS Name Resolution: Yes

      MS Endpoint Mapper: No

      WMI Connection: No

       

       

      EminentWare Provider Connection: No

       

       

      File and Print Sharing Ports: No

      Unable to connect to the NetBIOS (139) or NetBIOS over TCP/IP direct hosting (445) ports on WIN-6KKBOB40CTS and provisioning of the EminentWare provider requires the 'File and Print Sharing' exception to be enabled."

       

       

      Please provide solution for this.

       

      Regards,

      Ishant Walia

        • Re: Patch Manager showing Error
          frgpugs

          It looks like you have an OSD deployment computer you are trying to add?

          Did you add the client components WMI providers?  I imagine its because its not connected to your domain so theres no DNS record for that hostname 

            • Re: Patch Manager showing Error
              ishant_walia

              Please suggest what should i do?

                • Re: Patch Manager showing Error
                  frgpugs

                  well it depends if you have SCCM or just using MDT.  Integrating WSUS into MDT is a little tricky.

                   

                  You need to add an entry for a target group in your customsettings.ini.  Mine is like this

                  [Settings]

                  Priority=Default

                  Properties=Target Group

                   

                  [Default]

                  TargetGroup=MDT

                   

                   

                  Then create a task variable in your task sequence for the target group

                   

                  Then you need to edit ZTIwindowsupdate.wsf that is in your deployment share/scripts folder to add in the target group.

                  Add the following code

                   

                  If oEnvironment.Item("TargetGroup "" then
                  oShell.RegWrite "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\TargetGroup", oEnvironment.Item("TargetGroupREG_SZ"
                  oShell.RegWrite "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\TargetGroupEnabled", 1, "REG_DWORD"

                  End if

                   

                   

                  So in the end it will look like this

                   

                   

                   

                  '//----------------------------------------------------------------------------

                  '// Configure Windows Update settings

                  '//----------------------------------------------------------------------------

                   

                  If oEnvironment.Item("WsusServer "" then

                   

                    ' Configure the WSUS server in the registry. This needs to be a URL (e.g. http://myserver).

                   

                    oLogging.CreateEntry "Configuring client to use WSUS server " & oEnvironment.Item("WsusServerogTypeInfo

                   

                    oShell.RegWrite "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\WUServer", oEnvironment.Item("WsusServerREG_SZ"

                    oShell.RegWrite "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\WUStatusServer", oEnvironment.Item("WsusServerREG_SZ"

                   

                    If oEnvironment.Item("TargetGroup "" then

                    oShell.RegWrite "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\TargetGroup", oEnvironment.Item("TargetGroupREG_SZ"

                    oShell.RegWrite "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\TargetGroupEnabled", 1, "REG_DWORD"

                    End if

                   

                  End if

                   

                   

                   

                  You need to make sure that your WSUS server (not patch manager) is set to receive settings from registry or AD and not the console.  I dont remember offhand where that setting is at right now but im sure you can find it or google it.

                   

                  I have my cs.ini set to join the domain and put it in a prestaged MDT OU so when i apply group policy i get the Solarwinds Client Components.  The problem I ran into is that I did not want to change my PCs to use registry or AD, I wanted to still use the console and have PCs added to unassigned in patch manager, so i created a pause step in my task sequence so I can open up patch manager and move it to the group.  Either way, it does work, i just ended up not automatically moving it into the group even though i set it all up for it.

                   

                  I know this is more than you wanted, but since it took me awhile to figure it out i thought i would share since it is likely your intention to do the same thing.  The main thing is adding in the client components by either injecting as an application or joining the domain in MDT and using group policy.  Here is the settings in my CS.ini that does it

                   

                  4-7-2016 7-59-22 AM.jpg

                   

                  ts.jpg