Error: "1639. Invalid command line argument." when installing SCSM 2012 SP1

If you are installing System Centre Service Manager 2012 (SP1) and are receiving what appears to be quite a generic error Error: “1639. Invalid command line argument.” then hopefully this will save you some time.

Untitled

Having spent a good few hours installing & reinstalling, trying different operating system versions (even though they were on a office supported list) I decided to pay attention to what the log file was actually telling me. Each time the installer got to the same place with “Setting SDK username and password”. The password I was trying to use in my lab environment and a ‘@’ symbol in it (no prizes for guessing what the password was I was trying to use!) Once I had changed my password and removed the @ symbol everything sprung into life.

This is rather annoying as the wizard itself accepts and is quite happy with password during the process or specifying the service and workflow account details.

Hope that saves someone a bit of time if they come across a similar issue.

Advertisements

System Centre 2012 SP1 Rollup 2 for VMM

 

Microsoft released Update Rollup 2 for System Centre 2012 SP1 a few weeks back but with this release there was one missing component – VMM. Last week Microsoft updated RU2 to include the fixes for VMM 2012 (under the KBs KB2826405 & KB2826392).

It is worth noting that you MUST uninstall VMM RU1 before you install this RU2 release, this is due to a problem with the original Update Roll up 1 and the way the files were packaged.

If you download RU2 from the Microsoft update catalogue and have already manually installed it, you must uninstall RU2 then uninstall RU1 and reinstall RU2 again. If you use WSUS for your updating you won’t receive RU2 until you have manually uninstalled RU1.

Microsoft has released an apology for all this installing and uninstalling you have to do:

‘We apologize for any inconvenience this causes your organization. We have performed cause analysis on the issue and have established processes to prevent future recurrences of this situation.’

The updated fix and list of updates are available here >> http://support.microsoft.com/kb/2802159

SCOM 2012: System Centre Global Service Monitor (GSM)

Most businesses will be monitoring their IT services from an internal perspective with SCOM. Problems such as SQL service failures, disk failures or a web application pool that has stopped responding foe example but none of these monitoring from an external, customer perspective.

With System Centre 2012 SP1 Microsoft has released its System Centre Global Service Monitor (GSM) service. This new service allows you to test your externally facing websites and even more impressive is that your also able to configure multi step web transaction testing.

With GSM you will be able to test from a true user perspective – GSM can be a customer or user of your external site or service. A good example would be an online shop. You could have GSM login as a user, browse the store and try to preform a transaction on the checkout.

Its likely that you would know if your store was down completely – your internal SCOM monitoring would hopefully alert you to this but how about transactions times? Are customers going to wait if your checkout process is not rapid? With GSM feeding information back into SCOM (think Application Monitoring – APM) drill down into this data and if there is a delay taking place e.g. if there was a SQL query that was slowing your customers down for example you can get SCOM to automatically create a standard SCOM alert and if integrated with SCSM (System Centre Service Manager) get it to raise a service ticket for your development team to look into – very cool stuff!

Microsoft currently has the following 15 locations from around the world that you can test from which should cover the requirements of most users:

  • Australia: Sydney
  • Brazil: Sao Paulo
  • Europe: Amsterdam, London, Paris, Stockholm, Zurich
  • Russia: Moscow
  • Singapore
  • Taipei
  • United States: Chicago, Los Angeles, Miami, Newark, San Antonio

You can currently sign up for a free 90 day trial from here >> https://orgaccount.microsoft.com/signup?offerIds=BE2A46EF-0639-43a4-8323-BB5E1D4340D3. You will need to use a Microsoft Organisational account (if you use Office 365, Intune, Online Backup, CRM Online for example you already have one of these – if not you can create a new account for the trial period.). It is worth noting that you MUST have an active software assurance policy with Microsoft if you want to extend this into a full blown subscription after your 90 day trial is up.

To use GSM within your environment you need to be using the latest System Centre 2012 SP1 version which has recently gone to GA status so available for download from here >> http://technet.microsoft.com/en-us/evalcenter/hh505660

Once you have SCOM SP1 downloaded, installed and configured just download GSM & install into your SCOM server which will install and import the required management packs.

This video from the 2012 European TechNet event shows all this in action >> http://channel9.msdn.com/events/TechEd/Europe/2012/MGT307

System Centre 2012 SP1: Update Rollup 1

Hot on the heels of System Centre 2012 SP1 release which was released to TechNet, MSDN and VLC customers towards the end of last year and hit GA for everyone else earlier in the month a new Update Rollup (RU1 – KB2785682 ) has now been released. This update includes fixes for a few issues features found in the initial SP1 release code. The main area of focus is SCOM and VMM and App Controller. You can find the update here >> http://support.microsoft.com/kb/2785682.