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. _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
