nobody
Fri Aug 22 17:49:02 CDT 2008
My XML string is:
- <wap-provisioningdoc>
- <characteristic type="Wi-Fi">
- <characteristic type="access-point">
- <characteristic type="SSID_NAME">
<parm name="Authentication" value="AUTH_NO" />
<parm name="DestId" value="{436EF144-B4FB-4863-A041-8F905A62C572}" /
<parm name="EAPType" value="0" />
<parm name="Encryption" value="ENCR_NO" />
<parm name="KeyIndex" value="1" />
<parm name="KeyProvided" value="false" />
<parm name="NetworkKey" value="N/W_KEY" />
<parm name="Use8021x" value="0" />
</characteristic>
</characteristic>
</characteristic>
</wap-provisioningdoc>
"abhi" wrote:
> Hi,
>
> I am trying to use the above XML format to connect to a WEP network. But I
> am getting the CONFIG_E_TRANSACTIONINGFAILURE error. Could you please suggest
> what could be causing this error?
>
> Thanks,
> Abhi
>
> "A-Hobett" wrote:
>
> > Thank you. I had read a Microsoft WM Team member's blog stating the APIs
> > disparity, but not specifics.
> >
> > The reason for the WiFi CSP not working was combination of a typo and
> > conflicting articles/documentation. I have also entered some of the default
> > values to ensure that the settings are correct. The below example is for a
> > WPA-PSK WAP with TKIP/AES.
> >
> > <wap-provisioningdoc>
> > <characteristic type="Wi-Fi">
> > <characteristic type="access-point">
> >
> > // Had it as a closed element e.g. SSID"/>
> >
> > <characteristic type="NETWORK-SSID">
> > <parm name="Authentication" value="4"/>
> >
> > // Work network
> > <parm name="DestId"
> > value="{A1182988-0D73-439e-87AD-2A5B369F808B}"/>
> > <parm name="EAPType" value="0"/>
> > <parm name="Encryption" value="4"/>
> > <parm name="KeyIndex" value="1"/>
> >
> > //Should be 0 not false, copied from an example.
> >
> > <parm name="KeyProvided" value="false"/>"
> >
> > <parm name="NetworkKey" value="NETWORK-KEY"/>
> > <parm name="Use8021x" value="0"/>
> > </characteristic>
> > </characteristic>
> > </characteristic>
> > </wap-provisioningdoc>
> >
> >
> > "Peter Foot" wrote:
> >
> > > The iPaq 214 is a professional edition device - Pocket PC in old naming. For
> > > whatever illogical reason many of the configuration service providers are
> > > supported on Standard Edition (Smartphone) only and clock is one of these.
> > > I'm surprised you get a success response when you deploy the settings
> > > though!
> > > The Wi-Fi provider should be supported. You can try passing your settings
> > > directly into DMProcessConfigXML and requesting the metadata is returned
> > > which should shed light on what part of the config is causing problems...
> > >
> > > Peter
> > >
> > > --
> > > Peter Foot
> > > Microsoft Device Application Development MVP
> > > peterfoot.net | appamundi.com | inthehand.com
> > > APPA Mundi Ltd - Software Solutions for a Mobile World
> > > In The Hand Ltd - .NET Components for Mobility
> > >
> > > "A-Hobett" <A-Hobett@discussions.microsoft.com> wrote in message
> > > news:2ACDB5D0-9F6D-452D-B6E2-1DC7F5E923E9@microsoft.com...
> > > > Hello,
> > > >
> > > > I am trying to create a setup process for 150 HP iPAQ 214s.
> > > >
> > > > I have created several CAB files (MakeCab .\_setup.xml .\wireless.cab)
> > > > that
> > > > are
> > > > based on lots of the fragment examples in the MSDN.
> > > >
> > > > However when applied to the device via SD Card, they ask for authorization
> > > > then install successfully but do not make any changes, even after a soft
> > > > reset.
> > > >
> > > > Below is my xml for setting the Clock:
> > > >
> > > > <wap-provisioningdoc>
> > > > <characteristic type="clock">
> > > > <parm name="AlarmOn" value="0"/>
> > > > <parm name="Date" value="2008-07-18"/>
> > > > <parm name="Time" value="15:30:00Z"/>
> > > > <parm name="" value=""/>
> > > > <parm name="TimeZone" value="85"/>
> > > > </characteristic>
> > > > </wap-provisioningdoc>
> > > >
> > > > As stated in installs correctly on to a clean booted iPAQ but it does not
> > > > change any settings.
> > > >
> > > > Below is one for wireless, this fails to install.
> > > >
> > > > <wap-provisioningdoc>
> > > > <characteristic type="Wi-Fi">
> > > > <characteristic type="access-point">
> > > > <characteristic type="NETWORK-SSID"/>
> > > > <parm name="Authentication" value="4"/>
> > > > <parm name="DestId"
> > > > value="{A1182988-0D73-439e-87AD-2A5B369F808B}"/>
> > > > <parm name="KeyProvided" value="false"/>"
> > > > <parm name="NetworkKey" value="NETWORK-KEY"/>
> > > > <parm name="Encryption" value="4"/>
> > > > </characteristic>
> > > > </characteristic>
> > > > </characteristic>
> > > > </wap-provisioningdoc>
> > > >
> > > > Why does it not have any effect?
> > > > Why does it not install?
> > > > Why are there no full examples, only fragments, e.g. to just set the
> > > > timezone or an alarm?
> > > >
> > > > Is there something like the Scripting Guys for CSP? I know MDM 2008 is out
> > > > but these devices when we get them will be brand new with WM6 and not
> > > > WM6.1.
> > > >
> > > > Thank you in adcance for any help.
> > >