Friday, February 27, 2009

SCMDM SP1 Reset Feature

Hey.. I am working on a Microsoft System Center Mobile Device Manager 2008 project.. Just want to spread some goodies underway..

Among them is the ability for the users to reset their pin or poweron password.

This is a brand new feature of SP1 of great interest in an enterprise implementation. With this feature end users who have forgotten their device password or PIN, can recover (without wiping the device) and set a new device password or PIN. In this posting I will dive a little deeper and show how this all works on both the server and client side.

As nicely stated in the MDM Password Reset Client v1.0 download overview:
“MDM Password Reset Client provides a .cab file that you install on Windows Mobile 6.1 devices enrolled in MDM so that users can use the password reset feature in MDM. Password reset in MDM 2008 Service Pack 1 (SP1) enables a user who has forgotten his or her Windows Mobile device password to reset it by using MDM.
Password reset is supported on Windows Mobile 6.1 devices, starting with version 6.1.4. To use the feature, you must install the .cab file on the user’s Windows Mobile device as well as enable the feature in MDM by using Group Policy.
To reset the device password, the user chooses the password reset option, resets the device password, and then enters a one-time recovery password on the device to complete the process. The recovery password is stored on MDM servers and retrieved by the user when she or he has forgotten the device password.”

What is required?
Even though the client patch description mentioned above states it is first supported on Windows Mobile 6.1.4 or above device, the patch appears to install on some of my 6.1.1 devices. But “your mileage may vary” (YMMY) as they say.. The patch, available here, can be manually installed, but with MDM handy why not deploy it it out directly! Please note the installation failures on the devices that are below the 6.1.1 levels.
You also need the SCMDM 2008 SP1 installation on the back-end. Especially the changes on the DM server, SQL tables, and Self Service Portal (SSP) if you wish to use that for retrieving the reset password.

How it works:
After the client patch on the devices is installed and the device locked with a PIN, triggers a local generation of a password reset key. After 2 cycles of traffic to and from the Device Management server, that recovery password will have uploaded to the SCMDM side and be available for use. This can be verified with a cmdlet or on the MDM console by seeing that the “Display Recovery Password” action is no longer grayed out on the right hand side of the screen when a managed device is selected:
More details can also be found here on the overall user experience of this feature: http://technet.microsoft.com/en-us/library/dd252841.aspx
Client Functionality
These are actual screen-shots of a managed device that has the client patched installed.
In a locked state, the “Reset Password” option is no longer grayed out. Suggesting that the password reset key has been uploaded and ready to use:

After the “Reset Password” option is selected, a confirmation that the user can indeed retrieve the recovery password from an administrator or help desk.

It will then let the user create a new password. Using the same requirements that might have been enforced to the device.

Now the user must contact the administrator or help desk. In this example the administrator clicks on the “Display Recovery Password” in the MDM console and is shown the 20 digit Recovery Password that the device has uploaded into the MDM database.

The user must type in the 20 digit recovery password to validate the new password.

If there is a match with the recovery password stored on the device, the new password is granted and the device is unlocked!

Instead of the MDM console, the MDM Self Service Portal (SSP) could have been used. It also has a “Display Recovery Password” button at the bottom which will display the 20 digit recovery password:

The Password Recovery feature in the SSP is selectable by the administrator to be made available on the web site just as the Device Wipe and Device Enrollment features. Please see more information available here: http://technet.microsoft.com/en-us/library/dd261796.aspx.
Password Recovery References
SCMDM Cmdlets: http://technet.microsoft.com/en-us/library/dd261726.aspxSCMDM User Experience: http://technet.microsoft.com/en-us/library/dd252841.aspxWindows Mobile 6.x AKUs: http://myitforum.com/cs2/blogs/mnielsen/archive/2009/01/31/windows-mobile-6-x-akus.aspxWindows Mobile 6.1.x Upgrades and Build Levels: http://myitforum.com/cs2/blogs/mnielsen/archive/2009/01/24/windows-mobile-6-1-x-upgrades-now-available.aspx

Tuesday, February 17, 2009

NAP Design guide

Greg Lindsay (writer) and Allyson Adley (editor) won the Online Best of Show award for the NAP Design Guide at the Puget Sound Chapter of the Society for Technical Communication (STC) awards ceremony on January 29th.

Congratulations Greg and Allyson for the fantastic technical documentation on NAP!

It is a VERY good guide, that covers all areas you need in designing, deploying and managing the platform.

More NAP

Hey,

I just wanted to give you guys some more links to helpfull material that you can use for your NAP projects. Aswell as giving you some news on Windows 7 and Windows 2008 R2 integration.

In Windows 7, the NAP client user interface (UI) has been integrated into the Windows Action Center (previously known as the Windows Security Center). For example, Network Access Protection notifications appear in the list of messages when you click the Action Center message in the notification area of the Windows 7 desktop.

So you should start thinking about your design, and align it with your company standards regarding upgrading client OS's. You should start your PoC now on Windows 7, so you are ready to roll. Security wise you do get all the features you need built-in now.

-

If you want to play with a Network Access Protection with IPSec Enforcement virtual LAB please visit:
http://msevents.microsoft.com/CUI/WebCastEventDetails.aspx?EventID=1032345136&EventCategory=3&culture=en-US&CountryCode=US
It is build on previous versions, but gives a good baseline for your future designs and thoughts on deploying NAP with IPSec enforcement.