Archive

Archive for the ‘SCSM 2010’ Category

Desktop optimisation windows 7 and office 2010 – notes from the field

October 22nd, 2011 verteto 1 comment

Recently we hosted an event about “Desktop optimisation – efficient windows 7 and office 2010 deployment – notes from the field”. This seminar not only listed many of the new features and functionality that are included in Windows 7 and Office 2010 but also answered many deployment questions including some notes from the field.

The result can be found here:

http://seminar.the-d-spot.org/Desktop optimisation – notes from the field – 17102011.pdf

Belgium System Center Day

November 18th, 2010 Ben De Vriese No comments

Last week the SCUG community held an event covering all major System Center products. The first part was all about System Center Service Manager; implementing, customizing, and extending the product. Also a project overview about integrating Service Manager into an environment. The next topic was more about our interest: SCCM & PowerShell by Kim Oppalfens. Kim demonstrates how to add new computers to a collection using PowerShell with less lines and easier to read than VBScript. He showed the use of PowerShell in Task Sequences. And something we all love; code examples. The SCCM 2007 SDK contains tons of PowerShell examples which we can reuse! Take look at this blog post on Technet as a start.

Next runner up was Wally Mead, who we met before on a previous SCUG event. He talked about the similarities and changes in Software Distribution with Configuration Manager vNext. This was a very informative session, with working demos and some typical Wally Mead jokes :-) From his session, we learned some of the new features and the slight different approach in vNext’s software distribution. An user-centric approach that is, giving users more flexibility to switch between multiple devices and networks.

A part of this user-centric approach is a better integration with App-V, to deliver applications to users, instead of limiting software delivery to computers. For example, an owner of a computer will get his software deployed like before. But if he logs on to another machine, not all his software will be deployed to that computer. He will be presented with the virtual version of his software (through App-V or RDP/TS), which is a time and bandwidth saver.

Like I said above, vNext has an option to tie user(s) to a computer (User Device Affinity). This can be used in combination with Requirements and Conditions, to deliver software for example.

User Device Affinity provides the ability to define a relationship between a user and a device. It allows the admin to think “user first”, while also ensuring the application not being installed everywhere the user logs on.

Configuration Manager v.Next supports:

  • Single primary user to primary device
  • Multiple primary devices per user
  • Multiple primary users per device
  • The system allows both the administrator and user to define this relationship. It can be set in different ways. Based on usage threshold on the client, using an import file from external system, as part of the OSD, end-user through the Software Catalog and manual by an Administrator.

User Device Affinity allows the deployment of software-based on the nature of the relationship between the user and device. Each software can have multiple “installation-scenarios”. For example, we created 3 scenarios on how to install Outlook:

  1. It can be installed physically on the computer (MSI)
  2. It can be installed virtually (App-V)
  3. Check your mail online (OWA, Outlook Web Access)

When a user logs on to his computer where he is the owner of, you use scenario 1 and install the MSI. When a user logs on to a computer of his colleague, we don’t want to install outlook on the pc. Here we use scenario 2. And when he logs on to a computer, where he is not the owner of and no AppV-client is installed, we create a shortcut that leads him to the OWA or a RDP session to a TS (scenario 3).

So it doesn’t matter where the user logs on, he can always use his software and check his email.

A big improvement in vNext is that you can control exactly when to install the software.

Wally also showed us On Demand Software installation via a webportal. This way users can request software, and a manager must approve this request. This saves time for both the users and the IT staff.

You can find all sessions at the bottom of this post, we can suggest Wally’s session about vNext, it’s worth the time!

vNext official name will be System Center Configuration Manager 2012 so let’s start using this name.

We would like to thank the SCUG-team to organize this kind of events. Good Job!

Stijn & Ben.

08.30 – 09.00
Keynote by Alexandre Verkinderen & Kenny Buntinx
http://technet.microsoft.com/nl-nl/edge/system-center-day-belgium-keynote.aspx

09.00 – 10.15
Implementing, Customizing, and Extending System Center Service Manager by Travis Wright
http://technet.microsoft.com/nl-nl/edge/system-center-day-customizing-and-extending-service-manager.aspx

10.30 – 11.30
Pre-assessment of System Center Service Manager by Kurt Van Hoecke & Ricardo Noulez
http://technet.microsoft.com/nl-nl/edge/system-center-day-pre-assessment-of-system-center-service-manager.aspx

11.30 – 12.30
SCCM and that overrated Dos-box replacement by Kim Oppalfens
http://technet.microsoft.com/nl-nl/edge/system-center-day-sccm-and-that-overrated-command-prompt-replacement.aspx

13.30 – 15.00
Software Distribution in Configuration Manager v.Next – Similarities and Changes by Wally Mead
http://technet.microsoft.com/nl-nl/edge/system-center-day-configuration-manager-v-next-application-management.aspx

15.00 – 16.00
R3 power management : Lessons learned from the field by Kenny Buntinx
http://technet.microsoft.com/nl-nl/edge/system-center-day-configuration-manager-r3-lessons-learned-from-the-field.aspx

16.15 – 17.15
System Center Data Protection Manger 2010 in the datacenter by Jason Bufington
http://technet.microsoft.com/nl-nl/edge/system-center-day-data-protection-manager-dpm-2010-deep-dive.aspx

17.15 – 18.00
System Center in the Datacenter by Alexandre Verkinderen & co
http://technet.microsoft.com/nl-nl/edge/system-center-day-round-up-system-center-in-the-datacenter.aspx

How to setup System Center Service Manager 2010 (SCSM 2010), Web Portals

Like mentioned in my previous post, I’m currently working with the SCSM 2010 in a lab environment. After reading a discussion on TechNet I wondered what the feeling must be to work in the Web Portal (Web Console) instead of the SCSM 2010 client. That’s why I installed the Web Portal on my virtual machine.

Before you can install the setup of the Web Portal you need an IIS Server to be configured. Because my VM is a DC, I installed the IIS (Web Server) Role on this machine. 

web11

Prerequisites

  • SCSM 2010 Management Server
  • SQL Server 2008 SP1
  • 4 GB of RAM
  • IIS 7.0
  • ASP.NET 2.0
  • Installation

Run the setup.exe (the same one you used to install the SCSM Management Server) and you’ll be presented with the “Microsoft System Center Service Manager Setup Wizard” where you have to choose to “Install the Service Manager Web Portals” .

web1

Getting started – Product Registration”: You can or fill in the Product Key or you can use the Trial Option (which will only last for 180 days). Read the EULA, mark it as read and click Next.

web2

Getting started – Installation Location”: Choose a location for the virtual website and be sure you have enough disk space to run it.

web3

Prerequisites – System Check Results”: The installation of the Web Portals will only proceed once all the prerequisites are fulfilled. The IIS 7.0 needs to be installed before you start the setup for the Web Portals (install the IIS role in the Server Manager).

web4

Configuration – Configure the Service Manager self-service portal name and port”: Choose a website name and port (the default port is 443 (HTTPS)) and select the server which will issue the SSL Certificate.

web5

Configuration – Select the Service Manager Database”: This is the page where the info is required of the Service Manager Management Server. As you can notice in the screenshot the SCSM database I use is the ServiceManager which is created on the SRV2008 SQL Server.

web6

Configuration – Configure The Account For The Service Manager Portals”: I kept the default setting (Local System Account).

web7

Configuration – Help Improve System Center Service Manager”: Off course I’m willing to participate in the Customer Experience Improvement Program!

web8

Configuration – Installation Summary”: You can check if all the settings and components you configured are correct. If so, press Install.

web9

Finished – Setup Completed Successfully”: As you can see in the text on the top of the page two portals were created. One for the end-user and one for the analyst.

On the bottom of the page you can see the additional option to open the “Encryption or Restore Wizard”. In this wizard you’re able to generate a key which can be used to encrypt or restore your settings.

web10

More info:

The Self Service Portal

Google

How to setup System Center Service Manager 2010 (SCSM 2010), Management Server

Today I installed the SCSM 2010 in a lab environment and there where some issues I encountered during the installation. These issues will be explained during the series of screenshots.

Prerequisites:

  • SQL Server 2008 SP1
  • Domain with Active Directory
  • Connection to the internet
  • 4 GB of RAM
  • Authorization Manager Hotfix (975332)
  • .NET Framework 3.5 SP1

    Installation:

    When clicking on the setup.exe (which has been extracted to the temp folder of the used profile) the installer began to download & install the .NET Framework 3.5 SP1.

tutorial1

System Center Service Manager 2010 Setup” page installing the .NET Framework 3.5 SP1.

tutorial2

Once the .NET Framework was installed, the “Microsoft System Center Service Manager Setup Wizard” opened and I could choose between the “SM Management Server” and the “SM Data Warehouse Management Server”. I could notice a difference here for the requested memory. The “SM Management Server” needs 4 GB of RAM whereas the “SM Data Warehouse Management Server” needs 8 GB of RAM.

tutorial3

On the “Getting Started” page I did not register the software because I’m using it in a lab environment. If you are going to implement the software in your enterprise, be sure to request a license from Microsoft.

tutorial4

tutorial5

On the “Installation Location” page I didn’t change anything. Note that the System Center Service Manager only requires 1GB of free space!

tutorial6

The wizard is “Checking for requirements…

tutorial7

On this page – “System Check Results” – I encountered some issues. First, my virtual machine did not have 4 GB of RAM allocated. I changed this and re-ran the installation. This issue was covered but the wizard showed me that the “Authorization Manager Hotfix” was not installed. I subscripted on the Microsoft webpage in order to receive the hotfix in my inbox. The email contained a link to the download location and a password for the .exe file. The .exe file will extract to a default location and the following file is generated: “Windows6.1-KB975332-x64.msu”. Run this file and the hotfix will be installed.

tutorial8

On the “Configure The Service Manager Database” page I lost some time because I did not install the SP1 for the SQL Server. Because of this the wizard could not locate the freshly installed SQL Server 2008. Once SP1 was installed, the wizard could locate the SQL Server and I decided to create a new database for the SCSM, called “ServiceManager”.

tutorial9

On the “Configure the Service Manager management group” I chose the name “ServiceManagers”. The persons in this group will be able to manage the SCSM 2010. The “sm\ServiceManagers” stands for the AD Group “ServiceManagers” in the domain “SM”.

tutorial10

Configure The Account For Service Manager Services

tutorial11

Configure The Service Manager Workflow Account

tutorial12

Help Improve System Center Service Manager

tutorial13

Use Microsoft Update To Help Keep Your Computer Secure And Up-To-Date"

tutorial14

Installation Summary”. Short overview of the completed wizard.

tutorial15

Setup Completed Successfully

tutorial16

System Manager Management Console”. I’m now completely ready to go for it…

tutorial17

More info:

Documentation on Management Server

Documentation on Data Warehouse Management Server

Info on the installation of the Service Manager 2010 Beta 2 Data Warehouse Management Server

SCUG.be – System Center User Group

… and off course: Google