RAPI being block buy Windows mobile Security model?

[ink]

Hi all,

I have written a C# application that is to be used to commission(install and
setup) Symbol HHT (Windows mobile devices) with drivers, Wifi network
setting, phone settings and software.

I have got the application doing all the basics like coping files, deleting
files, editing the registry and running processes all using the
OpenNETCF.RAPI.Communication wrapper.

But the security seems to be blocking me at every turn.
It all works as long as I am not using any System folders(Windows,
Application) or protected Registry Keys (LocalMachine\Drivers)

The problem is that these are the exact places that I need to be executing
these things in order to set the devices up.

The problem with doing the commissioning manually is that we often need to
setup more that 1000 at a time. And doing this manually can take weeks. We
were hoping to streamline this process buy scripting it. But now it is
starting to seem like this cant be done either.

Any help on how to get around the Windows Mobile Security Model would be
great.

Thanks,
Ink

 

[DJMatty]

Hi Ink

With WM6 SDK there is a security configuration tool that allows you to
see what security model a device is currently set up for and also to
change it, it does allow you to look at devices that aren't WM6 as far
as I am aware.

I'd also suggest you take a look at Configuration Manager, we use CPF
files and DMProcessConfigXML API to process config manager XML files
to set up any registry settings, set shortcuts, configure gprs
connections etc. It can also be used to modify the security policy of
the device (I am sure this will be restricted when devices start to
ship with the multi-tier security model and the oems\networks have
locked them down)

I found some information here:

http://blogs.msdn.com/windowsmobile/archive/2006/10/30/what-is-the-metabase.aspx

http://msdn2.microsoft.com/en-us/library/ms890461.aspx

Theoretically, you could make a CPF file or XML and process it on the
device with a rapi command to change the security policy to a more lax
one, then run your installer, set everything up and then set the
policy back.

HTH

Matt

 

[Fabien]

Hi,

Check out this link :
http://fabdecret.blogspot.com/2007/04/windows-mobile-security.html
You must set the RAPI policy to 1:
HKLM\Security\Policies\Policie\00001001 (4097).

Hope this help you.

BR


Fabien Decret (Device Application Development MVP)
Windows Embedded Consultant


ADENEO (ADESET)
http://www.adeneo.adetelgroup.com/ | http://fabdecret.blogspot.com/

 

[Guest]

Have you considered using a CAB file ?