In case you are a little lost and need direction to this link, HERE it is. The most important thing, in my opinion, is the upgrade order. Good luck!
I just completed an upgrade from SCCM 2012 RTM to SP1. After doing so, I deployed the client manually from the SCCM console to a few Windows 8 machines in our environment to test management capabilities.
The agent installed successfully, yet I noticed that the machine was not reporting back as a client in SCCM. After using my cube walls like a punching bag and throwing a tantrum that would make a 5-year-old proud, I grabbed some coffee, relaxed and opened the Configuration Manager client agent properties on the troubled machine.
Lo and behold! I found very little information under the General tab!
When I visited the Site tab, I noticed that the site code was blank. After hitting the Configure Settings button and then Find Site, I got a friendly error message stating “Configuration Manager did not find a site to manage this client.”
Time to panic, right!? The upgrade was botched and now your entire SCCM environment is nothing but a fiery wasteland teeming with plague and sorrow!
The first instinct is to search every log, high and low, for any tiny bit of cryptic information. Maybe the ccmsetup.log has something? Possibly the ccm.log on the site server can lend a clue? Both are quality options…or, you can just raise your eyes for a second above the error message to see: “To find a site, the client must be in a configured boundary or the hierarchy must have a fallback site.”
Brilliant! I’ll check the Hierarchy settings…
Sure enough! Some of the settings from the pre-upgrade environment did not carry over, this being one of them. I just checked the box for “Use a fallback site” and ensured the site was the FQDN of my primary site server (as my hierarchy consists of a single Primary Site). After the changes, I checked the client and all of the properties were populated!