Same here. We had our Remedy system (7.5) on a Windows 2003 server which had
to go. The last supported part of AR System – a custom IT Ordering System –
was moved to a SCSM-based setup earlier this year so I was forced to shut it
all down. (We had been running since 1998 on
Yes, we moved to another solution. I enjoy learning the new stuff, but I miss
the comfort of what I knew like the back of my hand.
We have people come back for change records etc for legal things periodically
and have to keep it.
From: ARSList On Behalf Of LJ LongWing
If I'm not mistaken, they aren't using Remedy anymore (moved to another
solution)so Remedy for them is just in mothballs wanting/needing as
little time/effort as possible.
On Thu, Aug 15, 2019 at 12:54 PM Burns, Carina
> If it’s a custom app, why not import the defs with
If it’s a custom app, why not import the defs with Designer Studio then DDM the
records off the old ARSystem with migrator? Just be sure your database/system
can handle that volume of data.
I did that for our legacy custom help desk app (built on 4.3 and upgraded thru
8.1) and it’s all
Your option I think is to simply stop using Remedy at that point and just
access the data at the DB levelif you want to use the Remedy
Application, you need the Remedy application though.
On Thu, Aug 15, 2019 at 12:12 PM Sanford, Claire <
> Hey Old
Hey Old Friends!
We have an old Remedy server that is strictly an archive. We have people ask
for ticket info a few times a year or so. We have been told that we have to
upgrade the server. Since the old server is 32bit and the new one is 64bit,
they are telling me I have to reinstall the
Mail list logo