What Are You Doing Right Now
-
It is morning here in Tuscany. Having some espresso and catching up with you guys. My Internet is terrible so I cannot upload anything or download anything. And much of the time I cannot load ML threads. But when I can, I'm getting caught up.
It is SO hot, OMG.
-
Sitting at the local coffee shop because I got tired of waiting for the maintenance people to come look at my air conditioner
-
@travisdh1 said in What Are You Doing Right Now:
Sitting at the local coffee shop because I got tired of waiting for the maintenance people to come look at my air conditioner
We’ve been stuck using a portable ac and fans because the evap is toast. I was hoping it will survive until we get our new HVAC installed in about two weeks.
-
back from dinner. This trip is burning me out. My plan is to skip things tomorrow and just drop the family in Firenze and spend the day alone at the apartment.
-
Waiting...
-
Dinner is cooking. It's been a long day. I've had basically no sleep for two days. No idea if I will be able to sleep tonight. Very stressed.
If things go well, I will get to see Firenze tomorrow.
-
We came so close to dying tonight in 5e. all lvl 2 fighting something we shouldn't have been able to kill at that level. wild magic sorcerer rolls a 10 and lvl 5 magic magic missiles the thing to death. Legendary. All of us were one hit away from death.
-
Actually managed to sleep last night! No CPAP, but made due and feeling well.
-
@scottalanmiller Laura woke me up five times last night and then at 4:00 AM the cat was crying for food. I can't win
-
Another week. More fun times with Cisco AMP.
-
@EddieJennings AMP was pretty cool when I played with it.
-
@wirestyle22 said in What Are You Doing Right Now:
@EddieJennings AMP was pretty cool when I played with it
Our XenApp environment seems to be allergic to it.
-
@EddieJennings That's good to know. How much additional network traffic are you seeing?
-
@wirestyle22 said in What Are You Doing Right Now:
@EddieJennings That's good to know. How much additional network traffic are you seeing?
The root cause of the problem still has yet to be determined. I believe the issue is the disk IO caused on the VMs serving up the XenApp applications. After the initial catastrophe of deployment, we're slowly enabling the AMP service on silos one by one. We did one of our bigger silos on Thursday of last week, and yet again, its applications were brought to their knees.
-
@EddieJennings what were the issues with your deployment? AMP related or just XA? I just deployed a new environment here and we have yet to have any issues
-
@wirestyle22 said in What Are You Doing Right Now:
@EddieJennings what were the issues with your deployment? AMP related or just XA? I just deployed a new environment here and we have yet to have any issues
- Getting AMP properly installed on the golden images used by the XA streamed servers was a grave challenge.
- General terrible performance for users of applications served by XA (beyond normal the normal terrible that XA is).
- When the terrible from #1 is occurring, the VMs serving up the applications eventually become non-responsive -- killing the AMP service solves this.
- The MAP engine within amp, caused crash of our main file server. MAP is now disabled for that server, and has been disabled for the XA servers at TAC's suggestion for performance problems.
For non XA streamed servers, AMP seems to be doing its job and those servers are performing normally, though there are some one-off issues with deployment of the connector via SCCM.
-
@EddieJennings said in What Are You Doing Right Now:
@wirestyle22 said in What Are You Doing Right Now:
@EddieJennings what were the issues with your deployment? AMP related or just XA? I just deployed a new environment here and we have yet to have any issues
- Getting AMP properly installed on the golden images used by the XA streamed servers was a grave challenge.
- General terrible performance for users of applications served by XA (beyond normal the normal terrible that XA is).
- When the terrible from #1 is occurring, the VMs serving up the applications eventually become non-responsive -- killing the AMP service solves this.
- The MAP engine within amp, caused crash of our main file server. MAP is now disabled for that server, and has been disabled for the XA servers at TAC's suggestion for performance problems.
For non XA streamed servers, AMP seems to be doing its job and those servers are performing normally, though there are some one-off issues with deployment of the connector via SCCM.
My environment is extremely responsive. Not sure what the "normal terrible" would be
-
@wirestyle22 said in What Are You Doing Right Now:
@EddieJennings said in What Are You Doing Right Now:
@wirestyle22 said in What Are You Doing Right Now:
@EddieJennings what were the issues with your deployment? AMP related or just XA? I just deployed a new environment here and we have yet to have any issues
- Getting AMP properly installed on the golden images used by the XA streamed servers was a grave challenge.
- General terrible performance for users of applications served by XA (beyond normal the normal terrible that XA is).
- When the terrible from #1 is occurring, the VMs serving up the applications eventually become non-responsive -- killing the AMP service solves this.
- The MAP engine within amp, caused crash of our main file server. MAP is now disabled for that server, and has been disabled for the XA servers at TAC's suggestion for performance problems.
For non XA streamed servers, AMP seems to be doing its job and those servers are performing normally, though there are some one-off issues with deployment of the connector via SCCM.
My environment is extremely responsive. Not sure what the "normal terrible" would be
Greater than a minute to open an application from a Dell WYSE terminal. I'm sure there are usable XenApp environments out there. My first experience with one has been underwhelming at best. Honestly, I'm surprise there hasn't been some kind of user revolt in the last X years, where X equals the number of years XenApp has been used here.
-
@EddieJennings said in What Are You Doing Right Now:
@wirestyle22 said in What Are You Doing Right Now:
@EddieJennings said in What Are You Doing Right Now:
@wirestyle22 said in What Are You Doing Right Now:
@EddieJennings what were the issues with your deployment? AMP related or just XA? I just deployed a new environment here and we have yet to have any issues
- Getting AMP properly installed on the golden images used by the XA streamed servers was a grave challenge.
- General terrible performance for users of applications served by XA (beyond normal the normal terrible that XA is).
- When the terrible from #1 is occurring, the VMs serving up the applications eventually become non-responsive -- killing the AMP service solves this.
- The MAP engine within amp, caused crash of our main file server. MAP is now disabled for that server, and has been disabled for the XA servers at TAC's suggestion for performance problems.
For non XA streamed servers, AMP seems to be doing its job and those servers are performing normally, though there are some one-off issues with deployment of the connector via SCCM.
My environment is extremely responsive. Not sure what the "normal terrible" would be
Greater than a minute to open an application from a Dell WYSE terminal. I'm sure there are usable XenApp environments out there. My first experience with one has been underwhelming at best. Honestly, I'm surprise there hasn't been some kind of user revolt in the last X years, where X equals the number of years XenApp has been used here.
That's insane. Mine is sub 3 seconds
-
@EddieJennings said in What Are You Doing Right Now:
@wirestyle22 said in What Are You Doing Right Now:
@EddieJennings said in What Are You Doing Right Now:
@wirestyle22 said in What Are You Doing Right Now:
@EddieJennings what were the issues with your deployment? AMP related or just XA? I just deployed a new environment here and we have yet to have any issues
- Getting AMP properly installed on the golden images used by the XA streamed servers was a grave challenge.
- General terrible performance for users of applications served by XA (beyond normal the normal terrible that XA is).
- When the terrible from #1 is occurring, the VMs serving up the applications eventually become non-responsive -- killing the AMP service solves this.
- The MAP engine within amp, caused crash of our main file server. MAP is now disabled for that server, and has been disabled for the XA servers at TAC's suggestion for performance problems.
For non XA streamed servers, AMP seems to be doing its job and those servers are performing normally, though there are some one-off issues with deployment of the connector via SCCM.
My environment is extremely responsive. Not sure what the "normal terrible" would be
Greater than a minute to open an application from a Dell WYSE terminal. I'm sure there are usable XenApp environments out there. My first experience with one has been underwhelming at best. Honestly, I'm surprise there hasn't been some kind of user revolt in the last X years, where X equals the number of years XenApp has been used here.
That's just people being complacent with the performance they've been given and the response from the IT team who manages it.
