Desktop app not installing on some Windows 10 clients

Rob_Sked
Conversationalist

Desktop app not installing on some Windows 10 clients

Hi,

 

Have around 200 Microsoft Surface Windows 10 devices, and trying to install an Epson Virtual Port via the software inventory.

 

For one batch of devices, this is working fine without error, but on others, I see this in the activity log of the device:

 

Mar 03 16:33 Install desktop app 'Epson TM Virtual Port Driver Ver.8.70a' Error Mar 03 16:34
Mar 03 16:32 Apps refresh Error Mar 03 16:35
Mar 03 16:32 Client details refresh Success Mar 03 16:35

 

Reviewing the m_agent_service.log on the device, I see this:

 

2021-03-03 17:47:35.75132 [01826C50]: m_agent_service starts at Wed Mar 03 17:47:35 2021

2021-03-03 17:47:35.584973 [01826C50]: 3.0.2
Apr 20 2020 22:21:35
b5f2c12167ad015aff5433a7eb28d397f4f3a4a9
91701
bwhull
2021-03-03 17:47:35.597876 [01829AE8]: do_blocking_wmi_query(): command = C:\WINDOWS\system32\cscript.exe //E:vbscript //Nologo C:\WINDOWS\TEMP\m_aB001.tmp
2021-03-03 17:47:35.823602 [01829AE8]: main(): version = 3.0.2
2021-03-03 17:47:35.823602 [01829AE8]: main(): self_path = C:\Program Files (x86)\Meraki\PCC Agent 3.0.2\m_agent_service.exe
2021-03-03 17:47:35.823602 [01829AE8]: main(): self_dir = C:\Program Files (x86)\Meraki\PCC Agent 3.0.2\
2021-03-03 17:47:35.823602 [01829AE8]: main(): temp_dir = C:\WINDOWS\TEMP\
2021-03-03 17:47:35.827621 [01829AE8]: main(): temp_dir(current_user) = C:\Users\ADMINI~1\AppData\Local\Temp\
2021-03-03 17:47:35.827621 [01829AE8]: main(): system root = C:\WINDOWS\
2021-03-03 17:47:35.827621 [01829AE8]: main(): G::lobal()->UUID = 9E25E474-A388-4AE1-B8E4-95499AA1CFE6
2021-03-03 17:47:35.827621 [01829AE8]: main(): G::lobal()->session_id = 14093
2021-03-03 17:47:35.827621 [01829AE8]: main(): organization_id = 454076:659777345409840687
2021-03-03 17:47:35.828615 [01829AE8]: main(): G::lobal()->cf_fetch_url = [https://n172.meraki.com/cf/config]
2021-03-03 17:47:35.829586 [01829AE8]: main(): my etheraddr = 34:CF:F6:AF:6E:A4
2021-03-03 17:47:35.831581 [01829AE8]: do_blocking_wmi_query(): command = C:\WINDOWS\system32\cscript.exe //E:vbscript //Nologo C:\WINDOWS\TEMP\m_aB0EC.tmp
2021-03-03 17:47:36.469416 [01829AE8]: parse_config(), strange line in config: {"default_cloud_enrollment_network":659777345409830555}
2021-03-03 17:47:36.469416 [01829AE8]: main(): G::lobal()->config.tun_hosts has changed: (pcc172.meraki.com:993) (re)starting tun_clients
2021-03-03 17:47:36.481450 [0180CC40]: TunClient::main() [pcc172.meraki.com:993], starting up...
2021-03-03 17:49:37.554322 [01829AE8]: ClientManager::check_client_pulse(): client pcc172.meraki.com:993 timed out; restarting
2021-03-03 17:50:12.858793 [01829AE8]: Suicidal::commit_suicide(): failed. !is_dead().

I was advised to re-enrol the device, but as it's off site, once I tell the device to disconnect, it loses the wifi network settings.

 

As these are device in a retail store, its a large, large job to try and get the store staff to locate a wifi network and re-run the enrollment process.

 

I was wondering if there was another way to try and resolve the issue, without recalling 100+ devices. 

 

3 Replies 3
BlakeRichardson
Kind of a big deal
Kind of a big deal

Instead of recalling the devices could you not just provide the software to the store staff to install? I know it defeats the purpose of MDM however if its either that or recall devices I know which option I'd take.

 

 

Also I have found through my own experience that Epson software is a nightmare to deploy via MDM's not just Meraki but also Jamf. 

If you found this post helpful, please give it Kudos. If my answer solves your problem, please click Accept as Solution so others can benefit from it.
PhilipDAth
Kind of a big deal
Kind of a big deal

I think you'll need to try manually installing the software on one of the machines so you can watch and see why it is failing.

Rob_Sked
Conversationalist

Hi,

 

Have manually installed the software using psexec and that's installing without any issues.

 

Oddly enough, even once it's installed, it's not reporting back due to the above messages seen in the log. 

Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.
Labels