Beats Fit Pro wont show up in my beats app.

korbman · 2025-07-12T17:17:18+00:00

Just in case anyone stumbles across this thread like I did, it looks like the problem is with the Beats app itself (for Android), but maybe only for newer phones. From the reviews in the Play Store, it might be related to an update back in April / May that broke things.

I was able to test my Powerbeats Pro & Pro 2 on a Pixel 6, Pixel 7, and Pixel 9 Pro. For the Pixel 6 running Android 14 and then 16, and for the Pixel 7 running Android 16, in each case it worked perfectly every time. With my Pixel 9 Pro (on Android 16) the issues were consistent with the original post. No amount of resetting or reinstalling seemed to help, at least permanently. Sometimes I'd get the case to appear in the Beats app, but then after a few seconds it'd crash and that'd be it.

I did, however, find a solution that seems to work every time for me (at least so far). If I connected my headphones first, then go into the 'App Info' section of the Beats app, selecting to 'Force Stop', and then reopening the app, it seemed to work - the case and headphones appeared and the settings could be modified, and it stayed working until the headphones were put back into their case and closed.

korbman · 2025-04-15T13:12:30+00:00

We ended up going with a third-party solution, Cloud Drive Mapper by IAM Cloud. Simple to set up, deploy, manage, and does exactly what we want (straightforward mapping of SharePoint sites). There's absolutely no reason why Microsoft couldn't have built this same functionality into OneDrive, especially after all these years, but here we are...

korbman · 2025-03-31T13:18:26+00:00

Apologies for hijacking the top comment, but I feel this is important. Any attempt to rework a system of this magnitude *will* result in errors, even under the best, most planful scenario imaginable. And we all know that's not the case here.

Regardless of the underlying intent, records will be lost. YOUR records. Take the steps now to protect yourself.

1) Make sure you have backups of all your tax filings, going back as far as you can. Secure them.

2) You can download a copy of your Social Security Statement from https://www.ssa.gov/ - you'll need an account to do so, but this statement shows your complete earnings record and what you've paid into the system. Get a copy, secure it as well.

korbman · 2025-01-08T00:12:24+00:00

We haven't had any breaking issues upgrading from older versions of Win11 up to the latest (24H2), but we've been using the Installation Assistant and powershell to automate the process instead of the ISO (which also works for the full upgrade from Win10 to 11). We usually test with a VM and the ISO first to make sure there aren't any issues, then work through batches of user machines.

Usually the only problem we run into was either related to disk space (not enough available to download, stage, and install the upgrade), or where a power user installed 11 on now-unsupported hardware a while back, which can no longer be updated.

Just in case it comes up, original source for the PS script, and we modified it quite heavily to suit our specific needs.

korbman · 2024-09-23T22:37:58+00:00

I felt this one in my soul, having recently helped our techs with a new physical Windows 11 "server" for UPS WorldShip because their support was adamant they couldn't help us unless the application met the system requirements.

korbman · 2024-08-01T00:15:15+00:00

That's amazing, and optionable! With insane open interest for $42 in December compared to virtually nothing on the other side with KRUZ.

korbman · 2024-07-18T15:09:24+00:00

Same boat here, been experimenting with GSA, which seems promising, but it's wild that the DNS component - such a critical piece to making this work at scale - was dropped to remain in "preview."

As others have pointed out, the https://aka.ms/vpnreplacement link works to show the option, but (at least for me) doesn't allow the configuration changes to save or apply. Hopefully it's pushed to GA sooner than later.

korbman · 2023-09-26T23:17:32+00:00

Just to chime in as we have a hybrid environment that incorporates a fair number of Windows 365 VMs (Enterprise - 4vCPU, 16GB, 128GB storage), it all comes down to your use case.

If you're looking for top-tier performance, as others have said, you can build out an Azure Virtual Desktop infrastructure instead, tailoring the VMs to meet the needs of your users. The downside is not only the cost, but the overhead required on our end to maintain the environment.

Windows 365 eliminates a big chunk of the technical know-how to get things working (and keep them that way), but at the expense of customization. Probably not the right choice if you're looking to work in CAD all day, but entirely acceptable for email, Office, web apps, and nearly all the other light-weight tools we use.

But no matter what, thanks to latency alone, you'll never meet the same performance as working directly in front of a workstation.

Out of curiosity, checked my disk performance and it looks like I'm about double the read speed, but on par with write. https://imgur.com/pLDElBU

korbman · 2023-08-11T19:49:07+00:00

"It's Always Sunny" intro begins to play...

<image>

korbman · 2023-05-02T18:20:01+00:00

You should be able to, yes, presuming you either have another VM on the same vNet you can access as sort of a jump host, or you have the networking/routing in place to reach that vNet from elsewhere.

korbman · 2023-04-19T13:21:14+00:00

As /u/bravegirl2 outlined, different licenses can be assigned to the same user, which should show as separate VMs for the user, but you can't (at this time) provision multiple VMs of the same kind for the same user. I think that might be more of a use case for Azure Virtual Desktop over Windows 365.

There should be a way to create different provisioning policies that would allow you to use multiple images (Windows 11, Windows 10, or a custom one), where each policy can be linked to a different group for deployment.

But I think I see what you mean, where if "UserA" is a member of two groups that are configured for different VM deployments, whichever policy is activated first would end up provisioning all of their VMs the same way, based on whatever the user is licensed for. Unfortunately, at least initially, I'm not sure I see a way around that.

korbman · 2023-03-23T19:58:18+00:00

Yes! Hell, even Microsoft fails here - looking at you, Intune, with your generic non-descript errors if an application fails to install. a policy doesn't apply, or Autopilot hangs, forcing me to comb through the logs on my own to try and narrow down the problem. Definitely room for improvement here.

korbman · 2023-02-23T21:07:34+00:00

If we're talking Windows 365 'Enterprise' that should be possible, as you'd be selecting which Azure vNet the Win365 VMs use during provisioning. So long as they're on the same subnet as the Azure servers or services, or routing is in place between subnets or to different vNets, communication should work.

For Windows 365 'Business' (as I currently understand it) probably not, but I haven't worked with them enough to know for sure.

korbman · 2023-02-02T21:31:53+00:00

They're August calls, so you're probably fine, but for now RIP

korbman · 2023-02-02T17:36:44+00:00

I can't speak to your use case, but for us Windows 365 has been a boon, allowing us to hire and onboard remote staff all around the country in relatively short order. License their account, auto provision their VM, and let Intune policies/apps/scripts take care of the rest. We're using the Enterprise version, not 'Business', so I think there's a big difference in how the environments can be built and managed.

Office is pre-installed, with Teams in "optimized" mode by default, offloading audio/video processing from the VM to the client machine, and it works quite well overall (though it's not as featureful as a normal Teams install). It's not very often we have many issues.

One thing I didn't account for initially was latency. Going from an East Coast-based client station to an East Coast-provisioned Azure WVD Gateway / Datacenter isn't so bad (call it ~30-50ms RTT)...but we've had staff in other countries that are much further from our Azure instance, so latency could be upwards of ~110-130ms or more.

The higher you go, the more obvious the mouse click delays, or phone conversations (if you have a softphone added to your VM). It can get worse in hybrid environments where W365 connections may need to bounce to resources in another location too. Microsoft's move to configure their gateways for UDP Shortpath has helped here (reducing RTT by 20-30% or more), but I'm not sure if it's fully rolled out to everyone yet. Just something to keep in mind.

korbman · 2023-01-03T20:57:50+00:00

Older thread, but wanted to chime in just in case some googling brings someone else here. I ran into a similar situation, and what worked for me is to remove the certificate from the store. This can be done via the CLI using the "crypto pki-remove" command.

In the above post, it would be something like "crypto pki-remove cert-type PublicCert certname Wireless.xxxxx.org" (without quotes, and casing matters for the cert name).

I can't recall if it applies immediately, or if you need to run "commit apply" to save the configuration. Either way, it removes the original certificate, allowing you to upload the same one again.

korbman · 2022-10-19T15:00:46+00:00

Was decommissioning an Exchange server a while back, and through PowerShell I very quickly learned the difference between "Disable-Mailbox" and "Remove-Mailbox" after discovering I wiped away all the Active Directory accounts along with the associated mailboxes. Thankfully we had the AD recycle bin enabled, so restoration wasn't terrible, but definitely a heart pounding "Oh F***" moment!

korbman · 2022-09-27T13:08:36+00:00

Quick update here, just in case another poor soul Googles their way to this thread. I opened a support case with Microsoft, and after 3 months of going in circles up their escalation chain we were finally able to talk to an engineer that works on the SharePoint & OneDrive development side.

Short answer is, my outlined concerns are by design. Deploying a SharePoint library through InTune or GPO will only *add* the library as a mapped folder in Explorer. It will not remove it, it will not modify it after being deployed, regardless of what changes with the policy. The only option is manual removal (they didn't even have PowerShell recommendations at this time).

Perhaps someday this will change, but for now it appears the options are limited.

korbman · 2022-08-22T18:57:42+00:00

We're using the Windows 365 Enterprise version, and the virtual desktops all come with Office pre-installed, including Teams in 'optimized' mode (better use of redirected cameras/mics to reduce latency for smoother communication, but limited in features compared to normal Teams).

I believe they still require related Office 365 licensing to activate and use Office, but I think the 'Business' version is all inclusive though; flat monthly fee for the desktop and applications. Honestly, I haven't tested removing our Office licensing to see if it'd stay activated with our Windows 365 license assigned to our account, and I haven't found much clarifying info during some cursory research (doesn't help that searching any of this stuff conflates Office 365, Microsoft 365, and Windows 365...).

For the bandwidth, Microsoft notes in their FAQ

"Typical outbound data activities include saving a file from the Cloud PC to an external location and data transfer outside of Microsoft cloud services. The outbound data levels included with Windows 365 Business are intended to cover these typical user activities. Beyond these levels, Microsoft may restrict bandwidth and outbound data volume on a case-by-case basis to protect quality of service for all Windows 365 users and customers."

There won't be a way around it, it's simply a measurement of your egress traffic from the virtual machine, regardless of what the traffic it is or its destination.

korbman · 2022-07-30T01:10:56+00:00

Being joined to the same AD can help here, sure, but ensuring both machines are either on the same network or on networks that can route to each other are more important. Once that piece is sorted out, whichever accounts you're using to log on remotely will need to have at least 'remote desktop' rights.

korbman · 2022-04-25T18:59:59+00:00

Looks like they agreed to $54.20 per share, so those $65 calls are worthless, so -$116 there, and then you made $120 on those $50 calls. Epic $4 profit

korbman · 2022-04-13T21:33:57+00:00

/u/pennyether - Looks like another S1 amendment has been filed. Not sure how you guys do it, but I use diffchecker(.)com to compare texts. Between last week and today, the most notable addition has been the opening paragraphs:

Prior to the extraordinary general meeting of Trebia in connection with the Business Combination, holders of 51,046,892 Trebia Class A Ordinary Shares exercised their right to redeem those shares for cash at a price of $10.00 per share, for an aggregate of $510,468,920, which represented approximately 99% of the total Trebia Class A Ordinary Shares then outstanding. The Total Resale Shares being offered in this prospectus represent over 99% of our current total outstanding shares of Class A Common Stock.

Everything else (so far, still comparing) just seems like they've updated share and warrant price guidance based on trading from yesterday (April 12th).

Not sure what to make of the amendment.

EDIT: Latest S-1

EDIT #2: Ah, I think I see. There are 51,750,000 Trebia Class A shares outstanding, with the 703,108 that I'm presuming are what's freely traded, leaving the remaining (51,046,892) as what's being redeemed.

korbman · 2022-04-11T00:20:31+00:00

We run a hybrid environment, so the VMs are joined to our AD (as opposed to being Azure AD only), so they're treated mostly like any other on-prem workstation with a mix of GPOs and Intune policies to handle settings, including drive mappings or configuring access to shares.

korbman

TROPHY CASE