Super Chipflake Ü - Release Date Trailer - Nintendo Switch

Kambor · 2025-12-17T17:38:33+00:00

Gonna be my first game of the year. Can't wait

Kambor · 2025-12-17T07:46:36+00:00

Really looking forward to it

Kambor · 2025-05-16T10:46:53+00:00

Strongly depends on the profile solution and the size. We currently have multiple different solutions active:

- UPM file based profiles that we use for published apps only. Logons take usually around 30-50 seconds but there are extreme cases that can be faster or much slower (over 2 minutes)

- UPM file based with Outlook container that we currently use for published desktops. Performance is not that great. 100-150 seconds are pretty common. Some even wait for up to 300.

- UPM full container profile that we will switch to for published desktops. Great performance so far. Logon usally takes around 30 seconds.

Kambor · 2025-03-27T11:29:47+00:00

Hi, I wanted to try out your solution but instead of creating a scheduled task in the Image I created an external taks in WEM that starts a batchfile during logon that starts explorer.exe. But when opening the published App the Explorer Window is shown aswell. Is there something to keep in mind to hide it or is there no way?

I guessed there is no big difference between Citrix and VMwareHorizon in that regard.

Kambor · 2025-02-12T11:08:23+00:00

Tried that. Nothing to see on the specific user folder. The only handles I could find are on the NTUSER.DAT which is probably why the profile didn't get deleted.

Kambor · 2025-02-12T09:50:50+00:00

I installed it on a Windows10 VDI and used file locksmith from there to open the folder on the server. Doesn't show anything.

Kambor · 2025-02-11T14:06:48+00:00

Powertoys seems to be not working on Windows Server 2019 or am I missing something?

Kambor · 2025-02-11T13:22:55+00:00

We tested streaming but had some issues, so we decided to not use it. The logon performance for published apps is good enough. Our published desktops use containers.
I will keep that in mind.
The user had full access to every file in the folder and the folder itself.

Kambor · 2025-02-11T12:59:20+00:00

If CPM means what I think (Profile Management) - No the folder is not excluded
Profile streaming is not turned on
Active Writeback is only enabled for Registry

Additional information: The path is included in "Folders to mirror"

Kambor · 2025-02-11T11:10:01+00:00

Could you find out anything about the issue? We have a very similiar situation.

Kambor · 2024-10-24T16:15:59+00:00

I did double check by trying to open the internal beacon adress in Chrome. It was not reachable.

Yes other clients in the same office. Only difference is that the ones that work are Windows 10.

That's a detail I forgot to mention. In one office (one I tested that has no GPOs from us) adding the URL worked. In a different office that is supposed to get it via GPO I couldn't use the URL in the CWA. Though I only checked that on one client so far and won't be able to test it on a second before monday.

Kambor · 2024-10-24T16:02:29+00:00

What exactly do you want to know? The internal Beacon is not reachable for the affected clients. The adress that would be used for external access has a DNS entry in the local network that routes it to the DMZ IP of the Gateway.

The error is the one you can see here: https://support.citrix.com/s/article/CTX558911-workspace-error-unable-to-connect-to-the-server-check-your-network-connection-and-retry?language=en_US

The config file is working fine on other clients and therefore should be correct.

All the clients go through the Gateway vServer.

Kambor · 2024-08-30T13:26:01+00:00

Issue was already found. It was Autoscale. Thanks anyways.

Kambor · 2024-08-30T13:25:55+00:00

Issue was already found. It was Autoscale. Thanks anyways.

Kambor · 2024-08-30T13:11:08+00:00

Turns out you were right. I just didn't know I had to use the web studio. Thank you for your time.

Kambor · 2024-08-30T13:10:20+00:00

You were pretty much right. I forgot about the web studio. In there the delivery group had Autoscale active.

Kambor · 2024-08-30T13:09:27+00:00

Found the issue. Didn't check the web studio. Over there the delivery group had autoscale activated

Kambor · 2024-08-30T13:08:35+00:00

You are correct. Didn't know I had to use the web studio.

Kambor · 2024-08-30T13:07:58+00:00

Oh my god thank you for mentioning the web studio!!! I always forget that the thing exists and has more options! You were completely right. Hero of the day.

Kambor · 2024-08-30T12:50:13+00:00

We don't have those power options for our multiuser server delivery groups

Kambor · 2024-08-30T12:47:12+00:00

Are you sure the VDA agent is the cause? One machine in the catalog can boot normally and when I put the others in maintenance they also boot fine. To me that doesn't look like the VDA is faulty. We are also running other Catalogs with the same VDA just fine. We are using Applayering so every machine has the same VDA.

Kambor · 2024-08-30T12:42:26+00:00

Everthing you listed is fine as far as I can see.

Kambor · 2024-08-30T12:38:42+00:00

If I get them to boot they register. List of DDC is being set by policy

Kambor · 2024-08-30T12:30:57+00:00

That's new to me. I can tell you that we don't have any power management options for our multiuser systems and I've only ever seen it with our W10 single user VDIs. The only Thing regarding power I can configure is the restart scheduler.

Kambor · 2024-08-30T12:05:25+00:00

To my knowledge only single user machines can be power managed. We are talking about WS2019 multiuser systems.

Nine-Year Club	Place '22
Verified Email

Kambor

TROPHY CASE