SCCM vNext CEP Program Application Management Part 1

Standard

Last week we had the first part of the Application Management meetings from the CEP program. The primary takeaways from these session were:

  • Mainstream software distribution is made better, easier and faster
  • vNext Software Distribution enables: User Centric Client Management is introduced, Ability to deploy software to devices and new advanced application technologies and screnarios

In this meeting the team focused on the Empower Part of User Centric Client Management in vNext.

The following topics are covered in this ‘Empower Part’:

  • Enables IT to provide a flexible environment.
  • Users must have the ability to connect from anywhere on any device the choose
  • Automatically detects network conditions and device configuration to determine the most appropriate services.

Configuration Manager vNext does have the following new features  for Software Distribution:

  • Improvements on the application Model
    • Incorporates all supported software types such as MSI, Scripted Install Software, App-V Applications and mobile applications
    • Better dependency handling
    • It’s now possible to add installation requirement rules for software
    • User device Affinity. This is the ability to say on software installs on certain computers and don’t install on other computers.
    • The monitoring part of deploying software is improved. The in-console monitoring is improved.
    • New End user features as Software Catalog (Webportal where users can search for software and install it) and a Software Center
    • Beter Content Management on distribution points
      • State Based Distribution Groups; the ability to group Distribution points and deploy software through these distribution groups
      • Improved placing of software on the distribution points, such as single instance content store

See below the comparison diagram  of the changing names and functionalities:

In the 2007 version of Configuration Manager the App-V integration is not the most optimal integration. In vNext there are some imporovement which are needed:

  • Integration requires the App-V 4.6 Client
  • Also new improved User Centric features
    • Enable support for application dependencies
    • Improved Update behaviors
    • Selective publishing of components
    • Dynamic Suite Support
    • Integration with Remote Desktop Services
    • Content Impovements
      • Streaming improvements
      • Reduce virtual App Footprint when using Download and execute

So thankfully there are some improvements on the App-V integration. In the next weeks I will test the new integration and will come back on this topic

As said earlier one of the new things is the Software Catalog. The Software catalog is there for end-users to:

  • Browse and search for software
    • Fully localized for site and applications
    • Search via category or name
    • Install Software
      • Direct self-installation from software catalog
      • Automatic installation after approval
      • Request Application
        • Request approval for software
        • View request history

     

SCCM 2007 R3 Released Today

Standard

Today Microsoft released Configuration Manager R3. With this new version Microsoft has released some great functions to Configuration Manager 2007.  The most important improvment which comes with R3 is power management. With Power Management you can made a next step to a Green IT landcape. Other interesting functions are improved Active Directory discovery and dynamic collection membership. I already tried the Beta versions of R3 and it’s working great. So give it a try and install the R3 version of Configuration Manager

Installing Opalis 6.2.2 ServicePack 1

Standard

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.

Part 2: Installing your own Opalis Test Environment

Standard

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.

Solution:

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…

Part 1: Installing your own Opalis Test Environment

Standard

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:

Main Software
Opalis 6.2.2 SP1 180 day trial
Opalis sample workflow catalog
Libraries
Java JDK 6 Update 4
JBoss Application Server 4.2.3.GA
Hibernate Validator 3.0.0.GA
Hibernate Commons Annotations 3.3.0.GA
Richfaces-API 3.3.1.GA
Richfaces-UI 3.3.1.GA
Richfaces-Implementation 3.3.1.GA
JBoss-EL 2.0.1.GA
JSF-Facelets 1.1.14
Java Native Access 3.0.9
JAX-WS RI
JBoss Seam-Core 2.0.2_SP1
JBoss Seam-Remoting 2.0.2_SP1
JBoss Seam-UI 2.0.2_SP1
JBoss Seam-Debug 2.0.2_SP1
JBoss Seam-Mail 2.0.2_SP1

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!