u/nimraynn

Hi, this is probably a really silly question that I feel should be an obvious answer but getting slightly paranoid.

I have a UK passport that was issued in November 2017, due to expire November 2027.

I am planning to travel to Germany next week, figured this passport would be fine… however a lot of advice and travel info I’m being provided states:

“Your passport must:

have a ‘date of issue’ less than 10 years before the date you arrive - if you renewed your passport before 1st October 2018, it might have a date of issue that is more than 10 years ago, making it invalid for entry to the Schengen area”l

have an ‘expiry date’ at least 3 months after the day you plan to leave the Schengen area (the expiry date does not need to be within 10 years of the date of issue)”

Now, basic maths, I’m working out that 10 years ago would be May 2016, so the fact my passport has an issue date of November 2017, I’m fine, right?

I’m just a little confused about the mention of 10 years, then “before 1st October 2018”… I can’t grasp why 2018 is referenced and the fact mine is before 2018 is making me paranoid.

Put my mind at ease. I’m fine, right?

Thank you!

Is anyone else experiencing issues with TPM attestation during Autopilot pre-provisioning on Qualcomm devices? We are seeing “Something went wrong and TPM attestation timed out” at the first stage of Autopilot pre-provisioning.

When running Test-AutopilotAttestation, it shows Intel and AMD were successful but Qualcomm failed as it was unable to connect to 52.252.16.9 port 443.

I have checked and it’s documented that ekcert.spserv.microsoft.com is used for Qualcomm attestation & an nslookup shows that resolves to 52.252.16.9.

When checking a global DNS propagation checker, we noted that in some parts of the world (we are in the UK), it resolves to 104.42.39.215 and 13.77.211.69. When attempting to connect to these IPs, the 104 address also fails, but the 13 address responds with a valid, relevant certificate.

As a workaround, I was able to create a hostfile entry to point it to the 13 address and pre-provisioning works successfully, but this is obviously a very unsustainable workaround… added with that fact that this morning, the 13 address is also unavailable.

I have tried these addresses on my home broadband, office network, mobile 5G on both corporate and personal devices with and without VPNs to prove it’s not a local network issue.

We have an open ticket with Microsoft where I have asked the engineer about this, but so far he’s just shrugged at it.

Is anyone else experiencing these issues? Would be nice to have some extra ammo for MS, or proof maybe it is just us.

The full URL is https://ekcert.spserv.Microsoft.com/EKCertificate/GetEKCertificate/v1 if anyone fancies testing it!

Thank you!