We saw the same behavior on our nontrusted domains because there was left overs from a GOP that was settings SLP values. On Apr 12, 2014 12:42 PM, "Thomas Gonzalez" <[email protected]> wrote:
> I'm sort stuck between a rock and tree...I've recently (1 month ago) > upgraded to R2 (sccm2012) new hardware / vm. The DB is on a SQL cluster and > the application resides on a VM (win2012). So everything is good, clients > reporting in, the old 2012 RTM has been decommed. > > > > I now have one single primary and ip address range's, our AD Sites / > Services boundaries are set with /8 and I had issues. So I went with ranges > rather than allowing the boundaries to be created and added into the single > group. > > > > I currently have over 11k objects discovered via (network / heartbeat / ad > system); of those 11K I have 3700 (windows -client / server) and 900 > (macintosh) and 3800 (mobile / tablet). Pretty good numbers. > > > > So one item I'm noticing on a few systems that are outside the US > primarily in EMEA / HKG / Syd, is that they have the old RTM site code. > I've done some spot checking within the schema, the old site code is not > published, DNS is good, the new R2 server has rights to publish and the new > site code is presented. > > > > Now on some of the client the ccmsetup log shows the following: > > > > The MP set to the new server and the return code of 0, which is an > indication of success installation. > > > > However, within the locationservices.log I'm seeing a "failed to retireve > DNS service record using _*mssms_mp_(old sitecode).tcp*_child domain, DNS > returned error 9003" > > > > Not sure what is generating that since the system -> systemmanagement has > no record of the old site code at the forest / domain / child domain level. > > > > Has anyone seen this before, I've done everything by even doing a manual > (psexec remote execution of ccmsetup /uninstall) rebooted the resource and > then executed a auto install as well as manual and still fails. > > > > Thanks > > > > > > Thomas > >
