A lot of SMS Admins I speak too are telling me they are flat out getting MS08-067 rolled in to their environments. Great work guys, most are very responsive and understand the importance of getting it bedded in. Rolling this puppy out is definately a good idea, especially considering that the exploit...
Came across an SMS Admin today with an interesting problem. He has WSUS\SUP + all the other gubbings all on the one box, nothing really out of the norm and yet he gets Status Message ID 6701 followed by 6703 exactly 5 minutes later (the timeout value) in his WSYNCMGR log when attempting to get WSUS to...
I found this on a TechNet thread, thought might be handy for those of us that may want to sequence the ConfigMgr Console for deployment using App-V Sequencing Config Manager Admin Console (MMC)
I thought i'd write up a quicky blog post on using the ConfigMgr Task Sequence to deploy Software Packages, and reveal select parts of the functionality available to you to accomplish the task. Open up your ConfigMgr console, navigate to the Operating System Deployment node and right click "Task...
I thought I’d check out the ConfigMgr 2007 Console MMC; see how it goes on, where its settings reside and whether I can bring anything new to the current knowledge base. Unfortunately, I don’t bring anything new to the table; instead I’m just consolidating knowledge in to one place...
This issue won't impact many of you, and to induce the following behaviour you really need to go toggle some values most SMS Admins leave well alone. Hence why this one hasn't been spotted in the wild (there is a technet forum thread on this ...). Have you noticed in your environment that your...
... More a reference for me really, List of Log Files in Configuration Manager 2007 http://technet.microsoft.com/en-us/library/bb892800.aspx
Had an interesting problem yesterday, ConfigMgr RTM upgrade to SP1 two thirds of the way through induced a BSOD. Hard to troubleshoot, system reboots and all you're left with is a minidump (depending on your OS configuration for debugging) and a partially completed ConfigMgrSetup log file. ConfigMgrSetup...
Seen an interesting issue where the CCMSETUP parameters incorrectly specify MP as SMSMP, resulting in failure and exotic errors appearing in the CLIENT.MSI and CCMSETUP logs: Just need to fire up CLIENT.MSI in SMSTRACE, find Return value 3 and you'll possibly see the following: WARNING: The path...
I've recently spent a fair bit of time working on ConfigMgr R2 residing upon Windows Server 2008. There are a few issues in there that you'll need to become aware of, but it's not that difficult to get underway. I was going to write up a good article on this one, but it seems I was literally...