Avatar of timdk

by timdk

ConfigMgr 1606–Unable to modify language configuration

September 1, 2016 at 12:30 am in Configuration Manager by timdk

A customer of mine recently reported they could no longer add any client or server languages to their Configuration Manager 1606 site.

When running the setup wizard the option to modify language configuration is greyed out.

 

image

I have blogged full details on the cause and how to resolve the issue on my personal blog.

Hope it helps!

Tim

Tweet about this on TwitterShare on LinkedInEmail this to someonePrint this pageShare on Google+Digg thisShare on RedditShare on Facebook
Avatar of timdk

by timdk

Configuration Manager Update 1606 now available!

July 22, 2016 at 8:59 pm in Configuration Manager by timdk

Earlier today Microsoft has released version 1606 of System Center Configuration Manager current branch.

If you are already on current branch the update should soon become visible in the Updates and Servicing node of your Configuration Manager console. The global rollout is done in waves so it might not become available to you straight away. Similar to the earlier 1602 release you can also speed up the process a bit by running a script that adds the site to the early update ring.

CB1606-UpdatesServicing

Some relevant links to this release:

Time to spin up the lab! More details will follow later.

Tim

Tweet about this on TwitterShare on LinkedInEmail this to someonePrint this pageShare on Google+Digg thisShare on RedditShare on Facebook
Avatar of timdk

by timdk

ITPROCeed 2016 Speaker

June 13, 2016 at 2:05 pm in Community, Configuration Manager, Events by timdk

Tomorrow I will be presenting at ITPROCeed, Belgium’s biggest ITPro Conference.

Together with my partner in crime Kenny Buntinx I will be outlining a few pitfalls to avoid when upgrading to Configuration Manager current branch.

During this session we will bring our little black book with notes from the field. After this session you should be able to steer away from the troubles we have encountered during various upgrades.

image

There will be time for your specific upgrade questions during the Q&A at the end of the session or you can simply talk to us at the event – we will be around for the entire day so do not be afraid to reach out!

Interested? It is not too late to register!

Hope to see you tomorrow!

Tim

Tweet about this on TwitterShare on LinkedInEmail this to someonePrint this pageShare on Google+Digg thisShare on RedditShare on Facebook
Avatar of timdk

by timdk

Configuration Manager Technical Preview 1604 available

April 22, 2016 at 9:35 pm in Configuration Manager, Microsoft Intune by timdk

Microsoft has just released update 1604 for Configuration Manager Technical Preview.

The update includes the following new features:

  • Windows Store for Business integration – You can now manage and deploy applications purchased through the Windows Store for Business portal for both online and offline licensed apps.
  • Passport for Work policies – You can now deploy Passport for Work policies to domain-joined Windows 10 PCs managed by the ConfigMgr client as well as mobile devices managed by Microsoft Intune.
  • On-premises Health Attestation Service integration – You can now configure devices that cannot connect to the cloud-based Health Attestation Service to connect with the on-premises Health Attestation Service instead.
  • VPN for Windows 10 – You can now deploy VPN profiles with 3rd-party providers to Windows 10 devices managed with ConfigMgr client.
  • Software Updates Compliance dashboard – You can now use this dashboard to view the current compliance status of devices in your organization and quickly analyze the data to see which devices are at risk.

And an additional feature for hybrid setups:

  • New setting for Android devices – You now have an option to configure Smart Lock setting for Android 5.X devices in order to prevent users from bypassing the lock screen.

     

    On the Technet evaluation center the baseline version for new installations has also been updated. The Technical Preview 5 available for download is actually based on build 1603.

    More details on the release can be found on the Configuration Manager Team Blog.

    For details on the upgrading experience please have a look at my previous blog post.

    Quick sidenote: As I just upgraded a first lab environment with the 1604 TP build it seems the updates and servicing node gets cleaned up also. Previous builds (installed or not) are no longer listed after the upgrade.

    TP1604-UpdatesServicingBeforeAfter

    Have fun in your labs!

    Tim

Tweet about this on TwitterShare on LinkedInEmail this to someonePrint this pageShare on Google+Digg thisShare on RedditShare on Facebook
Avatar of timdk

by timdk

Configuration Manager 1511 – Client hangs on initializing during OSD

March 11, 2016 at 3:49 pm in Configuration Manager, Troubleshooting by timdk

A customer that recently upgraded to Configuration Manager 1511 CB ran into an issue with deploying newly captured OS images. The task sequence is hanging on client initialization and fails eventually. Images captured before the upgrade could still be deployed without any issues.

This blog post details how we resolved this.

Symptoms

When deploying an OS image captured using a Build and Capture task sequence in Configuration Manager 1511 the client hangs on the client initialization step. In the smsts.log we see an entry Waiting for the CCMExec service to be fully operational . After that there is one more entry referring to loading TSRES.DLL .

CB1511-OSD_Bug-ClientInitializing

 

Issue

This is a known bug in Configuration Manager 1511 which is logged on Connect (ID 2153746).

Feedback on the connect item indicates this will be fixed in an upcoming update to the Configuration Manager current branch. The workaround for now is to not include the client in the image.

Note : in 1602 Technical Preview this issue has already been fixed.

 

Workaround

There is another way to work around this if you do not want to pursue the alternative not to include the client in the image.

For this you would need to modify the Build and Capture task sequence to include two additional steps:

  • Step 1 : run ccmrepair
  • Step 2 : reboot the system
    An example is shown in the screenshot below.

image

When deploying the newly captured image using the modified task sequence the client will no longer hang on initializing.

Once the next update of Configuraiton Manager CB is implemented in your environment these two steps can be removed again.

Hope it helps!

Tim

Tweet about this on TwitterShare on LinkedInEmail this to someonePrint this pageShare on Google+Digg thisShare on RedditShare on Facebook
Avatar of timdk

by timdk

Configuration Manager Technical Preview 1601 available

January 27, 2016 at 10:18 am in Configuration Manager by timdk

Microsoft has released Configuration Manager Technical Preview 1601. This release includes the following new capabilities and improvements:

  • Improvements to Microsoft Intune integration and conditional access.
  • Client Online Status. This allows to see from the console whether a (Windows) client is online or not.
  • Improvements to application management: manage volume-purchased apps for iOS devices and iOS app configuration support.
  • Improvements to compliance settings: Edge browser settings, compliance settings for Windows 10 team and Kiosk Mode for Samsung KNOX Hybrid.

More details on this release are documented here.

If your service connection point is setup in online mode this new release will show up in the Updates and Servicing node in the Configuration Manager console.

image

The actual content is downloaded in the EasySetupPayLoad folder.

image

For more information on the actual upgrading experience please have a look at my previous blogpost.

Until next time!

Tim

Tweet about this on TwitterShare on LinkedInEmail this to someonePrint this pageShare on Google+Digg thisShare on RedditShare on Facebook
Avatar of timdk

by timdk

ConfigMgr Cmdlet Library v5.0.8328.1155 released

January 26, 2016 at 2:05 pm in Configuration Manager by timdk

metro-powershell-logoA quick blog post to inform you that Microsoft yesterday released version 5.0.8328.1155 of the System Center Configuration Manager Cmdlet Library.

This version includes support for Configuration Manager 1511.

Full list of versions of Configuration Manager supported in this release:

    • System Center 2012 Configuration Manager SP2
    • System Center 2012 R2 Configuration Manager
    • System Center 2012 R2 Configuration Manager SP1
    • System Center Configuration Manager (current branch version 1511)

    Full details and download link can be found here.

Tweet about this on TwitterShare on LinkedInEmail this to someonePrint this pageShare on Google+Digg thisShare on RedditShare on Facebook
Avatar of timdk

by timdk

Configuration Manager 1511 Updates and Servicing : a closer look at the updating experience

December 19, 2015 at 8:00 am in Configuration Manager by timdk

Earlier this week Microsoft has released update 1512 for Configuration Manager. In this post we will focus on the implementation experience and walk through the steps required to implement this update in an existing TP4 1511 environment. We will look at how an existing site becomes aware of updates, how to validate the prerequisites and update the site. After that we will also see how to update the other components like the console and clients.

image

Read the full blog post here.

Tweet about this on TwitterShare on LinkedInEmail this to someonePrint this pageShare on Google+Digg thisShare on RedditShare on Facebook
Avatar of timdk

by timdk

WMUG NL Community Event Speaker

December 14, 2015 at 11:55 pm in Community, Configuration Manager, Microsoft Intune by timdk

2015-12-14_23-41-19Tomorrow I will be presenting at a community event hosted by the Windows Management User Group (WMUG) in the Netherlands.

Session: What to expect from ConfigMgr vNext?

Abstract : The next version of Configuration Manager is soon to be released. In this session we will look at the future roadmap of Configuration Manager and explore the new features, enhancements and infrastructure changes that are coming with the next release. Additionally will also outline how to get to this release from your current environments.

More information on the sessions and the full event agenda can be found here.

Registrations are currently still open. Click here if you want to attend!

Hope to see you there!

Tweet about this on TwitterShare on LinkedInEmail this to someonePrint this pageShare on Google+Digg thisShare on RedditShare on Facebook
Avatar of timdk

by timdk

ConfigMgr vNext Feature Highlight : Multiple Deployments for ADR’s

December 8, 2015 at 2:00 pm in Configuration Manager by timdk

This blog post is part of the Coretech Global Xmas blogging marathon – today is my turn to share something new and as a subject I have picked a feature which will be available in the upcoming new release of Configuration Manager : support for multiple deployments with a single Automatic Deployment Rule (ADR).

Background

ADR’s are not entirely new as they already existed in Configuration Manager 2012. One of the shortcomings of ADR’s in 2012 is that they only support a single deployment. So if you have a phased deployment -for example lab, pilot and production- within your organization, you would have to create a new ADR for each phase. These ADR’s would be very much identical except for the target collection and the scheduling.

In the vNext release of Configuration Manager this is no longer an issue as a single ADR will now support multiple deployments. So following the above example we could use a single ADR for patching our lab, pilot and production machines. Time to have a closer look into how this will work.

The base ADR

Defining the rule for the machines in the first “Lab” phase is identical to what you have been doing in the past for Configuration Manager 2012. A quick walk through the steps:

clip_image001

After specifying a name and description for the ADR we pick the Patch Tuesday template that Microsoft has included out-of-the-box. We set the target collection to our lab workstations collection. Notice there are no options to define additional collections here. As this is the lab collection we opt to have the deployment enabled immediately.

clip_image002

In the deployment settings we picked the default settings.

clip_image003

In the Software Update settings we picked the default settings. Note that the last one day option offcourse only is valid if we let the rule run no later than one day after patch Tuesday.

clip_image004

We set the schedule to run every second Wednesday of the month.

clip_image005

For the lab phase both the available time and the installation deadline are set to as soon as possible.

clip_image006

Define the user experience. In our example we used the default settings.

clip_image007

In the next step we can specify the alert options. Also here we kept the default settings.

clip_image008

Also for the download settings we kept the defaults.

clip_image009

Specify the deployment package to store the patch binaries. In our example we used an existing package.

clip_image010

We will download the binaries from the internet.

clip_image011

In our environment only English is required.

clip_image012

Review the summary and click next.

clip_image013

At this point our our ADR has been created and we can close the wizard.

The end result is shown in the picture below. We have our ADR which currently still has a single deployment as defined in the wizard we just walked through.

clip_image014

Adding additional deployments

To add and additional deployment we need to select our ADR and select Add Deployment action either through the ribbon or via a right-click.

clip_image001[5]

This action will kick off a slightly trimmed down wizard similar to the regular ADR one.

clip_image002[5]

In step one we need to specify a target collection. We will take our second collection containing our pilot phase machines. By default the deployment would be enabled here also but as we would like some more control and make sure our lab tests were successful first, we will disable it. At a later point in time an administrator will have to enable the deployment manually.

clip_image003[5]

We kept the default Deployment settings.

clip_image004[5]

In our scenario we wanted one week of lab testing before deploying to the pilot collection so the schedule settings were adjusted accordingly.

clip_image005[5]

We kept the default User Experience settings.

clip_image006[5]

We kept the default Alerts settings.

clip_image007[5]

We kept the default download settings.

Note: I noticed that these download settings do not match with the default download settings from the Create ADR wizard. Clients on a slow boundary or using fallback by default will not install the updates. Also content download to Microsoft Updates is unchecked by default in the add deployment wizard. Make sure to check the options carefully before clicking next.

clip_image008[5]

Review the summary and click Next

clip_image009[5]

Our additional deployment was created successfully. Click close.

As you can see our second deployment is now in place. We still have only one ADR.

clip_image010[5]

To support our scenario end-to-end all we needed to do is to add a third deployment for our production environment. The end result would look like this:

clip_image011[5]

So what is the end result after running the rule? This is shown in the screenshot below. There are 3 Software Update Groups, each of these groups have a single deployment as per the schedules configured in the ADR.

clip_image012[5]

The names of the Update Groups get a numeric appendix based on the order and total number of deployments for the ADR.

That’s it for this feature highlight.

Enjoy the upcoming holiday period and until next time!

Tim

Tweet about this on TwitterShare on LinkedInEmail this to someonePrint this pageShare on Google+Digg thisShare on RedditShare on Facebook