locked
SCCM migrated to 1511/1602 on new hardware, client do not re-register with new site RRS feed

  • Question

  • Migrated SCCM 2012 R2 to new hardware, with new site ID (so I have 2 SCCM setup running concurrently till I retire old server)

    Existing clients (testing on few) do NOT re-register with new site

    I can change the site code in client properties, but in ClientIDManagerStartup.log I get:

    RegTask: Failed to refresh MP. Error: 0x8000ffff

    Anybody any idea how to re-register the client?

    Client still "thinks" that MP is still the old one

    Site Code is BG1; Management Point is https://old_server.domain.local; MP HTTPS enabled = 1

    where BG1 is new site, but MP points still to the old server.



    • Edited by scerazy Friday, April 29, 2016 12:28 PM
    Friday, April 29, 2016 12:27 PM

All replies

  • Just two lines from a log don't help at all. Please upload ClientLocation, LocationServices and ClientIDManagerStartup.log to OneDrive.

    Torsten Meringer | http://www.mssccmfaq.de

    Friday, April 29, 2016 12:31 PM
  • Thanks, there is nothing more in either of them that is any interesting

    Unlikely I would share my logs with public

    I gave up on this & simply do uninstall & re-install with

    ccmsetup.exe /mp:new_server /logon SMSSITECODE=new_site CCMDEBUGLOGGING=1 CCMLOGLEVEL=0 CCMLOGMAXSIZE=52488000 CCMLOGMAXHISTORY=5 CCMHTTPSSTATE=31 SMSCACHEFLAGS=PERCENTDISKSPACE;NTFSONLY SMSCACHESIZE=15

    It works, which means it should be possible to change existing client to point to the new site/MP

    How otherwise I can do migration without downtime

    Seb




    • Edited by scerazy Friday, April 29, 2016 3:17 PM
    Friday, April 29, 2016 2:19 PM
  • If it's a new site, then you can't simply reassign a client from another site to it -- that would be bad security wise. You must reset the Trusted Root Key on the client first. Uninstalling and reinstalling effectively does this.


    Jason | http://blog.configmgrftw.com | @jasonsandys

    Friday, April 29, 2016 4:25 PM
  • Yes, it is new site, but in same domain, same boundry, same CA,  it is the only way (or am I wrong) to do migration to new hardware and/or SCCM CB

    So how one would do it without downtime (clients unmanaged)

    Uninstall on every client (which might or might NOT happen for whatever reason) and then push new client?

    Not ideal.

    Runing on a client CCMSetup.exe RESETKEYINFORMATION=TRUE

    makes no difference

    Seb



    • Edited by scerazy Saturday, April 30, 2016 11:33 AM
    Saturday, April 30, 2016 10:34 AM
  • A backup and restore on the new hardware works perfectly well. Also, direct upgrade to CB is also possible on the same site server.

    As for the OS (not sure if that's a factor here or not) in-place OS upgrades are fully supported from 2012 to 2012 R2 and starting with 1602, an in in-place OS upgrade from 2008 R2 to 2012 R2 is also supported.

    when running ccmsetup, you also need to specify the new site code (using the SMSSITECODE property) and typically the MP (using the SMSMP property).


    Jason | http://blog.configmgrftw.com | @jasonsandys

    Saturday, April 30, 2016 1:01 PM
  • I was not interested in backup/restore or upgrade, but wanted to do migration.

    That part of the process is not a problem. Problem is to get all existing clients from site XXX to site YYY in controlled manner

    This does not seem to be as easy as I expected it to be

    Seb

    Saturday, April 30, 2016 8:13 PM
  • You asked how one would do it with downtime and that's what the backup and restore would get you close to and an in-place upgrade would certainly get you to.

    Not sure who said it would be easy.

    A simple push from the new site at this point will get you in short order though without any real additional pain at this point though.


    Jason | http://blog.configmgrftw.com | @jasonsandys

    Sunday, May 1, 2016 10:00 PM
  • Thanks, there is nothing more in either of them that is any interesting

    Unlikely I would share my logs with public



    There must be something in whatever log - otherwise it would work without any issues ... reassigning does work - even without using resetkeyinformation if I recall correctly as the clients should be able to retrieve the new TRK from AD. But: no logs/error, no help.

    Torsten Meringer | http://www.mssccmfaq.de

    Monday, May 2, 2016 6:24 AM
  • Guys, MVPs, decide on something.

    One says: "... can't simply reassign a client from another site to it..."

    Other says "... reassigning does work - even without using resetkeyinformation if I recall correctly as the clients should be able to retrieve the new TRK from AD..."

    So it does or does NOT work?

    I do not know how much client push is different from running ccsetup.exe with same switches (probably not different at all)

    And that does NOT work, only uninstall & re-install works correctly (even without RESETKEYINFORMATION in that case)

    To me no downtime means create new server setup the way one wants & swap all clients to it (with install or script) in one go. Pretty much instant.

    But that is not what I see happening

    Surely But: no logs/error, no help if very unfair. Logs might contain something that nobody wants to make public


    • Edited by scerazy Monday, May 2, 2016 8:30 AM
    Monday, May 2, 2016 8:26 AM
  • Surely But: no logs/error, no help if very unfair. Logs might contain something that nobody wants to make public



    Well ... I've done reassignment before and it worked. And it's not unfair, but reality. How should anyone be able to help without knowing details? That simply is not possible. A single line from a logfile does not help unfortunately.

    Torsten Meringer | http://www.mssccmfaq.de

    Monday, May 2, 2016 8:46 AM
  • OK, I have edited all the logs replacing "sensitive" info with bogus names

    Here are the logs

    Monday, May 2, 2016 9:11 AM
  • The client was able to get the new TRK from AD:

    Attempting to refresh TRK from AD LocationServices 02.05.2016 09:37:12 484 (0x01E4)
    Refreshed TRK from AD LocationServices 02.05.2016 09:37:12 484 (0x01E4)

    But there is also

    Group Policy Site Assignment key HKLM\Software\Microsoft\SMS\Mobile Client has changed, will attempt to re-assign the client. LocationServices 02.05.2016 09:37:12 4184 (0x1058)

    Any chance that there is or was a GPO that assignes the client to a site?


    Torsten Meringer | http://www.mssccmfaq.de

    Monday, May 2, 2016 9:51 AM
  • No, I have done site change with .vbs
    Monday, May 2, 2016 10:02 AM
  • How? Plus did you check if HKLM\Software\Microsoft\SMS\Mobile Client does contain the wrong sitecode?

    Torsten Meringer | http://www.mssccmfaq.de

    Monday, May 2, 2016 10:52 AM
  • On Error Resume Next 
    set oSMSClient = CreateObject ("Microsoft.SMS.Client") 
    if Err.Number <>0 then 
    wscript.echo "Could not create SMS Client Object - quitting" 
    end if 
    'Assign client to Servername 
    oSMSClient.SetAssignedSite "BG1",0 
    set oSMSClient=nothing
    It has the BG1 (exactly as I changed it to)
    Monday, May 2, 2016 11:21 AM
  • Anybody has any more ideas why it just does not work?
    Tuesday, May 3, 2016 8:43 AM
  • That's hard to tell without sitting in front of the system, having access to all logs and knowing all details about the configuration (servername and sitecode old and new etc).

    Torsten Meringer | http://www.mssccmfaq.de

    Tuesday, May 3, 2016 9:29 AM
  • I am in front of it, and none makes any sense.

    What does this error mean (in English?)

    There is no AMP for site code

    Tuesday, May 3, 2016 10:03 AM
  • Client is not able to find an internet / https MP.

    Torsten Meringer | http://www.mssccmfaq.de

    Tuesday, May 3, 2016 10:54 AM
  • From where?

    Both old & new site are published to AD, new client setup (after uninstall) does not have this problems, which means everything is correct (otherwise nothing ever would work)

    Also I noticed that log shows:

    LSUpdateInternetManagementPoints: No internet MPs were retrieved from MP OLDSERVER-NOT_THE_NEW_ONE.domain.local, clearing previous list.
    There is no AMP for site code 'BG1'.
    LsRefreshManagementPointEx failed with 0x8000ffff

    why the client tries to access OLD server? Of course there would be NO info there about new MP, right?



    • Edited by scerazy Tuesday, May 3, 2016 11:14 AM
    Tuesday, May 3, 2016 11:11 AM
  • What I am seeing in locationservices.log is totally wrong:

    Name: 'NEW_MIGRATED_SERVER.domain.local' HTTPS: 'Y' ForestTrust: 'N'

    It is domain joined client and I only have SINGLE domain

    Seb

    • Edited by scerazy Wednesday, May 4, 2016 10:30 AM
    Tuesday, May 3, 2016 1:10 PM
  • My answer above stands and was fact checked with the lead dev today. Unless you already trust a site, you cannot get the TRK from AD. Thus, if you trust site A, you cannot switch to site B and expect the client to pick up the TRK automatically. The reason your command-line did not work was exactly what I said, you need to supply the new site code and MP when reseting the TRK using ccmsetup. Performing an uninstall and reinstall is effectively doing this also.


    Jason | http://blog.configmgrftw.com | @jasonsandys

    Wednesday, May 4, 2016 2:36 AM
  • If that is the case, then all the site changing scripts, as well as clients Site tab would be totally pointless ... if one can not change the site...

    So in such case it would NOT be possible to do migration to new hardware (WITHOUT DB copy/restore) and move the clients that are in original site AAA to newly migrated site BBB within the SAME DOMAIN with same CA etc

    Somehow I am not convinced that design could be that bad!

    Seb

    • Edited by scerazy Wednesday, May 4, 2016 10:30 AM
    Wednesday, May 4, 2016 5:59 AM
  • OK, so here is what I had to do to get it working (as much as I do not understand it!)

    OLD_SCCM_SERVER = site SP1 (2012 R2)

    NEW_SCCM_SERVER = site BG1 (CM 1602)

    _mssms_mp_??? (Service Location SRV) exists in DNS for BOTH sites MPs

    On exiting client assigned to site SP1 I change the assignments via vbs to BG1

    That does not register client with BG1 & locationservices.log shows error:

    Refreshed security settings over AD
    No security settings update detected.
    Attempting to retrieve lookup MP(s) from AD
    Lookup Management Points from AD:
    Name: 'NEW_SCCM_SERVER.domain.local' HTTPS: 'Y' ForestTrust: 'N'
    Retrieved lookup MP(s) from AD
    Attempting to retrieve default management points from lookup MP(s) via HTTPS
    Current AD site of machine is Default-First-Site-Name
    LSUpdateInternetManagementPoints
    Current AD site of machine is Default-First-Site-Name
    LSUpdateInternetManagementPoints: No internet MPs were retrieved from MP OLD_SCCM_SERVER.domain.local, clearing previous list.
    There is no AMP for site code 'BG1'.
    LsRefreshManagementPointEx failed with 0x8000ffff

    Why does it want to communicate with MP from OLD_SCCM server?

    So in local hosts file I make entry

    NEW_SCCM_SERVER_IP              OLD_SCCM_SERVER.domain.local

    Restart SMS Agent & instantly I get in locationservices.log

    The MP name retrieved is 'NEW_SCCM_SERVER.domain.local' with version '8355' and capabilities '<Capabilities SchemaVersion="1.0"><Property Name="SSL" Version="1"/><Property Name="SSLState" Value="63"/></Capabilities>'
    MP 'NEW_SCCM_SERVER.domain.local' is compatible
    Refreshed security settings over AD
    No security settings update detected.
    Attempting to retrieve lookup MP(s) from AD
    Lookup Management Points from AD:
    Name: 'NEW_SCCM_SERVER.domain.local' HTTPS: 'Y' ForestTrust: 'N'
    Retrieved lookup MP(s) from AD
    Attempting to retrieve default management points from lookup MP(s) via HTTPS
    Current AD site of machine is Default-First-Site-Name
    Failed to send management point list Location Request Message to OLD_SCCM_SERVER.domain.local
    Current AD site of machine is Default-First-Site-Name
    Default Management Points from MP:
    Name: 'NEW_SCCM_SERVER.domain.local' HTTPS: 'Y' ForestTrust: 'Y'
    LSUpdateInternetManagementPoints
    Current AD site of machine is Default-First-Site-Name
    Internet Management Points from assigned MP:
    Name: 'IMP.domain.com' HTTPS: 'Y' ForestTrust: 'Y'
    LSUpdateInternetManagementPoints: Successfully refreshed internet MPs from MP NEW_SCCM_SERVER.domain.local.
    Persisting the default management points in WMI	LocationServices
    Default Management Points from MP:
    Name: 'NEW_SCCM_SERVER.domain.local' HTTPS: 'Y' ForestTrust: 'Y'
    Assigned MP changed from <NEW_SCCM_SERVER.domain.local> to <NEW_SCCM_SERVER.domain.local>.
    Persisted Default Management Point Locations locally
    Attempting to retrieve local MPs from the assigned MP
    Current AD site of machine is Default-First-Site-Name

    and the client registers with NEW_SERVER straight away

    Could anybody have any explanation?

    I did NOT uninstall client, just changed site assignment with vbs & "cheated" in hosts file

    As soon as client registers with new site I can remove the entry in hosts file

    Kind of similar issue is described here

    Seb


    • Edited by scerazy Wednesday, May 4, 2016 10:43 AM
    Wednesday, May 4, 2016 10:16 AM
  • Just tried it in my lab and I was able to "move" a client from site A to site B by just running ccmsetup.exe /MP:bla SMSSITECODE=NEW without any issues. I'll discuss that with Jason offline and will update this thread once we figured out details :-)

    Torsten Meringer | http://www.mssccmfaq.de

    Wednesday, May 4, 2016 11:55 AM
  • How did you arrive to have 2 sites?

    2 setups & migration job from AAA --> BBB

    In my tries (over days) I could not get this (just rerun the setup) working (always had the same errors)

    Only DNS "cheat" worked (tested in now on few clients, each with the same result)

    Seb

    Wednesday, May 4, 2016 12:24 PM
  • There are two standalone sites in my testlab (CM12 and CMCB) and I just upgraded and moved the client from "old" to "new".

    Torsten Meringer | http://www.mssccmfaq.de

    Wednesday, May 4, 2016 1:02 PM
  • That is not the same, it never had any migration job running on them, so they have no idea of one another in any way (not that this should matter)


    I can not even think of why the client tries to access OLD MP when registering to NEW site
    • Edited by scerazy Wednesday, May 4, 2016 1:22 PM
    Wednesday, May 4, 2016 1:21 PM
  • Migration jobs are completey unrelated in this context.

    Torsten Meringer | http://www.mssccmfaq.de

    Wednesday, May 4, 2016 1:27 PM
  • Torsten, any more ideas (after discuss with Jason...) ?
    Thursday, May 5, 2016 8:06 PM
  • Anybody? - why the client tries to access OLD MP when registering to NEW site?
    Wednesday, May 11, 2016 8:11 AM
  • So I assume that nobody knows...
    Sunday, June 12, 2016 8:40 AM
  • You should open a support case with Microsoft as this thread has become too muddled. As Torsten noted, if we were sitting there and had access to everything and ran through the scenarios ourselves, we could probably tell you what was going on but because we aren't and have to rely on second hand, possibly incomplete, or even interpreted info -- no matter how well you describe it -- then we simply are missing what we need to give you an answer.

    Jason | http://blog.configmgrftw.com | @jasonsandys

    • Proposed as answer by JFetter Monday, June 13, 2016 4:36 PM
    Sunday, June 12, 2016 6:09 PM
  • MS Support case is out of question, as on school licensing it is WAY too expensive!

    They true, give software almost for nothing, but that is all, just the software.

    I will live with my workaround



    • Edited by scerazy Sunday, June 12, 2016 8:02 PM
    Sunday, June 12, 2016 8:02 PM
  • When we move clients to a new SCCM Site, we wait for the next Client upgrade and simply deploy the new SCCM Client from the OLD site, specifying the new Site Code as a switch (assuming the NEW MP is registered in AD so the clients can find it) and the clients both upgrade and start reporting to the new Site.

    ccmsetup.exe /noservice /source:"<UNC Client Source>" DisableSiteOpt=True SMSCacheSize=25 SMSCacheFlags=PercentFreeDiskSpace SMSSiteCode=<SITE CODE> CCMHttpPort=<CUSTOM PORT>

    I will also say you sound a tad unappreciative, you've had a couple guys who have a lot better things to do than go back and forth with you and you've replied with what seems to be snotty answers to them...

    Jack

    Sunday, June 12, 2016 8:32 PM
  • Thanks Jack, somehow this did not work (as stated only full uninstall & then re-install worked).

    Absolutely nothing snotty about stating that only using a workaround worked for me...

    Monday, June 13, 2016 2:23 PM