A blog with focus on Windows 10 and cloud <solutions
RSS icon Email icon Home icon

  • A unique book on managing Windows clients in an enterprise environment

    Posted on April 27th, 2015 By Andreas Stenhall + No comments

    ECM-Cover-200wMost books written about Microsoft products are very focused on one single product. A book about Windows Server covers all you need about the server OS itself. A book about System Center Configuration Manager covers everything you need to know about ConfigMgr in its bubble and a book about a Windows client covers everything you need to know about the client itself.

    The book Enterprise Client Management using Windows Server 2012 R2 and System Center 2012 R2 covers not only the Windows client (Windows 7 as well as 8.1) but how to manage it using Windows Server 2012 R2 and the System Center 2012 R2 products. So all in all a complete scenario on how to manage your Windows clients in the enterprise in a very effective way using Microsoft management tools available.

    The book is now also available on Kindle as of mid April 2015!

  • MBAM 2.5: The SQL Reporting Services URL that point to the MBAM reports is not valid

    Posted on August 18th, 2014 By Andreas Stenhall + No comments

    When adding the Monitoring and Administration Feature of MBAM 2.5 and checking the System Center Configuration Manager Integraton features in the setup wizard you typically enter the URL to the Reporting Server, for instance http://configmgrsrv/ReportServer. If you get the error

    The SQL Reporting Services URL that point to the MBAM reports is not valid

    it actually means that you before installing the Monitoring and Administration features must install the MBAM Reports feature. That is even though you are integrating MBAM into System Center Configuration Manager. Why is that? Because when integrating MBAM with ConfigMgr, the only reports that are managed in ConfigMgr are the compliance reports.

  • Intune/ConfigMgr email profiles are removed and not readded on iOS devices

    Posted on July 16th, 2014 By Andreas Stenhall + No comments

    If you are using System Center Configuration Manager 2012 R2 and Windows Intune to deploy email profiles to your iOS devices you should be aware of the fact that the email policy will vanish from your users’ iOS devices and then user then need to log in to the company portal for the email profile to get deployed once again to the iOS device. This is true in the following scenarios:

    • You make a change to the email policy, for instance changing the name of the email policy in the ConfigMgr console.
    • You install Cumulative Update 2 for System Center Configuration Manager 2012 R2.

    No status on a fix for this bug at the moment.

  • Remove client from collection in OSD task sequence using Orchestrator

    Posted on July 7th, 2014 By Andreas Stenhall + 2 comments

    A common setup when using System Center Configuration Manager to deploy is to have an OSD collection which has a required deployment. Moving clients to that Collection will let them be reinstalled or installed. After deployment is done you typically want the machine removed from that collection. There are a few ways of doing that but my favorite is using an Orchestrator runbook.

    Orchestrator Runbook Configuration

    Note: In this guide I assume that you have installed System Center Orchestrator 2012 SP1 or 2012 R2 in your environment.

    1. First you need to download and install the Orchestrator Integration for Configuration Manager which will add the items we are using to remove the machines from a Collection in Orchestrator Runbook Designer.

    2. Start Orchestrator Runbook Designer and setup the connection to the ConfigMgr primary site server by going to Options > SC 2012 Configuration Manager.

    3. Add a connection to your SCCM server and make sure to test the connection using the Test connection button before proceeding.

    ORC23

    4. Now Create a new Runbook and go to Activities > Runbook control and drag “Initialize data” to the Orchestration pane. Do the same by choosing SC12012 Configuration Manager under Activities, and then drag  “Delete Collection Rule” out on the Orchestration pane.

    5. Hover over the Initialize data icon and then drag the arrow to the Delete Collection Rule. It should look like the below image.

    ORC
    6.  Right click Initialize Data and choose Properties. Add two details and name them CollectionID and ClientName.

    ORC21

    7. Right click Delete Collection Rule and choose Properties. Start by choosing the connection you created in step 3. Note: Do not type in the text as below, instead right click the area right to Collection and choose Subscribe > Published Data. Choose CollectionID and click OK. Repeat for Membership Rule. Choose Finish when done.

    If you type in the text manually you will get this error when executing the runbook: The SMS Provider reported an error. Details: Generic failure

    ORC22

    8. Before proceeding I strongly recommend that you execute the runbook in test mode, supplying a client name and collection ID of a machine located in the collection you want the client removed from.

    Note: Do not forget to check in the runbook after testing and when you are done, or it will fail to execute during operating system deployment.

    Task Sequence Configuration

    Now that the runbook is running successfully you can use it in your Task Sequence. Note: This requires that you have integrated Microsoft Deployment Toolkit with Configuration Manager and that you are using an MDT Task Sequence.

    Modify a task sequence and create a New group. The recommended section to run the Runbook is in the State Restore phase of the Task Sequence. To be on the safe side first run a “Gather”, then you must add “Use Toolkit Package” and last but not least execute the actual runbook by adding the “Execute Runbook” step.

    ORC4

    Also note that runbooks are run with the SCCM network access account so you must add that account to the Orchestrator user group that you have assigned, check the permissions and which group name to add to the relevant Orchestrator group in  Runbook Designer by right clicking the name of the runbook tab and then choose Permissions.

    If you do not you will get this error in the  ZTIExecuteRunbook.log (where all events related to the runbooks are stored):

    Unexpected response from web service. 405 Method Not Allowed
    < ?xml version=”1.0″ encoding=”utf-8″ standalone=”yes”?>
    < error xmlns=”http://schemas.microsoft.com/ado/2007/08/dataservices/metadata“>
    <code></code>
    <message xml:lang=”sv-SE”>The requested operation requires Publish permissions on the
    Runbook</message>
    < /error> ZTIExecuteRunbook 2014-07-03 10:01:56 0 (0x0000)

    Happy orchestration and deploying!

  • Deployment Roadshow vNext and Windows 8 loadfest

    Posted on November 2nd, 2011 By Andreas Stenhall + No comments

    Two events are coming up; Deployment Roadshow vNext featuring System Center Configuration Manager 2012 and Microsoft Deployment Toolkit 2012 and a Windows 8 loadfest.

    Deployment Roadshow vNext will take place in Sweden’s four largest cities and it will be presented by myself and colleague Johan Arwidmark from Knowledge Factory, Wally Mead the SCCM guru from Microsoft Corp and Mikael Nyström from Truesec. More info about the event at http://www.deploymentevents.se.

    The Windows 8 loadfest will take place in early December in Stockholm and it hosted by me, Johan Arwidmark, Lars Gustavsson and Tim Nilamaa. More info about the event at http://www.deploywindows8.se.

  • System Center ConfigMgr, what is up with that?

    Posted on February 8th, 2010 By Andreas Stenhall + No comments

    I haven’t been posting much about System Center Configuration Manager (SCCM) but that will change, starting right now. Well System Center ConfigMgr plays a significant role in for instance deployment, management and inventory of Windows clients so it feels natural to extend the posting about SCCM.  I start off with hinting at these two add-ons:

    Dashboard manager (beta): Present stats for ConfigMgr with charts, meters and such in a very graphical overview. See status for patch management, depployments and more! Sign up for beta and download at Microsoft Connect.

    ACT (Application Compatibility Toolkit) Connector: An updated Microsoft System Center Configuration Manager 2007 – Application Compatibility Toolkit Connector has been released. This connector presents ACT information in the ConfigMgr console. Download at Microsoft Download center.