SP1 has now been officially released and supported!!
Read all about it here: http://www.microsoft.com/systemcenter/mobile
All the resource kits tools have also been refreshed, see the downloads below!
Key Features and Benefits: Mobile Device Manager 2008 enables efficient control of Windows Mobile 6.1 devices by providing reliable, low-cost, and consistent manageability, easy integration with your existing Microsoft infrastructure, and secure access to the corporate network. SP1 is designed to cost-effectively support large-scale deployments of Mobile Device Manager with new features and enhancements:
• Multiple Instance: Supports deployments where multiple points of control are required within a single forest.
• PIN Reset: Allows users to request a PIN reset on their device. (details here: http://technet.microsoft.com/en-us/library/dd252841.aspx)
• Enrollment Auto Discovery: Facilitates easier self-service enrollments.
• Runs with Windows Server 2008: Provides support for Windows Server 2008 Active Directory functional level.
• Performance/Scalability: Increased system capacity.
• Virtualization: Provides Hyper-V testing support using Windows Server 2003 as a guest OS.
Information:
Get the evaluation here:
http://technet.microsoft.com/en-us/evalcenter/cc339027.aspx
Great must-read “What’s New” overview:
http://technet.microsoft.com/en-us/library/dd261938.aspx
Updated SP1 TechNet documentation appears to be slowly published here:
http://technet.microsoft.com/en-us/library/dd261783.aspx
Downloads:
System Center Mobile Device Manager 2008 SP1 Evaluation Edition - 120 day
System Center Mobile Device Manager (MDM) 2008 SP1 Evaluation Edition is a system that enables Windows Mobile devices to become managed and authenticated members of the IT infrastructure of an organization.
System Center Mobile Device Manager 2008 SP1 MSDN
System Center Mobile Device Manager (MDM) 2008 SP1 MSDN is a system that enables Windows Mobile devices to become managed and authenticated members of the IT infrastructure of an organization.
Mobile Device Manager 2008 SP1 MP for OpsMgr 2007 v1.0.2430.0
This Microsoft System Center Mobile Device Manager Service Pack 1 (MDM SP1) 2008 Management Pack provides proactive monitoring of your Microsoft System Center Mobile Device Manager 2008 SP1 environment.
MDM 2008 SP1 Resource Kit Tools - Password Reset Client v1.0
System Center Mobile Device Manager (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.
MDM 2008 SP1 Resource Kit Tools - Reporting Services v2.0
System Center Mobile Device Manager (MDM) 2008 Server Pack 1 (SP1) Reporting Services provides a reporting and data access service across all areas of an MDM system.
MDM 2008 SP1 Resource Kit Tools - Server Tools v2.0
System Center Mobile Device Manager (MDM) 2008 Service Pack 1 (SP1) Server Tools provides tools to help administrators manage deployment and cleanup tasks in an MDM system.
MDM 2008 SP1 Resource Kit Tools - Best Practices Analyzer v2.0
Best Practices Analyzer Tool for System Center Mobile Device Manager (MDM) 2008 Service Pack 1 (SP1) helps you analyze a group of servers to determine if the prerequisites and best practices are met for MDM deployment.
MDM 2008 SP1 Resource Kit Tools - Client Tools v2.0
System Center Mobile Device Manager (MDM) 2008 Service Pack 1 (SP1) Client Tools provides tools to help administrators troubleshoot connections and monitor device synchronization for Windows Mobile devices as part of an MDM system.
|\\arco..
mnielsen(at)enterprisemobile.com
http://marco.blogsite.org
15 Dec
Posted by mnielsen in SCMDM, Windows Mobile
I’ve been compiling a running alphabetical list of which devices now have official supported upgrades available for them since the summer of 2008. This may be useful for many of you as well. New entries are in red.. Sorted by mobile operator/OEM and now made it more condensed as well!
Now included the specific OS/AKU build for each upgrade for SCMDM SP1 support.
| MO/OEM | OS/AKU | Build Number |
| Alltel: | ||
| Alltel HTC PPC8600 | WM 6.1 | ? |
| Alltel HTC Touch | WM 6.1 | ? |
| ASUS: | ||
| ASUS PDA Phone P527 | WM 6.1 w/AKU 1.0.4 | Build 19214.1.0.4 |
| ASUS PDA Phone P750 Patch | WM 6.1 | ? |
| AT&T: | ||
| AT&T Motorola Q9h | WM 6.1 w/AKU 1.0.2? | Build 19209.1.0.2? |
| AT&T Tilt | WM 6.1 w/AKU 1.0.4 | Build 19214.1.0.4 |
| AT&T Pantech C810 Duo | WM 6.1 w/AKU 1.1.8 | Build 19597.1.1.8 |
| AT&T BlackJack II (SGH-i617) | WM 6.1 w/AKU 1.0.1 | Build 19208.1.0.1 |
| Bell: | ||
| Bell HTC Touch | WM 6.1 | ? |
| Fido: | ||
| Fido BlackJack (SGH-i616) | WM 6.1 | ? |
| HTC: | ||
| HTC TyTN II (unlocked) | WM 6.1 w/AKU 1.0.3 | Build 19212.1.0.3* |
| HTC Diamond (unlocked) | WM 6.1 w/AKU 1.2.3 | Build 19965.1.2.3* |
| HTC Touch Pro (unlocked) | WM 6.1 w/AKU 1.2.3 | Build 19965.1.2.3* |
| HTC Touch Cruise | WM 6.1 | ? |
| HTC Touch Dual | WM 6.1 | ? |
| i-mate: | ||
| Ultimate 6150 | WM 6.1 w/AKU 1.2.1 | Build 19959.1.2.1* |
| Ultimate 8150 | WM 6.1 w/AKU 1.2.1 | Build 19959.1.2.1* |
| Ultimate 8502 | WM 6.1 w/AKU 1.1.2 | Build 19585.1.1.2* |
| Ultimate 9502 | WM 6.1 w/AKU 1.1.2 | Build 19585.1.1.2 |
| JAMA 101 (Pending) | ||
| Intermec: | ||
| Intermec CN3 | WM 6.1 w/AKU 1.1.1 | Build 19581.1.1.1* |
| Intermec CK3 | WM 6.1 | ? |
| O2: | ||
| O2 XDA Stellar (HTC TyTN II) | WM 6.1 | ? |
| O2 XDA Orbit 2 (HTC Touch Cruise) | WM 6.1 | ? |
| O2 XDA Mantle (HTC P6500) NEW! | WM 6.1 | ? |
| Orange: | ||
| Orange HTC TyTN II | WM 6.1 | ? |
| Orange HTC P6500 | WM 6.1 | ? |
| Rogers: | ||
| Rogers BlackJack (SGH-i616) | WM 6.1 | ? |
| Samsung: | ||
| Samsung SCH-i200 | WM 6.1 w/1.0.4 | Build 19214.1.0.4* |
| Samsung SCH-i617 | WM 6.1 w/1.0.1 | Build 19208.1.0.1* |
| Samsung SCH-i760 | WM 6.1 | ? |
| Samsung Omnia SCH-i900 | WM 6.1 | ? |
| Samsung SGH-i780 (pending) | ||
| Sprint: | ||
| Sprint Motorola Q9c | WM 6.1 w/AKU 1.0.2? | Build 19209.1.0.2? |
| Sprint Mogul | WM 6.1 w/AKU 1.0.2 | Build 19208.1.0.2 |
| Sprint HTC Touch | WM 6.1 w/AKU 1.0.1 | Build 19208.1.0.1 |
| Sprint Samsung Ace (SPH-i325) | WM 6.1 | ? |
| Telus: | ||
| Telus HTC Touch | WM 6.1 | ? |
| Telus HTC S720 | WM 6.1 | ? |
| Telus HTC P4000 | WM 6.1 | ? |
| Verizon: | ||
| Verizon Samsung SCH-i760 | WM 6.1 | ? |
| Verizon UStarcom XV6800 | WM 6.1 w/AKU 1.0.3 | Build 19212.1.0.3 |
| Verizon HTC XV6900 | WM 6.1 w/AKU 1.0.3 | Build 19212.1.0.3 |
| Verizon Motorola Q9m | WM 6.1 w/AKU 1.0.2? | Build 19209.1.0.2? |
| Vodafone: | ||
| Vodafone v1615 | WM 6.1 w/AKU 1.0.3 | Build 19212.1.0.3 |
If you know of others, updates or corrections, please let me know!
Update Dec 15, 2008: * Thanks to Wayne Philips of Airloom for these build numbers!
|\\arco..
mnielsen(at)enterprisemobile.com
http://marco.blogsite.org
03 Oct
Posted by mnielsen in Mobile IE, SCMDM, Windows Mobile, security
UPDATED: Oct 5, 2008: Updated v1.1 .ADM file with corrections and additional settings. Download here.
One of the most powerful things about Microsoft System Center Mobile Device Manager (SCMDM) is the ability to manage all of your Windows Mobile 6.1 or above devices through Active Directory (AD) Group Policy Objects (GPOs). A large percentage of the corporate market is already using GPOs to manage their desktop, notebook and server environments.
The GPO technology was introduced in Windows 2000 Server. Before that there were System Policies in Windows NT 4.0. There is already a fair amount of documentation and knowledge around extending GPOs to your own needs. But here I will go into some aspects more important around making use of SCMDM and supporting Windows Mobile in an enterprise running AD.
In this article I will go through how you can extend your own GPOs to have additional settings not available out of the box in the default Windows Mobile GPO template supplied by Microsoft in SCMDM 2008. I will expect that you already know how to access and use the default SCMDM GPO settings.
Windows Mobile Registry Keys
GPOs work by manipulating how registry keys are changed and written on the client machines. This is no different on Windows Mobile, compared to other Windows platforms at this point in time.
I will save the discussion on where to find and research Windows Mobile registry locations. But will point out that many are bound to specific OS levels, OEM and hardware requirements. So what works on one WM device may not work on another. So I can’t stress enough the aspect of testing such settings before a larger deployment to end-users.
For this article I have asked my colleague, Chris De Herrera, to suggest some registry keys to use:
Improve text rendering performance by increasing the GLYPH Cache to 32k (decimal):
[HKEY_LOCAL_MACHINE\System\GDI\GLYPHCACHE]
“limit”=dword:00008000
Internet Explorer Mobile homepage settings:
[HKEY_LOCAL_MACHINE\Software\Microsoft\Internet Explorer\AboutURLs]
“home_0409″=”file://\\windows\\default_0409.htm“
“version_0409″=”file://\\windows\\about_0409.htm“
“blank”=”res://webview.dll/blank.htm”
Configure Communicator Mobile:
[HKEY_CURRENT_USER\Software\Microsoft\Communicator\System Settings]
“ServerInternal”=”sip.yourcompany.com”
“Server”=”sip.yourcompany.com:443″
Furthermore I have also researched the following registry keys which may be helpful in corporate environments:
ClearType Activation:
[HKEY_LOCAL_MACHINE\System\GDI\ClearType][HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings]
“ClearTypeText”=dword:1[HKEY_LOCAL_MACHINE\System\GDI\ClearTypeSettings]
“OffOnRotation”=dword:0
Browser History:
[HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Main]
“DaysToKeep”=dword:00001E
Default Search Page:
[HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Main]
“Search Page”=http://m.live.com/search/Results.aspx?q=%&mid=8001
Internet Explorer User Agent:
[HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Internet Settings\5.0\User Agent]
“Default”=”Mozilla/4.0″
“Platform”=”Windows CE”
“Version”=”MSIE 6.0″
Menu Animations:
[HKEY_LOCAL_MACHINE\SYSTEM\GWE\Menu]
“AniType”=dword:0
Windows Animations:
[HKEY_LOCAL_MACHINE\SYSTEM\GWE]
“Animate”=dword:0
Error Reporting:
[HKEY_LOCAL_MACHINE\System\ErrorReporting\DumpSettings]
“DumpEnabled”=dword:0
[HKEY_LOCAL_MACHINE\System\ErrorReporting\UploadSettings]
“DontUpload”=dword:1[HKEY_LOCAL_MACHINE\System\ErrorReporting\UploadSettings]
“ConnectionFlags”=dword:0
Today Screen Text:
[HKEY_LOCAL_MACHINE\Software\Microsoft\Shell\DeviceBeta]
“Today”=”EnterpriseMobile”
Display Time/Date in Taskbar or disable for battery indicator:
[HKEY_LOCAL_MACHINE\Software\Microsoft\Shell]
“TBOpt”=dword:3
“ShowTitleBarClock”=dword:1
Permit Bluetooth and IrDA File Transfer:
[HKEY_LOCAL_MACHINE\Software\Microsoft\Obex]
“IsEnabled”=dword:1
Please be aware that most of these settings require a soft reboot of the device before they become effective. The SCMDM policy agent should prompt you for a reboot of the device when an updated policy is synchronized from the Device Management Server.
Creating .ADM Files
Using the information published here about the correct registry key prefix to use for GPOs on Windows Mobile I created my own .ADM file with my sample registry keys listed above and a few other samples currently available.
You can download it here. I have noted in my sample the references used.
Look for a new folder called “Windows Mobile Settings-Extended” in the Computer Configuration section of the Group Policy Object Editor.
The single main trick was to prefix the native Windows Mobile registry keys with the <SOFTWARE\Policies\Microsoft\Windows Mobile Settings\Registry> path.
So the native:
<HKEY_LOCAL_MACHINE\Software\Microsoft\Internet Explorer\AboutURLs> became the longer:
<SOFTWARE\Policies\Microsoft\Windows Mobile Settings\Registry\HKLM\Software\Microsoft\Internet Explorer\AboutURLs>.
Note the collapsed HKEY_LOCAL_MACHINE hive into the named HKLM. This also works for the HKEY_CURRENT_USER hive into HKCU.
Further Information on .ADM Files
Please see the reference links below for more details on the syntax used in the example .ADM file. The syntax and commands are not the easiest in the world of IT.
I also found a ADM file editor, called ADM Template Editor from a small company in Australia that may be useful if you are planning to write and manage a large number of custom .ADM/.ADMX files.
Again, please test the policies on the OS platform, level, and hardware you wish to broadly deploy your Windows Mobile settings out to.
Look for more articles soon on useful Windows Mobile registry keys and GPOs!
References:
|\\arco..
mnielsen(at)enterprisemobile.com
http://marco.blogsite.org