Pain Points for Using ConfigMgr (SCCM) 2007

The poll has been running for about a month, and you have 2 days left to participate.

You can participate using this link:

http://www.myitforum.com/absolutenm/templates/site.aspx?articleid=16338&zoneid=120

Here’s some stats so far…and really provides some great information for developing the next version of ConfigMgr or for a 3rd party to fill a feature hole that Microsoft may have left open…

1) What are your current Pain Points working with ConfigMgr 2007? Check all the apply and/or add your own.

User Personality Migrations During Win7 Upgrades

(13.11%)

Privilege Account Elevations for Software Deployment

(21.31%)

Remote Control Support

(31.15%)

Internet-based Users

(19.67%)

Wake-on-LAN

(26.23%)

Client Installation

(21.31%)

Tracking Software licenses

(27.87%)

Mobile Users in Branch Offices

(3.28%)

2) Your pain point not listed? Add your own...

Keyword Filter :

• usmt, usb hard discs not being supported, pxe boot slow
• Windows Embedded Systems Management
• 3rd Party patching
• Anything involving Native-mode and PKI.
• Client Health
• software updates
• > The ability to postpone the reboot after the installation of updates(SUP). > The WSUS categories are not granular engouh => You select Windows XP and you recieve updates for Internet explorer.
• Client health
• client health
• Disaster recover is non-existent. Clients are always breaking.
• Software Update
• reporting is a pain in teh @$$. Should make it much easier (GUI) interface fro noice and managemetn users
• reliable PXE booting for OSD
• Locating and repairing broken clients (SCCM and WSUS) [SCCM 2007 SP2, WSUS 3.0 SP2]. It would almost have to be a logon script or a GPO machine policy script. Something else that would be nice - for Distribution Points - it would be nice if they could have a comment so I could add a office name to a WinXP DP.
• Locating and repairing broken clients (SCCM and WSUS) [SCCM 2007 SP2, WSUS 3.0 SP2]. It would almost have to be a logon script or a GPO machine policy script. Something else that would be nice - for Distribution Points - it would be nice if they could have a comment so I could add a office name to a WinXP DP.
• wmi
• SUM. The Windows Update agent is yet another client-side subsystem a failure/problem in which can cause "SMS" issues. (Adds to WMI, WSH, etc.) On the server side, the WSUS instance managed by SCCM still downloads patch binaries -- at least on a primary-site SUP -- an egregious waste of storage (10s of GBs), since SCCM will download, distribute and use its own copy of patch binaries for authorized patches.
• Software Updates
• Permissions. So far I haven't found a real good answer for divying up permissions to Admins, helpdesk, etc.
• MMC 3.0 crashing
• Software update queries not flexible enough. need queries that include all required except xyz patches. Also, the 500 updates in an update list is troubling.
• For OSD deployments, no built-in way to assign a Computer Name and AD OU to a bare-metal machine. There are third-party alternatives, but this should be a built-in feature like it was with MDT