Converting to a virtual environment
-
@scottalanmiller said in Converting to a virtual environment:
@PRPL said in Converting to a virtual environment:
None , except one vendor (Apogee PrePress), seemed to have any issues...
This is a red flag about the vendor. This implies that they don't have even basically competent IT staff. So how are they supporting their product at the best of times? I'd be worried that they are not a viable company or that the product has been abandoned internally and they are charging you for something that they cannot support. Is there a reason that this vendor is being used?
This, to me, sounds like the vendor is going to do nothing but point fingers and change their mind about supported scenarios every step of the way.
-
@coliver said in Converting to a virtual environment:
@scottalanmiller said in Converting to a virtual environment:
@PRPL said in Converting to a virtual environment:
None , except one vendor (Apogee PrePress), seemed to have any issues...
This is a red flag about the vendor. This implies that they don't have even basically competent IT staff. So how are they supporting their product at the best of times? I'd be worried that they are not a viable company or that the product has been abandoned internally and they are charging you for something that they cannot support. Is there a reason that this vendor is being used?
This, to me, sounds like the vendor is going to do nothing but point fingers and change their mind about supported scenarios every step of the way.
Exactly. This is a sign that the vendor is not on your side and you should be concerned about how this process is going to go.
-
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.
-
@Veet said in Converting to a virtual environment:
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
-
@scottalanmiller said in Converting to a virtual environment:
@Veet said in Converting to a virtual environment:
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 ...
-
@Veet my ears are bleeding now
-
@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..
-
@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!
-
@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!
-
@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!
-
@Veet said in Converting to a virtual environment:
@scottalanmiller said in Converting to a virtual environment:
@Veet said in Converting to a virtual environment:
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.
-
@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:
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.....
-
@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:
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
-
@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:
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.
