Hi Rick R.
Welcome to the forums.
NNNNxdat.exe Does Not contain the engine. Never has.
McAfee decided due to logic problems in the standalone sdatNNNN.exe files, could not update the engine adequately when upgrading to the 5600 engine. However, the Agent and ePO could update correctly. So, McAfee has let the sdatNNNN.exe files pass away.
. . . and they were very useful for standalone/non-networked systems to make sure both DAT and engine were up-to-date.
Yes, I agree. However, you can still set up standalone systems by creating an image of the new VSE configuration by using 'McAfee Installation Designer' (MID). Be sure to use a base install that does not specify an ePO server for communications and updates. The resulting files can then be used to install on non-networked or unmanaged systems.
. . . troubleshooting a McAfee installation that was acting oddly (e.g. failing its own DAT or engine updates), . . .
Sometimes repaired by doing a "Help-Repair' from the VSE Console. Many times this is caused by the McAfee Agent getting corrupted. This sometimes can be installed again on top of the existing agent. Executing FramePkg_UPD.exe can repair many of the communication issues when VSE fails to update correctly.
When all else fails, uninstall VSE and re-install from the MID developed image of VSE.
Hi Rick R.
rickrusselltx wrote:How do we maintain these standalone systems, now that the engine is no longer available as a standalone upgrade?
I am not sure what you mean by 'maintain?' The SDatNNNN.exe file is only different than the NNNNxDat.exe file by the engine. So the xDat file will update the Dat files in the event that the McAfee update site is not available via the Internet (communications issues or network unavailability).
If communications is broken to McAfee's site, for days on end, then running a 'repair' from the VSE Console is a good starting point. After a reboot, try the update manually. If successful, wait a day to see if it updates automatically. If not, then attempt the Framework_upd.exe on the system and attempt the update manually. Again, wait a day to see if the automatic updates take place.
The SDatNNNN.exe file only updated the Engine files (in addition to the Dat files). So they did not really 'maintain' much as long as the engine files were already installed and working. If the engine gets corrupted, then consider uninstalling VSE and reinstalling from the MID image. Reboot and test the update process again.
Step by step . . .
Going step by step will help if you need to escalate the issues with your McAfee support people.
Frankly, I have not had much issue with the engine files getting corrupted. Mostly, I use the SDatNNNN.exe file during install to update the engine version from a MID image that has a previous engine version. This was only a short gap measure until a new MID image was created with the new engine installed.