ESI 1.1.1 deploying new devices

[RSAAdmin]

I am having issues deploying new devices with ESI 1.1.1  I unzip the files in the nic\..\..\update folder and run the vps script, but it does not copy the device files into the correct folder or modify the ini file with the new device type number etc.

I manually copied the files and created the correct folder in the \etc\devices folder but ini file still has "999" as the device type/id.    

After all this, Envision still does not recognise the new devices anyway, aven though the XML parses correctly and the new "messages" are in the UI

[RSAAdmin]

You don't need to do any manual step except "extracting the contents of the .zip file and copy the files to the ..\nic\enVisionVersionNumber\SystemName\update folder", once you are done with that, You need to run "DeployEventSourceSetup.vbs" and that should do everyting for you. I believe you have run correct vbs script?

[RobertWengewicz]

no there is a issue because I have had the same issue. You follow the direction that RSA has but the XML will not load. So you have to manually copy it over and then change the numbers in the .INI file. Support told me to go to the next free number that is available. So I added the next number up and it worked the correct way.

DeviceType=XXX

DeviceGroup=Access Control
DeviceID=UXXX

Bob W

[RSAAdmin]

thanks for confirming that, still cant get envision to recognise the new devices..

[RSAAdmin]

If still device (xml) is not recognized, there is possibility that some other device is parsing injected log.