Hello Service Manager fans,
After a very successful launch of System Center Service Manager 2010 last April, Microsoft is pleased to announce the release of Service Pack 1, which is available NOW on Microsoft.com/Downloads.
System Center Service Manager 2010 SP1 addresses critical feedback received from customers and partners and provides greater language support, improved performance capabilities, and a number of usability enhancements.
With Service Pack 1 for System Center Service Manager, language support for the entire product is added for the following languages:
In addition to the additional language support, over 500 improvements were made to address issues and customer change requests.
SP1 also provides official support for SQL Server 2008 R2.
A few other important notes about the bits:
System Center Service Manager 2010 SP1 is available through the Microsoft Download Center here:
Eval/Retail bits - http://www.microsoft.com/downloads/details.aspx?FamilyID=5118055b-9cd7-45cd-bae6-7fc287d832d7
Authoring Tool bits - http://www.microsoft.com/downloads/details.aspx?FamilyID=78dcb15b-8744-4a93-b3fa-6a7a40ffeaae
Select Bits – supposedly these will be available for download today on the various Microsoft volume licensing sites.
Details on System Center Service Manager 2010 and the rest of the System Center suite can be found at www.microsoft.com/systemcenter.
Is their a non-eval version of Sp1 somewhere? The Link only shows an "Eval" version of Sp1.
The page says 'Eval' but it is also the 'Retail' bits if you have a product key that you can enter. Normally you would purchase the Retail bits from a licensed reseller and they woudl provide you the product key.
If you are a volume licensing customer you can get the 'Select' bits which dont require a product key from the various volume licensing download sites.
The select version of the SP seems to have been pulled back from the volume licensing sites short after the release.
Any ideas why?
They had to take the bits down temporarily because the German release notes were placed in all of the language folders. They should be back up soon. Hopefully today. Sorry for any inconvenience.
Would be nice if Microsoft would list the 500 fixes somewhere. I can't believe 6 months has passed and there are no new features. This product is in desperate need of feature enhancements before Q3 2011. Also SP1 hasn't been posted to VLSC website yet.
When might we expect to have SP1 available again on VLSC?
Would like to know about SP1 as well. As usual VLSC support is no help.
Would like to see a list of the 500 improvements.
Create Request still show step 1 regardless of the step you are on. I thought this was supposed to be fixed?
Since upgrading to SP1 a couple of weeks ago, I have experienced repeated console crashes when viewing configuration items. What I mean is ... the console user interface displays an error message and then the user interface dissappears.
Is my experience isolated, or is there a known issue I should be aware of?
In the three months prior to SP1 (using RTP + CU3) I never experienced anything like this
Is it really that hard to create a list. I'm not asking for all 500, but a top 20 would be nice. The following are still an issue after SP1. I actually can't find one thing that is fixed in SP1.
1. Scrolling and dropdowns over RDP don't function with mouse
2. Sorting by incident number is still incorrect, IR28 is before IR2
3. Alternate contact method still randomly used the SIP address instead of email
4. Console navigation performance is still sluggish at best
5. When creating a request through end-user portal, "Step" graphics don't change for step 2 and 3. Step 1 is always highlighted
6. No dashboard support for SharePoint 2010
7. High CPU on MonitoringHost.exe since SP1
Service Manager is in desperate need of enhancements. I know this is the first version, but there are some basic features missing.
Also seeing very high cpu with MonitoringHost.exe since SP1 on 2008 R2.
I see now that a lot of people are seeing very high CPU usage on MonitoringHost.exe since the installation of SP1. When this happens, it makes SCSM unusable as workflows grind to a halt.
Is this anything going on at Microsoft with regard to getting this fixed?
Although I have heard of a couple of customer having this issue, as far as I know it has not been filed as a case with Microsoft support. Therefore it also hasnt been escalated to the product development team. If you are experiencing this problem, please open a case with Microsoft support so we can get a closer look at what is going on. Based on that we may need to issue a fix.
Thanks, Travis. I might need to raise a case, it's unusable like this. Lucky for me it's not in production yet but we definately can't go live with it.
There's 2 or 3 people that say they've already opened cases in the forums. Probably like us, our support gets done out of China or somewhere so you probably don't even get to hear about it.