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

    Converting to a virtual environment

    Scheduled Pinned Locked Moved IT Discussion
    157 Posts 15 Posters 33.4k Views
    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.
    • V
      Veet @scottalanmiller
      last edited by

      @scottalanmiller said in Converting to a virtual environment:

      @Veet said in Converting to a virtual environment:

      @scottalanmiller

      This is precisely what we were discussing in the "Starting own IT consultancy .." thread ...

      This kind of crap happens all the time ..

      I recollect an instance, when a vendor went as far as to insist that the compute-name of the Server be a specific one (I think it was the name of their product), or ELSE, the application would not work properly .... Luckily, this was one of the rare occasions when the client backed us, instead of the vendor... I put my sparring gloves on, and TKO'ed the vendor.

      Wow, just... wow. I wonder if anyone thought to ask if it was the hostname or a DNS entry or the NetBIOS name 😉

      I'll explain ...

      The client side of the application, obviously needed to be pointed to the server via the hostname of the server ...Once it so happened that we installed a new desktop, and could could not connect to the product's tech support, to have them install the client app... So, we went ahead and installed it .. Upon starting-up the app, we were confronted with a "Server not found error" ... Upon digging around a bit, we discovered that the installation folder contained an ".ini" file, with the hostname of the server, and database path, predefined ... Stupid app design ... stupider tech support ...

      scottalanmillerS stacksofplatesS 2 Replies Last reply Reply Quote 2
      • scottalanmillerS
        scottalanmiller @Veet
        last edited by

        @Veet my ears are bleeding now 🙂

        V 1 Reply Last reply Reply Quote 1
        • V
          Veet @scottalanmiller
          last edited by

          @scottalanmiller said in Converting to a virtual environment:

          @Veet my ears are bleeding now 🙂

          oops, I didn't mean to sound like I'm griping incessantly .. sorry ... no more vendor bashing..

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

            @Veet said in Converting to a virtual environment:

            @scottalanmiller said in Converting to a virtual environment:

            @Veet my ears are bleeding now 🙂

            oops, I didn't mean to sound like I'm griping incessantly .. sorry ... no more vendor bashing..

            Vendor bashing is the whole point of IT folks getting together! 😉

            dafyreD 1 Reply Last reply Reply Quote 2
            • dafyreD
              dafyre @scottalanmiller
              last edited by

              @scottalanmiller said in Converting to a virtual environment:

              @Veet said in Converting to a virtual environment:

              @scottalanmiller said in Converting to a virtual environment:

              @Veet my ears are bleeding now 🙂

              oops, I didn't mean to sound like I'm griping incessantly .. sorry ... no more vendor bashing..

              Vendor bashing is the whole point of IT folks getting together! 😉

              Except for the (relatively) few vendors that we actually like and enjoy hanging out with!

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

                @dafyre said in Converting to a virtual environment:

                @scottalanmiller said in Converting to a virtual environment:

                @Veet said in Converting to a virtual environment:

                @scottalanmiller said in Converting to a virtual environment:

                @Veet my ears are bleeding now 🙂

                oops, I didn't mean to sound like I'm griping incessantly .. sorry ... no more vendor bashing..

                Vendor bashing is the whole point of IT folks getting together! 😉

                Except for the (relatively) few vendors that we actually like and enjoy hanging out with!

                Like the ones that join ML!

                1 Reply Last reply Reply Quote 1
                • stacksofplatesS
                  stacksofplates @Veet
                  last edited by

                  @Veet said in Converting to a virtual environment:

                  @scottalanmiller said in Converting to a virtual environment:

                  @Veet said in Converting to a virtual environment:

                  @scottalanmiller

                  This is precisely what we were discussing in the "Starting own IT consultancy .." thread ...

                  This kind of crap happens all the time ..

                  I recollect an instance, when a vendor went as far as to insist that the compute-name of the Server be a specific one (I think it was the name of their product), or ELSE, the application would not work properly .... Luckily, this was one of the rare occasions when the client backed us, instead of the vendor... I put my sparring gloves on, and TKO'ed the vendor.

                  Wow, just... wow. I wonder if anyone thought to ask if it was the hostname or a DNS entry or the NetBIOS name 😉

                  I'll explain ...

                  The client side of the application, obviously needed to be pointed to the server via the hostname of the server ...Once it so happened that we installed a new desktop, and could could not connect to the product's tech support, to have them install the client app... So, we went ahead and installed it .. Upon starting-up the app, we were confronted with a "Server not found error" ... Upon digging around a bit, we discovered that the installation folder contained an ".ini" file, with the hostname of the server, and database path, predefined ... Stupid app design ... stupider tech support ...

                  I can sympathize. The one place I did work for had an ERP that was written in FoxPro and it had a hard coded path to V:. If you mapped the drive under any other letter it wouldn't work. And since it was FoxPro it used DBF tables in that mapped directory. Awesome design.

                  scottalanmillerS travisdh1T 2 Replies Last reply Reply Quote 3
                  • scottalanmillerS
                    scottalanmiller @stacksofplates
                    last edited by

                    @stacksofplates said in Converting to a virtual environment:

                    @Veet said in Converting to a virtual environment:

                    @scottalanmiller said in Converting to a virtual environment:

                    @Veet said in Converting to a virtual environment:

                    @scottalanmiller

                    This is precisely what we were discussing in the "Starting own IT consultancy .." thread ...

                    This kind of crap happens all the time ..

                    I recollect an instance, when a vendor went as far as to insist that the compute-name of the Server be a specific one (I think it was the name of their product), or ELSE, the application would not work properly .... Luckily, this was one of the rare occasions when the client backed us, instead of the vendor... I put my sparring gloves on, and TKO'ed the vendor.

                    Wow, just... wow. I wonder if anyone thought to ask if it was the hostname or a DNS entry or the NetBIOS name 😉

                    I'll explain ...

                    The client side of the application, obviously needed to be pointed to the server via the hostname of the server ...Once it so happened that we installed a new desktop, and could could not connect to the product's tech support, to have them install the client app... So, we went ahead and installed it .. Upon starting-up the app, we were confronted with a "Server not found error" ... Upon digging around a bit, we discovered that the installation folder contained an ".ini" file, with the hostname of the server, and database path, predefined ... Stupid app design ... stupider tech support ...

                    I can sympathize. The one place I did work for had an ERP that was written in FoxPro and it had a hard coded path to V:. If you mapped the drive under any other letter it wouldn't work. And since it was FoxPro it used DBF tables in that mapped directory. Awesome design.

                    Which part is the bad part... FoxPro, Locked to specific drive..... 😉

                    stacksofplatesS 1 Reply Last reply Reply Quote 2
                    • stacksofplatesS
                      stacksofplates @scottalanmiller
                      last edited by

                      @scottalanmiller said in Converting to a virtual environment:

                      @stacksofplates said in Converting to a virtual environment:

                      @Veet said in Converting to a virtual environment:

                      @scottalanmiller said in Converting to a virtual environment:

                      @Veet said in Converting to a virtual environment:

                      @scottalanmiller

                      This is precisely what we were discussing in the "Starting own IT consultancy .." thread ...

                      This kind of crap happens all the time ..

                      I recollect an instance, when a vendor went as far as to insist that the compute-name of the Server be a specific one (I think it was the name of their product), or ELSE, the application would not work properly .... Luckily, this was one of the rare occasions when the client backed us, instead of the vendor... I put my sparring gloves on, and TKO'ed the vendor.

                      Wow, just... wow. I wonder if anyone thought to ask if it was the hostname or a DNS entry or the NetBIOS name 😉

                      I'll explain ...

                      The client side of the application, obviously needed to be pointed to the server via the hostname of the server ...Once it so happened that we installed a new desktop, and could could not connect to the product's tech support, to have them install the client app... So, we went ahead and installed it .. Upon starting-up the app, we were confronted with a "Server not found error" ... Upon digging around a bit, we discovered that the installation folder contained an ".ini" file, with the hostname of the server, and database path, predefined ... Stupid app design ... stupider tech support ...

                      I can sympathize. The one place I did work for had an ERP that was written in FoxPro and it had a hard coded path to V:. If you mapped the drive under any other letter it wouldn't work. And since it was FoxPro it used DBF tables in that mapped directory. Awesome design.

                      Which part is the bad part... FoxPro, Locked to specific drive..... 😉

                      Ha all of it. Just bad period. I showed the owner how without admin credentials to the system I could open the dbf table and edit anything I wanted. Change people's hours, prices, PAY SCALES, etc. He was shocked, but not enough to switch immediately. After a long time they finally ended up looking at Epicor

                      1 Reply Last reply Reply Quote 2
                      • travisdh1T
                        travisdh1 @stacksofplates
                        last edited by

                        @stacksofplates said in Converting to a virtual environment:

                        @Veet said in Converting to a virtual environment:

                        @scottalanmiller said in Converting to a virtual environment:

                        @Veet said in Converting to a virtual environment:

                        @scottalanmiller

                        This is precisely what we were discussing in the "Starting own IT consultancy .." thread ...

                        This kind of crap happens all the time ..

                        I recollect an instance, when a vendor went as far as to insist that the compute-name of the Server be a specific one (I think it was the name of their product), or ELSE, the application would not work properly .... Luckily, this was one of the rare occasions when the client backed us, instead of the vendor... I put my sparring gloves on, and TKO'ed the vendor.

                        Wow, just... wow. I wonder if anyone thought to ask if it was the hostname or a DNS entry or the NetBIOS name 😉

                        I'll explain ...

                        The client side of the application, obviously needed to be pointed to the server via the hostname of the server ...Once it so happened that we installed a new desktop, and could could not connect to the product's tech support, to have them install the client app... So, we went ahead and installed it .. Upon starting-up the app, we were confronted with a "Server not found error" ... Upon digging around a bit, we discovered that the installation folder contained an ".ini" file, with the hostname of the server, and database path, predefined ... Stupid app design ... stupider tech support ...

                        I can sympathize. The one place I did work for had an ERP that was written in FoxPro and it had a hard coded path to V:. If you mapped the drive under any other letter it wouldn't work. And since it was FoxPro it used DBF tables in that mapped directory. Awesome design.

                        Where's the duck tape? I need to collect the pieces of my head.

                        1 Reply Last reply Reply Quote 2
                        • 1
                        • 2
                        • 3
                        • 4
                        • 5
                        • 6
                        • 7
                        • 8
                        • 8 / 8
                        • First post
                          Last post