• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

SMS experince

My upcoming new project that I wanted to learn more about is SMS. I like to learn more about how SMS is install and how this make deploying and managing software easier. Can someone with experince tell me how the setup went and how it's use in your network? Tips, or links would great

Thanks
-KZ
 
I used to be an SMS Administrator for SMS 2.0

I would recommend you review the micrsoft provided docs like: http://www.microsoft.com/techn.../default.mspx?mfr=true

there is a lot of concepts to these docs so expect a lot of reading and re-reading.


What is cool about SMS is being able to deploy software based on asset inventory. For example you can deploy a patch to just the OSs that need it, or not deploy a big update to machines needing more RAM. We used it for software delivery of this type, asset inventory and remote control of PCs.


My impression of SMS 2.0 was:
I found it was a bear to install in a large corporate environment. So many sites, subsites and package sites.
The reporting tools were crude; however 2003 has improved these.
I also used LanDesk and found that all software deployment tools have their issues.

 
Back
Top