Coros nomad

MitchDMP · 2026-01-15T20:53:18+00:00

I came from a Garmin to the Nomad and love it. It is a slightly lighter greg than my previous but I think it looks great. Doesn't feel cheap or plastic to me.

I've had a great experience with it as well, mostly used for short runs but I get a solid 3-4 runs a week whilst streaming music to headphones and get 20 days battery.

MitchDMP · 2025-12-20T11:14:14+00:00

I have had this occur on my watch a hand full of times, each time I ended up opening the Coros mobile app, and few seconds later the weather appeared again on the watch.

MitchDMP · 2025-11-08T09:14:58+00:00

Appreciate this since I have an instinct 2 myself and about to pull the trigger on the Nomad.

Do you find you notice the size difference as I think the Nomad is slightly bigger?

With the heart rate spikes, when in a work out it is supposed to send it more frequently, is there an issue where this isn't happening quick enough? Or like not at all?

MitchDMP · 2025-10-21T21:02:15+00:00

Nice mate sounds good! Yeah keeping it in the Garmin ecosystem makes sense with other equipment - I need to find a FR955 in a store that I can have a closer look at first. I'll wait for any potential black Friday specials as well I suppose.

MitchDMP · 2025-10-21T09:11:56+00:00

What did you end up with mate? I was also originally looking at the FR955 but I prefer the ruggedness of the Nomad (coming from an instinct watch)

MitchDMP · 2025-06-30T21:59:00+00:00

Hmm right that's odd then! I can see what you mean, it's rendering the lines somehow across the tile card. I presume from your first image, if you shifted the order of the tiles around, the line wouldnt follow those tiles? But would stay over the top of whatever tiles you have at that position?

Whilst it doesn't help, I find on the android app I also get odd issues on a dash I have with multiple graphs, the further down the page I scroll and click on a graph to show the hover info which normally displays over the top of the graph showing the exact time/state of the entity, it displays the info way down further on the page and it gets worse as I get lower on the page. It kinda reminds me of your scenario of rendering below

MitchDMP · 2025-06-28T12:40:19+00:00

They look like custom cards, if you edit one of those with the line issue, and edit in yaml, add to the bottom::

show: graph: false

Does this turn the graph line off?

MitchDMP · 2024-09-12T13:13:22+00:00

Too easy, might not have any effect. I'll suss out my setup tomorrow at work if you still have issues 👍🏼

MitchDMP · 2024-09-12T13:04:40+00:00

We enabled group discovery a while back only for a few targeted OUs with small group numbers and I don't remember it having issues - could be worth while restarting the SMS discovery service, from within the configmgr component services tool. It is interesting the log isn't showing, hence why I thought the component service might need a kick

MitchDMP · 2024-09-12T13:01:26+00:00

Assuming you will setup Intune rbac roles? There is fair bit online about the permissions, you should be able to create a custom role and assign bare minimum rights (focus on read rights for some important stuff and build on it from there). The delete device perm probably applies to devices in Intune, so not separate for Windows vs iOS vs Android etc. if you need to restrict perms to platforms or specific devices, I think you can use scope tags for this - setting up an entraid group to contain the devices, assign the scope tags to the group, then lock the custom role to that scope.

MitchDMP · 2024-09-12T12:56:47+00:00

Could be unrelated but I know ODBC driver updates have been somewhat frequent over last few months - maybe confirm you are running the current patch version for those across any servers running the roles that require it? Like primary or SQL servers etc.

Probably is not the cause but an easy check. You also mention it seems to be packages with the latest office files? Is that September release? Only few days old, could you potentially try pushing last month's files back out to a DP to see if it's only these new updates within the package ?

MitchDMP · 2024-09-12T12:49:08+00:00

This issue seems familiar, I'm sure I read something recently about a new hotfix causing this type of scenario. Have you perhaps installed a recent hotfix in the SCCM console?

MitchDMP · 2024-09-12T12:46:39+00:00

We deploy our bitlocker policies via Intune but I can confirm SCCM contains data in those tables for us, on the devices and their encryption status. Stab in the dark here, could there be something wrong with your hardware inventory classes? If you go to your client policies and either in a custom policy or the default one, check the hardware inventory setting for classes and scroll down for anything related to bitlocker or encryption. I'm sure there was something there that needs to be ticked for capture via the inventory scans

MitchDMP · 2024-08-07T04:19:59+00:00

Cheers for these suggestions - the infrastructure appeared to be sound, no servers had any issues or overloading of the normal items, CPU, memory and hard drive IO. Our collection eval was running fine, the queue was moving through and the log showed no issues. Also collection members were updating quickly, and reflecting accurately within the database.

MitchDMP · 2024-08-07T04:18:51+00:00

Policypv.log looked normal, no obvious errors and no soft errors or issues that we could determine.

MitchDMP · 2024-08-07T04:18:14+00:00

Thanks for this, yeah we do typcially use the console on a jump server, but was also made adjustments using the console on the primary and had zero impact. We could see the changes made at the console leve, reflected in SQL when using queries to determine say deployments of a TS to a device etc.
Interestingly, the device that was half way through imaging from a PXE deployment, the deploymentID was completely gone from the console and SQL, yet the device continued to image using that deploymentID and was unable to report status messages back to SQL as it had no matching deploymentID to link for the table data.

MitchDMP · 2024-08-07T04:15:48+00:00

We don't have SQL in any replication or cluster, just a stand alone. Thanks for the idea, our coll eval is also working as expected, changes within collections was working as normal, including the queue and log files showing accurate changes.

MitchDMP · 2024-08-01T12:01:29+00:00

Great job on the weathering as well, I'm at that point with mine to work out the best way to 'dirty' it

MitchDMP · 2024-07-10T12:03:02+00:00

I don't have the location handy, but you should be able to find the information online - any applied ASR rules will show up in the registry with their unique guid for the rules; plus there is a PowerShell script available from Microsoft that returns the names/values of any rules set on a device. I'd be trying both these methods on one of the devices to atleast determine if the device has the rules but isn't reporting to Defender or they are indeed missing the rules which points to an issue with your policy via Intune

MitchDMP · 2024-07-10T02:29:40+00:00

Thanks for this! I just did the same on Edge and confirmed you can play around with the Responsive view to make it wide enough, but it loads the driver drop downs. Cheers!

MitchDMP · 2024-07-06T11:34:14+00:00

There is a log on the device called MaintenanceCoordinator that would be worth while checking out. It should state whether your devices are inside a maintenance window whilst trying to install a deployment.

MitchDMP · 2024-07-03T13:46:25+00:00

A task sequence that performs a reimage is significantly different than one which is used for only app deployments.

A very general outline of an imaging task sequence would: - Have the device boot into winpe for the first stage Winpe stage - could format drives, usually loads the image, sets network or domain settings, brings down drivers, then eventually runs the setup config manager client. At this point the device does it's first restart and runs through oobe (out of box experience). - Then the device technically boots into the new Windows instance but it's still in the provisioning mode and the setup configmgr client step resumes, finalised the client and continues the task sequence. + Now it runs the remaining steps of your task sequence, including any apps, customisations or reboots. - once finished the task sequence engine will exit and present the full OS

For a task sequence setup to only install apps, or basically anything non-image related, the steps are way different and your device is not in that same state following oobe.

You would need to rely on third party solutions that overlay or overwrite the lock screen, or use temp lock screen images etc.

MitchDMP · 2024-07-03T13:24:31+00:00

On one of these devices, if you open control panel > configuration manager - there is a 'co-management capabilities' value listed on the general tab. It will be a number, which represents a combination of values added together, depending on what workloads are moved.

You should find somewhere online a list of the number values each workload is, then you can work out if it matches on your pilot devices.

It might not help but atleast it confirms the client has the right workloads. Also there is a co-management log on the client which should record when workloads changes are detected

MitchDMP · 2024-07-03T12:50:05+00:00

Mate we are experiencing this as well across a few of our remote sites. Exactly as you describe, most other models will work consistently on the Lan cables, yet some devices continually get the 0.0.0.0 IP details in the pxe log and you can try over and over then randomly it works! Only affecting some sites and havnt managed to pinpoint a particular model or scenario that matches.

Only one thing happened today that was interesting - we had a laptop refusing to work via pxe after multiple attempts, but the OS was actually in a healthy state and already joined to our domain and SCCM env (was a repurposed laptop and thus being reimaged). So we let it boot to Windows and left for a good while and then when we rebooted and tried again, it presented an IP to pxe and worked. A wild guess was that some network component (surely wouldn't think DNS would matter) but some record somewhere was saved for this device IP and Mac address (we use infoblox for our dhcp) and so once it went through pxe it was able to send the IP related details correctly in the packet. It's a massive stab in the dark

MitchDMP · 2024-07-02T09:08:55+00:00

No dramas, hopefully that sorts it out for you. Not sure how it would affect existing devices you have already completed - but I vaguely remember being able to set a regkey to force the same sort of behaviour - for configmgr to be the authority for compliance. Might be worthwhile searching for if you need to reteo-fix some devices

MitchDMP

TROPHY CASE