What Are You Doing Right Now
-
@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.
-
@DustinB3403 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 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.
Yep. Said performance is for folks on our LAN here. I can't imagine what's it like for people connecting to us over our WAN. XA isn't technically my area of concern, but what I do crosses over into it from time to time.
-
@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 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
I figure whatever we have isn't indicative typical XenApp performance.
-
updating my multi boot USB with some updated ISO images
-
@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 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
Agreed - somethign is really broken in your environment.
-
@Dashrender 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 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
Agreed - somethign is really broken in your environment.
There are a multitude of problems
-
@EddieJennings said in What Are You Doing Right Now:
@Dashrender 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 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
Agreed - somethign is really broken in your environment.
There are a multitude of problems
Build a completely new environment, group policy and everything totally separate from everything else.
-
@wirestyle22 said in What Are You Doing Right Now:
@EddieJennings said in What Are You Doing Right Now:
@Dashrender 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 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
Agreed - somethign is really broken in your environment.
There are a multitude of problems
Build a completely new environment, group policy and everything totally separate from everything else.
Ha! Not going to happen. At least not in my professional lifetime. But I agree, ground-up rebuild would likely benefit us.
-
@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:
@Dashrender 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 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
Agreed - somethign is really broken in your environment.
There are a multitude of problems
Build a completely new environment, group policy and everything totally separate from everything else.
Ha! Not going to happen. At least not in my professional lifetime. But I agree, ground-up rebuild would likely benefit us.
If someone said this to me before I went through it i'd say the same thing, but it was actually easier than you'd think
-
Just surviving through a case of the Mondays!
-
@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 said in What Are You Doing Right Now:
@Dashrender 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 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
Agreed - somethign is really broken in your environment.
There are a multitude of problems
Build a completely new environment, group policy and everything totally separate from everything else.
Ha! Not going to happen. At least not in my professional lifetime. But I agree, ground-up rebuild would likely benefit us.
If someone said this to me before I went through it i'd say the same thing, but it was actually easier than you'd think
It likely wouldn't be that daunting of a technical task, but as I've learned from the last year, some of our greatest IT challenges are not technical.
-
Took a nice family picture at my little brothers wedding and I realized that his face looks like the troll face. It is now a reaction meme in my family
