-
-
The Configuration Manager 2007 Toolkit V2 contains 11 downloadable tools to help you manage and troubleshoot Configuration Manager 2007.
System Center Configuration Manager 2007 Toolkit V2
-
-
We are excited to announce the beta release of the Virtual Machine Servicing Tool v3.0.
Nexus SC: The System Center Team Blog : Virtual Machine Servicing Tool 3.0 - Now in Beta Release!
-
-
For those of you using MDT 2010 Deployment Workbench and Lite Touch deployments, the breakdown looks nice
Michael Niehaus' Windows and Office deployment ramblings : Driver Management: What you are doing
-
-
I missed this somehow, even though I am actually on the board, but wanted to post about it so you all know. Microsoft is driving cloud adoption from a number of different angles and this blog will be key to hearing about it.
[Blog] http://blogs.technet.com/icabblog/
[RSS Feed] http://blogs.technet.com/icabblog/rss.xml
-
-
So…now that you’re back from MMS 2010 and have unpacked – did you SAVE your Brush Buddy? Do you know where it is? You might want to go find it and keep it handy. Here’s why…
We’re gearing up for a “Where’s Brushy?” contest. Details are still being worked out, but it involves Brushy, a camera, the community, and a willingness to have eyebrows raised from folks around you.
Stay tuned…
-
-
I'd like to start a thread that can be captured into a document for posting to myITforum. Frequently, I receive emails asking for a list of questions to ask ConfigMgr 2007 interviewees, and it would be nice to gather the best questions and make them available on the site.
Post your best interview questions here:
http://www.myitforum.com/forums/ConfigMgr-2007-Interview-Questions-m217734.aspx
-
-
This was an issue that I came across from our recent upgrade from SMS 2003 to SCCM 2007. While we were still using SMS, some systems had been cloned/p2v’d from a production system to a virtual then renamed. It wasn’t caught at the time, but it appears SMS may have been unable to automatically give the cloned SMS clients a new GUID. When we migrated to SCCM, these clients were fighting over which of them was the real and live system in SCCM, such that some client records would suddenly disapper from the console…then if they’re client was fixed, a different client record would disappear.
Duplicate SCCM Client GUIDs / Full Client Reinstall « t3chn1ck
-
-
Participate in the survey:
http://www.surveymonkey.com/s/S55HFPN
-
-
What are your top pain points for the use of ConfigMgr and WSUS?
http://www.myitforum.com/absolutenm/templates/?a=17048
-
-
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
-
-
Faysal Bank is one of the fastest growing banks in Pakistan. It wanted to update its fragmented infrastructure, and make it easier to establish uniform settings across all computers. By deploying Active Directory, Microsoft System Center Configuration Manager 2007 R2, and Microsoft System Center Operations Manager 2007 R2, the infrastructure is more reliable, the IT team more efficient, and Group Policy can be implemented across all clients in minutes.
Microsoft Case Studies: Faysal Bank
-
-
Download Volume 8 of the:
*Available in 11 languages
The Microsoft Security Intelligence Report (SIR) is a comprehensive and wide-ranging study of the evolving threat landscape, and addresses such topics as software vulnerability disclosures and exploits, malicious software (malware), and potentially unwanted software.
Volume 8 of the Security Intelligence Report (SIR v8) covers July 2009 through December 2009. It includes data derived from more than 500 million computers worldwide, each running Windows. It also draws data from some of the busiest services on the Internet, such as Windows Live Hotmail and Bing.
In this volume, the analysis is from the perspective of the three Microsoft Trustworthy Computing Security Centers in addition to several Microsoft product groups.
Microsoft Security Intelligence Report Volume 8
-
-
If you did, we captured him for you in a one-on-one interview.
Check it out:
http://www.myitforum.com/absolutevc/avc-view.aspx?v=1736