For that matter, why not do an Active Link with a Run Process that calls the
wmic command to uninstall it. I forget the exact syntax but I’m sure it is
easily found on Google. Something like:
C:\> wmic product where “description=’BMC Remedy Action Request System 7.6.4’ “
uninstall
I don’t
Hi,
That should work fine.
You could add a 1 to the end to allow GroupID 1 (Administrators) the
possibility to use ARUser anyway.
Best Regards - Misi, RRR AB, http://rrr.se
> I've never had to use it, but do you guys think that the
> Disable-Client-Operation ar.cfg/conf setting would
Hi List,
There is a plan to migrate the certificates on the AD Server based on SHA1
algorithm to SHA2 algorithm.
Remedy uses the same certificates (imported into certdb – currently SHA1)
to authenticate via LDAP. I would like to know if moving to SHA2 would
potentially create any issues with
Rick,
I recommend this article :)
https://docs.bmc.com/docs/display/public/ars81/Running+the+database+consistency+checker
On Thu, Sep 24, 2015 at 9:27 AM, Rick Westbrock
wrote:
> **
>
> A while back my development server started throwing ARERR 481 on startup
> where
Hi
You can turn on sql-logging.
Another option is this tool:
https://docs.bmc.com/docs/display/public/ars81/Running+the+database+consistency+checker
--
J
2015-09-24 17:27 GMT+02:00 Rick Westbrock :
> **
>
> A while back my development server started throwing ARERR
AR 8.1 has achieved Common Criteria Certification in May 2015
Refer to the following Common Criteria Certification artifacts
Security Target document –
https://www.commoncriteriaportal.org/files/epfiles/bmc-remedy-v81-sec-eng.pdf
Certification document –
A while back my development server started throwing ARERR 481 on startup where
the log only says "Requested database table not found. Please check the
spelling (table name is case-sensitive)". I was really disappointed to see that
it did not actually list the table with which it was having
I made the rookie mistake of not including my ARS version 7.1 in my initial
post. /facepalm
LJ, I am not sure if that utility is available for 7.1 since one of the command
line parameters is the which I don’t think existed before
version 7.5. I will still try to make it work though.
Jarl, I
I just searched through our PDF archive back to 3.0. The earliest match for
the checkdb option was in the 7.5 docs.
I would expect that kind of thing to be captured in the sql log or at least
one of the logs. I would try logging API, SQL, Filter, Escalation to the
same log file and use LJ's
If you want to be a bit nasty but not alter their machine you can have a
Filter that looks for $CLIENT-TYPE$ = 3 that has Run Process:
Application-Invalidate-User.
Then they can't get back in until somebody resets/clears the password in
the User form. And it is a filter so there is no playing
Wondering if anyone out there has had a similar issue.
We are installing the whole ARS9/itsm 9 suite on a Virtual Server from
Amazon Web Services.
It's ITSM 9 patch 1 on Windows 2012 operating system connecting to SQL 2010
(I thinkmay be wrong about that last bit).
Anyway, my partner has
Warren,
I was installing Smart Reporting 9 SP1 and ran into a similar issue. The error
messages I was getting were not as clear as they should have been.
After a few days dealing with support and them talking to the developers of the
install package we were able to get my install to work by
Great news!
--
J
2015-09-24 17:41 GMT+02:00 Abhijit Rajwade :
> AR 8.1 has achieved Common Criteria Certification in May 2015
>
> Refer to the following Common Criteria Certification artifacts
>
> Security Target document –
>
13 matches
Mail list logo