[RESOLVED] Z: drive and domain allowlisting unavailable - Workaround for Z:
The Z: drive was not visible in the myDRE Workspaces due to an issue at Microsoft leaving proxy instances in an unhealthy state. The issue has been resolved. We apologise for any inconvenience this might cause you.
On 2023-03-23 at 18:26 (Amsterdam Time Zone), we received the first ticket regarding the Z: drive being invisible within the VM.
The myDRE platform is built on Microsoft Azure. On 2023-03-23 Microsoft admitted Azure Resource Manager failed after code change.
Azure Resource Manager (ARM) provides a centralized way to manage and deploy resources in Azure, allowing for efficient management and automation of resources. There was a pipeline run that usually configures DRE environment. That pipeline is supposed to be incremental, and not overwrite existing configurations. Due to the ARM issue at Microsoft it ran and overwrote the firewall and other resource configurations and left them in unusable freshly deployed state. So far, we have only seen that the proxy server is affected by this issue but there might be other resources. The proxy server is needed for seeing the Z: drive and domain allowlisting.
The anDREa development team has re-run the resource specific scripts and deployments to try and restore their desired state. The issue has been resolved.
Workaround (no longer needed)
- In your VM go to the magnifying glass on the bottom left and type 'proxy settings' and click on Change proxy settings. Under Manual proxy setup turn Use a proxy server to Off.
- Open File Explorer and go to This PC > Windows (C:) > Scripts. Run the script MountStorageDrivetoVirtualMachine with Powershell. You should then have access to your Z: drive again. Currently, there is no workaround for domain allowlisting.
So far, we have received 6 support tickets regarding this issue. However, this impacts all Workspaces, as all Workspaces make use of the proxy.
As this was an issue on Microsoft's end and myDRE depends on Microsoft Azure, there is not much we can do prevent this issue from happening.
Event log - real time updates
2023-03-24 @ 10:42
The proxy instances are stable again. The Z: drive should be visible again and domain allowlisting should be possible again. If your VM was already running, you might need a restart to see the Z: drive again. Please submit a ticket if this is not the case.
2023-03-24 @ 09:58
Root cause identified. The anDREa development team is working on a solution. A workaround to access your Z: drive is posted. The next update will follow at 11:00 (Amsterdam Time Zone).
2023-03-23 @ 18:26
Issue first reported. Root cause investigation started shortly after.
[Resolved] Z: drive unavailable for a short period
Version: 2023-01-19 TL;DR The Z: drive was not visible in the myDRE Workspaces due to the push of an incorrect configuration file. The issue has been resolved. We apologise for any inconvenience this might have caused you. What happened? On ...
Z:-drive not available in newly created VM from image
Bug description A VM based on an image does not mount the Z-drive for those who were part of the VM from which the image was created. However this is visible: Related to: Create VM-templates for your Workspace Creating VM images for Shared Gallery ...
[Resolved] Data drive not accessible
Version: 2022-12-12 Updated: 2022-12-13 TL;DR TL;DR: Some myDRE Workspaces experienced an issue regarding the availability of the data drive. It has been resolved, the workaround is no longer needed. We apologise for any inconvenience this might ...
Domain and IP Allowlisting [External Access]
Roles for External Access in the Workspace Accountable and Privileged: Read + Write Advanced: Read only Rest All: No access Platform Support Team (PST members): Read + Write These steps will be performed only by the Accountable and Privileged Member ...
RESOLVED: File Share not accessible
The issue A number of users experience after the migrations the following: No files/folders visible in the Files Tab No share with files/folders visible in the VM The above is an access issue, no data is lost. Update: 2021-03-25 @12:39 Root cause ...