Windows 32bit Client - EOL

What

Here we want to explain the purpose of this content...i.e. what does this function do?

Note about how this impacts 15.3... and the future..

• As the new desktop kiosk for Windows is based on 64b64bit librairies,libraries, FileWave 15.3.0 will not be supported on Windows 32b32bit platforms. FileWave Agent (fwcld) is currently still a 32b32bit executable, meaning there is no change in how filesetsFilesets are deployeddeployed, and scripts are executed.executed with this initial change. 

  When/Why

  Windows 32bit has long been on the way out. Because it can only handle 3.5Gb of RAM there has long been a lot of progress to get away from it by customers. 

  How

  At first the Kiosk in FileWave 15.3.0 will be 64bit, and in a future release the entire agent will transition. Moving to a 64b64bit application is expected to happen later this year.

When/Why

Now that we know what this function is used for, when/why would we use it?

How

And now, since we know everything else, how do we use this function to do something special?

macOS

Related Content

• InsertWindows here links to any articles that relate to this content.Enrollment

Digging Deeper

Want to provide more detail or other examples? Want to wax poetic? Do that here, and keep the top of these documents crisp and clean.