Pages

Showing posts with label WDM. Show all posts
Showing posts with label WDM. Show all posts

Tuesday, February 2, 2016

Dell Wyse Device Manager Version 5.0 WDMServiceLog process pegs processor at 100%

Problem

Dell Wyse Device Manager Version 5.0 is installed onto a Windows Server 2012 R2 server:

clip_image002

… and you notice that the WDMServiceLog (32 bit) / RptSvcLog.exe process consistently consumes close to 100% of the CPU process pegging the processor at 100% and allowing the server down to a crawl:

clip_image002

clip_image002[4]

Solution

While the following may not be the best solution for the issue as it’s more of a workaround, it was the only one I could find while searching:

http://www.technicalhelp.de/forums/topic/problem-with-wdm-service-log-makes-cpu-usage-go-to-100/

The suggestion was to disable the WDM Service Logs logging service found here in the Preferences options:

clip_image002[6]

Disabling this service will cause the WDMServiceLog (32 bit) / RptSvcLog.exe never to run and therefore fixes the issue.

Friday, December 12, 2014

Attempting to register a package from a script file (.RSP) on a Wyse Device Manager manager fails with: “Unable to connect to the HTTP Repository”

Problem

You need to move Package Manager Images from one WDM server to another by following the instructions found at this URL:

https://support.wyse.com/OA_HTML/csksxvm.jsp?nSetId=26518&nUsePub=NO&jttst0=6_23871,23871,-1,0,&jtfm0=&etfm1=&jfn=ZGAC0F217415CC7186A83C4B85C3E8044B1347842403EDE204F64AE27372AEDC74F923EF3C8412DD9F0B17F866C966EE089B&oas=hPgVmjwPoeUVu6hGtLpgiA

image

image

image

image

image

image

… but notice that you are unable to register the image because it fails with:

Unable to connect to the HTTP Repository

image

Proceeding to use the Test Connection feature for the Software Repository as such:

image

… fails with the error:

Name: HTTP Connection
Progress: Test Testing Complete
Status: Failed

image

Clicking on the Errors tab displays the following error:

[Error:Not Available] [WebDAV error:Failed to upload buffer. HTTP Response Code: 401Remote File Path: {A33AADB7-443F-4113-A478-D5A07E5518E0}.tmp Error Code: 401]

image

Solution

While there could be various reasons why this error would be thrown, one of the users is if the rapport service account password has expired and requires a new password to be set.  To determine this, launch the Computer Management console on the Wyse Device Manager server and navigate to the Local Users and Groups –> Users node, then open the rapport service account properties:

image

Notice that the User must change password at next login is checked which means the password has expired and must be changed.  Proceed by unchecking the checkbox and check the Password never expires checkbox:

image

Run Test Connection again for the Software Repository to ensure that the test completes successfully:

image

You should now be able to register the image.

Wednesday, November 12, 2014

Attempting to “Get Device Image” for a Wyse Z90QQ7P Thin Client from within Dell Wyse Device Manager Version 5.0 errors with: “Flash is corrupted or improper repository/network configuration”

Problem

You attempt to use the Get Device Image for a Wyse Z90QQ7P Thin Client from within Dell Wyse Device Manager Version 5.0 but receive the following error message:

==================Imaging Failed=====================

ERROR: Error while uploading MBR file. Http Error code: .

ERROR STAGE: MBR validation

REASON: Flash is corrupted or improper repository/network configuration.

SOLUTION: Disable anonymous authentication if enabled on software repository under MyWDM virtual directory or check the device flash.

==================================================

Activating OS partition …

image

Solution

As the Wyse Z90QQ7P was the new model that was just released, I was unable to find a solution through searching the internet so I ended up reaching out to Wyse technical support and was told that we had to install a WDM 5.0 MR pack to resolve the issue.  At the time of writing this, 2 maintenance releases was available:

  1. WDM5.0_MR1_WRK_HF050026414
  2. WDM5.0_MR1.1_WRK_HF050027314

image

I tested installing MR1 first then MR1.1 and can confirm that both of them resolves this issue.

image