Prior to version 2 of the firmware, the 3446xA multimeters did not show the time since calibration, when upgraded to a version 2 firmware, the firmware assumes a default date as no date is set in the calibration data.
With a cal string of 24Nov14, I would guess that this multimeter is essentially new old-stock, with the reseller upgrading the firmware and running it through their own verification. Keysight recommend that an adjustment is always made, even if the multimeter is within specification at the calibration interval. The logic behind this, is that Keysight specify accuracy limits following a calibration and adjustment. If you calibrate the multimeter in the more traditional sense (i.e. verification) you are only testing the accuracy on the multimeter at that exact moment and there is no guarantee of its accuracy in a month or a year. Essentially, Keysight have gone to a lot of effort figuring out how the accuracy of the multimeter will drift, if you don't adjust the multimeter, there is no way to tell how it will drift.
Also the calibration count of 128 is very odd.
Doesn't inspire confidence.
A cal count of 128 is not too suspicious - my 34470A came with a count of 76, the reason being is that each write to the cal memory (done after each cal constant / step) increments the count. A count of 128, makes me think that the multimeter has been calibrated twice - but this can happen in the factory (i.e. a bad calibration or Keysight refreshing their stock).
As far as cal certificates go, I wouldn't trust that one at all - even cheap cals (done by RS, here in the UK) give more information than that. Personally, I would send the multimeter back to the seller and order a multimeter from a better source.