I meant the Adobe Flash player that’s required to display quite a few things these days which include control type flash objects embedded in DVF’s (data visualization fields)..
ITSM 7.6.04 have controls like close, expand, etc. that get displayed a little differently (close to ugly) with an incompatible flash player, and clicking those control does nothing until you install a compatible Adobe Flash player version. Then it looks better visually and works as well.. For ITSM 7.6.04, Adobe Flash does play a major role. I’ve heard of future plans to not utilize Flash at all to get rid of yet another dependency that has come into play, but nothings known about how far down the line that will be. Its not that high on the priority list of enhancements that have got the yes nod from what I heard, so until then its best that we do take into consideration that dependency and learn to adapt around it.. Joe From: LJ LongWing Sent: Friday, October 14, 2011 6:04 PM Newsgroups: public.remedy.arsystem.general To: arslist@ARSLIST.ORG Subject: Re: Server 2008 R2 ** Interesting…we don’t have any Flashboards in our app…so hopefully that impact will be negative, if any…but I’ll keep it in my notes J From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Joe Martin D'Souza Sent: Friday, October 14, 2011 3:23 PM To: arslist@ARSLIST.ORG Subject: Re: Server 2008 R2 ** You may also want to turn off automatic update of the flash player on client PC’s belonging to end users. Although the compatibility only lists a minimum version of the Flash player (or plugin if you use non IE browsers), its better to stay close to the nearest version known to you that you have tested it to be working on. Incompatibility with the version of flash player can turn out ugly too as in one of my past experience wherein the available player on site was actually less than the minimum version recommended for 7.6.04 by BMC Remedy. While I have had no negative experience so far on my laptop upgrading my player as and when newer releases of the player were available (as my laptop is personal and I use it at customer sites), you wouldn’t want to find out some upgrade of the player is not compatible with the consoles that require the Flash player by upgrading end user PC’s.. The problems you will face do not immediately suggest it may be a possible flash problem. Some of the controls that are flash based do not work, and sometimes do not even display correctly (like the expansion buttons, etc.). And the problem does not get logged into most of the logging tools available (mid tier logging, Fiddler, etc.) as an error, because its not an error. Just an incompatible player for ‘playing’ the object. So it displays it best as it can, but does not ‘play’ it. Joe From: strauss Sent: Friday, October 14, 2011 2:19 PM Newsgroups: public.remedy.arsystem.general To: arslist@ARSLIST.ORG Subject: Re: Server 2008 R2 ** Yes, it requires that both are available; I installed the Sun JDK 1.6.0_24 x64 and Sun JDK 1.6.0_24 x86 at the time. And no, I don’t allow java to update automatically; EVER! On 2008 R2 (and Windows 7) it takes deleting the files in C:\Program Files (x86)\Common Files\Java\Java Update to kill it off. Christopher Strauss, Ph.D. Call Tracking Administration Manager University of North Texas Computing & IT Center http://itsm.unt.edu/ From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Danny Kellett Sent: Friday, October 14, 2011 1:08 PM To: arslist@ARSLIST.ORG Subject: Re: Server 2008 R2 ** It installs everything in Program Files\ and no there isn’t a 32 bit version. Looking at my notes there was one thing but this is probably my fault. I downloaded Java from ninite.com as a package. I love the site and use it all the time. Well the AR install didn’t detect it. So I think I had to install both the 64 and 32 bit Java to get it to see it. From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of LJ LongWing Sent: 14 October 2011 18:32 To: arslist@ARSLIST.ORG Subject: Re: Server 2008 R2 ** Permissions – Check MAPI – Not an issue, we use smtp J Alarm Point – Not an issue Additional question….we have never used the default install path…have always installed to an E drive…this will be my first Server based 64 Bit system and I know there are things like ‘if it’s a 32 Bit App, it must be installed in c:\Program Files (x86) to run properly’….is this something I need to be on the lookout for?....I seem to remember reading somewhere that the arserver in 7.6.4 was 64 Bit…but having just downloaded the SP2…I don’t recall seeing a 64 Bit separate download….does the installer take care of that then?....if it’s 64 bit does it need to be in a specific folder to be handled properly? From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of strauss Sent: Friday, October 14, 2011 10:57 AM To: arslist@ARSLIST.ORG Subject: Re: Server 2008 R2 ** Almost all of your problems will be from the tighter permissions, especially if you are mixing domain accounts with local accounts or using domain accounts to run your services. Expect to have to apply explicit permissions to folders for the AR Server service account and the tomcat service account or they will be unable to do simple things like update the ar.cfg file! This applies to BMC folders, Tomcat, maybe even Java folders if you have trouble getting the plugins to run. The service accounts have to be local admins or power user group members, AND get explicit access to the folders. Make a C:\Home folder with full permissions for those accounts, and force User, Import, DevStudio to use it for their workspaces or you will be looking for files deep in the \user directory structures depending on how you are logged in. If you use MAPI with Outlook for AREMail you are in for some fun; I never saw that service work properly on 2008 R2 unless you had a current logged-in session open with the email service user account, and started the service while logged in as that user. Logging out killed it (the service kept running but could no longer access mail via MAP). It was one of the main reasons that we switched to SMTP instead (and stayed that way even after reverting to 2003 R2 due to alarmpoint). Hopefully you are not using AlarmPoint; it is NOT supported on 2008/2008 R2, especially the java client that must reside on the AR Server. It is a moot point – even an onsite visit has failed to get Alarmpoint working with our ITSM 7.6.04.01 system, which we kept on 2003 R2 specifically to support that product. The most annoying change in 2008 R2 is the local firewall; it takes far more work in 2008 R2 versus 2003 R2 to set up anything for programs or ports; far more knobs to turn to get the same effect. Christopher Strauss, Ph.D. Call Tracking Administration Manager University of North Texas Computing & IT Center http://itsm.unt.edu/ From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of LJ LongWing Sent: Friday, October 14, 2011 10:56 AM To: arslist@ARSLIST.ORG Subject: Server 2008 R2 ** I’m running 7.6.4 SP1 on Windows 2003 with a remote SQL Server 2008. My Windows SA’s asked me the other day when I was going to move to Windows Server 2008 R2. I did some initial testing and found that 7.6.4 installs on the 64 Bit OS and seems to run fine (I could connect and such)…what are the gotcha’s I’m going to come across when doing this move? I don’t run any OOTB apps, all custom, so I don’t need to deal with some of the problems associated with the ITSM suite…I’m just talking about problems running Remedy Server on 2008 R2…your time and already hard learned lessons are appreciated. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"