Tag: knowledgebase

Fix Windows Mobile Device Center Hanging at Launch and Mobile Devices Will Not Connect

While Windows Mobile Device Center is largely considered a thing of the past in many environments, there are plenty of industries and situations where it is still used to connect and sync mobile devices such as Intermec scanners to other systems. With Windows 10 Update 1703, there was a change regarding svchost.exe that can cause this issue. In this blog post, I’ll explore the two changes I’ve discovered that have worked for me to resolve this issue.

Introduction

While Windows Mobile Device Center is largely considered a thing of the past in many environments, there are plenty of industries and situations where it is still used to connect and sync mobile devices such as Intermec scanners to other systems. With Windows 10 Update 1703, there was a change regarding svchost.exe that can cause this issue. In this blog post, I’ll explore the two changes I’ve discovered that have worked for me to resolve this issue.

Prerequisites

To resolve this issue, access to a local account on the affected device which is a member of the Local Administrators NT group is required.

Problem

When the Windows Mobile Device Center is launched, the splash screen appears and hangs at “Please wait while Windows Mobile Device Center starts…”

Additionally, if the application does launch successfully, mobile devices may show connected on the mobile devices’ screens, but the Windows Mobile Device Center will show them as “Not Connected.”

Environment

Workstations with Windows 10 Professional or Enterprise Version 1703 or newer and Windows Mobile Device Center installed. This issue is operating system architecture agnostic. Affected workstations have Intermec handheld computers seated in their dock, which is attached to the affected workstation via USB cable.

Cause

Update 1703 for Windows 10, like other Windows updates, may revert older version of .NET Frameworks to be disabled; additionally, Update 1703 also has a new feature related to svchost.exe: the services will not share by default the same svchost.exe, even they are assigned to be run within of the same group with -k option. More detailed has been described in the winhelponline.com article under the Additional Reading section of this article.

Rapimgr and Wcescomm (Windows Mobile-based device connectivity and Windows Mobile-2003-based device connectivity) are such services: they are defined to be started in the same shared svchost.exe (-k WindowsMobile). RapiMgr creates a kernel semaphore AS_ACCEPTANCE_SEMA, because it starts first.  WcesComm tries to do this too, but fails: the semaphore has been already created and should be only opened. This will fail: not enough permissions (remember: two different svchost.exe, different SID, etc). So, wcescomm is just stopped.

Solution(s)

Enabling .NET Framework 3.5 Completely

Strike Win+R on the keyboard, and in the resulting Run Prompt, type appwiz.cpl then strike the Enter/Return key on the keyboard.

In the resulting Programs and Features window, select the Turn Windows features on or off option from the navigation pane at the left side of the window.

In the resulting Windows Features window, expand the option for .NET Framework 3.5 (includes .NET 2.0 and 3.0), then ensure it’s check box is fully enabled with a check mark–not a filled square–and that you do the same for the two child items, Windows Communication Foundation HTTP Activation and Windows Communications Foundation Non-HTTP Activation, then click OK. Windows will take a few moments to enable the selected features.

At this point, it is recommended that you restart/reboot the workstation.

Adding “SvcHostSplit Disable” in the System Registry

Warning: Editing the system’s registry can be dangerous unless you know exactly what you are doing. It is advisable that if a solution exists without editing the registry, that it be the selected resolution. If editing the registry is required, always export a backup of the working registry to both the local hard drive as well as removable storage prior to proceeding. Alternatively, a System Restore Point may be set.

Strike Win+R on the keyboard, and in the resulting Run Prompt, type regedit then strike the Enter/Return key on the keyboard.

In the resulting Registry Editor window, select File from the menu bar at the top of the window, then Export to save a backup of the affected workstation’s registry. When completed, close the Registry Editor.

Open an elevated Command Prompt shell (running as administrator. This can be done by clicking the Start Menu icon on the Taskbar in the bottom-left corner of the desktop environment and typing cmd then right-clicking the Command Prompt result and selecting Run as Administrator. Note that this must be done from a local account that is a member of the Local Administrators NT group on the affected workstation. Alternatively, you may browse to C:\WINDOWS\System32 and right-click cmd.exe and select Run as Administrator.

In the resulting Administrator: Command Prompt window, paste the below commands in and strike the Enter/Return key in sequence.

REG ADD HKLM\SYSTEM\CurrentControlSet\Services\RapiMgr /v SvcHostSplitDisable /t REG_DWORD /d 1 /f1 REG ADD HKLM\SYSTEM\CurrentControlSet\Services\WcesComm /v SvcHostSplitDisable /t REG_DWORD /d 1 /f

When completed, you may close the Administrator: Command Prompt window.

Verifying Service Properties

Strike Win+R on the keyboard, and in the resulting Run Prompt, type services.msc then strike the Enter/Return key on the keyboard.

In the resulting Services window, locate the Windows Mobile-based device connectivity and Windows Mobile-2003-based device connectivity services. For each, do the following:

Right-click the desired service and from the context menu, select Properties.

In the Log On tab, ensure the second radio button is selected and that the This account: field displays Local Service. If the Local System account radio button is selected, you’ll need to change the selection to the second option and enter Local System in the This account: field. The password is blank. When complete, click Apply.

In the Recovery tab, ensure the drop-down menus for First failure:, Second failure:, and Subsequent failures: all have Restart the Service selected. When complete, click Apply.

When complete, click OK to close the Properties window for the service.

At this point, a reboot/restart of the affected workstation is required.

Upon startup, the Windows Mobile Device Center should launch normally when the Start Menu entry or desktop shortcut is clicked. Once the WMDC window is open and, subsequently, the Intermec mobile computer is docked, you should see the device begin to connect; this is indicated by a spinning green icon in the bottom-left quadrant of the Windows Mobile Device Center window. The device should then connect and use of Advantage Scan on the Intermec and Drop Utility on the affected workstation may be resumed.

Additional reading

https://social.technet.microsoft.com/Forums/office/en-US/9cab3e8e-6cc4-48e4-8ed9-d595bc83f04b/windows-mobile-device-centre

https://www.winhelponline.com/blog/view-resources-usage-each-service-svchost-windows-10/

Configuring KeyWatcher TrueTouch Using RDS RemoteApps for a New User

Morse Watchmans KeyWatcher TrueTouch

Purpose

This document will delineate the steps necessary to enable a new RemoteApps user to access the KeyWatcher TrueTouch software via Remote Desktop Application Services.

Assumptions

This document assumes that your environment has a remote desktop services farm and that users are accessing applications via published RemoteApps, that KeyWatcher TrueTouch is installed on the RDS Session Host, is published, and that the user is a member of the “Domain Users” security group and that they have Modify permissions to the directory where the KW Configurator is located.

Step 1 – User Profile Generation

The KeyWatcher True Touch application is installed on the remote desktop session host. Because the software provisions its configuration based on Windows user profile, it is necessary for the new user to remotely log into the server at least once prior to attempt logon to the application.

From the user’s workstation, have them open Remote Desktop Connection by going to the Start menu located in the lower-left portion of the Taskbar.

In the Start menu, search “Remote Desktop” and select the first returned search result.

In the Remote Desktop window, input the hostname of the remote desktop session host.

Alternatively, you can strike Windows+R on the keyboard and input mstsc into the resulting Run prompt, then click OK or strike Enter/Return on the keyboard.

Connect and have the user provide their usual credentials to log in. Once the user profile is generated and the user is looking at either (a) the Windows desktop environtment or (b) the Windows Server manager, have the user log out of the server and close Remote Desktop Connection.

Step 2 – TrueTouch Configurator

Once the user profile has been generated, Log into the remote session host as an administrator and navigate to the location of the TrueTouch configurator application, then launch the configurator application in the directory.

In the resulting application window, fill the checkboxes of all users that you want to be able to use the TrueTouch software.

Note: You’ll need to check all users who need access every time. If you only check the new user’s username, then only the new user will have access. This process overwrites all prior configurations.

When the appropriate users are selected, click the Configure button at the left of the application window. When the completion message appears, you may close all windows and disconnect from the server.

Step 3 – Launching Keywatcher TrueTouch via RemoteApps

The user should now be able to go to their Start menu again, locate their RemoteApps folder and expand it to reveal the KeyWatcher TrueTouch application. Upon launch, it should result in a popup login window and the status bar at the bottom of the application window should show that it is connected to the correct KeyWatcher application server.

Additional information

See the Morse Watchman KeyWatcher TrueTouch documentation for additional information. This can be obtained from Genesis Resources.

IGT Advantage & EZ-Pay Clients Installation

IGT Advantage logo – Please note I am not affliated with IGT in any way, nor is this article endorsed by them.

Purpose

This document delineates the steps necessary to do a clean installation of IGT’s Advantage and EZ-Pay client applications on a Windows workstation.

Assumptions

This document assumes perquisites such as file share permissions, domain membership, network connectivity, etc. are already in place. This document also assumes that the target workstation is running Windows 10 with update 1903 or newer installed.

Step 1 – Workstation logon

Log in as an administrator to the workstation on which you wish to install IGT client applications.

NOTE: The installing user must be a local administrator, and must also have modify permissions and modify share permissions to the file share: \\%igt_eft_server%\MAP

Step 2 – DOTNETFX (.Net Framework) 3.5 check

IGT Advantage applications require .NET Framework version 3.5. This is included as a feature in Windows 10, but is disabled by default. Prior to installation, you will need to enable this feature.

You can enable .NET Framework version 3.5 by like so:

Open a Run prompt by striking Windows+R on the keyboard
Type optionalfeatures and strike Enter/Return on the keyboard
In the resulting Windows Features window, check the box for .NET Framework 3.5 (includes .NET 2.0 and 3.0). It will partially fill with a box instead of a checkmark—this is fine.

NOTE: If the box is already partially marked with the square, then you can skip to Step #3 of this document.

Click OK.

Windows Update will now prompt stating that additional files are required and when you click Let Windows get the files for you, it will try to download them.

Click through the process until the feature has completed install. If the download of the additional files hangs at around 10% for more than 15-20 seconds or fails with an 0xxxxxxxxxxxx error code, then see the below section of Step #2.

If Enabling .NET Framework 3.5 fails or hangs
In certain domain environments using SCCM, the Windows 10 Update feature which enables the feature may not work, in which case the following is necessary.

While logged in as an administrator, open an elevated PowerShell session and enter the following commands:

Stop-Service -Name wuauserv
Remove-Item "HKLM:\Software\Policies\Microsoft\Windows\WindowsUpdate"
Start-Service -Name wuauserv
Exit

This removes the Windows Update configuration provided by the domain (using SCCM) that way Windows Update will pull the .NET Framework files from Microsoft directly. If you have Group Policy Objects configured to manage the Windows Update settings of domain computers, the Windows Update policies will be reapplied when the GPO next reapplies/refreshes on the workstation.
Once this has been done, go back and to sub-steps 2.1-2.4 again and the process should succeed in enabling the feature .NET Framework 3.5.

Step 3 – IGT Provisioning System (IPS) installation

Open a Run prompt by striking Windows+R on the keyboard.

Type \\%igt_eft_server%\map and strike Enter/Return on the keyboard
In the resulting directory, locate IPSSetup – Shortcut and run it as administrator.

Step 4 – Client application installations

Launch the IPS application from the Desktop shortcut or by locating it in the Start Menu under IGT or IGT Systems; the IPS deployment window will open.

On the Welcome page, click OK.

On the Load Manifest File page, click Select Manifest File and navigate to
\\%igt_eft_server%\map\manifest and select the approrpaite .xml manifest file for your company/property, then click Open.

Click Continue.

On the Main page, click Configure and Install.

On the Identify Installation Types page, ensure the checkboxes for Client Install and Services Install are both checked, then click Continue.

On the Select Installers to Install page, check the boxes for any applications which are necessary.

On the Parameters Configuration page, test and validate any of the settings that are predefined by the installer. If they pass/succeed, continue to sub-step 4.8.

On the Validation Check screen, click Validate to have IPS validate the target
workstation’s operating system. When it passes, click Continue.

On the Run Install Sequence page, verify that all of the information looks accurate, then click Begin Installation.

When all install sequences have completed and show a green checkmark icon at the right, click Exit.

Step 5 – Disable User Account Control (UAC)

Because IGT applications must always run with unrestricted administrative permissions, Windows will always want to display the UAC prompt. This can be disabled by doing the following:

Open a Run prompt by striking Windows+R on the keyboard.

Type useraccountcontrolsettings and strike Enter/Return on the keyboard.

In the resulting User Account Control Settings window, move the slider to the bottom position and click OK.

Step 6 – Set RunAs administrator

As mentioned in Step #5, IGT applications must always run with unrestricted administrative permissions. To allow this, locate the desktop icon for each IGT application and, for each, do the following:

Right-click the application shortcut on the desktop and select Properties from the context menu.

In the Shortcut tab, click Advanced and in the resulting Advanced Properties window, check the box for “Run as administrator,” then click OK. Click Apply, the Continue, if prompted.

In the Compatibility tab, click “Change settings for all users,” and in the resulting application properties window, check the box for Run the program as an administrator.

Click Apply, then OK.

Be sure to do this for each IGT application shortcut. If the shortcut is not configured as such, the application will not run.

NOTE: This step must be completed for each user that logs on unless you
configure the application shortcuts via the Public Desktop, which is highly
recommended.

Step 7 – Configure local administrators

Finally, add the user who will be using the IGT applications to the Local Administrators local security group.

Open a Run prompt by striking Windows+R on the keyboard.

Type compmgmt.msc and strike Enter/Return on the keyboard.

In the navigation pane at the left, expand Local Users and Groups, then select Groups.

Double-click the Administrators group and in the resulting Administrator Properties window, click Add.

In the resulting Select Users, Computers, Service Accounts, or Groups window, enter the username(s) as appropriate—separated by semicolons—then click OK.

You can now close all windows, and the installation should be complete.

Additional information

Please refer to the official documentation from IGT for installation. This is intended only to be a reference to a real-world installation process that works and isn’t the same verbiage as the vendor’s. For any questions, be sure to reach out to IGT Support or your account representative.

IDP Solid 510 User Cleaning and Maintenance

Just like any other card printer, the IDP SOLID 510 Casino Printer requires regular cleaning as the rollers can build debris on the surface over time, which will change the traction characteristics of the rollers and could lead to card slipping, which could cascade into a myriad of other problems including card jams, ribbon breakage, etc. Fortunately, maintenance is easy and takes less than 2 minutes.

Introduction

The IDP Solid series plastic card printers are some of the best in their class. But like any device, they require some maintenance. While periodic service from your VAR or the manufacturer may be necessary, to reduce operational issues, service requests to your IT department, and the need to ship one out for repair, regular user maintainence should take place. Cleaning these card printers is easy and only takes a couple of minutes.

Maintenance

Just like any other card printer, the IDP SOLID 510 Casino Printer requires regular cleaning as the rollers can build debris on the surface over time, which will change the traction characteristics of the rollers and could lead to card slipping, which could cascade into a myriad of other problems including card jams, ribbon breakage, etc. Fortunately, maintenance is easy and takes less than 2 minutes.

Simply open the ribbon/card covers and remove the ribbon cartridge and cards. Then, press and hold the buttons on both sides of the LCD screen for 5 seconds. Next, open and insert the long cleaning card. Then, close the ribbon cover to start the cleaning process.

Finally, remove the cleaning card, and open the ribbon cover. Allow it to dry for 1 minutes before returning to regular use.

That’s all there is to it! Performing this process regularly can help keep your plastic card printer in good operating condition and reduce service requests and scheduled maintenance with your VAR or the manufacturer.