As with any piece of software, how you deploy it can greatly impact its reliability, performance and scalability. System Center 2012 is no different and here on the Service Manager support team we see quite a few issues that could have been prevented with just a slightly different approach to how the product was implemented.
For example, take a look at Deployment Scenario Topics in our System Center 2012 Service Manager (SCSM 2012) documentation library on TechNet. It includes a scenario for installing Service Manager on a single computer, a scenario for installing Service Manager on two computers, and a scenario for installing Service Manager on four computers. While all three of these scenarios offer a workable topology for implementing Service Manager, only the scenario for installing Service Manager on four computers is recommended for use in a production environment.
So if you have a SCSM 2012 deployment planned, feel free to test using the one and two computer scenarios in your lab, but when it comes to production, plan on using the four computer topology and be sure you read through our short installation guide here. Spending a few minutes reading through the TechNet documentation may end up saving you a great deal of pain, frustration and troubleshooting man-hours later on down the road.
J.C. Hornbeck | Solution Asset PM | Microsoft GBS Management and Security Division
Get the latest System Center news on Facebook and Twitter:
System Center All Up: http://blogs.technet.com/b/systemcenter/ System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/ System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/ System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/ System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/ System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm
Windows Intune: http://blogs.technet.com/b/windowsintune/ WSUS Support Team blog: http://blogs.technet.com/sus/ The AD RMS blog: http://blogs.technet.com/b/rmssupp/
The Forefront Endpoint Protection blog : http://blogs.technet.com/b/clientsecurity/ The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/ The Forefront TMG blog: http://blogs.technet.com/b/isablog/ The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/
我想问下为什么我的epson lx300+ii打印机安装到windows server2012r2不能兼容，问题如下安装64打印出来的不是字体太大就是太小，或者乱码，请问应该如何修改谢谢
My questions are more around how the SQL Server ServiceManager database should be configured?
- how to set MAXDOP (with H/T)
- when/ how often/ what to run for maintenance plans? reindexing, update stats. (I have noticed quite a few high 'Full Scans/sec' periods)
- autogrow settings
- simple/ full recovery? i have read different opinions.
We have seen some issues on scheduler deadlocking.
Any additional BP's would be greatly appreciated.
And this is why after 2010 and 2012 we're probably moving off of SCSM onto another software or SaaS platform. The installs are bloated, performance mediocre at best, not flexible for things like the SSP, and prone to breaking.
I've had to rebuild the DW at least 4 times in the last year, and now my SM server has some strange workflow issue that not even MS is sure where the cause is.
Why cannot MS (a) keep Service Manager simple and easy to use?(b) develop SM for easy deployment ? ( be it for small / big).The whole process right from installation - configuration - customization is like unraveling crypto codes. Each time you encounter an issue and by any luck there's progress, then there's another surprise which catches you off-guard.With all those good products that you have built (with multiple products enhancements ), this product is completely botched up.