March 2010 - Posts

• TechDays: New session about Dynamic Memory and RemoteFX

  There was still one session in the IT Pro track that I could not disclose because the announcement was not made yet. But now that we announced the Dynamic Memory and RemoteFX capabilities in SP1 I can disclose the following session: Windows Server 2008 R2 Hyper-V and NEW SP1 features! In this session, we will look at Hyper-V’s progression from Windows Server 2008, to R2, and will also give you a sneak peek of the new Hyper-V features coming in SP1. SP1 will include both Microsoft Remote-FX and Dynamic...(read more) Posted Mar 28 2010, 09:32 AM by SCUG.be Filed under: Virtualization, Hyper-V, Announcement, techdays, Windows Server 2008 R2, Windows 7

• WMI for the SCCM Admin (Techdays Belgium 2010) – MMS 2010 Birds of a feather session

  Hi All, I just proposed a birds of a feather session on WMI for the SCCM Admin. This is the session I’ll be delivering at the end of this month at the Belgian Techdays. Quite a few people have asked me whether the session will be recorded, to which I have no answer right now. However, if you can’t come to Belgium (shame on you, as we have great beer and chocolate), yet you will attend MMS and would like to hear more about this, here is your chance.   If you want to see this session go through...(read more) Posted Mar 24 2010, 10:08 AM by SCUG.be Filed under: configmgr2007, Configmgr 2007, Events, mms

• How to remove a dead server from DPM 2010

  Hey All, Every DPM administrator will have sooner or later this problem.  A server has been removed, decommissioned or went dead suddenly.  But the agent was never installed through the UI so it remains there.  DPM starts to throw errors at you because it’s not possible anymore to backup that server and you want to delete the agent from the console.  And, of course, business requires that you retain the data for a specific period. If that period is within the thresholds that have been set, then there is no problem as you will see later in this post.  However, if you need to maintain the data longer, then you better “restore” the data to a tape, so you can store it away for a longer time. But, for today, here is the procedure how to remove the ‘dead’ agent In this screenshot you can see an agent that is not reachable anymore. So I tried to remove the agent.  I did right click and choose Uninstall This is the error I’m getting.  The server is still in one of my protection groups, so I can’t remove it until I first remove it from the protection group. So I’m going to the protection group Right-click and choose Stop Protection of Group. Note: In case you want to remove a server out of a protection group, but don’t remove the protection group then you need to modify it.  It will automatically create an Inactive protection for previously protected data in the UI I choose to delete the protection group and retain the data After the job, I have an inactive protection for this source So back to my management, right-click on the dead server and Uninstall I have to enter my credentials The agent is being uninstalled But as said, the server is dead, so this is not going to work.  DPM now asks me if I want to remove the agent record from the database.  I choose Yes At the end, DPM still tells me that the job has failed, but since I told him to remove the record, it should have done the job after all.  And indeed, the server will not be listed anymore in the UI. When I go back to protection, I will see that I still have data for that source and still can restore if needed.  Again, don’t forget to restore to somewhere if you need it longer, otherwise the data will be gone after it’s protection period is over Cheers, Mike Posted Mar 22 2010, 03:30 AM by SCUG.be Filed under: dpm, Agent, dpm 2010, System Center Data Protection Manager, Tips and Trics, SCDPM2010

• Service Manager role based security scoping

  An important aspect in the overall configuration of the Service Manager environment is providing access to the SCSM environment to perform operations. This in a controlled way, so End Users, Operators, Resolvers, Change Owners… can easily access SCSM and perform the their tasks in a controlled environment. With Role based security scoping in SCSM there is the possibility to configure a controlled environment for different service roles. A SCSM role profile is a configuration set to define access to objects, views in the console, operations they can perform and members of the role (AD User/Group). SCSM components of a User role are: The security scope: Is the security boundary in SCSM. Boundaries can be set on Group/queue, Class, Property & relationships. UI filter scope: This filter is for defining what an operator can see in the SCSM console. Limiting the options visible in the console improves the usability. UI filters can be set on console tasks, templates and views. User role profile: SCSM includes some predefined user profiles who include a set of allowed operations with a class/property/relationship scope over objects. User Assignment: The members of the user role in SCSM. This can be set for users or groups. (Always recommended to use groups) When configuring role based security scoping we have to think about the profiles that have to be defined in SCSM with the corresponding operations. The different profiles for an implementation is specific and is something that needs to be defined upfront. The following example “runs” through the creation of the Mail incident resolver role. Example info: Only incidents from the “Email problem" category need to be visible for the role. The mgmt console Views access is limited. User roles can be controlled with AD security group. Preparing the Security Scope As specified above, Security Scope for a user profile can be specified on different levels. This preparation step goes through the creation of the group and the incident queue for further use in the user profile creation. Create a group in SCSM Creating a group in the SCSM console is a straightforward task. In this example the In the Service Manager console, click Library, expand Library, and then click Groups. In the Tasks pane, click Create Group. On the Before You Begin page, click Next. On the General page, do the following: Provide a name for the group, such as Email Servers. In the Description text box, type a description for the group. Under Management pack, make sure that an unsealed management pack is selected. In our example we store the information in a dedicated custom mgmt pack. Click Next. On the Included Members page, click Add. In the Select Objects dialog box, select a class such as “Windows Computer”. (Groups can includes members of the same class or from different classes.) In our example select all the Exchange servers in the organization. Click OK, click Next On the Dynamic members page, click Next. On the Subgroups page, click Next. On the Excluded Members page, click Next. On the Summary page, confirm the group settings that you made, and then click Create. On the Completion page, make sure that you receive the following confirmation message, and then click Close.   Create the incident queue Next step in the preparation of the User Role profile configuration is to create a Queue for incidents. In the Library pane, expand Library, and then click Queues. In the Tasks pane, click Create Queue. On the Before You Begin page, click Next. On the General page, type a name in the Queue name box. (In our example, Mail incidents Queue) Work item type box, in the Select a Class dialog box, select a class. In our case “Incident”, and then click OK. In the Management pack list, select the same “roles” mgmt pack that is used to create the group. (keeping the thing together) Click Next. On the Criteria page, build the criteria that you want to use to filter work items for the queue, and then click Next.  In our example, select the Classification Category property in the “Available Properties” area, click Add. In the list, select Email Problems, and then click Next. (more the one criteria can be specified on this page) On the Summary page, click Create to create the queue. On the Completion page, click Close.   Create a User role Profile in SCSM Group and queue are created in the SCSM console, the User Role Profile creation can start. Groups and queues are two configuration items of a User Profile. Mgmt Pack access, Views, templates & tasks are other configuration items in the wizard. If there is a need to limit access to these items then this information needs to be available before the creation of the profile. Example step-by-step for the email incident resolver user profile: In the Administration pane of the SCSM console, expand Security, and then select User Roles. In the Tasks pane under User Roles, select Create User Role, and then select the user role profile. In our example we select the Incident Resolver role. On the Before You Begin page, click Next. On the General page, enter a name and description for this user role, and then click Next. Important Info: on the general page of each predefined role there is a clear description of the rights of the selected role profile. On the Management Packs page, select the management packs that contain the data that you want to assigned access to. In our example “select all” and click Next. On the Queues page, select the Queues that this user role will have access to, and click Next. Here we use the just created Queue for our Email Incident Resolvers role. On the Groups page, select the Groups that this user role will have access to, and click Next. Here we use the just created Group for our Email Incident Resolvers role. On the Tasks page, select the Tasks that this user role will have access to, and click Next. In our example I don’t limit the available tasks. On the Views page, select the Views that this user role will have access to, and click Next. In our example I want to limit the view in the mgmt console and selected only items from Incident management and configuration management. On the Form Templates page, select the Templates that this user role will have access to, and click Next. In our example I don’t limit the available templates. On the Users page, click Add, and use the Select Users or Groups dialog box to select users and user groups from Active Directory Domain Services for this user role, and click Next. On the Summary page, review settings and click Create. On the Completion page, click Close.   To validate the creation of a user role In the Service Manager console, verify that the newly created user role appears in the middle pane. Log on to the Service Manager console as one of the users assigned to the user role. Verify the access in the mgmt console Verify the Views in the mgmt console Only the “Work Items” and “Configuration Items” pane are visible for the user. “Work Items” pane is limited by the Views filter in the configuration of the profile. Only Incidents from the Email queue are visible in the console Read-only access to the configuration items in the console This is just an example how you can setup a user profile. There are a lot of different roles with different configuration items that can be set in SCSM, all depends on the requirements of the environment. Keep in mind that each additional role profile that is created will have an additional load on the server. I hope this gives you an idea how to configure role based security scoping for your environment.   Have fun!   Kurt Posted Mar 21 2010, 05:12 PM by SCUG.be

• Application Virtualization Dashboard – Now in Beta Release!

  The Application Virtualization (App-V) Dashboard helps customers monitor virtualized software applications with a graphical display that makes it easy to stay on top of application usage, health, and compliance. Using the Dashboard’s built-in charts, gauges, and tables, customers can track any APP-V dataset in near-real time.   The Dashboard is now in beta release. Want to give your customers an advance look at the Dashboard, and a chance to provide feedback so it best meets their needs...(read more) Posted Mar 19 2010, 09:32 AM by SCUG.be Filed under: configmgr, sccm, SCCM 2007, configmgr2007, sccm2007, Configmgr 2007, AppV, SCCM 2007 R2, ConfigMgr 2007 R2, SCCM 2007 SP2, ConfigMgr SP2

• Sharepoint 2010 protection in DPM 2010: Part 3

  Hey All, This is part 3 of our Sharepoint protection in DPM 2010 serie and also the last part. You can find the other two parts here: http://scug.be/blogs/scdpm/archive/2010/03/11/sharepoint-2010-protection-in-dpm-2010-part-1.aspx http://scug.be/blogs/scdpm/archive/2010/03/12/sharepoint-2010-protection-in-dpm-2010-part-2.aspx   Item-level recovery So what is Item-level recovery?  Item-level recovery means that you can recover a single document, list, page or whatever.  While it was already possible in Sharepoint 2007 and DPM 2007, you needed a sharepoint recovery farm to do this.  And the recovery farm had to be at the exact level as the production farm.  If you hadn’t had this farm, then you could only recover a complete farm or site collection. With Sharepoint 2010 and DPM 2010, you can do item-level recovery without the need of a recovery farm. Every 24 hours, DPM will create a catalogue of the Sharepoint environment in order to allow the item-level recovery.  In case you need to do an item-level recovery before the 24 hour (such as demo-purposes :-)) you can run the following powershell commands to force this task $pg = Get-ProtectionGroup <dpmservername> $ds = Get-Datasource $pg[index1] (index1 points to the protection where SharePoint is protected, to see all protection groups try $pg) Start-CreateCatalog $ds[index2] (index2 points to the SharePoint datasource, to see all datasources try $ds) Example In my demo environment, I have a sharepoint farm running which is the view you will get after a basic installation with one site configured As you can see in the screenshot, I have modified the home page a bit.  Now I’m going to modify it again Of course, now I realize I made a mistake, don’t have a clue what it used to be before and I call IT to restore :-) So IT will start from the DPM UI As you can see, In the recovery pane, I can see the sharepoint farm and some items under there.  I need to recover a page, so I need to be in the WSS Content After some drilling down, I reached the page that need to be recovered.  I select this page, also select the time from which I want to recover and start a recovery. So here are my options. Recover to original site Recover to alternate site Export selected items into a network folder (not possible in this case) to tape In our case, I’m going to recover to the original site Now I get the option to do a recovery without or with a recovery farm.  Since the purpose of today was to demonstrate it without the recovery farm… Now you need to make some decisions.  The first you need to decide is the SQL instance that you want to use to recover temporarily the content database where the item is located.  You can use the same SQL instance as where the production farm is located, but this will give some additional load so if that is not an option, choose another SQL instance if possible. The second choice you need to make is a location where the database can be temporarily copied to.  This can be any volume or share that you want, but you need to have enough space free to copy the entire database to that location. Next screen, you will need to give again a file location for the temporary location of the item that you want to recover.  This has to be on a front-end web server so that the item can be inserted from there into the sharepoint farm. Again some options in the next screen.  the security that you want to apply, bandwidth throttling if necessary,  SAN recovery if that is supported and a notification if you have configured email notification Finally you will receive the summary. And here the recovery is busy.  You can close this window and follow the progress in the jobs pane. And here you can see that the recovery is successful. Now when I switch back to the sharepoint farm, you can see that my original page is restored That’s it Cheers, Mike Posted Mar 16 2010, 04:37 AM by SCUG.be Filed under: Sharepoint, dpm 2010, System Center Data Protection Manager, SCDPM2010

• System Center Service Manager Update

  The last weeks there were some major updates on the release of System Center Service Manager. A little overview: The Service Manager announce the availability of the EN-US version of Service Manager Release Candidate (RC). In this build there are some significant improvements to stability and performance as well as a number of additional features: Improved Performance, Scale and Stability Improved Notifications with batching email New Change Management Features Reviewer Notification Line Manager Approval New and Updated Reports Improved Self Service Software Provisioning Improved View Editing UX Improvements throughout the product Data Warehouse improvements Authoring Tool Improvements Extending and adding classes and relationships Support for controls in form customization Added workflow activities in activity library Disaster Recovery Localizability and Globalization bug fixed Supportability bug fixes To download, simply go to the Downloads link for this connection, and find Service Manager Release Candidate or follow this direct link and then select all of the following three files on the download details page: SMCDImage_AMD64.exe SMCDImage_x86.exe SCSM_RC_documentation.zip Service Manager needs Authorization Manager Hotfix http://support.microsoft.com/kb/975332/en-us http://blogs.technet.com/umeno/archive/2010/03/12/service-manager-needs-authorization-manager-hotfix.aspx This hotfox fixes an issue that occurs with Data Access Service (sdk service) or the Management Service (healthservice) when either SM or DWStagingandConfig database servers become temporarily unavailable. Maybe not direct the latest news, but an important topic in the Service Manager environment is the Microsoft Operations Framework. Microsoft Operations Framework (MOF) 4.0 delivers practical guidance for everyday IT practices and activities. SCSM helps to apply and automate these activities. People who want to go a bit deeper in this framework: Microsoft Operations Framework 4.0 library Microsoft Operations Framework (MOF) 4.0 download Have fun with the RC testing. Kind Regards, Kurt Posted Mar 15 2010, 05:28 AM by SCUG.be

• Sharepoint 2010 protection in DPM 2010: Part 2

  Hey All, This is the second part of the 3-part sharepoint 2010 protection series In the first part we looked at the things that were necessary as prerequiste to protect a sharepoint farm.  We also looked at some details about sharepoint protection. Today, we gonna create a protection group for sharepoint. Background information This picture shows how DPM works for sharepoint protection. So when we are protecting a sharepoint farm (as said in the previous post) with one click, then we are protecting all these items with their different writers. Basically, when you want to protect a sharepoint farm, DPM 2010 will do everything for you in the back-end.  That’s easy :-) Don’t forget, whenever you create a new content database, and the auto-protect option is enabled, then it will be automatically protected within 24 hours. You will however get a warning alert in the Console that there is a new content database. The same will happen when the Sharepoint Administrators delete a content database.  DPM 2010 will figure this out, give you a warning alert, and you just need to follow the information in that alert to reconfigure the protection group. One other thing that can go wrong is that the Sharepoint administrators change the farm administrator password that you use to protect (see previous post).  At that moment, you will get a warning alert but DPM will continue to backup everything he knows.  However, he won’t be able to query the config database anymore, so he won’t know when there are (for example) new content databases.  So if you are having this issue, perform the commands again from my previous post with the new password (or even new user and passwords) and you’re back ok. Create the protection group Ok, so let’s create a protection group for sharepoint. Choose Servers to continue When I open my sharepoint server, I will see a possibility of choosing a sharepoint farm.  So I select it Here I choose my short-term and long term protection.  No tape library in my environment here so… Time to choose the settings for the short-term protection.  So here you can define how long you want to be able to recover and when he needs to take a full express backup.  Note that this is the only possibility for sharepoint farm protection.  Synchronizations are not possible.  If you wander how many disk space this is going to eat, then you need to calculate your chunk that you have each day.  But how do you calculate this chunk?  Well, with DPM you can find out, so my suggestion would be to use the tool a few days to see the changes, and use the excel sheets that can do an estimate based on your input. DPM will calculate itself the diskspace, but since it doesn’t know how many data changes there are on average a day, it will remain an estimate.  You can however choose to let the auto-grow option on so that it will automatically grows the volume.  (DPM admins, don’t forget to review the great disk utilization reports weekly :-)) Note that the co-location option is not selectable.  This is because co-location is not supported for Sharepoint protection. Choose when you want to create the initial replica.  This is preferred to do outside the working hours if you are having a large farm that is used intensively. Here you have the option to do an automatic consistency check when the replica isn’t consistent anymore or to do it on a daily base on a fixed hour.  My advice, if possible, do it automatically whenever it is inconsistent but if the load is too heavy on your production sharepoint servers, then schedule it on a daily base after working hours or at the most convenient time. Finally the summary Ok.  In our next post, we will show you how you can do an item-level recovery. Cheers, Mike Posted Mar 12 2010, 01:42 AM by SCUG.be Filed under: Sharepoint, System Center Data Protection Manager, SCDPM2010

• Sharepoint 2010 protection in DPM 2010: Part 1

  Hey All, This post will the first of three about sharepoint protection. Part 1 will be about the preparation to protect a sharepoint farm and some background information what DPM can do with your sharepoint farm. Part 2 will be about creating a protection group for the sharepoint farm and some explanation on how it works Part 3 will be an example of how you can do level-item restore and what is necessary to achieve this.   Background information So what can we protect with DPM 2010?  Here’s the list Microsoft Office SharePoint Portal Server 2003 Microsoft Office SharePoint Server 2007 Microsoft Office SharePoint Server 2010 Windows SharePoint Foundation 2010 Windows SharePoint Services version 3.0 Windows SharePoint Services version 2.0 So what can we do?  We can do a farm protection with one-click, there is the possibility of automatically protecting new content databases.  We can do a recovery of an entire farm, an entier Database, a Site Collection, a Site and an Item.  Please note that this Site and Item level recovery only works with Sharepoint 2010 without a recovery farm. Oke, sound all good, time to prepare my environment for Sharepoint protection.   Preparing the Sharepoint environment First is first, in my labo environment, I only had one server running everything from sharepoint, the front-end IIS, the Sharepoint 2010 application and the SQL server.  It ran on a windows server 2008 R2 and was the latest beta available on the connect site. I started with deploying an agent to the sharepoint server.  After that is done, you need to configure something extra on the sharepoint box. So here goes: Open a command prompt as administrator and go to the DPM agent installation bin folder(default: %programfiles%\Microsoft Data Protection Manager\DPM\bin) Run the command ConfigureSharepoint.exe –enableSharepointProtection This will enable the protection of the sharepoint farm.  It will enable the WSSCmdletsWrapper DCOM object and the WSS VSS writer.  As you can see in the screenshot, it will ask you for a username and password.  This needs to be the (or a) farm administrator account. After that, we are going to run another command: ConfigureSharepoint.exe EnableSPSearchProtection This will enable the protection of the Search provider.  Again, you need to enter the username and password for a sharepoint administrator. Oke, now let’s have a better look at the command.   Syntax: ConfigureSharePoint.exe [-EnableSharePointProtection] | [-EnableSPSearchProtection] | [-ResolveAllSqlAliases] | [-SetTempPath <Path>] Requirement: This command should be run as a local administrator. For Windows 2008 onwards, ensure that this command is run from an elevated command prompt. Parameters: -EnableSharePointProtection Enables the protection of SharePoint farm. It registers the WSSCmdletsWrapper DCOM object and enables the WSS VSS writer. When prompted to enter user name and password, enter the credentials of the SharePoint farm administrator. -EnableSPSearchProtection Enables the protection of WSS 3.0 Search and MOSS 2007 SSP. It registers the WSSCmdletsWrapper DCOM object. When prompted to enter user name and password, enter the credentials of the SharePoint farm administrator. -ResolveAllSqlAliases This option can be run only after running -EnableSharePointProtection or -EnableSPSearchProtection on the server. It provides information about all the SQL aliases reported by the WSS VSS writer and resolves them to the corresponding SQL Server instance names. If a SharePoint database is mirrored and configured with SQL alias then the corresponding mirror's SQL Server instance name is displayed as well. This option also reports all the SQL aliases that cannot be resolved to any SQL Server. -SetTempPath <Path> Sets the environment variable TEMP and TMP to the specified path   The good observer ;-) has seen that you can run the parameters all at once so that you don’t need to give the username and password twice. One important note… The farm administrator account doesn’t need to be local administrator on the Web Front End.  This was a requirement for DPM 2007.  From the moment you do perform the command, DPM 2010 will give the following permissions to the sharepoint farm administrator: Read and Execute to all DPM directories. Read, Execute and Write (all) access on Temp directory in the DPM directory. Read permissions to the DPM hive in the registry. That’s it for now, next post will be the creation of a protection group Cheers, Mike Posted Mar 11 2010, 11:42 AM by SCUG.be Filed under: Sharepoint, dpm 2010, System Center Data Protection Manager

• How to manually install an agent and attach it to the DPM server

  Hey All, I’m receiving sometimes the question about manual installation of DPM agents.  Sometimes this is because off using deployment tools, other times it is because of firewall restrictions on the server. The DPM agent installer from the console works great but when it needs to be done manual, it just needs to be done manual. So for this, here is a small example on how to achieve this.   In this example, I will install the agent manually on the server, but it is perfectly possible to do this with SCCM or SCE or MDT.   First we need to find the agent installer sources Depending on which version you need, choose it.  In this case it was a 64-bit server. When the agent installation is complete, we need to run following command The command is: SetDpmServer.exe –dpmServerName <name server> Note that when the DPM server is in another domain, use the FQDN As you can see, the DPM command is now configuring a few items After that, you need to go to the console and choose to install agents But instead of choosing the option Install Agents you need to choose Attach Agents and then depending on your situation: Computers on Active Directory Domain or Computers in Workgroup or Untrusted Domain In my case, it is Computers on Active Directory Domain In this window you need to choose your servers.  This can be one server but multiple at the same time is also possible. Give the correct credentials A review, press Attach to start the task And quickly after, you will get the notification that it is a success. That’s it. But what if you want to do the command part on the server to be protected automatically? This can be achieved by using parameters in your installation package for SCCM, MDT or SCE USAGE: DpmAgentInstaller.exe [/q] [<DPM server name>] [<DPM server name>] The name of the DPM server to be used for protecting this computer. Specify this parameter if the DPM server is known. If you are installing the DPM protection agent as a part of an image, skip this parameter. You can set the DPM server later using the SetDpmServer.exe tool. [/q] Performs a silent install. So using the following command in your package should solve your problem here: DpmAgentInstaller.exe /q <DPMServerName> So is this something you would want to use or not?  In my opinion, every windows server that you deploy should receive an agent.  Why?  Because you never know when you need to backup that server.  With DPM it is very easy to set the agent for a server as disabled.  It won’t use any license so that won’t cause a problem. Just my 2 cents Cheers, Mike Posted Mar 10 2010, 01:54 PM by SCUG.be Filed under: Agent, dpm 2010, System Center Data Protection Manager

• Infrastructure Planning and Design Guides—Microsoft Application Virtualization 4.6

  This IPD guide, updated for App-V 4.6, provides actionable guidance for planning your application virtualization infrastructure. With App-V, your organization can respond to the complex challenge of managing applications. This guide simplifies your App-V planning process; updates now include support for Windows 7 and Windows Server 2008 R2, including such features as BranchCache; support for 64-bit clients; and server-sizing data. Strategically planning your infrastructure can help you avoid problems...(read more) Posted Mar 08 2010, 07:32 AM by SCUG.be Filed under: Technet, Virtualization, Windows Server 2008 R2, Windows 7

• Infront TrendMicro Management Pack

  The Infront TrendMicro Management Pack allows customers to proactively monitor their TrendMicro environment. This Management Pack allows for the monitoring of the end-to-end security and spam protection starting from the TrendMicro OfficeScan client to the OfficeScan server, your ScanMail environment and your Interscan Messaging Security Suite. The Management Pack supplies critical events and alerts on viruses and spam to Operations Manager, and also monitors the health, performance, security and...(read more) Posted Mar 08 2010, 05:23 AM by SCUG.be Filed under: Management Pack, Infront Consulting, Scanmail, office Scan, TrendMicro, IMSS

• The Quest QMX VMware extension is now free via vCenter and vSphere

  Quest has announced that the QMX VMware extension is now free via vCenter and vSphere. The Quest Management Extensions (QMX) - Operations Manager 2007 Edition VMware solution supports all versions of VMware. You can download it from here http://www.management-extensions.org/entry.jspa?externalID=100338&categoryID=252     Have fun, Alexandre Verkinderen...(read more) Posted Mar 05 2010, 03:28 AM by SCUG.be Filed under: opsmgr, Management Pack, opsmgr R2, Vmware, Opmsgr 2007 R2, vCenter, vSphere, esx

• Unique OpsMgr 2007 R2 Bootcamp training event (Belgium) :

  Hi all, I am very proud to be able to announce that we will be able to host a Unique OpsMgr 2007 R2 training event in Belgium. Is the average training not meeting the depth of technical content you need? Would you like the receive your training from someone that received the prestigious MVP Award? Wished you could receive training from someone that co-authored a book on the topic he is teaching? Are you looking for real 400 level training? Want training from a consultant with plenty of real-life...(read more) Posted Mar 04 2010, 04:38 AM by SCUG.be Filed under: opsmgr, MVP, Training, opsmgr R2, Infront Consulting, realdolmen

• MMS 2010 is only 6 weeks away and SCUG will be there…

  Yes, MMS 2010 is coming soon and it will be an exciting week. The complete SCUG team from Belgium will be there! MMS info : Microsoft Management Summit 2010 The entire session schedule is available on http://www.mms-2010.com/public/sessions.aspx My schedule is made and I will have a more or less complete Service Manager week. From Service Manager assessment to customizing the environment, a complete track is available in this week. Little overview: Breakout sessions: Implementation, Architecture and Administration of a Service Manager Deployment Service Manager Integration with System Center Extending and Customizing Service Manager Service Manager 2010: Drilldown System Center Service Manager: Pre-assessment Considerations Service Manager: Data Warehouse and Custom Report Creation Real World Incident Management on microsoft.com Automating and Simplifying Compliance and Risk with System Center: Tour Compliance and Risk Mgmt with System Center Service Manager 2010 + 3 breakout session on Opalis Integration Server + some partner sessions who are covering their solutions on top of Service Manager Instructor lab sessions: Service Manager 2010 Data Warehouse and Reporting Automating IT Processes on Service Manager 2010 Incident and Change Management in Service Manager 2010 Service Manager Integration with System Center Implementing Service Manager 2010 Introduction to Opalis For the other System Center products, I see a lot of SCCM vNext and SCOM customization sessions. Will be certainly followed by our other SCUG attendees :-) Maybe we have a big announcement at MMS. There is some speculating and people who are taking bets that Service Manager might be announced as RTM at MMS. (Microsoft to RTM System Center Service Manager at MMS?) I’ll keep you posted on this ! Posted Mar 03 2010, 05:35 AM by SCUG.be