Are you speaking of SMS 2003 or SCCM? A lot has to do with the size of your environment, number of clients, etc. 1. The installation is straight forward provided you spec out a decent server or set of servers. 2. Make a decision to install it on the same with SQL server or put it and SQL on separate boxes. I vote put them on the same server. 3. If SMS 2003 a challenge "may" be getting the SMS client installed. So make sure to read over the installation methods. 4. Another challenge "may" be tied to how routing is configured in your environment as software deployments "may" lead to bandwidth saturation. Therefore read up on configuring throttling at the sites.
There's a lot tied to the installation and configuration but once you get her up she pretty much hums. Then again like any woman she can be hard to figure out at times. Be sure to check out the MyItforum site as it's considered probably the Best resource for SMS related issues. It really doesn't matter which book you get just get one as it'll at least give you an overview of the basics. After that it's all hands on. gl hth On Fri, May 22, 2009 at 9:00 AM, Owens, Michael <[email protected]>wrote: > All - > > I have been tasked with starting up SMS on our environment. The problem is, > I cannot fins a good start to finish write up on it... Is there a good > resource for this? Or if SMS sucks I am open to alternatives as well... I > know nothing about this. > > Thanks. > > Mike > > This message, and any response to it, may constitute a public record and > thus may be publicly available to anyone who requests it in accordance > with Chapter 149 of the Ohio Revised Code. > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
