| 個人檔案Omar's Blog on Systems M...相片部落格清單 |  工具  說明 |
|
4月24日 RIP - My 18 year old Ray Bans :'(It was a lovely day in the Netherlands yesterday, so I took my vintage Honda VF 700 C "super magna" for a ride to the office. On my way back home later that day, i had to take the free way to the next exit to take a more touristic route. Riding up the ramp of the freeway I checked to the left for passing trafic as came behind my Ray bans and ripped it off... right under a passing truck.
I am declaring three days of mouring!!!
BTW: Does anyone have a ORIGINAL ray ban Outdoorsman II with brown glasses (G-15) for sale? Just leave me an E-mail 4月23日 How to set up Vista for SMS 2003 client push: enable file sharing and remote registry serviceJust a simple check list to get the client push of SMS 2003 to work with Vista
I was struggling to get SMS 2003 SP 2 automaticly push it's client to my Vista machine. The setup works fine for XP but somehow the client could not install. I checked the application compatibility by installing the client manually, and it works (keeping in mind that not all functionality is supported, but software distribution works fine!).
On the SMS site server the CCM.log revealed that SMS could not connect to the client: error 53. So the network path was not found? Looking into the initial CCR file, ip address and computername were correct. Mapping to the admin share? Not possible. As i went along i noticed that Vista has its share of security 'thingies' that have to be set.
The Checklist
In general, bullit one is already set through logon script or GPO adding the client push account to the local admins group of the client. But file sharing: Default disabled (at least on my Vista Ultimate). Remote Registry Service was configured for manual startup, so i fixed that to start automatic (delayed startup). Maybe a good idea to create a new GPO for it? SMS 2003 ITMU support timeline after SCCM 2007As posted earlier, SCCM will use the WSUS 3.0 engine for patch management of Microsoft and partner products. So what does that mean for organizations that use ITxU variants for software & hardware updates?
Software Update Point (SUP)
With the introduction of SCCM 2007 later this year, Microsoft and partner updates will be deployed with the SCCM 2007 patch management solution based on the WSUS 3.x engine. One of the mayor announcements on that part was HP/Compaq joining the line of partners who will use SCCM as a means to deploy updates for their hardware platform.
During MMS 2007, product managers Marc Umeno and Brian Keller presented patch scenario's using SCCM (see picture attached). Please notice the Software Update Point (SUP) which is a WSUS 3.0 server with a SCCM installed component. This means that any existing WSUS server can be integrated. WSUS is scaled to support 25,000 clients.
SMS 2003 ITxU will remain supported for at least six months
The big question: "Will Microsoft continue to support ITMU?" The answer was yes, but the speakers could not give me an exact timeline - a period of 6 months was named as 'at least'.
Dell Updates
Dell representative John Holleran who was attending, also stated that Dell is commited to provide their updates for the SCCM version soon after the product has launched (unsupported / untested within less than two weeks), but will continue to support ITDU for at least a half year. 4月9日 ITMU V.2 discartedAs of March 27, ITMU V2 is discarted as the update catalogs are not being updated to the latest patches. As you use ITMU with SMS, you should consider an update by errr... last month.
Anthony Clendenen at Myitforum has a well written background article about the development path as wel the symptoms that you are late and upgrade as soon as possible. Please read it here |
|
|
