Have you ever get any successful remote control session running with other device brand/models on your MobiControl server?  

Do you have similar problem with other Samsung devices using the same device agent version+build?

Has there been any upgrade on your server, device agent(s) or device firmware recently?

Have you configured any skin for the J7 Star before trying to open a remote session? If not, just choose Samsung J7 or J7 Pro and see if there is any skin downloaded and displayed. in the remote control session

Correct me if I'm wrong, you enrolled this devices as Android plus and not as android enterprise (android for work). 

I suggest you do the following procedures:

1. Create MGPA account

2. Create a rule and bind the MGPA account

3. Factory reset the device

4. Follow setup Wizard and stop at Google account creation

5. On Google Account, type in "afw#mobicontrol"

6. Follow setup wizard

7. Input enrollment ID


I think there will be a problem if you have used android+ deployment on Android OS-8.0+

Have you ever get any successful remote control session running with other device brand/models on your MobiControl server?  Yes, we have tested with several devices. Brands such as Alcatel, Huawei, LG.

Do you have similar problem with other Samsung devices using the same device agent version+build? 

Yes, the same problem was presented with the J7 and J7 Star

Has there been any upgrade on your server, device agent(s) or device firmware recently?  We have not had updates, we have two servers, one in version 14 and the other in 13.4.0.3985. em both present the error

Have you configured any skin for the J7 Star before trying to open a remote session? If not, just choose Samsung J7 or J7 Pro 

We already use the skins but without success.

I still do not do the tests for enterprise, I do not doubt that it works. The tests are carried out on Android + because our client requests it and therefore the need to do it on that platform. I'll do the tests also in enterprise, thanks.

i am having this same exact issue with the Samsung -i have some AT&T Samsung SM-T387AA. i can assign profiles and deploy the lockdown kiosk just fine, i can send scripts to the devices just fine as well, i just cant remote into them. this is catching me off guard because i have Verizon Samsung SM-T378V android 8.1 tablets enrolled with android + that let me remote in. i dont believe the issue is revolved around with the enrollment, but i wont rule it out just yet. i will keep trouble shooting. if i find anything out i will let you know. i was actually about to post the same question but i saw yours. hopefully we can get more eyes on this issue.

Enrollment by Enterprise, remote view does not work either.

I am having the same issue with sm-a530f (Galaxy A8)
not an enterprise setup.

Remote Control works fine on other samsung devices.

Jair,

I had this issue with the Samsung Tab A 8.0 (2018). I had to wait until Samsung pushed a firmware update for the device before it would render the screen in MobiControl. 

You may want to open a ticket with SOTI so they can document and test on their end and open a ticket with Samsung if they experience the same issue.