Duncan
Sun Jun 29 19:39:15 PDT 2008
Thanks - looks to work swimmingly well.
--
Duncan
In article <0D7D75D1-1E88-450B-9368-D8B139130464@microsoft.com>,
Quilnux@discussions.microsoft.com says...
> We are having problems getting the web administration tools migrated onto our
> production server (we use a test environment seperately for software/config
> changes) but I was able to test the wipe on Saturday in the test env. Here
> are the results.
>
> (This was taken from my personal IT report. I took some unrelated elements
> out)
>
> Report: QS-11205-01
> Authority: Phillip Frabott 1000
>
> Reporting: Exchange Server 2003 Web Administration Tools
>
> Remote Wipe results
>
> I tested the remote wipe capability during phase 3 of our regression testing
> procedures. I found promising results as the device was successfully wiped
> remotely. The device responded to the command after 17 seconds which is
> within our TTL threshold currently set at 300 seconds (5 minutes). Advisory
> that this test was run while the device was powered on and inside the data
> network on the wireless providers service area. The TTL set allows extended
> time for devices that are powered off. TTL threshold does not take effect
> until the device has been powered on at least once after the remote wipe
> command is queued on the server. If the device is outside the data network
> (or roaming) the device may not receive the command until it enters the data
> network. Queued remote wipe commands are required to have their statuses
> checked once every 24 hours until complete. During weekends or off duty hours
> the on-call IT is required to check the server at least once per day (00:00
> EST to 23:59 EST) during his on-call time. Terminal Service is permitted for
> this operation.
>
> The wipe did not seem to remove any data from the server. All exchange data
> remained and the dummy user's desktop outlook application continued as normal
> and remained uneffected. Once the remote wipe command completed on the device
> it preformed a soft reset (may be device specific; If another device other
> then the Motorola Q 9c is used, retest this and update the written policy)
> and returned to it's factory settings. Add data including non-exchange data
> was wiped. Our software had to be re-installed on the device and all user
> data (word documents, excel, etc.) were gone. It was as if we preformed a
> Persistant Storage Format on the device. Reconnecting the device to exchange
> (during phase 3-2 test) seemed to bring back all exchange data. This test was
> used to provide results for a scenario of lost device that is later found.
> Testing did not include a storage card (CF/SD etc.) so data wipe of these
> cards is unknown. Testing will need to be done when we begin assigning
> storage cards to these devices.
>
> My conclusion is the testing provided very good results. I personally
> believe that the new web application will be very useful for our company in
> the event our techs or other personnel lose the device or the device is
> stolen. See the IT Test Report for details of the tests preformed and
> detailed results.
>
> -------
>
> This reports agrees with Gregg Hill (previous poster). I do not think you
> should be afraid any longer! Now go forth and wipe everyones devices! (just
> be sure you don't make the suits mad; They get grumpy when they cannot check
> their email from their sports cars ;-P )
>
> "Duncan McC" wrote:
>
> > In article <2DFED27F-0C60-452D-9F6B-F285967BA555@microsoft.com>,
> > Quilnux@discussions.microsoft.com says...
> > > Not yet. We are getting our batch of WM6 devices on Monday or Tuesday next
> > > week and before we deploy we have to test the remote wipe. I'll report my
> > > findings here. I would assume that it just works like a hard reset on the
> > > device only your doing it remotely vs. using the stylis/paperclip and
> > > buttons. I doubt the exchange data is touched and it's probably just a matter
> > > of re-configuring the device to the server again. But once we get them in
> > > I'll report our findings (I didn't really think about it until you mentioned
> > > something so I will use a dummy account on the server just to play it safe.)
> >
> > Fantastic - will eagerly await the results.
> >
> > Cheers.
> >
> > --
> > Duncan
> >
> > >
> > > "Duncan McC" wrote:
> > >
> > > > In article <FA6F364E-E856-446D-B759-7280382BC207@microsoft.com>,
> > > > Quilnux@discussions.microsoft.com says...
> > > > > Works for me! Thanks again for your help!
> > > >
> > > > Great stuff - now don't dissapear on me :) - I've got a question back
> > > > for you.
> > > >
> > > > Have you remotely wiped a WM device?
> > > >
> > > > (I'm too scared to try it!! :)
> > > >
> > > > What happens? - can you just sync everything back up later (ie basically
> > > > scratch reset it up?) Would there be anything lost (forever) ?
> > > >
> > > > --
> > > > Duncan
> > > >
> > > > >
> > > > > "Duncan McC" wrote:
> > > > >
> > > > > > In article <7ED14D7D-BCC6-4A4E-BD21-420947EE3773@microsoft.com>,
> > > > > > Quilnux@discussions.microsoft.com says...
> > > > > > > Evening. I have been authorized to begin planning and deployment of Windows
> > > > > > > Mobile 6 devices to our field workers which will be using PDA/Mobile phones
> > > > > > > from Verizon Wireless (More specifically the Motorola Q). I have finished
> > > > > > > almost all my policy checks with the exception of Remote Wipe. I can't seem
> > > > > > > to find this anywhere on the server. How do we remote wipe a WM6 device in
> > > > > > > the field if it is lost? I saw on a SBS 2003 promo video an area on the
> > > > > > > server that looked like SharePoint Services 2.0. The problem is, we do not
> > > > > > > use SharePoint Services 2.0 (we use 3.0) and as such I removed SharePoint 2.0
> > > > > > > early last year. Is there another way to wipe the WM6 device without the need
> > > > > > > to use SharePoint? Thanks for your help!
> > > > > >
> > > > > > You need to install the Microsoft Exchange Server ActiveSync Web
> > > > > > Administration Tool. Go grab a copy (just a couple of megs IIRC).
> > > > > >
> > > > > > BUT... you need to do a special install for SBS !
> > > > > >
> > > > > > Have a look at this article.
> > > > > >
> > > > > >
http://sbs.seandaniel.com/2006/02/using-microsoft-exchange-server.html
> > > > > >
> > > > > > --
> > > > > > Duncan
> > > > > >
> > > > >
> > > >
> > >
> >
>