個人檔案Omar's Blog on Systems M...相片部落格清單 工具 說明
9月18日

SMS 2003 OSDFP update available!!

Microsoft has released the OSDFP update for SMS 2003 The updated OS deployment feature pack can now deploy the x64 bit edition of Windows XP and is Vista Ready, so you can use it as the deployment method to upgrade your desktops from your current OS to Windows Vista. It also can use the enhanced User State Migration tooling (USMT 2.6.1 / USMT 3.0) for maintaining the customised settings for the desktop etc. The update also contains some extra reports for deployment status reporting through the reporting site.
 
Read more and get the download here!
9月8日

SMS 2003: Upgrade OSDPF for Vista support!

Great news: SMS 2003 will support the deployment for Vista through an update of the Operating System Deployment Feature Pack (OSDFP). But will this version also support our precious XP etc. WIM images made with OSDFP v1 ??
 
I haven't seen it yet, but I am afraid that one needs to redo all existing images. The old version created a WIM image file that does not comply with the current WIM specs for Windows Vista, or like Wally Mead said at MMS 2006: let's call the OSDFP v1 WIM version 0.9, Vista will have 1.0  . He explained that the OSDFP team created OSDFP v1 based on the latest WIM specs at that time available. Due to the continuing enhancements being made on WIM during the Vista development, they will be quite 'out of sync'. Reason enough to wait when you're about to start with OSDFP for your current XP desktops. Wait untill the upgrade goes RTM!!
 
The Update is in public beta for a while, so let's hope it will be availlable soon!
9月7日

SMS 2003 DMFP Updated for WM5 devices

The updated SMS 2003 Device Management Feature Pack allows SMS 2003 to manage mobile devices running Windows CE (3.0 or later) and Windows Mobile software for Pocket PCs (2002 or later) with updated support for Windows Mobile 5.0 and Windows Mobile Pocket PC Phone Edition 5.0.
 
Read more here or download the feature pack. I'll be trying the DMFP at home, so I'll probably post something about my experiences with it later on....

SMS 2003 Management Point IIS Account Permissions

One that will save your skin! A very good article about Management Point IIS Account Permissions from the From the SMS & MOM supportability log. Read it here ......
9月3日

SMS V4: P2P distribution tool superseded?

One of the new features in SCCM 2007  (SMS V4) will be the integration of a Peer-to-peer (P2P) distribution method. Microsoft offers this solution for the smaller remote offices where no local DP is availlable and/or low bandwith connectivity scenarios. 
 
You'll probably just have to pick out a workstation at the remote office and add it as a SMS site system, check the "Use this system as a remote office distribution point" and set a subnet or site code like a protected DP. This system will download the software package from a 'real' DP and presents it to it's peers. After installation the package will be discarted I guess, concidering impact on disc space, network etc.
 
I was re-reading some implementations I did, and started to wonder if we really needed this feature. Or is it already superseded before going RTM?
 
First of all, it's not new. SMS Alliance Partner 1E (www.1E.com) had this working in it’s SMSBranch Nomad product, which checks availability (on-line, disc space, useractivity etc.) of all branch office PC’s and picks the best one available. Microsoft implements it as a static method (earlier article).
 
Second, I can image that there are still parts of the world that do not have DSL or other high speed links at their disposal or a Windows Server platform (for an SMS Distribution Point) at their site. But these situations were even more current in the days of SMS 2.0 and SMS 2003. And we still got that fixed. I remember an implementation were we used Windows 2000 Pro boxes with an extra 80 Gb HDD to facilitate as Distribution Points (protected). Sure, it could do max 5-10 connections at one time, but what's wrong with that at a remote office?
 
Don't get me wrong here: I really think that adding all featured tools of SCCM2007 are necessary to make SMS more "admin friendly" and more competative towards other Systems Management solutions like Altiris, Tivoli, UniCentre etc. The people who need to do their daily work behind the console will love it!
 
But as an implementor, I do hope that the innovation on SMS V5 will focus on:
  • A better performing SMS client. Please: a new one from design up... . No more cyclic processes, we do have Pentium 4 and higher nowadays.
  • Less confusing data entries and sharper reports (just open the report for OS versions. Why are there multiple entries for the same machine with no obvious diffences? Try to to explain it to your average ITIL process guy  )
  • Integration into a 'Common Infrastructure': get rid of that MP and give us a AD application partition!!