ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    What Are You Doing Right Now

    Water Closet
    time waster
    285
    88.9k
    41.3m
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • EddieJenningsE
      EddieJennings @wirestyle22
      last edited by

      @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

      1. Getting AMP properly installed on the golden images used by the XA streamed servers was a grave challenge.
      2. General terrible performance for users of applications served by XA (beyond normal the normal terrible that XA is).
      3. When the terrible from #1 is occurring, the VMs serving up the applications eventually become non-responsive -- killing the AMP service solves this.
      4. 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.

      wirestyle22W 1 Reply Last reply Reply Quote 0
      • wirestyle22W
        wirestyle22 @EddieJennings
        last edited by

        @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

        1. Getting AMP properly installed on the golden images used by the XA streamed servers was a grave challenge.
        2. General terrible performance for users of applications served by XA (beyond normal the normal terrible that XA is).
        3. When the terrible from #1 is occurring, the VMs serving up the applications eventually become non-responsive -- killing the AMP service solves this.
        4. 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

        EddieJenningsE 1 Reply Last reply Reply Quote 0
        • EddieJenningsE
          EddieJennings @wirestyle22
          last edited by

          @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

          1. Getting AMP properly installed on the golden images used by the XA streamed servers was a grave challenge.
          2. General terrible performance for users of applications served by XA (beyond normal the normal terrible that XA is).
          3. When the terrible from #1 is occurring, the VMs serving up the applications eventually become non-responsive -- killing the AMP service solves this.
          4. 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.

          wirestyle22W DustinB3403D 2 Replies Last reply Reply Quote 0
          • wirestyle22W
            wirestyle22 @EddieJennings
            last edited by

            @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

            1. Getting AMP properly installed on the golden images used by the XA streamed servers was a grave challenge.
            2. General terrible performance for users of applications served by XA (beyond normal the normal terrible that XA is).
            3. When the terrible from #1 is occurring, the VMs serving up the applications eventually become non-responsive -- killing the AMP service solves this.
            4. 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

            EddieJenningsE DashrenderD 2 Replies Last reply Reply Quote 1
            • DustinB3403D
              DustinB3403 @EddieJennings
              last edited by

              @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

              1. Getting AMP properly installed on the golden images used by the XA streamed servers was a grave challenge.
              2. General terrible performance for users of applications served by XA (beyond normal the normal terrible that XA is).
              3. When the terrible from #1 is occurring, the VMs serving up the applications eventually become non-responsive -- killing the AMP service solves this.
              4. 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.

              EddieJenningsE 1 Reply Last reply Reply Quote 0
              • EddieJenningsE
                EddieJennings @DustinB3403
                last edited by

                @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

                1. Getting AMP properly installed on the golden images used by the XA streamed servers was a grave challenge.
                2. General terrible performance for users of applications served by XA (beyond normal the normal terrible that XA is).
                3. When the terrible from #1 is occurring, the VMs serving up the applications eventually become non-responsive -- killing the AMP service solves this.
                4. 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.

                1 Reply Last reply Reply Quote 0
                • EddieJenningsE
                  EddieJennings @wirestyle22
                  last edited by

                  @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

                  1. Getting AMP properly installed on the golden images used by the XA streamed servers was a grave challenge.
                  2. General terrible performance for users of applications served by XA (beyond normal the normal terrible that XA is).
                  3. When the terrible from #1 is occurring, the VMs serving up the applications eventually become non-responsive -- killing the AMP service solves this.
                  4. 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.

                  1 Reply Last reply Reply Quote 0
                  • hobbit666H
                    hobbit666
                    last edited by

                    updating my multi boot USB with some updated ISO images

                    1 Reply Last reply Reply Quote 0
                    • DashrenderD
                      Dashrender @wirestyle22
                      last edited by

                      @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

                      1. Getting AMP properly installed on the golden images used by the XA streamed servers was a grave challenge.
                      2. General terrible performance for users of applications served by XA (beyond normal the normal terrible that XA is).
                      3. When the terrible from #1 is occurring, the VMs serving up the applications eventually become non-responsive -- killing the AMP service solves this.
                      4. 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.

                      EddieJenningsE 1 Reply Last reply Reply Quote 0
                      • EddieJenningsE
                        EddieJennings @Dashrender
                        last edited by

                        @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

                        1. Getting AMP properly installed on the golden images used by the XA streamed servers was a grave challenge.
                        2. General terrible performance for users of applications served by XA (beyond normal the normal terrible that XA is).
                        3. When the terrible from #1 is occurring, the VMs serving up the applications eventually become non-responsive -- killing the AMP service solves this.
                        4. 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 😛

                        wirestyle22W 1 Reply Last reply Reply Quote 0
                        • wirestyle22W
                          wirestyle22 @EddieJennings
                          last edited by

                          @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

                          1. Getting AMP properly installed on the golden images used by the XA streamed servers was a grave challenge.
                          2. General terrible performance for users of applications served by XA (beyond normal the normal terrible that XA is).
                          3. When the terrible from #1 is occurring, the VMs serving up the applications eventually become non-responsive -- killing the AMP service solves this.
                          4. 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.

                          EddieJenningsE 1 Reply Last reply Reply Quote 0
                          • EddieJenningsE
                            EddieJennings @wirestyle22
                            last edited by

                            @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

                            1. Getting AMP properly installed on the golden images used by the XA streamed servers was a grave challenge.
                            2. General terrible performance for users of applications served by XA (beyond normal the normal terrible that XA is).
                            3. When the terrible from #1 is occurring, the VMs serving up the applications eventually become non-responsive -- killing the AMP service solves this.
                            4. 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.

                            wirestyle22W 1 Reply Last reply Reply Quote 1
                            • wirestyle22W
                              wirestyle22 @EddieJennings
                              last edited by

                              @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

                              1. Getting AMP properly installed on the golden images used by the XA streamed servers was a grave challenge.
                              2. General terrible performance for users of applications served by XA (beyond normal the normal terrible that XA is).
                              3. When the terrible from #1 is occurring, the VMs serving up the applications eventually become non-responsive -- killing the AMP service solves this.
                              4. 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

                              EddieJenningsE 1 Reply Last reply Reply Quote 0
                              • dafyreD
                                dafyre
                                last edited by

                                Just surviving through a case of the Mondays!

                                1 Reply Last reply Reply Quote 1
                                • EddieJenningsE
                                  EddieJennings @wirestyle22
                                  last edited by

                                  @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

                                  1. Getting AMP properly installed on the golden images used by the XA streamed servers was a grave challenge.
                                  2. General terrible performance for users of applications served by XA (beyond normal the normal terrible that XA is).
                                  3. When the terrible from #1 is occurring, the VMs serving up the applications eventually become non-responsive -- killing the AMP service solves this.
                                  4. 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.

                                  1 Reply Last reply Reply Quote 0
                                  • wirestyle22W
                                    wirestyle22
                                    last edited by

                                    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
                                    snide.jpg

                                    1 Reply Last reply Reply Quote 4
                                    • scottalanmillerS
                                      scottalanmiller
                                      last edited by

                                      Just back to the apartment from a day of touring Firenze. Learned to make pasta from scratch today. That was so much fun. Heading to Switzerland and Paris tomorrow.

                                      wrx7mW 1 Reply Last reply Reply Quote 1
                                      • wrx7mW
                                        wrx7m @scottalanmiller
                                        last edited by

                                        @scottalanmiller said in What Are You Doing Right Now:

                                        Just back to the apartment from a day of touring Firenze. Learned to make pasta from scratch today. That was so much fun. Heading to Switzerland and Paris tomorrow.

                                        Oh, nice! Fresh pasta is so much better.

                                        scottalanmillerS 1 Reply Last reply Reply Quote 1
                                        • scottalanmillerS
                                          scottalanmiller @wrx7m
                                          last edited by

                                          @wrx7m said in What Are You Doing Right Now:

                                          @scottalanmiller said in What Are You Doing Right Now:

                                          Just back to the apartment from a day of touring Firenze. Learned to make pasta from scratch today. That was so much fun. Heading to Switzerland and Paris tomorrow.

                                          Oh, nice! Fresh pasta is so much better.

                                          It was amazing. I'm so glad to be able to make it now.

                                          1 Reply Last reply Reply Quote 0
                                          • EddieJenningsE
                                            EddieJennings
                                            last edited by

                                            Fun times practicing creating senarios using file ACLs for RHCSA objectives. 🙂

                                            1 Reply Last reply Reply Quote 0
                                            • 1
                                            • 2
                                            • 3670
                                            • 3671
                                            • 3672
                                            • 3673
                                            • 3674
                                            • 4443
                                            • 4444
                                            • 3672 / 4444
                                            • First post
                                              Last post