Sccm 2016 logs not updating

There are three sections: Phase 1 – Client PC, Phase 2 – MP Server, and Phase 3 – Site Server.

There are two minor challenges here: Firstly, there are lots of different log files, and secondly SCCM puts them in different paths depending on what phase the deployment is in.

Since the core thread of deployment is the task-sequence, we need to find the log for that. This log is always the first step to troubleshooting any deployment issue. Unfortunately, SCCM can put in one of seven places, depending on the stage of the build and the architecture of the OS, as per Table 1 - SCCM task-sequence log paths.

Which I could update to and see if its sorted, but they do specify many issues can carry accross in the upgrade so it's best to get them sorted first. Now the hourglass just wont go away, have had it there for over a week. SCCM has a habit of doing some decent logging, what about the log files on the server and viewing them with cmtrace when you try and add to a collection i've troubleshot several problems with the existing sccm at work and have used the logfiles many times to work out whats going on (or what was not) hasn't been any changes to account rights on sccm itself, or any of the service / network accounts your system uses?

I went to google it yesterday and came across the fact there's a new SCCM version (current branch). So I'm doing this and they are not moving and the hourglass appears.

It is not a support upgrade path from Config Mgr 2007 or 2012.

This is the most exciting time in a long while to be in the Config Mgr space because we are getting new features rolled into our consoles on a more rapid release cycle than ever. (1602 features) it is worth noting Config Mgr 1606 this has the 1602 features and KB’s within it.

So if you’re upgrading to 1606 from 1511 you will not have to upgrade to 1602 first.

Below is a few of the top new features: This link will give you a full list of features 1606 new Features, Click Here The Config Mgr 1606 upgrade is being rolled out over the next few weeks, however, you may find that you will not get 1606 in your Console right now.

When troubleshooting a client PC, the will never say that it is doing a hardware inventory cycle, software inventory cycle, etc.

Tags: , ,