Software Deployment

Yeah Avaya has some interesting ideas about shortcuts. My notes don't say how I found out what the shortcut really was but you have to figure out the command line on the original machine (probably just looking at the shortcut properties or what it points to) and create an command line shortcut with the correct command line. The reason I say command line is that I am assuming you did not setup capture Java with the app so Java is not part of the MSI meaning you have to put in a command line shortcut. Sorry I cannot help more but here is the command line I used for VaLManager I am not sure if VAM is the same product.

C:\Program Files\JavaSoft\JRE\1.3.1_02\bin\javaw.exe -Dvalpath="C:\Program Files\Avaya\Voice Announcement Over LAN Manager" -Dvaldebuglevel=0 -jar "C:\Program Files\Avaya\Voice Announcement Over LAN Manager\bin\valmgr_patch.jar".

Thanks for the information, I do remember seeing a similiar looking path in a text file that was captured. It caught my attention but I dismissed it for some reason. Hopefully, I can make a couple of adjustments and it will work now. I will report back afterwards. I have to wait for a new version of the software (other unrelated issues) that should arrive on Friday. My repack and testing need to be completed for deployment on Saturday. Gotta love those eleventh hour changes.

I do think the VaLManager is the same thing. I have heard the telecom folks calling it both VAL and VAM.

Thanks again,

Doug

Unfortunatlly I have not been able to get Voice Announcement Manager to work. If I use a command line similiar to the one posted here I see the splash screen for VAL. After it disappears, javaw.exe is showing up in the task list but I never get the Java window.

I am running out of time. It looks like I will have to do a scripted install instead of a repacking into a MSI. I am going to give it one last try on Saturday.

Doug

I wanted to let those who cared, or search the board later, that I figured out the problem. The problem was somewhere within WPS itself. When I did the setup capture I used the default settings of Snapshot and SmartMonitor. This combo did not work. I read on Wise Package Studio for Newbies that they believed this caused some issues. So I decided to try one or the other. I redid my capture using only snapshot and it worked perfectly. I can now launch the packaged application using launchVAL.exe just like the original install.

Doug

I am not sure if VAM is the same product.

BTW, I figured out the the product used to be called Voice Announcement over LAN Manger. Avaya has since dropped the 'over LAN' part. Thus VAM versus VAL.

Hi Doug,

Wow finally after searching the web long and hard I have found some one in the same predicament with this damn Avaya VAM packaging!!!

Just a quick question you said that if you did a Snapshot only cpature of the package it worked. Can you advise if this was from the Autorun.exe or did you run the Required Components, then Jave install and then the VAM install manually??

Thanks

Also what version of WPS are you using?? I can't imagine this would make a difference but just in case?

Regards

I packaged without the Java so I think that is why I had shortcut issues because Java does not exist in the install. I think if you do a straight up snapshot capture with the Java it should package easily.

I just prefer to manage Java seperately from the applications because I have seen my fair share of Java issues when it comes to making everything work on the same desktop. Again, it's a personal call but I personally think packaging Java (Sun native install) with the applications adds some headaches down the road when conflict arise.

Thanks for the info kkaminsk.

Question; I am going to trya capture as you have suggested installing without Java and then install Java 1.3.1_02 after the capture manually to see if this works. I take it u ran the installs manuall from nwshare\Avaya\Avaya VisAbility Suite\REQ_install\setup.exe and nwshare\Avaya\Avaya VisAbility Suite\VAL_install\setup.exe and THEN installed J2RE or did you have J2RE installed on the PC before??

I will try the same with J2RE 1.4.2_05 as well as ideally would like the most up to date vers.

I am going to be working on this over the w.e as well so any other help you could provide would be ace!

Thanks

I had JRE installed first then I did the capture. But the shortcuts might not work so you might be using a fair bit of time to determine the command line. Also I should warn if you do use this method, any shortcut to Java will not be able to advertised.

I used WPS 4.61 to do the capture.

Jim,

I had Java installed prior to the capturing of VAM. Since the version of Java on Avaya CD was older (1.4.2 vs 1.4.2_05 or 1.5.0) I tried using an updated version, but none would work. It seems that Avaya wanted the specific version that is provided on the CD. I decided not to fight it and use what they provided. I created a unattended install of 1.4.2 using some of the instructions found on this site. Since Java is now installed I captured the required components and VAM together launching from autorun.exe.

I am using WPS 5.1 evaluation version (still fighting to get the $$$ to purchase). After it was all said and done, I did not have to worry about any funky command line. I was able to use launchVAL.exe just like the install straight from the CD did.

If you have any other questions that I can help with just post here and I will keep an eye out for them this weekend.

Doug

[:)] Well I am delighted to say that we have finally managed to get the Avaya VAM and Site Admin apps packaged and tested as a non-admin user on lock down build!!

How I did it in the end was by packaging using WPS, Smartmonitor method, with using the default repackage.ini stored locally on the packaging pc rather than using the pre-written repackage.ini located on the Wise sharepoint.

Then soem filed permissions and registry permissions were changed to allow the users to modify, the data files and open thw launchVAL.exe.

I then had to remove all the HKCU registry settings from the package this then allowed the install to work for multple users.

Thanks to both Doug and kkaminsk for all your advice last week and over the w.e.

It is a real confidence booster to know there are folks out there that have seen the same issues as you!!!!

Cheers
Jim