Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Installing Shopping Agent, Tachyon Agent, or 1E Client

Multiexcerpt
MultiExcerptNameClientInstallationIssues


IssueDescription
No issues known.



Issues specific to Shopping

IssueDescription
Shopping module does not send send machine details on a TLS enabled Windows 7 environmentThe Shopping module in the Tachyon 3.2 Agent fails to send machine details on a TLS enabled Windows 7 (32 and 64 bit) environment.
An error is reported in the Shopping log file when WQL support is enabled.A 'ERROR Shopping (null) – Exception Checking for Approval timeouts' exception may be written to the Shopping log file when WQL Support Enabled = True. This error has no effect on core Shopping functionality.
Branch application prompting for approval request information.When requesting Branch applications from a search list, users may be prompted to provide a comment to justify their request even though approval is not required. Provided some text and submit the request. No approval is initiated or required and the text is discarded.
Tiles not formatting text correctly in list view.In certain circumstances, tiles may show poorly formatted text for the order status when you are viewing it in list view.
SSO Identity HeaderThe SSO Identity Header in property in the Shopping Admin Console UI is for a future implementation.
User Category is visible to a user despite a restriction in a Limiting Collection in Configuration Manager.It is possible to limit the visibility of the user category on a particular machine. This requires adding the machine to the corresponding limiting collection in Configuration Manager. However, this does not prevent the user from seeing the user category if they are on a different machine.
Multiple bindings lost on upgrade to Shopping 5.3.100To reinstate the bindings, you will need to add them manually after the upgrade at IIS > Shopping Website.
Installer values are lost after a Shopping Receiver side-by-side install.You'll need to manually update the installer values post side-by-side install.
The Shopping installer may proceed with the installation even though ActiveEfficiency Server isn't installed on the network.

Shopping requires ActiveEfficiency v1.5 or later to support the correct retrieval of machine and user information for ConfigMgr.

The Shopping installer will proceed with the installation if it discovers the presence of ActiveEfficiency Server 1.4, however some functionality will be lacking. The installer will also incorrectly prompt for ActiveEfficiency Server 1.4 if it doesn't find one installed. It should prompt for ActiveEfficiency Server 1.5 or later.

Hiding the sidebar in the Shopping Web Portal sometimes does not work as expected.Hiding the sidebar does not work on the Application Details page.
Changing Centralized Mode value from True to False prior to upgrading Shopping causes issues with advertisements.If you have changed the Centralized Mode value from True to False before upgrading Shopping you will need to manually remove from ConfigMgr any advertisements created when the Centralized Mode was set to True.
Shopping website banner displays error message related to missing images.The banner images must be manually updated for all the sites in case of multiple websites.
Empty Miscellaneous user category appears to ShoppersMiscellaneous user category that only contains disabled applications is still visible on the Shopping web portal, by design disabled applications do not appear so the user category will appear empty.
Unexpected navigation occurs in the Shopping website when viewing Application Details.URL provided in an Application Description is navigated to after clicking on the Application Details panel.
Blank searches do not return results in the Shopping Web PortalBecause full text searching is now enabled by default in the Shopping web portal blank searches have been disabled for performance reasons to prevent long searches from being initiated by accident. If Shoppers want to retrieve all available Applications they should enter % in the search field.
Blank emails may be sent to users where their default language is set to a general language rather than a country specific languageShopping comes with translations files for country specific languages (de-DE, es-ES, fr-FR, it-IT and pt-BR). However, if users' browser are configured to use only just the the base language folders are not populated. If using the French or German translations, please copy files from the regional folders to the base folders and rename/update as per instructions in the administrators guide.
If a Shopper creates an overlapping delivery window on the Shopping website it causes problemsAlthough the Delivery Windows page lets Shoppers create overlapping windows this is not supported by Shopping. These need to be deleted or resized in order for Shopping to process the windows correctly.
Using the name localhost for the Shopping DB server causes problems during installationThe Shopping installer does not support using the name localhost to refer to the Database server. You should use either the text: (local) or type in the server name explicitly in either the interactive installer or when setting the SQLSERVER installer command-line parameter
Computer name in website is sometimes set to the first three digits of the computer's IP addressThe computer name may be displayed as the first three digits of the computer's IP address if reverse DNS lookup is being used but the machine name cannot be resolved correctly. If this occurs please check with the system administrator that the Shopping Agent is installed and that the computer is correctly configured with respect to ConfigMgr and DNS.
After making changes to the Admin-Email parameter in the Shopping Admin Console these are not reflected in the Shopping Web PagesAfter making changes to the Admin-Email parameter in the Shopping Admin Console you will need to perform an iisreset to refresh the Shopping web site to reflect the changes.
Assigning users from another domain causes errors when configuring Shopping Admin Console node security

This issue only affects use of the Shopping Admin Console. Shopping Admin Console does not support AD security groups in one domain that contain AD users, computers, or security groups from another domain.

If you are using Shopping in a multi-domain environment the following items must be in the same AD domain:

  • The AD security groups specified for Shopping Admin Console access in the installer
  • The users that you want to give access to the Shopping Admin Console via Node Security
  • The server or workstation where the Shopping Admin Console is being installed

If this restriction does not suit your requirements you will need to define Shopping Admin Console node security to use multiple groups where each AD security group covers a single domain.

In this case, during installation you must specify an AD security group from the installation domain for each of the Shopping Console Access groups: Shopping Full database access; Shopping Limited database admin access and Shopping Configuration Manager database access.  Then add the other domain security groups by hand post installation as per the instructions Node Security. This requires each of the Shopping Console Access groups to be Universal and not Global Security groups.

Rental Applications are not uninstalled if they are deleted from the Shopping Admin Console during the rental periodWhen making rental Applications available to Shoppers the Shopping Administrator must be careful that any rental Applications they want to remove from Shopping are not currently being rented, otherwise the Application may be left on the Shopper's machine after the rental period.
Errors occur when AD accounts used by Shopping do not have emails definedThe Global-License-Manager field in Shopping Web Settings will be empty if the License Manager account or group provided during installation does not have an email defined.  This means that no email notifications will be sent on license boundary conditions
Problems occur if the Shopping Admin Account is changed post installationIf the default Shopping Admin Account is changed post installation Shopping will not automatically add the changed user to the AD groups to provide necessary access to the Shopping and ConfigMgr databases.  If this is the case, you will need to add the account into these by hand
Updates to Shopping Admin Console WebURL settings are not applied to Central and Receiver servicesIf you update the Web Settings WebUrl value, you will also need to update the server details in the ShoppingInternal setting in the Shopping Central service ShoppingCentral.exe.config file. And ShoppingWebUrl setting in the Shopping Receiver service Shopping.Receiver.exe.config file.
An SMS Site cannot be removed from Shopping if application uninstalls have been requested for machines belonging to that siteIf application uninstalls have been requested from machines belonging to a ConfigMgr site then the Admin Console will now allow the removal of site from Sites. If this occurs you should contact 1E support to guide you through the process of removing the affected site.
Branch Administrators will not be able view applications from another branchIf Branch Administrators happen to login to Shopping from a machine that belongs to another branch not managed by them, then they will not be able view apps specific to the machines branch.
Shopping Receiver running as Network Service account can't connect to Configuration Manager

When the Shopping Receiver is installed to run as "Network Service", with everything configured on the same server the installer thus explicitly adds the "Network Service" into the ConfigMgr security with class rights. This works as expected on Windows 2003. However, on Windows 2008 the shopping receiver comes in as DomainName\Servername$ as if the shopping receiver was connecting from a remote machine and fails.

If this happens, in ConfigMgr Console > Security node, clone the 'NETWORK SERVICE' account created by Shopping Receiver installer for Servername$ and restart Receiver service.

Empty user categories appear to ShoppersUser categories that only contain applications upon which user has no permissions are still visible on the Shopping web portal, by design applications having no permissions upon do not appear to the user so the user category will appear empty.


Issues specific to the Windows Servicing Suite Assistant

IssueDescription
WSA wizard provides an option to restore to the the same machine, if it was captured previously.It is possible to capture the data from a machine and then restore it to the same machine.
Task sequence fails to find the PBA host during execution.

Although WSA ensures the availability of PBA host during its preparation, there is a possibility that the machine is not reachable when the task sequence execution.

  • Enable PBA high availability to reduce the probability of occurrence
  • For Wipe and Load deployments in remote locations, set capture options on admin console to use USB only.
When a Remote user logs on, WSA Wizard doesn't get launched automatically for existing order.This can happen in Remote [VPN] scenarios, when a manual connect VPN is expected to happen as and when user logs back in. In this event, after VPN is connected, launch WSA Wizard explicitly from Shopping portal.
WSA size estimation fails spuriously.This can happen When a content hash check fails for USMT package. In this instance, you will need to inform your administrator.
Content Space Check doesn't check if USB has sufficient free space.When a USB was chosen in the Wizard, it ensures that the chosen USB has enough disk space. After that, there are no checks to ensure that there is enough free space on the USB. If the user fills up the USB outside of WSA manually, then the content download check might fail.
When machine is put to sleep manually and upon logon, WSA wizard indicate spurious failure.This is a timing issue and retrying readiness checks could remediate the issue.
WSA wizard continues to indicate that checks are in progress, after tachyon service has stopped.When Tachyon is started back again, the readiness checks are automatically restarted from the beginning.
Tachyon crashes during service stop, when WSA readiness is in progress.Due to timing issues, readiness checks sometimes does not take appropriate action on service stop and leads to service crash. It doesn't have affect readiness checks functionally and upon starting the service they should get resumed normally.
User fails to launch WSA Wizard from the Shopping portal, after the completion of previous WSA deployment.This can happen when a task sequence execution has actually ended but the Configuration Manager client has not yet updated the task sequence execution status in WMI. Deleting the WMI record will remediate the issue.
WSA wizard's Done button doesn't indicate anything when you click it.If a user clicks on the Done button multiple times, the following error can appear in the tachyon logs: "ERROR - WsaAcknowledgementHandler: No WSA order to acknowledge".
User may not be notified about the status of the deployment, if the task sequence fails.Happens in very rare cases in the event of a bluescreen.
Wipe and Load Non-destructive Task Sequence fails to apply OS, as it fails to delete directory "..\Windows.old\Program Files\WindowsApps".This is a limitation of Configuration Manager. We recommended adding a custom task sequence step to delete those folders before the ApplyOperatingSystem step.
Wipe and Load Non-destructive task sequence files to apply OS, as it is unable to delete files in Windows\System32\wdi\This is a limitation of Configuration Manager. We recommend adding a custom task sequence step to delete those folders before the ApplyOperatingSystem step.
When the Zero touch task sequence fails at the initialize step, the Shopping order remains in the In-progress state and never completes.WSA Initialize could fail if client couldn't connect with shopping server for any reason. After fixing that, administrator could re-run restore TS manually on that machine to complete the deployment. If the TS couldn't be deployed manually, then ensure that Tachyon agent is installed on the machine and upon restarting the service, it would do take the order to completion, so that user can go to shopping portal, launch WSA and restore it manually.
WSA wizard doesn't launch from Firefox, when Shopping is configured to use HTTPS.For self signed certificates, an exception needs to be added to the Firefox browser manually.
After rebooting the machine, Required free space in USB is appearing as '0 GB' for an existing order.This is a limitation of Wizard that it doesn't persist the USB size requirements. If user wants to switch USB, then user should navigate to the page previous to USB page and click on next. That would trigger a new estimation of USB size requirement and after its completion user can choose a different USB.
After rebooting the machine, Applications are not appearing on the summary page for an existing order.Currently this is a limitation of Wizard, to view the applications user can navigate back to applications page.
TS gets stuck on launch, waiting for another program to finish.If another task sequence is run just before the Readiness checks are to complete it get stuck waiting for another program to finish.
WSA TS fails when refreshing from win 10 to win 10 OS [UEFI machine].This is an SCCM issue, work around is to clean up folders in TS before applying OS.
WSA TS fails when the USB goes unrecognizable momentarily.Ensure USB is unplugged during the TS in progress and entire WSA deployment operation.
Tachyon uninstallation doesn't fail, when WSA is in progress and it continues run even after uninstallation.Ensure that WSA wizard isn't running before uninstalling Tachyon.
Task sequence gets stuck on launch, when a pending reboot is detected.Work around is to reboot the machine and the TS will be triggered automatically after reboot soon after the connection is established.
When Capture deployment is ran multiple times on same machine, Restore could incorrectly choose older USMT data.This is due to the limitation of Nomad PBA, which doesn't have a notion of versions. So in case of multiple captures of a machine, a restore might pick a backup data randomly without regard to which is the most recent.
WSA Application Migration page pops up an error, when device is not yet synced with SLA.Cannot proceed with deployment if AppMigration is enabled and the respective machine is not sync with SLA. throws error. Work around is to ensure that the machine is synced with SLA.
WSA launch fails to launch on restored VM's.work around is to unjoin and rejoin domain. Re launch WSA wizard.
Readiness check "Content download Check" gets stuck if USB drive is not available.This is expected behavior of Nomad, which endlessly retries to look for destination. When content download check gets stuck, one of things to look for is to ensure USB is plugged in properly if it is being used. After the USB is plugged in properly, check will continue automatically.
WSA Wizard Readiness checks UI overlaps Windows taskbar when WSA application is moved around the Desktop.If the WSA wizard is partially covered under the taskbar, opening the Details popup on the Readiness page could overlap the taskbar.
WSA Wizard pops up an error on Application Migration page, when name of the machine is longer than 15 characters.Occurs when there are two entries of machine.one machine has different full name and NET BIOS name(full name is - Client2-WindowsX64Enterprise and Net Bios name is - Client2-Windows.
Target Machine is not identified with full domain (e.g. ezio.lab\win10) during WSA Capture.Target PC is recognized only when initial domain name is given with machine name (ezio\win10)

Unable to license Shopping on Hyper-V VM configuration version greater than 8.0.

Unable to license shopping where the host is upgraded to Windows 10 1803 and the guest OS for Shopping is Server 2016. Pleae concact 1E Support if you have this issue.