New S25 Ultra Unable to setup work profile using company portal

[userS1pDcmBfQl]

I installed company portal on my new S25 Ultra and signed using my work credentials and then I press Begin to create a Work Profile. It does something for 3-5 seconds and gives me an error "Can't add Work Profile'.

I checked with my company's IT Admin and there are no policy restrictions and they asked me to try on other devices.

I tried it then on my Note 20 Ultra and S24 Ultra and it worked fine. Seems like there is an issue with S25 software compatibility or something.

I called Samsung Care and they blindly shirked off their hands and told me to contact my IT Department 😞 Pretty useless. If there is no solution I might have to return the phone since I can't have a phone without my work email and apps.

[Samsung_X87EoVt]

Same problem here, can't create work profile. S25 t-Mobil unlock  

[BadgerVA]

Same here.  S25 Ultra, Verizon.  We use Ivanti Go at work. IT has been unable to help

[Aron1]

Alright folks, gather 'round for the 92nd rendition of "My Work Profile Won't Play Nice!" (Give this user a prize, they've earned it!)

Yes, you guessed it! Another phone, another unlocked SIM, another work profile throwing a tantrum. It's like they're allergic to productivity! (Maybe it's trying to tell us something...)

But fear not, dear reader, for I have braved the depths of the verbose log (and may need therapy afterwards) and consulted the all-knowing Google Gemini. Think of it as a digital Ouija board, but instead of contacting spirits, we're trying to figure out why this work profile is playing dead.

So, grab your popcorn, settle in, and let's see what Gemini has to say! (Hopefully, it's more entertaining than watching paint dry, which is what Samsung and Microsoft seem to be doing while we wait for a fix.)

(P.S. If anyone figures out how to teach a work profile to juggle, please let me know. I'm desperate for some real entertainment at this point.)

This log, while quite verbose, doesn't show any critical errors that would immediately explain a problem with the Company Portal app. However, there are some points of interest and potential areas for investigation:

1. Database Upgrade:

• The log shows a lengthy database upgrade process, going from version 0 to 586. This suggests that the app was either newly installed or had a significant update. While the upgrade completed successfully, it's possible that there might be issues with data migration or compatibility with the new schema.

2. Firebase Remote Config Failure:

• Similar to the previous log, there's an error related to Firebase Installations: Firebase Installations failed to get installation auth token for fetch. This could prevent the app from receiving remote configuration updates, potentially affecting features and settings.

3. Key Protector Issues:

• There are multiple instances where the MAMKeyProtector reports that AES and RSA keys were unrecoverable and needed to be re-initialized. This might indicate a problem with the key storage or access mechanisms. While the keys were successfully re-initialized, it's worth monitoring for any recurring issues.

4. Enrollment Failure:

• Towards the end of the log, there's an indication of an enrollment failure: AwaitActivity failed... reason: managed profile request failure. This suggests that the app attempted to create a managed profile (work profile) but failed. This is often due to the user canceling the process or the device encountering an issue during profile creation.

5. MDM Backend Switching:

• The log shows the MDM backend switching from NATIVE to SAMSUNG_SAFE. This is expected on Samsung devices with Knox support, but it's something to keep in mind when analyzing policies and device management behavior.

6. Work Profile Enrollment Cancellation:

• There are entries indicating that a managed profile request failed, and cleanup tasks were scheduled. This reinforces the possibility of a work profile enrollment issue.

7. SQLite Exception:

• Right at the end, there's an SQLiteException: no such column: period_start_time. This suggests a database query is failing because a required column is missing. This could be due to a database schema mismatch or an outdated app version.

Overall Analysis and Recommendations:

While this log doesn't show clear errors like the previous one, the enrollment failure and the SQLite exception are the most concerning points.

• Enrollment: Investigate why the managed profile creation failed. Was it user cancellation, a device issue, or a problem with the enrollment process itself?
• Database: The SQLiteException needs to be addressed as it could lead to further problems. Ensure the app is up-to-date and consider clearing app data or reinstalling the app if necessary.
• Key Protector: Monitor for any recurring issues with key recovery. If the problem persists, it might indicate a deeper issue with the key storage mechanism.
• Firebase: Keep an eye on the Firebase remote configuration errors. If they persist, it could hinder the app's ability to receive updates and function correctly.

[avolatte]

With the greatest of respect to your answer, I'm not sure how I am supposed to use this information. What actionable steps for end users like myself are you actually suggesting?

[SamUserNumeroUno]

Just to confirm - people are failing with a fresh setup for Intune (as in you did not configure ANY google services what so ever (email account, play store account, etc) and no work accounts established either?  I know I had this **bleep** issue when I got my S22 Ultra I had to rip all things google off the phone, do the enrollment with company portal (Intune), then add all my personal google things back on.

I think I read people tried this but just confirming lotta reading in this thread.  And I'm trying to avoid undoing all the **bleep** app setup work I just went thru totally forgetting that I experienced issues like this before.  (Neither MSFT nor Samsung was any help - it was some redditor who stated it was the Google Security on the phone preventing Intune Company Portal from taking over) and sure as **bleep**e it was...

[RanmaKei]

Out of curiosity. Do those having issues use an eSIM?

[avolatte]

I am eSim.

[Members_oE12P8T]

I am esim but tried on an S25 Ultra with physical sim and it did not work either.

[BadgerVA]

Also had an issue at initial set up with esim and physical sim.  Had to contact support (verizon for me) and after hours they had it fixed.  Did the chat support and talked to about 8 different people.

[userQSY12KlvAx]

Is this issue related to a specific S25 model as in the Ultra. I have the Ultra and cannot setup the work profile.

Anyone with the S25 or S25 plus also having issues?