Monthly Archives: July 2016

Wsyncmgr.log Sync failed: WSUS server not configured. Please refer to WCM.log for configuration error details.

On Server 2012 R2  I was unable to synchronize software updates in my ConfigMgr Current Branch environment. Server Manager kept reporting that the WSUS service was stopped. Each time I would restart the service, it would stop again.

When checking the ConfigMgr logs:

Wsyncmgr.log Sync failed: WSUS server not configured. Please refer to WCM.log for configuration error details.. Source: CWSyncMgr::DoSync
WCM.log Remote configuration failed on WSUS Server.

I previously had no issues with my SUP. Last change was that it was patched as it was a new environment. Upon more research I had applied patch KB3159706 

To fix this there were some post update tasks to do which I did not do:

Load up cmd prompt:

cd “C:\Program Files\Update Services\Tools\”
“wsusutil.exe postinstall /servicing”

Then open up Server Manager, add roles and features wizard, in the features section under .Net Framework 4.5, then under WCF Services, select to install HTTP Activation

After this I had to restart my ConfigMgr site server which had the WSUS installed and it was fixed (same issue after restarting the WSUS service, I needed to do a full reboot)

Advertisements

ConfigMgr 1606 – Microsoft Operations Management Suite (OMS) in Azure

With ConfigMgr 1606, you can now connect Configuration Manager collections to the Microsoft Operations Management Suite (OMS) in Azure. The OMS Connector is currently a prerelease feature. As so, this is done in a lab. This blog will go through the steps on how to add the connector in ConfigMgr and the preqreuisite steps to take in Azure.

This blog post assumes you have a running ConfigMgr 1606 environment and a subscription in Azure.

The first step is to configure your ConfigMgr 1606 site to consent to use Pre-Release features.Make sure you read the disclaimer.

OMS1

After this is done, we will turn on the “Pre-release  Microsoft Operations Management Suite (OMS) Connector”

OMS2.jpg

Click Yes to the dialogue box (make sure to read the disclaimer)

OMS3

Log in to the Azure Classic portal https://manage.windowsazure.com an go into your Azure AD, select Applications. Click on Add down the bottom.

OMS4

Enter in the name you would like to use and select web application and/or web API and click next.

OMS5

Enter in sign on URL and APP ID URI. I added in my ConfigMgr server name (http://configmgr.domain.com) for both.

OMS6

Next we will log into the Azure Resource Manager https://portal.azure.com and create our OMS Workspace. Click on Browse then go to “Log Analytics (OMS)” then click on Add

OMS7

Once this is created, we will go back in the Azure Classic Portal and go into our Azure AD then Application we created earlier to make a note of our Client ID and generate a key.

OMS8OMS9

Next we will create our connection to OMS back in the ConfigMgr console:

OMS10

This is the part that Technet did not tell us. The part with the red box around it is misleading. We actually need to give our application we created earlier access to our Resource Group in the Azure Resource Manager Portal (portal.azure.com). This is probably because Operation Insights was moved from Azure Classic Portal to Azure Resource Manager. Without doing this, I will show you what happens:

OMS11

I will type in my tenant name and Client ID and secret key from before, click Verify, then click Next.

OMS12

ConfigMgr is unable to pull any information about the subscription or Resource Group or the OMS Workspace

OMS13

To fix this, we need to log back into https://portal.azure.com and go into our Resource Group with our OMS workspace and give our Application we created earlier access.

OMS14

Go to Settings, then click Users

OMS15

Click on Add, and type in the name of the Application you created in the classic portal https://manage.windowsazure.com I gave mine Contributor role for testing.

OMS16

Now if we go back and try and add the Operations Management Suite Connection again, you will see that ConfigMgr can pull the information from our Resource Group and OMS Workspace.

OMS17

There we go. This looks better! It pulled the information now that it has access.

OMS18

OMS19OMS20

You can view the OMS Connector here. You can also right click on it and go to properties to view the properties and add collections.

OMS21

Once the connector is set up, it should install the Microsoft Monitoring Agent.

OMS29.jpg

Next we will log into the Azure Resource Manager portal https://portal.azure.com and enable the ConfigMgr collections. Once you’re in the Azure portal, go to Log Analytics (OMS) then click on OMS Portal

OMS22

Once in the OMS Portal, go to Settings

OMS23

Go to the COMPUTER GROUPS tab, and click on SCCM, then click “Import Configuration Manager collection memberships” and save.

OMS26

After it updates you should see the collections (I added some more)

OMS27

You can click on the links to view more information

OMS28

 

PXE – CAS environment – device is in the database no advertisements found

I had an issue in a ConfigMgr 2012 R2 environment with a CAS and multiple Primary Sites. In this site we would import the MAC address of a machine into a collection with the OSD task sequence deployed. When PXE building a machine it would fail on abortpxe.com

When I checked the smspxe.log it said:

Client lookup reply:
XX:XX:XX:XX:XX:XX, XXXXXXXX-xxxx-xxxx-xxxx-xxxxxxxxxxxx: device is in the database.
XX:XX:XX:XX:XX:XX, XXXXXXXX-xxxx-xxxx-xxxx-xxxxxxxxxxxx: no advertisements found

The machine was definitely in the collection with a task sequence assigned. Even if I deleted the computer object out of the DB in the Primary Site, smspxe.log still showed “XX:XX:XX:XX:XX:XX, XXXXXXXX-xxxx-xxxx-xxxx-xxxxxxxxxxxx: device is in the database.”

On the Primary Site the machine was added to, I ran a query to search for the MAC address which found no results.

select distinct SMS_R_System.Name, SMS_R_System.MACAddresses, SMS_R_System.SMBIOSGUID, SMS_R_System.IPAddresses
from SMS_R_System where SMS_R_System.MACAddresses = ##PRM:SMS_R_System.MACAddresses## order by SMS_R_System.MACAddresses

I ended up connecting to the CAS, then did a search for “Resource ID” which was the “ItemKey” above in the SMSPXE.log. It found a machine which was originally joined to the Primary Site I am trying to PXE build from, but was currently assigned to another Primary Site and marked as inactive.

resourceid

After deleting that object from the CAS in the ConfigMgr console, the machine could build successfully.

SCCM 1606 – Support for cache size in Client Settings

One of the nice new features in ConfigMgr 1606 is the ability to set the client cache in the Client Settings. Previously in other version of ConfigMgr, you could set the size when installing the ConfigMgr client, or use a VBS/PowerShell script, or change it in the Configuration Manager Client Properties in Control Panel. You can see those scripts here.

Now in Update 1606 for ConfigMgr Current Branch, in \Administration\Overview\Client Settings you can see the new “Client Cache Settings” section.

clientcache

Update 1606 released for SCCM Current Branch

Microsoft have released update 1606 for ConfigMgr Current Branch. You can update directly to version 1602 from version 1511, or you can update from version 1602 to 1606.

If you cannot find the update in \Administration\Overview\Cloud Services\Updates and Servicing there is a PowerShell script here you can run which will make the update available. It worked for me.

What’s new in version 1606 of System Center Configuration Manager
https://technet.microsoft.com/en-US/library/mt752488.aspx

1606

1602_21606_31606_41606_5

1606_7