That means when HIIClient.exe asks WinPE what devices are connected, WinPE will not return information about the USB3 hub or eXtensible host controller. The USB3.0 bus is not visible to WinPE by default because WinPE does not have a USB3.0 controller driver by default. However, the Root Hub and eXtensible host controller devices are not on the PCI bus they are on a separate USB3.0 bus. HIIClient can see it and choose a driver for it. The USB3.0 controller is connected to and available on the PCI bus, which is visible to the WinPE OS. It contains a USB controller, a USB3.0 Root Hub, and, for Intel devices, an eXtensible host controller. LDMS console, HII Driver library and boot.wim image files. Note that server and network names are changed. However I doubt that directly as first action after a reboot. Only thing I can think of is that LANDesk is busy with the deployment and can not take the certificate request at this time. Maybe somebody here knows about this error code?Įrror code 322 is misleading I guess since it states ERROR_DEVICE_NO_RESOURCES (The target device has insufficient resources to complete the operation). "%programfiles(x86)%\landesk\ldclient\brokerconfig.exe" -rġ2:32:17 BrokerConfig Started with 1st param: no paramsġ3:23:03 BrokerConfig Started with 1st param: -rġ3:23:03 PostCertificate() posting cert to host, proxyġ3:23:03 PostCertificate() StartSession returned 0ġ3:23:03 PostCertificate() request returned 0ġ3:23:03 PostCertificate() Write returned 0ġ3:23:03 PostCertificate() Response returned 0, status of 202ġ3:28:03 GetCertificate() File did not appear after 300 secondsġ3:41:00 BrokerConfig Started with 1st param: no paramsĬ:\Program Files (x86)\LANDesk\LDClient\sdmcache\deploy\DSL\LDMS Gateway>call "get CSA Certificate.bat"ġ3:28:04 RunPackageInstall: stop on returncode=8db5002d of package=Get CSA Certificateġ3:28:04 processing of package is complete, result -1917517779 (0x8db5002d - code 45)ġ2:07:02 RunPackageInstall: stop on returncode=8db50142 of package=Get CSA Certificateġ2:07:02 processing of package is complete, result -1917517502 (0x8db50142 - code 322)Įrror code 45 seems not to be present in Windows (see System Error Codes (0-499) (Windows) ) or in LANDesk error codes list.ĨDB5002D seems not to be known either and surpisingly even the all knowing Google failed me this time. Target: %%programfiles(x86)%%\landesk\ldclient\brokerconfig.exe PS: Hopefully that is the last problem I discover after upgrading to 9.6 SP 2.Ģ - Distribute Software in System Configurationģ - Distribute Software in System ConfigurationĪfter installing the provisioning agent and reboot.Īfter installing the final agent and 120s wait, batchfile.Īs last action after rebooting the device, batchfile. Is there another simple method to supply a machine with the gateway certificate in os deployment? Just the os deployment action seems to fail in every case. Our devices should be deployed ready to go, this includes the gateway (CSA) certificate.Ī scheduled package or manually execution of BrokerConfig.exe -r works flawlessly.Įven if you just open a command line and enter brokerconfig.exe -r it works. You already pointed me in the right direction a few times so I hope you can help me one more time. Is it possible I missed something in the serverconfig.Hello LANDesk Community and administrators, If it's a requirement I may need to play around with NAT some since there's another process using 8080 on my system so I remapped it to 8085 Telnet makes the IT geek in me have seizures and there's no reason that I know of to open the web panel unless it's a requirement. I haven't opened up the web server and I disabled telnet. I was also looking at a netstat output, I can see 26900 TCP and 2900-26902 UDP as open listening ports, but I didn't see any others that were in the port range for 7DTD nor did I see any strange ports associated with a 7DTD process tree. This will help narrow things down a bit but it will take me some time to diagnose it (Maybe run some TCP dumps to see what inbound packets are hitting it) I think my next step is going to be to put the system into a DMZ so that it's directly exposed to the internet without NAT. I followed the link and opened ports pretty liberally, however it's still not working
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |