Today I upgraded my OpsMgr 2012 SP1 Beta environment to SP1 RTM. The upgrade process is not supported by Microsoft but works without any problems. The upgrade process of the server components completed in 45 minutes.
The original Operations Manager 2012 SP1 Beta version number was 7.0.8925.0:
Yesterday it toke me 30 minutes to upgrade my current Configmgr 2012 lab environment from SP1 beta to SP1 RTM. From Microsoft perspective it’s a unsupported way of upgrading but in my case the upgrade process was very easy and completed without any problems.
The Beta version number was 5.0.7782.1000:
Last week Microsoft released the updates KB2506143 and KB2506146 through Windows Update. Caution with installing these updates when using Configuration Manager 2012. After installing this update you could end up with broken clients and/or servers. The client health check on clients will show the following error in the console:
Based on the existing script from Jörgen Nilsson (http://ccmexec.com/2012/04/unattended-installation-of-the-configmgr-2012-pre-reqs/) I have created my own ConfigMgr 2012 pre-requisites installation script. I have made the following adjustments:
– Used Powershell function ‘Add-WindowsFeature’ instead of deprecated ‘ServerManagerCMd -i’ command
– Automatically download of .Net 4.0 Framework redistributable
– Removed the installation of KB2552033. This update needs to be installed seperately
It’s a basic script, at the moment there is no error reporting available. The script can be downloaded here: Download Here
Besides the pre-reqs which will be installed through the script you need to solve the pre-reqs stated below:
– Grant Administrator rights on the SQL server if the database is hosted on a seperate server
– Prepare the Active Directory and grant rights on the System Management container
– Install WSUS if you plan to use the Software Updates functionality
– Install KB2552033 if needed
If you have any questions or suggestions for the script, please let me know!
Yesterday evening I had finally some time to install the Beta 2 of SCCM2012. I created my own VNEXT.LOCAL network and I was ready for the installation.
I followed the wizard and started the installation. After 0,5 hour waiting on the following status:
Creating SQL Server machine certificate for Server [VNEXT-DB01]…
INFO: VNEXT-CM01.VNEXT.LOCAL’ is a valid FQDN.
So the installation was doing with my SQL server and that action had broken my SQL server. See the status below:
In the Event Viewer on the SQL server I found the following errors:
Unable to load user-specified certificate. The server will not accept a connection. You should verify that the certificate is correctly installed. See “Configuring Certificate for Use by SSL” in Books Online.
For more information, see Help and Support Center at http://support.microsoft.com.
TDSSNIClient initialization failed with error 0x80092004, status code 0x80.
I removed the SSL Certificate from the SQL Server, after that I was able to start the SQL Server. So the problem was the certificate. I searched the Microsoft Connect site for a solution and found one. The solution was to grant the SQL Server service account read rights on the private key of the certificate. To do this follow the steps below:
2. Add the Certificates snap-in (Note: Select computer account and Local computer in the two pages on the wizard that appears.
When the SQL server is started the installation of SCCM will continue..
Today I run in a very strange issue at a customer site. During the installation of a new Primary Site the Management Point could not be installed due to a incomplete WebDAV configuration.
I was installing the Primary Site on a fresh Windows 2008 Standard Server. I installed all the prerequisites and followed the following technet article to install and configure WebDAV. I started the Configuration Manager installation and when the installation was finished I saw a blue question mark for the installation of the Management Point. I checked the MPSetup.log file in the Logs Directory of the installation and found the following error :Failed to get WebDAV settings on the machine (0x80070002).
I checked the WebDAV configuration for the second time and found out that I was forgotten to Enable WebDAV on my Default IIS Website. So I enabled WebDAV and tried to reinstall the Management Point. The installation still fails with the following log entries in the MPSetup.log:
checking WebDAV configurations WebDAV settings is not setup appropriately [Allow property queries with infinite depth] should be true (false) [Allow Custom Properties] should be false (true) [Allow anonymous property queries] should be true (false) Allow [All users read access to All content] authoring rule should exist (exist)
This was very strange because the settings were correct. After some testing I found the solution to this problem. The solution was very simple. I changed the settings back to how they were in the original state. After applying those settings I did the configuration based on the technet article again. After applying again I installed the MP and the installation ended successfully. Very strange but in the end it worked for me.
After the installation of Opalis which is described on my last two blogs there are 2 things what needs to be done. The 1st thing is to install ServicePack 1 and second one is creating a service for the Operator Console. The first one will be covered in this blogpost. The steps which described below are partly from the install documentation and from my expierence in installing Service Pack 1.
| 1. | Extract the contents of the downloaded Opalis Integration Server 6.2.2 Service Pack 1_6.2.2.51310.zip file |
| 2. | Run the extracted OpalisServicePack1.exe file |
| 3. | Click twice on Next |
| 4. | Click no OK and don’t change the unzip folder and click on Unzip |
| Update the File Management Objects | |
| 1. | Open the Management Server installation folder, by default located in %SystemDrive%Program FilesOpalis SoftwareOpalis Integration ServerManagement Service. Browse to the ComponentsObjects folder. |
| 2. | Replace the existing OpalisIntegrationServer_FoundationObjects.msi file with the OpalisIntegrationServer_FoundationObjects.msi file provided in this service pack. |
| 3. | Perform the following steps to deploy the new Foundation Objects on all Action Servers and Clients: a. Verify that no policies are running, and that no clients or Testing Consoles are open on the computer that you are updating. b. In Add or Remove Programs, uninstall Opalis Integration Server – Foundation Objects. c. Run the OpalisIntegrationServer_FoundationObjects.msi installer. Do not change any of the default values on the installation screens. |
| Update the Operator Console | |
| 1. | Stop the Operator Console. |
| 2. | Copy the OpalisOperatorConsoleSP1.zip file to the computer on which the Operator Console server is installed. |
| 3. | Right-click OpalisOperatorConsoleSP1.zip, and then click Extract All. |
| 4. | Specify or Browse to the location where the Operator Console server was installed during the initial Operator Console server installation. If you followed part 2 of my install opalis blog the location is: C:OperatorConsole. |
| 5. | Click Extract. |
| 6. | On the Confirm Folder Replace page, click Yes for all folders. |
| 7. | On the Copy File page, click Copy and Replace for all files. Confirm that the existing files were successfully replaced with the updated files. |
| 8. | Start the Operator Console. |
After following these steps ServicePack 1 is installed.
The second part of installing your own Opalis Test Environment covers the installation of the Opalis Operator Console. This is not the easiest part of setting up your Opalis environment, but with the steps below you must succeed. If you followed part 1 on the series you have already downloaded the software which is needed for the installation. Follow the steps below to install the Operator Console:
| 1. | Unpack the Opalis Operator Console Installer Script 1.0_1.0.0.0001.zip file to a temp folder |
| 2. | Run the self-extracting file OpalisOperatorConsoleInstaller.exe from the temp folder |
| 3. | Click Yes Twice |
| 4. | Read the importent notes and click OK |
| 5. | Don’t change the extract folder and leave it default and click Unzip |
| 6. | Click Close |
| 7. | Now install the Java Development Kit 6 Update 4 by using the default settings |
| 8. | Go to the Advanced tab of the System Properties (Right Click on My Computer, then Properties) |
| 9. | Click on Environment Variables Button, Under System Variables Click New |
| 10. | Enter the following Information; Variable Name: JAVA_HOME and Variable Value: C:Program FilesJavaJdk1.6.0_04 and click OK |
| 11. | Now search for the Path System Variable and click Edit |
| 12. | At the end of the line add the following: ;%JAVA_HOME%bin |
| 13. | Now extract the JBoss Application Server (jboss-4.2.3.GA.zip) to C:JBoss |
| 14. | Open a command prompt and run the following command in the folder where this file is: java -jar JAXWS2.1.2-20070917.jar |
| 15. | Read the License Agreement and click Accept |
| 16. | Check and make sure that the Jaxws-riLib folder was created |
| 17. | Copy the Operator Console folder from the Opalis Integration Server 6.22_6.2.2.5229 folder to you C: Drive |
| 18. | Open a Powershell console through, Start, All Programs, Accessoires, Windows Powershell and Click Windows Powershell |
| 19. | At the Windows PowerShell prompt, type set-executionpolicy RemoteSigned |
| 20. | Then Type in the following: C:OpConsoleInstallerinstallOpConsole.ps1. This starts the installation of the Operator Console |
| 21. | Press Enter and browse to your JBoss Installation folder from Step 13, Select the folder: jboss-4.2.3.GA, not the root folder |
| 22. | Press Enter and browse to your Operator Console folder from Step 17 |
| 23. | Select No for the question of the Libraries Folder, then press Enter and select the right Libraries folder, which we created in part 1. |
| 24. | Then Select your Database type, in my case it’s the Default: Microsoft SQL Server. Press Enter or choose 2 for Oracle |
| 25. | Then Type in your Database server and click Enter |
| 26. | Then choose your type of SQL Authentication, Press Enter or choose 2 for SQL Authentication |
| 27. | Then type in your Databasename, if you decided not to change the default database name during the installation, press ENTER |
| 28. | Choose the default value for the JBoss bind, so press Enter |
| 29. | Then choose your type of User Authentication, in my case ‘Active Directory’. Type 2 and press ENTER |
| 30. | Then type for Active Directory root DN or choose the default and press ENTER |
| 31. | Select your Domaincontroller and press Enter |
| 32. | Type in your Active Directory port or press ENTER for the default |
| 33. | Then type in your Active Directory Opalis Admins group and click ENTER |
| 34. | The installation of the console is now complete, type exit to close Powershell |
| 35. | Then Open your the LIB folder of your JBoss Installation, in my case: C:JBossjboss-4.2.3.GAbin |
| 36. | Run the run.bat to start the JBoss Server |
| 37. | After some time the console window must say somethin like: Started in 35s:530ms |
| 38. | To start the Operator Console, Go to Start, All Programs, Opalis Software, Opalis Integration Server and Click Operator Console |
| 39. | Then try to Login with the user name which is a member of the Security Group you entered in Step 34 |
| 40. | Congrats your logged in to your Opalis Operator Console!! |
If you get the following error:”The username or password you have entered is not correct.” in Step 39. Check the console window and search for the LDAP Error. This was in my case:
21:11:33,866 ERROR [AccountServicesActiveDirectory] LDAP error javax.naming.AuthenticationException: [LDAP: error code 49 – 80090308: LdapErr: DSID-0C0903A9, comment: AcceptSecurityContext error, data 52e, v1db0 ].
This is a typical AD Authentication Error.
I had to type in my domain before my username in the Username Login field. So MYDOMMYACCOUNT instead of MYACCOUNT. Hope this solves your authentication error also.
NOTE:
When you start the JBoss server with the run.bat. The console window must be open. If you close the console window the operator console will be stopped. In my next Blog I will explain how to run the JBoss server as a service…
Last week I started with the installation of my own Opalis test environment. Based on the CEP information and Technet I was able to install my own Test Environment. This post contains only the installation of the core server components of Opalis. In Part 2 I will describe the installation of the operator console. I will start with the system Prerequisites for Opalis Integration Server:
| Component | Minimum Requirement Technet | What I used |
| Processor | 2.1 GHz dual-core Intel Xeon 3000 series or equivalent | 1 Ghz Pentium III Xeon (Hyper-V) |
| Memory | 2GB | 1GB (Hyper-V) |
| Harddisk | Managament Server: 100MB Operator Console: 200MB Action Server: 50MB |
20GB OS Disk (Hyper-V) 40GB Data Disk(Hyper-V) |
| Operating System | Windows Server 2003 with Service Pack 1 or 2 (32-bit) | Windows 2003 R2 Standard SP2 |
| Additional Software | Windows Installer 3.1 .msi Microsoft .NET Framework 2.0 Microsoft SQL Server 2005 or SQL Server 2008 Microsoft Internet Explorer 7, Internet Explorer 8 (Internet Explorer 7 compatibility mode), or Mozilla Firefox 3 JavaScript must be enabled in the browser. |
Windows Installer 3.1 .msi Microsoft .NET Framework 2.0 Microsoft SQL Server 2005 or SQL Server 2008 Microsoft Internet Explorer 7, Internet Explorer 8 (Internet Explorer 7 compatibility mode), or Mozilla Firefox 3 JavaScript must be enabled in the browser. |
As said earlier installing the Prerequisites are not covered by this post. So in my own test environment I have a dedicated SQL 2008 SP1 server for the database. For the Opalis Server I installed the above server with the prerequisites. The first step is to download all the necessary software. See the table below:
Now it’s time to install Opalis, see below the steps:
| Preparation | |
| 1. | Create a temporary folder on the local disk of your Opalis Server |
| 2. | Copy all the libraries to this folder in a Folder called Libraries |
| 3. | Copy the Sample workflow to the root of the folder |
| 4. | Run the Opalis_180_Day_Evaluation.exe |
| 5. | Click Yes to accept the license agreement |
| 6. | Select the temporary folder that you created earlier |
| 7. | The extractor put all the required files in that folder |
| Install Opalis | |
| 1. | Extract the Opalis Integration Server 6.22_6.2.2.5229.zip file to a folder |
| 2. | Extract the Opalis Integration Server 6.2.2 Service Pack 1_6.2.2.51310.zip file to a folder |
| 3. | Extract the Opalis Quick Integration Kit 3.10_3.1.0.0001.zip file to a folder |
| 4. | Extract the Opalis Integration Pack for Microsoft SC Operations Manager 2007 5.53_5.5.3.0003.zip file to a folder |
| 5. | Extract the Opalis Integration Pack for Microsoft Active Directory 6.10_6.1.0.0010.zip file to a folder |
| 6. | Extract the 180 Day Eval Licenses.zip file to a folder |
| 7. | Start the setup.exe in the Opalis Integration Server 6.22_6.2.2.5229 folder |
| 8. | Click on Install Opalis Integration Server |
| Step 1: Install Management Server | |
| 1. | Click on Install the Management Server |
| 2. | On the first installation screen click Next |
| 3. | Click I Accept the license agreement |
| 4. | Click Next |
| 5. | Choose the installation folder and click Next |
| 6. | Choose a network account, which can access your database and has the right to install software. After entering the username and password click Next |
| 7. | Click Next to install the Management Server |
| 8. | Click Finish to end the installation of the Management Server |
| Step 2: Configure the Datastore | |
| 1. | Click on Configure the Datastore |
| 2. | On the first screen click Next |
| 3. | Enter your SQL Servername into the Server: field and choose your way of authentication |
| 4. | Enter the name of the database and click Finish |
| 5. | Then the database will be created and configured |
| Step 3: Import a License | |
| 1. | Click on Import a License |
| 2. | On the first screen click Import |
| 3. | Search for the OpalisIntegrationServer_180DAY_EVAL.lic file and select that license file |
| 4. | Copy the key from the Opalis Eval Product Licenses.docx file to the Key input field and Click OK |
| 5. | Folow step 2-4 for each of the Integration Packs you want to install |
| 6. | Check if the license is valid en click on Close |
| Step 4: Install the Client | |
| 1. | Click on Install the Client |
| 2. | On the first installation screen click Next |
| 3. | Click I Accept the license agreement |
| 4. | Click Next |
| 5. | Choose the installation folder and click Next |
| 6. | Click Next |
| 7. | Click Finish to end the installation of the Client |
| Configure Opalis | |
| 1. | Start the Deployment Manager from the Startmenu |
| 2. | Right Click on Action Servers and choose ‘Deploy new Action Server’ |
| 3. | Click Next |
| 4. | Fill in the Servername on which you want to Install the Action Server |
| 5. | Choose another service account for the Action Server, the workflows will be executed through this account so choose the right permissions. This account needs the user right assignment ‘Log on as a Service’ |
| 6. | Click Next |
| 7. | Click Next |
| 8. | Click Finish to deploy the action server |
| 9. | Right Click on Integration Packs and choose ‘Register IP with the Management Server’ |
| 10. | Click Next |
| 11. | Click Add en select both of the extracted managament packs |
| 12. | Click Next |
| 13. | Click Finish |
| 14. | Click 2x Agree and now the Integration Packs are imported |
| 9. | Right Click on Integration Packs and choose ‘Deploy tot Action Server or Client’ |
| 10. | Click Next |
| 11. | Select the 2 integration packs and click next |
| 12. | Select the Action Server and click Add |
| 13. | Click Next |
| 14. | Click Finish to deploy the Integration Packs |
Now the basic components of Opalis are installed. You can check this through opening the Opalis Integration Server Client. In one of my following blogs I will explain how to install the Operator Console. If you have questions about this tutorial or about Opalis, please let me know!