Just Released! What’s new with Wyse Management Suite 1.3?

Dell Releases Wyse Management Suite 1.3

The Dell Wyse team has recently released Wyse Management Suite (WMS) 1.3 and also updated the cloud hosted version at www.wysemanagementsuite.com!

You can see a quick summary of the new features below.

You can download this new WMS 1.3 and documentation from here.

New features

Dell Wyse Podcast – Subscribe Now!

Like podcasts? Like VDI & thin clients? Check out the Dell Wyse Podcast to stay up to date on all things Dell Wyse thin clients and VDI news!

Search for “Dell Wyse” in your favorite podcast app and it should come up, “The Dell Wyse Podcast”.

You can also link to it here: https://dellwyse.podbean.com

Enjoy!

@chris_messer ~~> Subscribe to blog to get latest updates <~~

Wyse Management Suite – Error pulling Windows 10 IoT Image

In some recent lab testing I ran into the following error: “CCM on-prem Server authentication token is not available in configuration file.”

I got this error when attempting to pull a Windows 10 IoT Image off a Wyse 5060 client.

The fix was to push the updated Merlin package, aka boot agent, to the device prior to capturing image.

This package is already pre-loaded in the Wyse Management Suite software and listed under “Apps & Data\App Inventory\Thin Client” – MerlinPackage_Common.exe.

You will need to create and App Policy containing this package and push to the client.

  1. To create App Policy go to, Apps & Data\App Policies\Thin Client\Add Policy
  2. Complete the policy using the details below:
  3. Once policy is created, go to, “Jobs\Schedule App Policy” and create your policy similar to below:
  4. Once the policy is pushed successfully you should now be able to pull the image!

Error details:

(Status: Failed – [ERROR: CCM on-prem Server authentication token is not available in configuration file. (error code : 107).]
[ERROR STAGE: Repository validation.]
[REASON: Configuration file is missing authentication token of on prem Server.]
[SOLUTION: Make sure config file is updated with proper CCM on prem Server authentication token.]
| (107))

Hope this helps someone else down the road!

@chris_messer ~~> Subscribe to blog to get latest updates <~~

Additional support resources as noted below:

Dell TechCenter Wyse Product Support Forums – these are a great resource for getting up and running with the solutions as well as tips and tricks for troubleshooting common issues. Once you join the Dell TechCenter community you will have a variety of resources to get started!

Dell Wyse Support Site – Wyse documentation, log support incident, etc…

Available categories with forum and topic lists:

  • Wyse general forum: for discussions that, for example, span multiple categories, involve end-to-end methods, heterogeneous environments, new use cases or topics not found under the support documentation or existing discussions.
  • Wyse thin clients: includes Cloud Connect, Linux, Windows Embedded Standard, ThinOS and zero clients for Citrix, MultiPoint Server and VMware.
  • Wyse software: includes Wyse Management Suite, Wyse Device Manager, Wyse WSM and Wyse Virtualization Software

Wyse Converter for PCs Installation Steps

The following steps outline the typical installation of Wyse Converter for PCs

  1. Download a copy of Wyse Converter for PCs here
  2. Ensure the PC you wish to convert meets the minimum requirements and pre-requisites noted here
  3. You will also want to get access to the Wyse Management Suite software to have a centralized way to configure and manage your converted PC’s. You can get access to Wyse Management Suite by going here. Alternatively, you can manually configure the device using local GUI during testing.
  4. Run ‘WyseConverterforPCs.exe’ on your Windows 7 or Windows 10 PC you wish to convert. Note: By default, you will get a 45 day trial license as part of the installation.
  5. Follow the steps below for a typical installation:
    1. After installation completes and PC reboots you will be brought to the following screen:

WyseUser2

8. By default, Converter for PC will auto-logon as the locked down Standard User, ‘WyseUser’ as noted in step 4. In order to login as ‘WyseAdmin’ hold down ‘shift’ key and log off and you will be brought to Windows logon screen where you can select the user account you want to log in as.

  • default credentials
    • username: wyseadmin | password: DellCCCvdi
    • username: wyseuser | password: DellCCCvdi

9. At this point, you can begin your configuration of the Citrix client, VMware client, etc… using one of 2 methods:

10. You can access documentation Wyse Converter for PC documentation here and Wyse Management Suite documentation here.

Additional support resources as noted below:

Dell TechCenter Wyse Product Support Forums – these are a great resource for getting up and running with the solutions as well as tips and tricks for troubleshooting common issues. Once you join the Dell TechCenter community you will have a variety of resources to get started!

Dell Wyse Support Site – Wyse documentation, log support incident, etc…

Available categories with forum and topic lists:

  • Wyse general forum: for discussions that, for example, span multiple categories, involve end-to-end methods, heterogeneous environments, new use cases or topics not found under the support documentation or existing discussions.
  • Wyse thin clients: includes Cloud Connect, Linux, Windows Embedded Standard, ThinOS and zero clients for Citrix, MultiPoint Server and VMware.
  • Wyse software: includes Wyse Management Suite, Wyse Device Manager, Wyse WSM and Wyse Virtualization Software

@chris_messier ~~> Subscribe to blog to get latest updates <~~

 

Using HTTP for StoreFront Server

In some recent lab testing I setup Citrix StoreFront to use HTTP as I was running some quick tests and didn’t need HTTPS for my test.

Unfortunely, by default, the Citrix Receiver only allows you to connect via HTTPS. If you enter an HTTP URL, it won’t allow you to save it and instead, get the following error:

“The specified server address is not secure”

StoreFront1

Once you click, “Add”, you will get the following:

“HTTP Store requires additional configuration before being added to the Citrix Receiver. Please contact your system administrator.”

StoreFront3

The fix for this is to edit/add the following Registry keys on the client your using the Citrix Receiver to connect from:

  1. Set HKLM\Software\[Wow6432Node\]Citrix\Dazzle\AllowAddStore to A to allow users to add non-secure stores.
  2. (Optional) Set HKLM\Software\[Wow6432Node\]Citrix\Dazzle\AllowSavePwd to A to allow users to save their passwords for non-secure stores.
  3. To enable the addition of a store that is configured in StoreFront with a TransportType of HTTP, add to HKLM\Software\[Wow6432Node\]Citrix\AuthManager the value ConnectionSecurityMode (REG_SZ type) and set it to Any.
  4. Exit and restart Citrix Receiver.

Source: Configure and install Receiver for Windows using command-line parameters

You should now be able to use an HTTP URL in your Citrix Receiver to connect to StoreFront successfully!

Hope this helps someone else down the road!

@chris_messer ~~> Subscribe to blog to get latest updates <~~