I've got a serious problem with my newly rolled out Vista machines. It seems that after some period of time, the brokerconfig certificate becomes invalid, or stops working for some reason. We currently use the ISO, but we'll be changing to the appliance within a few weeks (and I'm going to have to figure out how to get the new certs onto machines that are nowhere near my office, much less in my state--grr).
In any case. here's the log when I hit test on one of these machines with brokerconfig:
09:40.362 Attempting Direct HTTP connection to host <core FQDN>:80
09:40.362 Starting HTTP session with host <core FQDN>:80, proxy "", and proxy user ""
09:40.396 Unable to resolve host <core FQDN> address 255.255.255.255
09:40.396 Direct connection failed 6 Name resolution error
09:40.396 Using certificate file C:\Program Files\LANDesk\Shared Files\cbaroot\broker\broker.crt and keyfile C:\Program Files\LANDesk\Shared Files\cbaroot\broker\broker.key
09:40.397 Certificate/key loaded. Certificate file "C:\Program Files\LANDesk\Shared Files\cbaroot\broker\broker.crt". Key file "C:\Program Files\LANDesk\Shared Files\cbaroot\broker\broker.key"
09:40.397 Attempting managment gateway connection at host and address <LDMG FQDN>
09:40.397 Starting HTTPS session with host <LDMG FQDN>, proxy "", and proxy user ""
09:40.397 Connecting to address <LDMG IP>
09:40.862 Waiting for link connection to core through managment gateway
09:40.862 Begining link request
09:40.862 HTTPS Request: POST /services/link
09:40.862 Waiting for match response
09:40.862 Waiting for HTTPS response
09:40.949 HTTPS response finished status 201 description Created
09:40.949 Creating session from client computer through managment gateway to core computer
09:41.027 Starting long session client
09:41.190 Match request completed 0 Success
09:41.190 Link to core successful
09:41.190 HTTPS Request: POST /landesk/managementsuite/core/RemoteControlLogging/RemoteControlLog.asmx
09:41.190 Waiting for HTTPS response
09:41.213 Error 4 Closed reading response line
Checking the brokerconfig log on one of them, I see:
Tue, 24 Mar 2009 11:32:28 PostCertificate() posting cert to host <core FQDN>, proxy
Tue, 24 Mar 2009 11:32:28 PostCertificate() StartSession returned 6
Tue, 24 Mar 2009 11:32:28 PostSoapRequest() Starting with host <core FQDN>, user <core>\<username>
Tue, 24 Mar 2009 11:32:28 PostSoapRequest() StartSession returned 0
Tue, 24 Mar 2009 11:32:28 PostSoapRequest() Request returned 0
Tue, 24 Mar 2009 11:32:28 PostSoapRequest() Write returned 0
Tue, 24 Mar 2009 11:32:30 ReadSoapResponseToFile() StartSession returned 0, and status 200
Tue, 24 Mar 2009 11:32:30 ReadSoapResponseToFile() Read returned 0, and read 1809 bytes
Tue, 24 Mar 2009 11:32:30 GetCertificate() Found cert file
Fri, 17 Apr 2009 09:33:12 Response problem; ret = 4, status = 0
If I then request a new cert, it works fine. But for how long? I just confirmed this issue this morning, so I'm not sure if the cert lasts until a reboot or what.
Anyone have any ideas?