- This topic is empty.
-
AuthorPosts
-
May 29, 2014 at 12:38 am #8232
Can the 9455XL be made discoverable by 4.9.1?
I created a device list entry manually, was able to push the 9455XL image to the unit via PXE, and see that it shows the WDM server IP in the Rapport Control panel, but it doesn’t check in.
I’ve tried Find Device w/o effect.
I gather 4.9.1 required a lot of tweaking to the HAgents, as many devices are poorly served by the HAgents that were included in 4.9.1, requiring subsequent updated versions.
Is there a way to manually install the latest XP HAgent to this device, or some other fix? Should I expect 4.9.1 to be able to pick up these old devices?
May 30, 2014 at 1:06 pm #24770These old devices are typically no longer tested with leter WDM versions.
So no guarantee that it will work.
But you can try and manually update the HAgent.
Do a right click in WDM on the XPHAgentUpgrade package and select “View script”.
Do all the step in the script manually.CG
June 10, 2014 at 6:43 pm #24785I think I went through the script steps, but without apparent effect.
With the FBWF off and in Admin mode, and using your excellent Creating Rapport 4 Packages pdf to understand the script command, I did the following:
1- copied all the files from the Rapport directory for XPe HAgent 5.2.0.10 to C:Temp on the 9455XL
2- from the CMD line, I navigated to that directory and executed PortRegtoIni.exe and install.bat. These were the only two executables I saw in the script.
3- rebootedThe only feedback during the process was several lines indicating files being copied upon execution of install.bat. The reboot appeared normal, with none of the HAgent updating evidence that you see whe using WDM. Client Info still shows the old HAgent.
The WDM Control Panel has disappeared from the client.
Did I follow the right process? Might it be worthwhile trying an earlier version of the HAgent, such as one that was current for WDM 4.8.5?
June 11, 2014 at 10:02 am #24790The steps look fine. You could try to go through the install script step by step instead of running it directly.
CG
August 1, 2014 at 7:04 am #24900Thanks, starting with the simpler XPe HAgent 5.1.1.59 which I knew would check in to WDM 4.9.1, I copied the files to the indicated client directories, then executed the commands from the install.bat file manually. Simply running the batch file in CMD prompt from the C:Temp directory did not work.
Interestingly, once the 9455 checked in I tried to upgrade the HAgent to 5.2.0.32 via WDM. Though the WDM Update Manager and log show the process completed, the client initiated but didn’t fully perform the familiar steps, and the HAgent still shows as 5.1.1.59 on the client and in Device Manager.
-
AuthorPosts
- You must be logged in to reply to this topic.