Bind client device to specific platform

Question

Is there any method how to force a device to register on mobile server as some specific platform?
To speak concretely - I have 2 WM5 PDAs on my desk. The first device (Symbol MC70) has XScale CPU, the other has ARMV4 CPU (Acer n300). I used the same installation cab for both devices (the cab for PPC2003 XScale), but each device registers itself to different platform in Oracle Lite Mobile Server (Oracle Lite PPC2003 ARMV4 versus Oracle Lite PPC2003 XScale). So I need to publish each application twice to be available for both devices even though both devices/platforms are fully compatible - this is very uncomfortable for application evolution...
I would be probably able to change the platform in the mobileadmin.dm$all_devices or something like this, but this would be no system-solution and could maybe cause some problems on client side (the platform is also stored on client device in polite.txt file afaik - "TYPE=WINCE_XScale_CS_OLITE_2003").

Answer 1

What you are deploying is a Client Settings policy, not the client itself. This is akin to a Group Policy Object being linked to an OU. The machines in the collection which already have the ConfigMgr client will process those policies, but additional non-client
machines added to the collection will not automatically install the client.
As Torsten indicated, you can deploy the client to these machines using the manual client push method.  Simply right click on the clients themselves (or the collection) and select Install Client.  If doing it at the collection level, I recommend
against selecting "Always install the client software" in the wizard as it will force an unnecessary repair of the existing ConfigMgr clients. I would recommend testing this on one machine in the collection in question before attempting to do them in bulk.
Note that this requires that a Client Push Installation account be configured (Administration > Site Configuration > Sites > Client Installation Settings >  Client Push Installation > Accounts tab) which has admin rights on the clients.
You *DO NOT need to enabled site-wide client push installation* to be able to use the Install Client method in the console. Enabling this will force the client to attempt installation on ALL systems that ConfigMgr sees.