Attention: Confluence is not suitable for the storage of highly confidential data. Please ensure that any data classified as Highly Protected is stored using a more secure platform.
If you have any questions, please refer to the University's data classification guide or contact ict.askcyber@sydney.edu.au

Skip to end of banner
Go to start of banner

Argus Known Issues and Self-Support

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

This section contains Argus’s known issues and self-support information.

Desktop is frozen or feels like it crashed:

ReasonSolution
This mostly happens due to poor Wifi or Network Connectivity from your Local Client to Argus-VRD.Users are advised to use Ethernet over WiFi, if available Or move to a location where you can get good WiFi signal. 

Desktops are Laggy and are unusable:

ReasonSolution
Using University VPN to Access VRD

This is not recommened approach to access VRD. Browse to argus.sydney.edu.au using Google Chrome, Mozilla Firefox IE via your standard Cable/Broadband Network or University network to access VRD. Click on the Desktop/Monitor Icon to access VRD using Citrix Workspaces App.

Poor wifi or Network connectivity.

Try accessing VRD from a different plugged in Ethernet cable port.

Citrix Receiver is no longer supported by vendor and is replaced with Citrix Workspace App.

Please make sure you are using Citrix Workspace app. If you are using Citrix Receiver, uninstall Citrix Receiver and install Citrix Workspace App.  

Note: If you come across issues uninstalling Citrix Receiver on Windows local client, please use Receiver Cleanup Utility (ReceiverCleanupUtility-Windows.zip)  to uninstall Citrix Receiver.

Desktop Disconnects (crashes) while copying files from my USB device connect to local client:

USB 2.0 is not supported. Trying to copy files from USB 2.0 connected devices to your local client devices to VRD will disconnect your Desktop session.

Try re-launch desktop, your session will be at a point it disconnected. 


Can't start desktop Example: "WIN10-YourMachineName":


If you encounter this issue it probably means that someone else is logged on to the current machine.

Only an admin user can see who is logged on and end their session. This is done through https://argus-director.sydney.edu.au/ as described in User Management, Click on the Filters Menu > Sessions > All Sessions, locate the user/machine in the list and select them and then Log them Off through the "Session Control" button. 

Unable to access to argus portal

If you are unable to access argus portal, please make sure to check below points:

  1. Make sure your account/unikey exists in SHARED Domain.
  2. Make sure your unikey is not locked out.
  3. Make sure you are entering your username and password correct.

Argus Desktop Screen does not look right:

Argus Linux VRD's may display desktop display similar to below screen shot.

To fix this, click on "Full screen" icon on Citrix Viewer on top.


Grey screen when launching Argus Redhat desktops

When launching an Argus Redhat desktop for the first time, or relaunching after a period of time, you will see a grey screen. Sometimes this screen will be displayed for about 15-30 seconds before you see the desktop. Please be patient and wait until you see the Redhat desktop.

Initialization failed error when launching Argus desktops from Mac computers

If you receive “Initialization failed” error while launching Argus desktop from a Mac computer, please make sure you have the latest Citrix Workspace App installed.

“Your session could not be established” error when logging into argus.sydney.edu.au

If you received “Your session could not be established” error on argus.sydney.edu.au login page, please follow below steps for troubleshooting.

  1. Make sure the unikey and password provided in the Username and Password fields are correct.
  2. Click on "click here" link on the page (highlighted in blue) to start a new session and try re-enter your unikey and password.
  3. Check your unikey account in shared domain is not locked out with service desk.

  • No labels