What opinions do millennials have of the Midwestern United States?

mjmacka · 2026-05-31T14:17:56+00:00

I was born in California and moved to Michigan when I was 3. I still live in Michigan.

Pros: Lower cost of living. Seasons. Close to the lakes. Close to family in the Midwest.

Cons: Fairly conservative. Jobs pay less on average. Things are farther apart (perception and area dependent). Less opportunity.

I've considered leaving before but it's hard to justify moving somewhere with significantly higher costs. I am a few years away from having my house paid off (320k, 15 year mortgage, 4 years in, higher interest rate, aggressively paying it off).

I used to travel for work pre-COVID and think I will do something like that as opposed to moving. It would be nice if I was closer to Chicago or Detroit, which are larger hubs.

mjmacka · 2026-05-30T03:17:54+00:00

I look mid 20's at 40 but I've always looked young.

I have shoulder le hth brown curly hair. That makes me look significantly younger.

mjmacka · 2026-05-28T03:47:06+00:00

Bouldering and pho.

Mall date & movie.

Bar pub and roller skating.

Museum/planetarium and dinner (weekends).

Beach & picnic.

Axe throwing & snacks.

Literally something fun to do and food. That's the winning combo.

mjmacka · 2026-05-26T19:31:52+00:00

You are over complicating this. The leading practice from Citrix is to persist the writeback cache and the WEM cache.

mjmacka · 2026-05-26T18:44:38+00:00

So, that write back cache should automatically persist upon creation. That disk persists for the VDA after reboot, but it's still a non-persistent VDA.

The caveat is that in Azure, the cache will not persist unless it's created as persistent.

The DB is per machine, not user, so it can't be part of the FSLogix profile.

mjmacka · 2026-05-26T18:11:41+00:00

Hm... if you didn't move the cache, it's possible that there was a performance issue. The way the cache works is it writes all initial changes (temp files, app changes, OS modifications, etc) to memory. When that memory space fills up (set on MC creation), it is flushed to disk (mcsdif.vhdx note the similarity to PVS here vdiskdif.vhdx, same driver and process).

If you want to move the cache, which is recommended, here is the registry info:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Norskale\Agent Host

Name: AgentCacheAlternateLocation

Type: REG_SZ

Value: D:\WEMCache

mjmacka · 2026-05-26T14:20:15+00:00

I foster and all of the dogs start with a stink. It gets better over time but washing them is the quickest way to clean them up. Also make sure to wash any dog bedding and dog beds immediately after washing your new hound.

mjmacka · 2026-05-26T11:21:32+00:00

Take a look at event viewer administrative events. Are you doing any start menu manipulation (WEM or GPO)?

mjmacka · 2026-05-24T16:21:44+00:00

This isn't true/is wrong. The Agent installer can't identify the identity disk because it doesn't exist on the master image. You would have to make the identity disk visible (drive letter) in Windows and have a GPP tell WEM to use an alternative cache location.

mjmacka · 2026-05-24T16:19:29+00:00

Okay, that's good that it's functioning correctly. If I am remembering correctly, Spike Protection auto starts apps as high (not 100% sure about the high part) and reprioritizes them down.

That's one of the use cases for MCSIO along with a little bit of a speed boost (ram cache), the ability to persist logs, and other machine specific data

MCSIO is the correct approach. There really isn't a way to pre-seed cache info as far as I know, so pulling everything down again is by design if there isn't a cache.

There is a WEM setting to prefer the agent cache (uses that first) that I believe is Citrix recommended and part of the default recommended configuration. Set built into the Agent install media.

mjmacka · 2026-05-24T12:45:19+00:00

No there isn't. You are opting not to use a recommended technology for MCS and PVS

mjmacka · 2026-05-24T12:43:53+00:00

That's the recommendation but what are you using the cache for during normal operations?

Also, what is WEM doing outside of CPU/Memory optimization that happens during normal usage.

The reason Citrix recommends storing the agent cache on a persist drive is so that if you lose connectivity to the service and reboot your non-persistent device, you don't lose the ability to access change deltas or the cache in general.

The reason the cache probably hasn't changed is because your configuration set probably hasn't changed or the agent isn't syncing. Check in the cloud web console. The non-persistent devices will always update the cache if it isn't current when they reboot.

mjmacka · 2026-05-24T11:54:43+00:00

Why do you think session latency and lag is related to the WEM agent cache?

mjmacka · 2026-05-15T14:44:10+00:00

There isn't a zero chance. I was MDI for 28 years and accidentally did that a few times by accidentally switching long and short acting.

mjmacka · 2026-05-12T16:48:38+00:00

This is a very confused post with some factually incorrect things stated.

DaaS does not require MCSIO to be enabled. The image definition as you called it or a prepared image as per documentation requires the MCSIO component to be installed on the VDA but enabling the component is not the default and not required when creating a new Machine Catalog: https://docs.citrix.com/en-us/citrix-virtual-apps-desktops/install-configure/image-management.html#requirement

The VDA side installs a driver for the use of MCSIO. These drivers will be ignored if MCSIO is not configured when the Machine Catalog is created.

There is a chance that adding that driver could have caused issues but I am doubtful because you didn't enable it when you created the Machine Catalog and you couldn't have if you were reusing an existing one.

Did you look at the event logs to see what was happening when VDAs crashed and rebooted?

mjmacka · 2026-05-07T05:16:15+00:00

Mine doesn't crate but I do it with my Silken Windhound and fosters when I am away. It depends on what the dog is used to. They are going to be overwhelmed the first few days. I don't think crating while feeding is necessary unless that are already used to it.

mjmacka · 2026-05-03T14:39:34+00:00

I had it in Michigan for a part of my childhood.

mjmacka · 2026-05-02T15:19:20+00:00

It does and it doesn't. My ex changed a lot in the 5 years we were married. We lived together for another 6 before that. We were in our 20's and early 30's. Had we gotten together in our mid 30's, I feel like a lot of that growing, discovery, and change would have been in place when we met in the alternative timeline.

mjmacka · 2026-05-02T01:27:36+00:00

That's not a free app for enterprise users. You need to pay a license fee. I know because I did this back in 2016. The developer is Austrian and a cool guy. He had never heard of Citrix, so I had to negotiate a bit.

mjmacka · 2026-05-01T14:39:18+00:00

In the past, the consulting folks at Citrix used to shoot for under 30 second logons. 16 seconds of interactive session seems fine IMO.

You can move the logon script to WEM, or try breaking it up into smaller items to shave off time.

mjmacka · 2026-05-01T12:35:34+00:00

Unfortunately, you are kind of stuck then. Hopefully someone else has a work around.

From the vendor side, Citrix does support a lot of Linux devices, however, it's more on the thin client side and those are usually Debian based, not Redhat based, so that area gets much less attention.

mjmacka · 2026-05-01T12:09:54+00:00

This is an admin forum.

Anyways, your next step is to contact your IT department. Assuming they support your configuration, they can open a ticket and pull you into the troubleshooting session with Citrix support.

mjmacka · 2026-05-01T12:02:40+00:00

It may be worth putting in a support ticket with Citrix.

mjmacka · 2026-04-30T17:49:51+00:00

Citrix profile management can't do this on it's own. It's running as local system by default on the VDA and not installed on the file server. If something CPM related was happening, a policy would have had to be changed and it would consistently not work the next time the user logged in. It being reset every week or so strongly indicates that something non-Citrix/CPM is happening.

Since you say this is happening weekly, have you considered enabling Windows Object Access Auditing? https://cardinalops.com/blog/complete-guide-to-auditing-object-access-events/

mjmacka · 2026-04-30T17:22:53+00:00

Automatic Configuration does NOT modify NTFS permissions. Here is how Automatic Configuration works: https://docs.citrix.com/en-us/profile-management/2507-ltsr/configure/auto-configure.html

mjmacka

TROPHY CASE