I'll be going through the details of troubleshooting and hoping I can keep it under an hour. :)
No, John's up next month. Then, "Rodtober". November is Michael Niehaus with MDT and ConfigMgr 2007, 2012. And, we'll round out the year with Wally Mead again (another ask Wally). In December, we'll announce the line-up for the first 6 months of 2012, which will include some live stuff from MMS 2012. -----Original Message----- From: Joseph Heaton [mailto:[email protected]] Sent: Friday, August 12, 2011 2:04 PM To: NT System Admin Issues Subject: RE: SCCM Install/SQL Question Rod, thought you were talking next month... by the way, what will you be discussing in your presentation? >>> Rod Trent <[email protected]> 8/12/2011 10:37 AM >>> Hi, Seth. You should definitely test this scenario first. ConfigMgr can create stress on any server due to the processes it manages, however, for your situation, you should be fine. Incidentally, next month's SCCM Guru event is being presented by the "SQL god", John Nelson. You should plan to attend: http://bit.ly/nTP0Yg -----Original Message----- From: S Conn. [mailto:[email protected]] Sent: Friday, August 12, 2011 1:09 PM To: NT System Admin Issues Subject: SCCM Install/SQL Question Hello everyone. I'm about to install SCCM for the first time. I'm confident about my plans so far, but I have questions. Right now I have SCCM planned for one server and a dedicated SQL server, hosting a number of databases for other products. I would like to save money and just have SCCM use that SQL server as well for its databases. However, everything that I've read in books/help file/internet talks about installing to either a local SQL server or a freshly-installed SQL server. I have found no information regarding what would be affected if I installed it on an existing SQL server. I'm sure everything will be fine, however due to the lack of information I don't feel confortable going forward without asking some experts. My question: What impact should I expect if I ran the install for SCCM and told it to use the existing SQL server? Will SCCM play nice with the existing configuations? Will it play nice with anything using Reporting Services? I'm also installing Sharepoint to use this SQL server as well, will those two play nice? I was thinking about installing SQL locally, installing SCCM, then migrating the database to my existing SQL server and uninstalling the local install. Would this be a suggested route to take? I also read that it's suggested to keep the database local. I'm looking at 1300 clients in this system. Would I really see that big of an impact to warrant using a local database? Since SCCM can handle 25k clients, I'd assume my lowly 1300 wouldn't be taxing at all. If you have done this in your environment, I apprieciate any insight you have on this. I'm sure "Test Lab" would answer much of these questions, but I don't have the resources at the time. Thanks, Seth ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
